Related
hi
after open oem lock we cant install trw or autoroot for 1week ...
this problem is
only official release binaries are allowed to be flashed
is any solution for this problem?
1week is very long time
thx
XDA:DevDB Information
1week time for oem lock a720f a7 2017 . only official release binaries are allowed , ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
hossputer
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2018-01-15
Last Updated 2018-01-15
download the latest firmware and replace the boot loader with an older one from android 6 then flash boot oen unlock again and your bootloader will be unlocked
What makes you think there is some sort of 1 week limitation?
On what are basing this info?
If the bootloader is locked its locked.
Hello I wanted to ask if that is the right time to wait a week
And if the flashing has worked?
Gesendet von meinem SM-A520F mit Tapatalk
[email protected] said:
Hello I wanted to ask if that is the right time to wait a week
And if the flashing has worked?
Gesendet von meinem SM-A520F mit Tapatalk
Click to expand...
Click to collapse
There is no 1 week wait. :silly:
I do not understand anything here anymore [emoji848][emoji848]
Gesendet von meinem SM-A520F mit Tapatalk
Some people stated that the bootloader unlocked itself one week after it was locked for the first time.
I think this has to do with that RMM STATE: PRENORMAL sh.
Supposedly if you have your phone for a total of 1 week of uptime then rmm state change allowing you to flash whatever
carlosmedia said:
Some people stated that the bootloader unlocked itself one week after it was locked for the first time.
I think this has to do with that RMM STATE: PRENORMAL sh.
Supposedly if you have your phone for a total of 1 week of uptime then rmm state change allowing you to flash whatever
Click to expand...
Click to collapse
The what, please explain and give further details.
Are you saying the bootloader unlocked itself or the OEM_UNLOCK appeared?
ashyx said:
The what, please explain and give further details.
Are you saying the bootloader unlocked itself or the OEM_UNLOCK appeared?
Click to expand...
Click to collapse
Yeah, didn't explained properly.
OEM_UNLOCK option appeared.
The strange thing is for example I have that RMM STATE: PRENORMAL But oem_unlock is still active.
Buut, if I try to flash somethin, apparently not official, it triggers an error, cancels flashing and a message "custom binaries cannot be flashed (BOOT)" appears at Download mode screen.
Some others with that same RMM thing stated what I said, they didnt have OEM_UNLOCK option appearing at developer options, and with that 1 week uptime it magically appeared.
Dont know if its the same with the custom binaries locked, but i got any other option but wait the week so ill see what happens
carlosmedia said:
Yeah, didn't explained properly.
OEM_UNLOCK option appeared.
The strange thing is for example I have that RMM STATE: PRENORMAL But oem_unlock is still active.
Buut, if I try to flash somethin, apparently not official, it triggers an error, cancels flashing and a message "custom binaries cannot be flashed (BOOT)" appears at Download mode screen.
Some others with that same RMM thing stated what I said, they didnt have OEM_UNLOCK option appearing at developer options, and with that 1 week uptime it magically appeared.
Dont know if its the same with the custom binaries locked, but i got any other option but wait the week so ill see what happens
Click to expand...
Click to collapse
I find it hard to get my head around why Samsung would implement such a feature?
In any case this started happening when Samsung updated the bootloader to XXU2.
However we managed to circumvent that by flashing the XXU2 marshmallow bootloader.
Now, some are on the XXU3 or XXU4 bootloader.
Currently we are trying to circumvent this. However according to what you've said these should automatically unlock after 7 days? Strange :silly:
ashyx said:
I find it hard to get my head around why Samsung would implement such a feature?
In any case this started happening when Samsung updated the bootloader to XXU2.
However we managed to circumvent that by flashing the XXU2 marshmallow bootloader.
Now, some are on the XXU3 or XXU4 bootloader.
Currently we are trying to circumvent this. However according to what you've said these should automatically unlock after 7 days? Strange :silly:
Click to expand...
Click to collapse
Thinking logically, if RMM is what makes OEM_UNLOCK disappear and it deactivate past 7 uptime days, then it probably goes the same for ofivial binaries lock
Cuz, is anybody without RMM having this issue?
I dont even know, this got me unprevented trying to flash a patched boot.img today.
ashyx said:
There is no 1 week wait. :silly:
Click to expand...
Click to collapse
Some users are testing the 7 day/168 hour theory. Let's see what happens
So I opened up a MD with Samsung support in twitter, just in case someome could tell to me what RMM state iz but our conversation ended with the guy at the support saying "They are not able to provide info about this" strange enough, I didnt ask if it was because they didnt know about it or they werent allowed, but I think Samsung its trying to hide it from us
Can this phone be rooted today? The truth is an urgency. I lost the imei and the base band
DaniPS2002 said:
Can this phone be rooted today? The truth is an urgency. I lost the imei and the base band
Click to expand...
Click to collapse
If you are missing OEM lock option at dev options》 You must have 168h of uptime
If you have rmm in prenormal and OEM unlock option active, you can only flash official/ non corrupted binaries
carlosmedia said:
If you are missing OEM lock option at dev options》 You must have 168h of uptime
If you have rmm in prenormal and OEM unlock option active, you can only flash official/ non corrupted binaries
Click to expand...
Click to collapse
Well then to be expected. The second case happens to me
i even waited 8 days .. but still RMM Prenormal and same error
hossputer said:
hi
after open oem lock we cant install trw or autoroot for 1week ...
this problem is
only official release binaries are allowed to be flashed
is any solution for this problem?
1week is very long time
thx
XDA:DevDB Information
1week time for oem lock a720f a7 2017 . only official release binaries are allowed , ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
hossputer
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2018-01-15
Last Updated 2018-01-15
Click to expand...
Click to collapse
I have a similar problem on my device, but to make matters worse it does not start. The least he gets is Download Mode. This all happened after I installed TWRP and Root. Someone help me!
ronisson_a said:
I have a similar problem on my device, but to make matters worse it does not start. The least he gets is Download Mode. This all happened after I installed TWRP and Root. Someone help me!
Click to expand...
Click to collapse
You mean it won't boot?
Sent from my SM-A520W using XDA Labs
iloveoreos said:
You mean it won't boot?
Sent from my SM-A520W using XDA Labs
Click to expand...
Click to collapse
I can not boot
---------- Post added at 11:04 AM ---------- Previous post was at 10:59 AM ----------
iloveoreos said:
You mean it won't boot?
Sent from my SM-A520W using XDA Labs
Click to expand...
Click to collapse
In Download mode it appears: "rev check fail device 3 binary 1". But it always varies. When I try to turn the power on, it appears: "only official released binaries are allowed to be flashed" and then "Warning: CMOLINE parameter modified" appears.
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?
[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,
Click to expand...
Click to collapse
bootloader unlock code different from frp unlock code.
installing other device firmware has chance to replace oeminfo.img partition. Changing this partitin often causes locked frp.
If lucky you can wipe from the erecovery that is loading. maybe even couple times. Then maybe it will boot. Other that that there has been no public mention of any fix.
do your best to fix it using hisuite or other methods if you can. if you have twrp that can help if you have stock recovery and locked frp your only hope might be hisuite and if that fails you will need a paid option like dc-phoenix or funkyhuewei. i only have experience with dc-phoenix, and it did fix my locked frp completely bricked phone, but i read that funky also works well but is nearly 3 times as expensive. (15€ vs 50€)
[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?
Click to expand...
Click to collapse
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .
sygladiator said:
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .
Click to expand...
Click to collapse
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed
mrmazak said:
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed
Click to expand...
Click to collapse
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull
sygladiator said:
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull
Click to expand...
Click to collapse
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
mrmazak said:
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
Click to expand...
Click to collapse
It all goes above my head , what exactly i have to do please elaborate .
sygladiator said:
It all goes above my head , what exactly i have to do please elaborate .
Click to expand...
Click to collapse
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.
mrmazak said:
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.
Click to expand...
Click to collapse
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good
sygladiator said:
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good
Click to expand...
Click to collapse
I know each device has it's own proceedure to, flash and all, and they are similar but different.
So can be confussing
Hi , Hello everyone
I Have gakaxy (A705FN) . it Stop getting updates from September 01, 2019
Anyone know this problem ??
When I enter download Mod , This phrase appears at the bottom of the screen :
Reboot Recovery Caose is ((bootchecker ) rebootRecoverywithkey)#
blocked-based OTA
Supported API : 3
MANUAL MOD v1.0.0#
I understood from some forums that if I flashing it with officiel rom void warranty .
Is this true ??
Two months ago I tried to unlock bootloader , and until now I don't know whether it is unlocked or Still locked.
I tried the adb command (fastboot oem device-info) But the adb tell me that waiting for device.
Then I tried this code : *#*#7378423*#*# connection problem or invalid mmi code.
is there method exept adb and dialler phone ??
Please help me to get updates by OTA
Need Help
Replies: 0 Views: 40
What's wrong with you!?
Where are you, xda senior
Have you checked that an update is available first?
I'm on September and no updates have been released yet. Same baseband as you.
Why do you want to unlock your bootloader? Checking that OEM unlocking box in the Developer settings doesn't unlock your bootloader.
Flashing anything on the phone will trip Knox and Void your warranty as well as prevent you from receiving updates including the Android 10 update coming this April. Your phone didn't stop receiving updates, it's just not available where you live yet. Just like waiting for replies to your post, you're impatient to get a security update that won't make much difference to your phone. My phone is on the November patch even though it's January and I couldn't care less, because I'm patient you should give that a try
xomikron said:
Why do you want to unlock your bootloader? Checking that OEM unlocking box in the Developer settings doesn't unlock your bootloader.
Flashing anything on the phone will trip Knox and Void your warranty as well as prevent you from receiving updates including the Android 10 update coming this April.
Click to expand...
Click to collapse
Flashing official roms with odin doesnt void any warranty.
God bless you
xomikron said:
Why do you want to unlock your bootloader? Checking that OEM unlocking box in the Developer settings doesn't unlock your bootloader.
Flashing anything on the phone will trip Knox and Void your warranty as well as prevent you from receiving updates including the Android 10 update coming this April. Your phone didn't stop receiving updates, it's just not available where you live yet. Just like waiting for replies to your post, you're impatient to get a security update that won't make much difference to your phone. My phone is on the November patch even though it's January and I couldn't care less, because I'm patient you should give that a try
Click to expand...
Click to collapse
I’m really grateful, thank you for responding to my topic
I Unlock bootloader in this manner
Step 1 – Allow bootloader unlocking in Developer options > enableOEM unlocking.
Step 2 – Power off your device. Press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
Step 3– Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Then I locked it again in the same manner.
I don’t know yet if the bootloader is locked or unlocked
and how to fix this : Block-Based OTA
So... have I broken my phone?
I need help
God bless you....
Thanks a lot
James.Miller said:
Flashing official roms with odin doesnt void any warranty.
Click to expand...
Click to collapse
Thanks a lot
This question puzzled me a lot and I did not find any answer :/
before Flashing official rom, will I enable OEM unlocking in Developer options ? or disable it .?
Does this term : ( Block-Based OTA ) will disappear or still appear ?
athmane_dz said:
Thanks a lot
This question puzzled me a lot and I did not find any answer :/
before Flashing official rom, will I enable OEM unlocking in Developer options ? or disable it .?
Does this term : ( Block-Based OTA ) will disappear or still appear ?
Click to expand...
Click to collapse
The other user mentioned that official firmware through Odin wouldn't trip knox which is something I've read before but wasn't sure. In any case, I forgot to mention that if you live somewhere in the European Union, a tripped knox shouldn't void your warranty. If you want to flash with Odin I do think you need to have the bootloader unlocked, but I'm not sure how you would do that.
It's time for me to end your ignorance (im looking arrogant right )
first of all you dont need to unlock your bootloader to install official firmware.
-the Reboot Recovery Cause is ((bootchecker) rebootRecoverywithkey)#
blocked-based OTA
Supported API : 3
MANUAL MOD v1.0.0# is not an error
-Block based means what it means and OTA means Over The Air.
-manual mode if just stock recovery.
-flashing latest official firmware wont trip knox/void anything.
-it's completely 'normal' that you don't have latest update if you live in an area where providers (like algeria) don't give a damn about you.
here is the firmware you should flash in order to get latest update faster than any others countries: https://samfrew.com/download/Galaxy__A70__/to3j/SEK/A705FNXXU5ASL4/A705FNOXM5ATA1/
Samsung Galaxy J6+ flashing crash - Boot loop endlessly
Hello, I have a problem with my phone : Samsung J6+ (SM-J610FN/DS) I have crached a flashing Rom with Odin and I'm sure it is because of that my phone can't start by pressing the power button. Now my phone has the message : An error has...
forum.xda-developers.com
Hi i've got a question. I recently purchased the A5 2017 (A520F) secondhand and i want to put a custom rom on it. I have unlocked and flashed tons of phones and tablets in the past so i'm far from a newbee.
My phone has "Bootloader OEM unlock" in dev options.
When i go into odin download mode (vol-, home+power) i dont get any message regarding "RMM state: Prenormal". FRP is unlocked.
Does this mean i'm all set to flash anything without the RMM.zip?
I'm having the latest security patch Jan2020 and Oreo bootloader. Knox is 0x0. Are there any other ways to check RMM state?
JMailuhu said:
Hi i've got a question. I recently purchased the A5 2017 (A520F) secondhand and i want to put a custom rom on it. I have unlocked and flashed tons of phones and tablets in the past so i'm far from a newbee.
My phone has "Bootloader OEM unlock" in dev options.
When i go into odin download mode (vol-, home+power) i dont get any message regarding "RMM state: Prenormal". FRP is unlocked.
Does this mean i'm all set to flash anything without the RMM.zip?
I'm having the latest security patch Jan2020 and Oreo bootloader. Knox is 0x0. Are there any other ways to check RMM state?
Click to expand...
Click to collapse
Reboot device just to check that OEM unlock is still enabled.
Yes, Bootloader OEM unlock switch is still activated.
JMailuhu said:
Yes, Bootloader OEM unlock switch is still activated.
Click to expand...
Click to collapse
Then read a guide like this, there are other workarounds though https://forum.xda-developers.com/t/...e-prenormal-on-oneui-android-pie-9-0.3911862/ but don't flash custom binaries while you don't bypass RMM prenormal status.
Yeah this requires a linux distro so i guess for that method i have to run linux in a VM or dualboot on another partition.
However, it still doesn't explain why i don't have a RMM message. Maybe RMM is gone altogether (not sure if thats possible tho).
Anyway thanks for your replies.
JMailuhu said:
However, it still doesn't explain why i don't have a RMM message. Maybe RMM is gone altogether (not sure if thats possible tho).
Click to expand...
Click to collapse
What do you mean with? You said RMM appears like prenormal.
SubwayChamp said:
What do you mean with? You said RMM appears like prenormal.
Click to expand...
Click to collapse
No i said i did NOT have any message regarding RMM state in download mode
JMailuhu said:
No i said i did NOT have any message regarding RMM state in download mode
Click to expand...
Click to collapse
Oh, sorry, I read bad, and nothing about KG?
It means you don't have remote restrictions, even with FRP.
In this case, you are able to flash custom binaries.
No problem bud, happens to the best of us. Nope nothing about KG either. I wil try and flash twrp etc. Worst case i'll flash back official firmware. Thanks for the help!
Solved: There was no RMM/KG on the device at all so i went and flashed TWRP and Rise-Q OneUI 2.5. Everything went smooth as butter.
Good, if it is not present in download screen, then in this device, either RMM/KG are not implemented.
hi i unlocked my bootloader and it still doesnt let me install twrp says that "only official released binaries are allowed to be flashed (recovery)"
How do you flash and what file?
log in to google account
ze7zez said:
How do you flash and what file?
Click to expand...
Click to collapse
odin and any non offcial file
olek123123124 said:
log in to google account
Click to expand...
Click to collapse
you didnt understand what i said
Win_7 said:
odin and any non offcial file
Click to expand...
Click to collapse
Read this:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
ze7zez said:
Read this:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
Click to expand...
Click to collapse
is there any permanent way of disabling it without flashing anything (ie like if for example i need another recovery other than twrp and i cant flash this?) im not saying that i currently need that but its good to be prepaired iguess
btw my phone thinks that its stolen?