Related
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.
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.
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
Before I get going - yes I know I messed up. I do have plenty of experience flashing ROMs etc, albeit I'm absolutely not an expert. This was purely a not thinking moment.
So I flashed my Samsung Tab S4 with Kali Nethunter a while back, not really used the tab since. Without a great deal of thought, I decided to put the device back to factory. I went back into the OS and flicked the OEM toggle - utter braindead move. Obviously the device now comes up with a warning, the exact wording is:
"Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair / return for this issue may have additional cost"
I can still access download mode.
Right, now you've finished laughing/cussing me I did some digging and apparently I can still flash with Odin if its the official ROM? I went to SAMMobile and downloaded the latest ROM and Odin fails with a write error.
What I need to know is:
How bad have I messed up?
Is this recoverable?
Any help appreciated.
Hello there,
So yes, pretty bad mistake but these things happen but it should be recoverable. Just follow the link to get your device booted up! Hopefully the link is for your variant, if not look into installing twrp recovery for your device. Once installed you can back up your data and flash the rom compatible using twrp. Then set up the device and restore your data but make sure it's unlocked or your error may repeat itself! Also you have to find the right version of Odin, they do vary some are patched. Have fun!!
Recovery
Hi,
Thanks for the reply Jedi.
It already has TWRP on it, but recovery is inaccessible since I turned the OEM lock back on. The only thing I can now access is download mode but it can't seem to write to it, which I'm guessing is because the OEM lock is back on. I thought I might still be able to write the official Samsung ROMs even with the OEM lock but it doesnt seem like its the case. Obviously no access to ADB to do a Fastboot unlock either. Fresh out of ideas.
Any other solutions?
bump - anyone? lol, really not looking for an expensive door stop.
It seems you're at the dead end. However, there might be a solution for this, not sure though does it work. But go to OnePlus forum and you'll find how to recover from bricked device. You still got hope because of TWRP. good luck bro
OK, so for anyone wondering if this is fixable, the answer is YES!
You can flash the standard ROM even with the bootloader locked. Clearly what I downloaded from SAMMobile wasnt compatible, however when I used Frija, it found and downloaded the correct ROMs.
Another sticking point of this was the infamous USB 2.0 issue, I assumed the ROM was failing again, however when I finally could be arsed to try it on my old PC, its worked like a charm.
So there you have it:
Latest version of Odin
Latest Samsung USB drivers
Latest ROM downloaded from Frija
Put the tablet into download mode and flash away.
Hello everyone, so as the title suggests I have an a520f device that suddenly got frp locked after a reboot, and I'm guessing it was because I disabled and re-enabled developer options and forgot to turn on OEM unlocking again. anyway the thing is I tried using Tenorshare 4ukey but it didn't detect my device and same thing with Odin when I tried to flash a stock rom. I tried every possible fix (using a different cable a different usb port a dfferent pc etcc..) and none of them worked until I decided to take the phone to a local workshop and they told me that the data transfer port was broken and honestly they asked for more than what the whole device is worth to replace it. So I was wondering if there is a way to install a stock rom without a pc or/and rooting (directly from an sd card using recovery mode maybe)? any help would be greatly appreciated! and sorry about the long read I just tried to include any detail that might be helpful.
astralsabbat said:
Hello everyone, so as the title suggests I have an a520f device that suddenly got frp locked after a reboot, and I'm guessing it was because I disabled and re-enabled developer options and forgot to turn on OEM unlocking again. anyway the thing is I tried using Tenorshare 4ukey but it didn't detect my device and same thing with Odin when I tried to flash a stock rom. I tried every possible fix (using a different cable a different usb port a dfferent pc etcc..) and none of them worked until I decided to take the phone to a local workshop and they told me that the data transfer port was broken and honestly they asked for more than what the whole device is worth to replace it. So I was wondering if there is a way to install a stock rom without a pc or/and rooting (directly from an sd card using recovery mode maybe)? any help would be greatly appreciated! and sorry about the long read I just tried to include any detail that might be helpful.
Click to expand...
Click to collapse
twrp recovery flashed on phone or not?
matkali said:
twrp recovery flashed on phone or not?
Click to expand...
Click to collapse
unfortunately not, Is there a way to flash it without Magisk or PC?
In know a rooter app "kingroot" [ I don't recommend for security reasons], which could be root your phone online!
If you can get root access!
you can use twrp flasher apps to flash your recovery!
Can't you just bypass frp?