SG prenormal state - blocks twrp installation so can't root - Samsung Galaxy A50 Questions & Answers

Hi,
I've previously managed to install twrp and boot into it. however, forgot to install dmverify.
since then the SG prenormal flag shows on download screen.
i've reinstalled stock rom and everything works fine, except the bootloader warning appears. (can remove this by turning bootloader unlock off).
tried reinstalling twrp again, but this time keep getting error message that unofficial binaries cannot be installed, due to the SG prenormal flag.
How can this be reset so I can install twrp to finally root device (and later remove all bootloader warnings)?
please help.

it seems I need to unlock knoxguard (used to be unlock rmm)
so that KG prenormal stops blocking twrp installation.
Seems to be a paid way to do this via chimera tool.
https://chimeratool.com/en/docs/sam...onitoring-and-management-rmm-unlock-functions
If they can do it paid, then its technically possible to unlock knoxguard.
Does anybody have another way to all TWRP installation after KG prenormal is set in download mode?
thanks

lawmanukdc said:
it seems I need to unlock knoxguard (used to be unlock rmm)
so that KG prenormal stops blocking twrp installation.
Seems to be a paid way to do this via chimera tool.
https://chimeratool.com/en/docs/sam...onitoring-and-management-rmm-unlock-functions
If they can do it paid, then its technically possible to unlock knoxguard.
Does anybody have another way to all TWRP installation after KG prenormal is set in download mode?
thanks
Click to expand...
Click to collapse
Reflash stock,just skip all setup go to develop options and enable usb debug.And try again.If you don't succeed first time try again.

muhamet said:
Reflash stock,just skip all setup go to develop options and enable usb debug.And try again.If you don't succeed first time try again.
Click to expand...
Click to collapse
Hi,
1. I enabled usb debug, then went back into download mode.
2. It still shows KG STATE prenormal.
3. tried to install twrp again and same problem = refused to install unknown binary.
4. reinstalled stock (with home_csc)
5. went back into download mode and still showed KG STATE PRENORMAL.
6. Tried to install twrp again and same problem = refused to install unknown binary.
please confirm:
A. Is KG STATE PRENORMAL supposed to change after usb debug?
B. when you say 'try again', what are you referring to?
1) try installing twrp again - tried this already as above
2) try installing stock again? (with/without home crc?) - tried this already as above
still stuck but sounds like you may have the answer?
thanks

lawmanukdc said:
Hi,
1. I enabled usb debug, then went back into download mode.
2. It still shows KG STATE prenormal.
3. tried to install twrp again and same problem = refused to install unknown binary.
4. reinstalled stock (with home_csc)
5. went back into download mode and still showed KG STATE PRENORMAL.
6. Tried to install twrp again and same problem = refused to install unknown binary.
please confirm:
A. Is KG STATE PRENORMAL supposed to change after usb debug?
B. when you say 'try again', what are you referring to?
1) try installing twrp again - tried this already as above
2) try installing stock again? (with/without home crc?) - tried this already as above
still stuck but sounds like you may have the answer?
thanks
Click to expand...
Click to collapse
What model you are using??FN? Don't flash twrp magisk patched.Use just twrp. @samsunggalaxya50
Use telegram chanel i will help from there

muhamet said:
What model you are using??FN? Don't flash twrp magisk patched.Use just twrp. @samsunggalaxya50
Use telegram chanel i will help from there
Click to expand...
Click to collapse
Surprised so few responses. Had expected KG tripping to be a common problem.
I'm using 505FN.
Installed TWRP once in beginning and it worked but forgot to do the dm-verify thing.
Since then tried others including the magisk patched one, but KG PRENORMAL stops any unofficial binaries.
Been trying this TWRP from xda but still no joy.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
totally stuck at this point on how to progress, and hope there is a way to kill KG PRENORMAL.
Installed Telegram, but no option to add channel - only to create one. Searched in https://tlgrm.eu/channels for channel samsunggalaxya50 but couldn't find it. Please advise how to install channel?
Thanks

ok, i follwed below guide and that seems to have fixed the KG prenormal issue turning it into KG checking...
https://www.youtube.com/watch?v=zqbu7jCmeMY
I then tried installing TWRP.
1. this version flashed ok ,but wouldn't go into recovery - just kept looping.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
2. I then installed another version I had got without magisk in it v. 3.3.1
this flashed ok and I rebooted into TWRP recovery.
Only problem is theres no way to install the DMverify file.
1. Not sure to install DMVerify
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
or
2. Multi-disabler?
https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
It doesn't matter anyway, as TWRP sideload isn't working properly... keeps saying starting.
On my windows or linux machine, adb start-server, adb devices doesn't show anything.
So I can't install the above fixes and worried it will go crazy after I turn phone off.
How can I get anything onto the a50 now without sideload on twrp working?
Maybe you know of a twrp version that works fine with sideload?

lawmanukdc said:
Surprised so few responses. Had expected KG tripping to be a common problem.
I'm using 505FN.
Installed TWRP once in beginning and it worked but forgot to do the dm-verify thing.
Since then tried others including the magisk patched one, but KG PRENORMAL stops any unofficial binaries.
Been trying this TWRP from xda but still no joy.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
totally stuck at this point on how to progress, and hope there is a way to kill KG PRENORMAL.
Installed Telegram, but no option to add channel - only to create one. Searched in https://tlgrm.eu/channels for channel samsunggalaxya50 but couldn't find it. Please advise how to install channel?
Thanks
Click to expand...
Click to collapse
kg is not a common problem if u followed the steps correctly from the start

lawmanukdc said:
ok, i follwed below guide and that seems to have fixed the KG prenormal issue turning it into KG checking...
I then tried installing TWRP.
1. this version flashed ok ,but wouldn't go into recovery - just kept looping.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
2. I then installed another version I had got without magisk in it v. 3.3.1
this flashed ok and I rebooted into TWRP recovery.
Only problem is theres no way to install the DMverify file.
1. Not sure to install DMVerify
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
or
2. Multi-disabler?
https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
It doesn't matter anyway, as TWRP sideload isn't working properly... keeps saying starting.
On my windows or linux machine, adb start-server, adb devices doesn't show anything.
So I can't install the above fixes and worried it will go crazy after I turn phone off.
How can I get anything onto the a50 now without sideload on twrp working?
Maybe you know of a twrp version that works fine with sideload?
Click to expand...
Click to collapse
you just got all sorts of problems lol.. y dont u follow the instructions exactly in the proper thread? when u go off n start missin stuff or usin other files etc. then ur bound to have problems if u dont know what ur doing.. just saying

Which thread works correctly?

I installed multi disabler and then magisk.
Rebooted twrp into official ROM.
Multi disabler didn't work.
On reboot, phone had KG prenormal again and refused to boot due to twrp installation.
What to do?
1. Is there a better disabler that works
2. Would installing custom ROM help?

lawmanukdc said:
I installed multi disabler and then magisk.
Rebooted twrp into official ROM.
Multi disabler didn't work.
On reboot, phone had KG prenormal again and refused to boot due to twrp installation.
What to do?
1. Is there a better disabler that works
2. Would installing custom ROM help?
Click to expand...
Click to collapse
technically you dont even need it lol.. my s10 5g is rooted simply using a patched tar

Related

Huawei Mate SE stuck on "just a sec" after factory reset with FRP lock on

So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
rkevin_arch said:
So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
Click to expand...
Click to collapse
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
mrmazak said:
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
Click to expand...
Click to collapse
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
mrmazak said:
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
Click to expand...
Click to collapse
Thanks for the help! It worked, and the bootloader says FRP unlocked. It didn't help the "just a sec" issue, but since I can use fastboot flash, I might be able to flash a new rom in it and just ditch EMUI[probably]. I'll play around with it a bit. Again, thanks a lot for your help!
I got everything working now! Just in case anyone had the same "just a sec" issue: it was fixed by flashing stock recovery then doing a factory reset there(I'm not sure how that's different from wiping dalvik/cache/data/internal storage in twrp, but it makes a difference apparantly). Just flashing custom ROMs didn't solve the problem. After that I installed magisk, and then installed this version of xposed: https://forum.xda-developers.com/showpost.php?p=76582399&postcount=11 . I installed the v90-beta3 version before which caused the bootloop, but it is fixed in the next version. Magisk has some issues so the magisk manager can't start with internet(adb logcat says there's a NullPointerException in com.topjohnwu.magisk.database.RepoDatabaseHelper.removeRepo) but frankly I don't need to open it with internet anyways. Now I have everything I need on my new phone! Thanks to mrmazak for pointing me to the right direction.

Need locked bootloader to install 5.0.6 OxygenOS (Oreo) but...

My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Still nothing?
DranzerX13 said:
My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Click to expand...
Click to collapse
I watched your video,
Before you relock the bootloader you must install the stock recovery for your device, you can't relock while TWRP is installed, use this guide, (read the guide once completely before you start).
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Also make shure you use the latest ADB drivers Inside (SDK Platform-Tools) from google:
https://developer.android.com/studio/releases/platform-tools
Good Luck!
It worked like a charm. Thank you!

Bypass KG state prenormal

So i just understand that only Pie has this issue so we need to downgrade to Oreo.
Download this file
https://drive.google.com/file/d/1FQKt_lWUxxbaZGk37r4tkEMO0Faaci-R/view
unzip
Now put AP in AP and CSC in CSC and flash and now it works for you
I have Oreo and I am on prenormal state as well
I can't root or instal TWRP nothing pass by odin, and OEM unlock is now missing from dev menu
I have waited 190 hours of continious up time but still stuck on the same state
will this fiile remove the prenormal state even for oreo allowing me to install TWRP ?
Lu Han said:
So i just understand that only Pie has this issue so we need to downgrade to Oreo.
Download this file
https://drive.google.com/file/d/1FQK...ew?usp=sharing
unzip
Now put AP in AP and CSC in CSC and flash and now it works for you
Click to expand...
Click to collapse
FYI : the provided link doesn't work
Pro Cal said:
I have Oreo and I am on prenormal state as well
I can't root or instal TWRP nothing pass by odin, and OEM unlock is now missing from dev menu
I have waited 190 hours of continious up time but still stuck on the same state
will this fiile remove the prenormal state even for oreo allowing me to install TWRP ?
Click to expand...
Click to collapse
Link fixed and you can't removed RMM state prenormal with that you need to have Exynos version and flash One Ui firmware for your device and wait 168H
After I installed Pie 9 I did not open the Developer Option. After that I opened the Download Mode and did not have RMM Prenormal. With ODIN I installed TWRP and after that I root my phone.
Lu Han said:
Link fixed and you can't removed RMM state prenormal with that you need to have Exynos version and flash One Ui firmware for your device and wait 168H
Click to expand...
Click to collapse
tell me please, for the 168H up-time, should it be with data enabled continuously all the time, or just not to reboot or shutdown the phone is enough and we can enable disable the data and airplane mode ?
Pro Cal said:
tell me please, for the 168H up-time, should it be with data enabled continuously all the time, or just not to reboot or shutdown the phone is enough and we can enable disable the data and airplane mode ?
Click to expand...
Click to collapse
For 168 hours no reboots I'm not sure about data connection during my 168 hour did lose data and after went pass 168 hour I was able flash twrp.
yet theres no way to bypass kg state without downgrading ??
587.saboor said:
yet theres no way to bypass kg state without downgrading
Click to expand...
Click to collapse
So there is no revision number 5 of oreo for making the downgrade, isn't there? I am on Pie and waiting the 168 hours but I don't know if after that I would install magisk...
What about that comment of install a clean Pie system and not opening the Dev Options? I cannot try it.
pabloluih said:
So there is no revision number 5 of oreo for making the downgrade, isn't there? I am on Pie and waiting the 168 hours but I don't know if after that I would install magisk...
What about that comment of install a clean Pie system and not opening the Dev Options? I cannot try it.
Click to expand...
Click to collapse
After install Pie, don't open developer options, install TWRP with ODIN. SM-A530F. It work for me.
ZmisiS said:
After install Pie, don't open developer options, install TWRP with ODIN. SM-A530F. It work for me.
Click to expand...
Click to collapse
Sorry, but no working... I am at 'KG STATE: checking' and nothing more. I followed this and same result: https://forum.xda-developers.com/galaxy-s8/how-to/how-to-bypass-rmm-prenormal-to-install-t3891193
Thanks.
ZmisiS said:
After install Pie, don't open developer options, install TWRP with ODIN. SM-A530F. It work for me.
Click to expand...
Click to collapse
So, just so that I understand this right:
1) Re-flash Pie
2) Boot into OS, do not add Google or Samsung account, and connect to WiFi
3) Set the date to 8 days back?
4) Flash TWRP and boot directly into it
5) Format Data
6) Flash DM-Verity disabler and Magisk
Done? Or is there anything else that needs to be added or removed?

the proper way to unlock bootloader install magisk and twrp ?

[fixed]
i unlocked bootloader i installed magisk following this guide " https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952"
after that i tried to install twrp following this guide "https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396"
the device boots but seems to be stuck in the lock screen very heavy i flashed force disable encryption it worked fine the device booted normally but magisk is gone and manager force stop
please can u show me the proper way to install magisk and twrp without problemes ?
but still would be great if someone would volunteer and share the proper way
farrouk said:
[fixed]
i unlocked bootloader i installed magisk following this guide " https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952"
after that i tried to install twrp following this guide "https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396"
the device boots but seems to be stuck in the lock screen very heavy i flashed force disable encryption it worked fine the device booted normally but magisk is gone and manager force stop
please can u show me the proper way to install magisk and twrp without problemes ?
but still would be great if someone would volunteer and share the proper way
Click to expand...
Click to collapse
Flash magisk again via TWRP

Only official released binaries are allowed to be flashed Download Mode error message

So , I just tried to flash TWRP on a SM-G960F/DS via Odin v3.13.3 and I got the error from the title in the Download Mode. The phone works 100% but I really wanna get another UI . I forgot to mention I already unlocked the OEM from dev mode.
EDIT In a way or another the ODIN said PASS but after flashing the TWRP and trying to boot into recovery I was shocked to see the stock Recovery , just why?
Maybe you have Prenormal status. You'll have to wait few days without turning off your phone and then you'll be able to flash twrp.
ZoiraP said:
Maybe you have Prenormal status. You'll have to wait few days without turning off your phone and then you'll be able to flash twrp.
Click to expand...
Click to collapse
the prenormal is likely correct, unsure if the waiting 168 hours is still a thing or not tho.

Categories

Resources