Develop Bugs

Oneplus 3 Bricked - Unbrick doesn't work...

Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!

Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.

Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.

min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?

I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...

Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.

drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.

min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...

If recovery, boot or system partition is modified. There's no harm in re locking otherwise..

Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off

Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)

SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?

Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload

SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?

Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working

Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP

SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it

Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.

RMM STATE:Prenormal

So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.

carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076

arys64 said:
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076
Click to expand...
Click to collapse
Yeah...a few users are testing the 168 hour theory. We will find out what happens in 6 days

carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.

billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped

carlosmedia said:
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped
Click to expand...
Click to collapse
Try to flash it with combination firmware, enable OEM Unlock, remove screen lock and Google account.
Finally disable the RMM app called RLC, and modify the build.prop as posted earlier. If your don't do all those, the RMM lock will re-activate as soon as you try to flash a custom recovery.
Unfortunately simply waiting for a week, will not auto-magically solve all you problems, you must disable it manually.
The reason you had to wait, is to able able to flash signed firmware again.

billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste

carlosmedia said:
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste
Click to expand...
Click to collapse
Unfortunately there's no way for us mere mortals to "untrip Knox". I'm pretty sure Samsung can do it internally but not us, so you just gonna have to live with it. It's not the end of the world, just a flag to tell Samsung that someone has messed with it.

ANDROID 10 with MAGISK ROOT working on s10+

*****This was done on an EXYNOS s10+ SM-G975F*****
All you have to do is download the firmware
Get the AP file
Patch it with MAGISK
then take the patched file and flash it in place of the AP file WITH THE REST OF THE FIRMWARE FILES with ODIN
But make sure you uncheck auto reboot
Then when you are done flashing turn if off
The turn it on holding the recovery buttons till the first screen comes back for a couple seconds the let go
You should now have ANDROID 10 (Q) rooted with MAGISK
Enjoy

Taking this one step further, would we be able to insert a twrp image into the AP file so that we also have TWRP installed? Or is it incompatible?
I might try this later.

Really? its good news. But is battery life any better in Android Q?

need to unlock oem or not ?

tofayas said:
need to unlock oem or not ?
Click to expand...
Click to collapse
1- unlock oem
2- unlock Bootloader
3- root

can we patch twrp too and pu that in the ap file?

Has anyone managed to root Android10 but without losing data?

Tried it but ended up with bootloop: Unable to disable quotas on /dev/block/platform/13d60000.ufs/by-name/userdata because /system/bin/tune2fs is missing. Followed instructions exactly. Pathed image, moved image to odin along with the other files, flashed, passed, turned off and started with recovery buttons.

Need to press and hold buttons in order to start device in rooted mode each time you restart or power off and power on device??

ShahbazParviez said:
Need to press and hold buttons in order to start device in rooted mode each time you restart or power off and power on device??
Click to expand...
Click to collapse
Yes,

Player04 said:
Yes,
Click to expand...
Click to collapse
This what i don't want. I believe mostly people don't like this method too. Device must be work in normal mode with root and key combination to enter in recovery mode.

ShahbazParviez said:
This what i don't want. I believe mostly people don't like this method too. Device must be work in normal mode with root and key combination to enter in recovery mode.
Click to expand...
Click to collapse
hi. you meant its not working in root mode after restart if we dont press the combination button ? Is android 9 same thing ? Sorry still new with Magisk things

I mean you have to press several buttons to enter in rooted mode after rooting your device and it's obviously not a good way.

Does this work with the latest Android 10 stable build? Can anyone confirm please?

I wonder the same thing...... Does this work with the latest stable version of Android 10? Can anyone please confirm?

Merry Christmas ALL!!
Anyone had tried upgrading to Android 10 successfully?
Thank you.

Link from Gofile are down.
Fix this....

iamsyh said:
Does this work with the latest Android 10 stable build? Can anyone confirm please?
Click to expand...
Click to collapse
yes, work

hi. i was running android 9 rooted and i decided to upgrade to android 10. i also included twrp in the installation using magisk and patching the AP file.
The first boot was fine. i had to reboot the phone and now if i start with root, i can't unlock the screen, i put the pin,it gives black screen and then pin request again. i rebooted with no root (same problem). i wiped the cache and now i can use phone if i start without root. i tried to remove pin and fingerprint, but anyway if i start with root i cannot use phone, it goes in bootloop after the unlock screen.
Any suggestion?
thank

81! said:
*****This was done on an EXYNOS s10+ SM-G975F*****
All you have to do is download the firmware
Get the AP file
Patch it with MAGISK
then take the patched file and flash it in place of the AP file WITH THE REST OF THE FIRMWARE FILES with ODIN
But make sure you uncheck auto reboot
Then when you are done flashing turn if off
The turn it on holding the recovery buttons till the first screen comes back for a couple seconds the let go
You should now have ANDROID 10 (Q) rooted with MAGISK
Enjoy
Click to expand...
Click to collapse
Which firmware?
Get AP file from where?
Which Magisk?
Sorry, new to S10 and no links showing.
Thank you

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.

SG prenormal state - blocks twrp installation so can't root

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