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.
Related
Hi, I flash my samsung s6 edge + G928T using the files for Misterjunky that I thanks a lot, and my phone was very good. But now I forgot to diseable the oem lock and i reset it. the phone ask me now the last user account, but when I buy the phone, i hadn't put a google account there. I flash it because it was a costum rom and I wanted an official.
Now I want to know how can I found the last user account whitch block my frp, and then I will go to where I buy the phone and try to found the password and reset my phone. The seller says me that he haven't put an account there, even if it was there when he clean it, normally I will not got a frp lock problem, but if I can know whitch google account was there maybe he can remember to the password and help me to resolve my problem.
Thanks a lot.
Sorry for my bad english
re: OEM lock
Amir Tech said:
Hi, I flash my samsung s6 edge + G928T using the files for Misterjunky that I thanks a lot, and my phone was very good. But now I forgot to diseable the oem lock and i reset it. the phone ask me now the last user account, but when I buy the phone, i hadn't put a google account there. I flash it because it was a costum rom and I wanted an official.
Now I want to know how can I found the last user account whitch block my frp, and then I will go to where I buy the phone and try to found the password and reset my phone. The seller says me that he haven't put an account there, even if it was there when he clean it, normally I will not got a frp lock problem, but if I can know whitch google account was there maybe he can remember to the password and help me to resolve my problem.
Thanks a lot.
Sorry for my bad english
Click to expand...
Click to collapse
You should have NEVER disable the OEM Unlock.
It should always remain ENABLED even if you
upgrade firmware or flash a new or different rom.
After flashing any custom roms the phone will never
display "Official", usually it will display "unknown".
The thing you need to do to fix the problem is:
#1: Be sure you have Odin v3.10.7 ready to use. (other versions may not be fully compatible)
#2: Download the official Samsung G928T TAR firmware (unless you already have it)
#3: Open Odin and put the official firmware tar file into Odin's AP slot.
#4: Put the phone into "download" mode.
#5: Connect USB cable from phone to your computer.
#6: Be sure Odin recognizes your phone (com:xx should light up)
#7: Don't change any options in Odin
#8: Click START in odin and wait until it's done flashing and rebooting the phone.
If you have done all 8 steps correctly, your phone will reboot and work properly.
If it's not working properly after it reboots then go into the phone's stock recovery
mode and do a "factory data reset" then when it reboots everything should be fine.
Good luck,
Have a very Merry Christmas!
I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.
It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.
Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...
BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?
I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.
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.
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Hi there,
first of all, sorry for my bad english.
I want to remove the Stock ROM from my Tablet (Samsung Galaxy Tab S4 | SM-T830) and install something else (https://www.getdroidtips.com/android-12samsung-galaxy-tab-s4/).
For some Reason Samsung forced me to do a factory reset to unlock the bootloader (maybe I did it wrong, but now it happened, so it is how it is). Now the OEM Unlock Options says "Bootloader is already unlocked", but when I go into Download mode, I have multiple Problems:
1.: When I enter download mode by Booting into Recovery (adb reboot recovery) and choose "reboot to bootloader", OR by entering it directly using "adb reboot bootloader", I dont get the Warning Screen so I get into download mode directly.
2.: When entering Dowload mode as descibed in problem 1, I also dont get the informations at the Top left, I only see the Download Icon on a blue background but when restarting the tablet and holding Volume Up and Volume Down simuntainuasly, it will show the warning (in the correct cyan colors) and in the next step it shows me those status informations at the top left.
3.: However, regardless to how I get into download mode, the colors of the download mode screen will change to a blue filter version after one second. but I did never activate any blue filter on the device, and on any other device, the colors are displayed correctly.
4.: Any instalation with Odin3 failed on the device, regardless to how i got into download mode
In any online article I read, noone has any problems with installing something when in download mode.
Also, the KG-Status is displayed as "checking, I dont know if this is good or not.
What am I doing wrong, why can't I install anything on the device?
what is wrong with download mode? post a picture.
drivers installed correctly? check in windows device manager.
what does not work with Odin? what error message?
First of all, thank you for your reply!
1.: The Picture shows that the is something wrong with the Download mode of the Tab S4, because the Colors are not being displayed correctly (as you can see, the colors of the other devices are much more cyan), and I would not have mentioned that if the device would just be unable to show colors correctly, but in the Warning before the Download mode, the Colors are displayed as they are on the other devices, so the eventually the device wants to tell me something, but I dont know what.
2.: Well, I am pretty sure that the drivers are installed Correctly, because Flashing a Galaxy Tab S2, Galaxy S8 and Galaxy S5 worked perfectly with the same driver.
3.: I'l attach a Screenshot of Odin.
ALso, what does "KG STatus: Checking" mean? Is it the reason for the problem, or is it good? On the Web I could only find "Kg Status: Locked" and "KG Status: Unlocked". should I unlock it? If yes, how?
you say any installation with Odin3 failed. you are trying to flash TWRP.
try to flash something different.
https://topjohnwu.github.io/Magisk/install.html#instructions
not sure about the display, though.
Well, I have a porblem with the Program that is mentioned in the Guide you linked, Frija asks for a CSC, and I dont know what I have to enter there, I only know that the device is a SM-T830/gts4lwifi.
CSC is region code
Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices
Since a lot of people will have their Galaxy S22 Ultra soon and I myself am thinking about either getting an S21 Ultra or S22 Ultra, I wanted to summarise a lot of information I found out during researching as Samsung devices are quite different...
forum.xda-developers.com
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Well, if RMM/KG state is prenormal you would see message "Only official released binaries are allowed to be flashed"
Anyway, try to flash official ROM and wait for KG state while device is connected to internet.
you can download according to your region from https://samfw.com/firmware/SM-T830
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
Setting the 7 days back works
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
try this: https://forum.xda-developers.com/t/...-twrp-and-magisk.4059227/page-2#post-88134465