Related
HI Guys, I have installed the G955FXXU1CRAP at my s8+ but when I try to flash twrp with odin it get status fail and the phone says that installation of custom binaries are not allow (OEM LOCK and RMM STATE: PRENORMAL).
Did you tryed to install Twrp and root G955FXXU1CRAP? How you solve this bootloader lock?.
thanks in advance.
Alex.
In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.
This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -
Well, thank you so much for that information guys. I did not know it.
Geekser said:
This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -
Click to expand...
Click to collapse
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.
cyborgium said:
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.
Click to expand...
Click to collapse
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..
Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol
cyborgium said:
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..
Click to expand...
Click to collapse
Go into download mode (Power, Bixby and Vol Down) when you are in download mode, you can see what the RMM State is - it will either say NORMAL or PRE-NORMAL.
If yours says NORMAL - then you go can go ahead and flash TWRP via ODIN. If you are having flash issues at this point, ask in the TWRP Thread and you should be able to get some help.
However, if you are PRE-NORMAL in download mode, then you are locked and won't be able to flash anything until you pass the 7 day period.I think the 7 days begins on the date you flashed your current firmware.
YOu can be in PRE-NORMAL and still see OEM UNLOCK. BUT if you are pre-normal and you see OEM UNLOCK you cannot flash until your RMM State changes to NORMAL.
I hope that helps.
xxxrichievxxx said:
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol
Click to expand...
Click to collapse
Yes, the RMM Fix must be flashed after you flash TWRP or after you flash a custom rom, everytime. UNLESS the rom has the RMM Fix baked into the rom - some do - some may not. Won't hurt to fllash it just in case, everytime.
Thanks again for the rapid response but, I'm identifying an issue with the storage on this firmware g955fxxu1crap. My phone exynos g955f has 64 gb of internal storage, but after this upgrade it shows only 16 gb of internal storage.
Did get this same error , how you solve it?
thanks in advance.
Ale3385
josegon30 said:
In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.
Click to expand...
Click to collapse
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.
Psyscope said:
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.
Click to expand...
Click to collapse
After 7 days I could perfectly flash TWRP and root, no big deal. If you go into download mode and see RMM STATE: PRENORMAL then you can't flash. I guess all new phones with 8.0 since January are pre-normal, but I'm not sure.
Ive seen in the other thread that you could flash the entire nougat stock rom (nov 2017 perhaps) which will allow you to bypass the rmm and then flash TWRP and custom ROM? Could anyone confirm this workaround?
A simple guide for users which will help them to install TWRP on their S8 after Oreo Update.
This guide is only for Exynos models.
Requirement -
1. PC/Laptop
2. Original Samsung USB Type-C Cable
3. Prince Comsy Odin (Because some users reported on this thread that normal Odin doesn't work)
Instructions -
1. Backup your important data from internal storage before proceeding towards the installation.
2. Now go to Settings - About Phone - Software Information - Tap On Build Number 7 Times.
3. Now come back to Settings Home and Open Developer Options. Check OEM Unlock is turned ON.
4. Power off device and boot into download mode.
5. Connect your device to the PC/Laptop.
6. Now Open Prince Comsy Odin and click on the AP option.
7. Choose the TWRP .tar file and press the START button.
8. Now after Odin says PASS, press the VOLUME UP, BIXBY KEY, and POWER BUTTON at the same time until device boots into TWRP recovery.
9. Now allow the modifications and go to WIPE option.
10. Choose FORMAT DATA - Type yes - ENTER.
11. Just Reboot Once Into Recovery Once.
12. Flash no-verity-opt-encrypt.zip.
12. Now Choose INSTALL option and install Magisk or SuperSU.
13. Done!
You can also refer to this video for installation of TWRP - https://www.youtube.com/watch?v=2SqgHFcHLMw
Downloads -
Latest TWRP For Exynos S8 - TWRP 3.2.1-0-DREAMLTE
Prince Comsy Odin - https://drive.google.com/open?id=1enVG5a_ocyjhRlta8AX_0b7LLoHWciVU
No dm-verity - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk - https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
SuperSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Credits -
@jesec for TWRP
@topjohnwu for Magisk
@Chainfire for SuperSU
Prince Comsy Odin
The main problem is that most users dont have oem unlock after oreo update (e.g me)
EugenStanis said:
The main problem is that most users dont have oem unlock after oreo update (e.g me)
Click to expand...
Click to collapse
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Ruturaj Kadam said:
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Click to expand...
Click to collapse
Flashed official XEO for Poland and still OEM unlock isnt there :/
Does the Oreo update affect the the locked bootloader on the Snapdragon version? I thought it was impossible to install TWRP on the Snapdragon versions of the S8?
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
EugenStanis said:
Flashed official XEO for Poland and still OEM unlock isnt there :/
Click to expand...
Click to collapse
Try use AQK7 ( 4 file firmware + re-partition PIT)
In my case I 100% success returned form CRAP to AQK7.
OEM unlock is in dev settings, no RMM and FRP.
Powodzenia ^_^
I'm guessing this is not for the US snapdragon variant.
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Will822 said:
I'm guessing this is not for the US snapdragon variant.
Click to expand...
Click to collapse
I'm sorry! It was one of my friends who told me the method is same. I'm sorry again. OP edited
iamnotexisting said:
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Click to expand...
Click to collapse
I'm sorry for that! Edited the OP! Got misguided due to one of my friends
Silenus21 said:
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Click to expand...
Click to collapse
Haha yes! Exynos devices are best in performance and battery too.
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
168 hours Open my device oem lock on of after twrp flash data storage 0 dm verity flash wipe data
thiagomed said:
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
Click to expand...
Click to collapse
TWRP trips Knox if I'm not mistaken.
i did this guide and everything is went good but when i restarted the phone it went to a softbrick and i had to do a restore...
the error was something on the original binary
to have the OEM option, will I have to go back to crap?
I have just tried this method and booted into TWRP but the screen was totally unresponsive, rebooted and still the same. I had to go back to Oreo.
How do I get around this problem?
dr.vetony said:
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
Click to expand...
Click to collapse
Wipe / format data - " yes"
Hello Guys
I want to tell how to bypass RMM state: prenormal to install TWRP
Also this will resolve "Only official binaries are allowed"
Disclaimer:
I am NOT responsible for any damage done if you use my guide.
It worked for me 100% and should normally work for everybody!
Feel free to share to anyone else or to embed if you want.
-------------------------------------------------
1. Download latest Stock base via SamFirm
2. Install latest Stock base via Odin Odin v3.13.1 direct download
3. Boot into system
4. Skip the setup
5. Activate Developer settings
6. search and turn of automatic system update
7. Go to time settings and deactivate automatic time
8. Turn back the day for more than 7 days. ( I have turned to the 20th Dec 2018)
9. Search for Software update -> Don't install update
10. Look if latest time searched for updates is the date which you have set. (for me 20th Dec 2018)
11. Reboot your device
12. go into the time settings and reactivate the automatic time
13. Search again for software update - > Still don't install
14. Go to Developer settings
15. deactivate OEM Unlock and reactivate
16. Go to download mode and you will don't see RMM state anymore
18. install TWRP by odin
19. boot into TWRP
20. format data
21. reboot recovery
22. flash verity.zip // found on https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
23. Et voilà! You got completely functional TWRP on your device with Pie Bootloader
24. Flash your preferred Rom!
-------------------------------------------------
Thanks to:
zxz0O0 for SamFirm
Have Fun
this verity.zip is necessary? or can I flash another rom right after install twrp?
edit: by "update.zip" you mean the PIE Beta?
LucasBernardesLopes said:
this verity.zip is necessary? or can I flash another rom right after install twrp?
edit: by "update.zip" you mean the PIE Beta?
Click to expand...
Click to collapse
It decrypt the Userdata.
Yes i mean the Pie Beta.
It works perfect, I was worried because I could not find a solution, very good guide thank you very much
Laiyox said:
Hello Guys
-------------------------------------------------
1. Download CRL3 via Samfirm SamFirm Download from mega.nz
2. Install CRL3 via Odin Odin v3.13.1 direct download
3. Boot Stock CRL3 after install with Odin
Click to expand...
Click to collapse
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
tomaasz said:
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
Click to expand...
Click to collapse
I don't really know. The Beta was published while CRL3. So i think it is needed, but you can try. If it dont work you just can reflash CRL3 via Odin
tomaasz said:
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
Click to expand...
Click to collapse
Following this thread you should be on CRL3.
https://forum.xda-developers.com/galaxy-s8/how-to/s8-exynos-pie-oneui-beta-official-t3890376
do we have to flash twrp after every pie beta update?
How to root s8plus 9.0 one ui
I need help root android 9.0 one ui s8plus ??
i followed everything 9.0 Pie beta also done but after format wipe OEM is gone.
actually i want to root my G955F but its showing error becous RMM status is Prenormal so i cant root my S8 plus
please guide me how to root after beta pie 9.0?
Thx.
talhagsm said:
i followed everything 9.0 Pie beta also done but after format wipe OEM is gone.
actually i want to root my G955F but its showing error becous RMM status is Prenormal so i cant root my S8 plus
please guide me how to root after beta pie 9.0?
Thx.
Click to expand...
Click to collapse
I have just written a new thread with a new method to bypass it:
https://forum.xda-developers.com/galaxy-s8/how-to/guide-skipping-kg-prenormal-oneui-t3911862
How to install the crlb via odin
When I do this on Pie, the OEM Unlock toggle in Dev Options shows up. When I toggle it, it shows the following in download mode:
RMM STATE: Prenormal
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF
And I am unable to flash TWRP or any custom binaries.
So I downgraded to Oreo, and followed the exact same steps as outlined and now I cannot get the OEM toggle to show up! And of course it says Prenormal in download... but not KG State.
RMM STATE: Prenormal
FRP LOCK: OFF
OEM LOCK: ON
WTF am I doing wrong??
kgr said:
When I do this on Pie, the OEM Unlock toggle in Dev Options shows up. When I toggle it, it shows the following in download mode:
RMM STATE: Prenormal
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF
And I am unable to flash TWRP or any custom binaries.
So I downgraded to Oreo, and followed the exact same steps as outlined and now I cannot get the OEM toggle to show up! And of course it says Prenormal in download... but not KG State.
RMM STATE: Prenormal
FRP LOCK: OFF
OEM LOCK: ON
WTF am I doing wrong??
Click to expand...
Click to collapse
Did you did everything step by step?
If you miss any step it won't work
Laiyox said:
Did you did everything step by step?
If you miss any step it won't work
Click to expand...
Click to collapse
Yep absolutely followed the directions exactly. In the end I just wanted the 7 days
kgr said:
Yep absolutely followed the directions exactly. In the end I just wanted the 7 days
Click to expand...
Click to collapse
Also used latest Base?
I didn't update the thread to official Pie
can I still flash without root?
I have a J337VPP galaxy J3 running on android oreo 8.0.0 and the hardware version is J337v.04. it is non-rooted. Would I be able to do your steps without root? it has to be able to be done without root since the only way to root is by unlocking the bootloader using the OEM unlock (which I can't do because of this stupid RMM prenormal Samsung decided to create). Thanks! been trying to root different phone of mine for years to take complete control over annoying system apps! (atleast I already have Package Disabler Pro) Thanks again. Hope I can have help. I've heard of going to download mode and seting the date before RMM prenormal. I think I am good with tech but new to this RMM stuff.
---------- Post added at 12:18 AM ---------- Previous post was at 12:01 AM ----------
Turns out RMM state prenormal isn't in download mode/odin. Weird... maybe J3 doesn't support oem unlock
just tried this on SM-G950F (Galaxy S8), RMM state is still prenormal and I can't flash TWRP. I did have the oem unlock option available before doing this though, and had turned it on, but I'm on android 9 which might make a difference
hiden oem option
Laiyox said:
Hello Guys
I want to tell how to bypass RMM state: prenormal to install TWRP
Also this will resolve "Only official binaries are allowed"
Disclaimer:
I am NOT responsible for any damage done if you use my guide.
It worked for me 100% and should normally work for everybody!
Feel free to share to anyone else or to embed if you want.
-------------------------------------------------
1. Download latest Stock base via SamFirm
2. Install latest Stock base via Odin Odin v3.13.1 direct download
3. Boot into system
4. Skip the setup
5. Activate Developer settings
6. search and turn of automatic system update
7. Go to time settings and deactivate automatic time
8. Turn back the day for more than 7 days. ( I have turned to the 20th Dec 2018)
9. Search for Software update -> Don't install update
10. Look if latest time searched for updates is the date which you have set. (for me 20th Dec 2018)
11. Reboot your device
12. go into the time settings and reactivate the automatic time
13. Search again for software update - > Still don't install
14. Go to Developer settings
15. deactivate OEM Unlock and reactivate
16. Go to download mode and you will don't see RMM state anymore
18. install TWRP by odin
19. boot into TWRP
20. format data
21. reboot recovery
22. flash verity.zip // found on https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
23. Et voilà! You got completely functional TWRP on your device with Pie Bootloader
24. Flash your preferred Rom!
-------------------------------------------------
Thanks to:
zxz0O0 for SamFirm
Have Fun
Click to expand...
Click to collapse
when i do deactivate oem option ask for factory reset when i do then thereh is no oem option ?
Hi guys, i have a problem with my S8 (SM-G950F), I want to flash twrp and a custom rom but I can't flash twrp because i have last update (1 september 2019), someone can help me? When I flash the twrp from odin I have FAIL ever, how can i fix kg state prenormal? I used adb and fastboot, i used odin, odin patched-b, princecomsy odin but I can't flash it. I used linux ubuntu 19 with Heimdall flash but it's the same. Thanks in advance.
EDIT: This problem has been resolved thanks to good advice in this thread!
I'm not sure what I've managed to do, but here are the symptoms:
I installed a custom rom and it was working, had TWRP and magisk installed, but couldn't get the s7 exynos to recognize that magisk was installed. I attempted to restore to a stock rom. At this point, it will not boot past the samsung logo. It will also not boot into recovery. I can boot into download mode. The DL mode screen reports the error SW rev check fail (bootloader) device: 5 binary: 2
No matter stock ROM what I attempt to flash via Odin, just after the process log gets to sboot.bin, the next line is FAIL! then Complete (Write) operation failed. I am attempting to flash the latest version of 8.0 from sammobile for s7 exynos (I selected BTU).
kettir said:
I'm not sure what I've managed to do, but here are the symptoms:
I installed a custom rom and it was working, had TWRP and magisk installed, but couldn't get the s7 exynos to recognize that magisk was installed. I attempted to restore to a stock rom. At this point, it will not boot past the samsung logo. It will also not boot into recovery. I can boot into download mode. The DL mode screen reports the error SW rev check fail (bootloader) device: 5 binary: 2
No matter stock ROM what I attempt to flash via Odin, just after the process log gets to sboot.bin, the next line is FAIL! then Complete (Write) operation failed. I am attempting to flash the latest version of 8.0 from sammobile for s7 exynos (I selected BTU).
Click to expand...
Click to collapse
Device 5 means boot loader version 5, binary 2 means bootloder your trying to flash is older, you cannot flash an older boot loader than version 5. This means the firmware you are trying to flash is not the latest.
Sammobile has BTU version 5, search for it and download it, follow the guide how to flash.
cooltt said:
Device 5 means boot loader version 5, binary 2 means bootloder your trying to flash is older, you cannot flash an older boot loader than version 5. This means the firmware you are trying to flash is not the latest.
Sammobile has BTU version 5, search for it and download it, follow the guide how to flash.
Click to expand...
Click to collapse
Thank you, this is invaluable advice and just what I was hoping for.
When the phone arrived I could briefly see that it was a Saudi Arabia firmware. Looking at saudi STC SFU the date is 7/1/19, that might explain this. I flashed Alexndr 8.0 over that. It was during the time I tried to get magisk to stick that I bricked the phone.
I did download and attempt (with fail) to flash G930FXXS4ESC1_G930FOXA4ERKF_BTU dated 5/12/19 on the sammobile page. So I may try United Kingdom dated 7/11/19 and see if that will flash. I can't tell which version of BTU might have a boot loader version 5 among those listed. Does this seem a reasonable attempt to you?
EDIT: I did download and flash, and it's starting to boot....huzzah! I'm now filling out the startup information. Thank you!!
kettir said:
Thank you, this is invaluable advice and just what I was hoping for.
When the phone arrived I could briefly see that it was a Saudi Arabia firmware. Looking at saudi STC SFU the date is 7/1/19, that might explain this. I flashed Alexndr 8.0 over that. It was during the time I tried to get magisk to stick that I bricked the phone.
I did download and attempt (with fail) to flash G930FXXS4ESC1_G930FOXA4ERKF_BTU dated 5/12/19 on the sammobile page. So I may try United Kingdom dated 7/11/19 and see if that will flash. I can't tell which version of BTU might have a boot loader version 5 among those listed. Does this seem a reasonable attempt to you?
EDIT: I did download and flash, and it's starting to boot....huzzah! I'm now filling out the startup information. Thank you!!
Click to expand...
Click to collapse
Great.
The boot loader version is shown in the firmware, G930FXXS4ESC1 is boot loader version 4, S4= V4.
S5 = V5 etc.
For info, version 5 (S5) was the final BTU firmware release for the S7 so no more firmware updates after that.
cooltt said:
Great.
The boot loader version is shown in the firmware, G930FXXS4ESC1 is boot loader version 4, S4= V4.
S5 = V5 etc.
For info, version 5 (S5) was the final BTU firmware release for the S7 so no more firmware updates after that.
Click to expand...
Click to collapse
Thanks for the clue, it is much appreciated!
Root Samsung Galaxy A52 SM-A525F Android 11 Official - AUC4 Firmware. TWRP Recovery for Galaxy A52 Android 11 does not available yet when I posted this rooting guide. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Rooting Instructions ( Don't make mistake )
Make sure the bootloader are unlocked, OEM unlock option is grey out
Patch boot.img then Pack it to magisk_patched.tar. If you don't want to do it by your self, you can download it from link below
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN
Insert magisk_patched.tar in AP, then click start. The phone will rebooting to ANDROID RECOVERY MODE
in ANDROID RECOVERY, Select Factory data reset and press power key to confirm
select 'Factory data reset' again and confirm
Setup the phone
Connect to Internet
Install and Open Magisk App, it will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Download
magisk_patched
Telegram: https://t.me/SamsunGalaxyA52
Watch This Video Tutorial
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
<deleted>
VonSparq said:
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
Click to expand...
Click to collapse
On qcom devices, not really. Even on exynos devices after removing that you still need to physically press the power button or if you don't wanna even do that you have to w8 bout 10 to 15 extra seconds..
hansxl said:
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Click to expand...
Click to collapse
Okay, solved. Flashed latest firmware (AUC5) and patched boot.img with Magisk. Fingerprints works now and no reboots so far
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Rerel14 said:
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Click to expand...
Click to collapse
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
hansxl said:
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Rerel14 said:
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Click to expand...
Click to collapse
Yes, it's more or less the procedure. But I would just download the latest magisk (22.1) from
Magisk v22.1 brings an improved log writer, resetprop bootloop fixes, and much more
The latest stable update for Magisk (v22.1) has been released with tons of bug fixes and feature improvements. Read on to know more!
www.xda-developers.com
the UI is a bit different from the one in your video
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Rerel14 said:
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Click to expand...
Click to collapse
bootloader unlocked
hansxl said:
bootloader unlocked
Click to expand...
Click to collapse
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Rerel14 said:
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Click to expand...
Click to collapse
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
hansxl said:
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
Click to expand...
Click to collapse
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
I think I found one :
Rerel14 said:
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
Click to expand...
Click to collapse
How To Unlock Samsung Galaxy A52 Bootloader - NaldoTech
In this tutorial, you will learn how to unlock the bootloader on your Samsung Galaxy A52. A bootloader is the piece of code that runs before the operating
www.naldotech.com
don't forget to backup your data. I think after unlocking bootloader your phone will return to factory settings
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
I installed Magisk from an other source and eventually I succeeded to get root !
Huge thanks Hansxl for your help and patience. Really appreciated it.
Last question : if I update the firmware I'll need to make the full procedure described above again ?
Rerel14 said:
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
Click to expand...
Click to collapse
deinstall magisk and install magisk again