Develop Bugs

TWRP S965F Install Question with a slight twist

Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.

jusx10i said:
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
Click to expand...
Click to collapse
I'd love any info on this as well.

Unfortunately, I just had to wait the week.
I will say though when you come to install TWRP make sure you follow the instructions. I didn't, then I had to wait another week for the OEM Unlock to re-appear again!

unlock bootloader SM-J260A

Does anyone know how to root or unlock the bootloader of this phone? I can't find anywhere else on how to do it.

It seems to be pretty similar in all Samsung phones
- Go to settings
- Go to About Phone
- Go to Software information
- Tap Build number 7 times to activate developer options
- Return to settings
- Select developer options
- Activate OEM Unlock
And you should now have an unlocked bootloader

ShaDisNX255 said:
It seems to be pretty similar in all Samsung phones
- Go to settings
- Go to About Phone
- Go to Software information
- Tap Build number 7 times to activate developer options
- Return to settings
- Select developer options
- Activate OEM Unlock
And you should now have an unlocked bootloader
Click to expand...
Click to collapse
it's not there.

yah2000 said:
it's not there.
Click to expand...
Click to collapse
There are two possible reasons why OEM unlock is not on your phone
1) Either the bootloader is not unlockable for this phone (very common for U.S. phones)
or
2) You have RMM lock.
What is this?
You can read all about it here:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
corsicanu said:
How to know if you are locked
There are 3 things at this chapter:
1. "Only official released binaries are allowed to be flashed" message shows up and now you know for sure you got locked outside your phone
2. Missing OEM unlock toggle in developer settings, if your device has FRP
3. "RMM state = Prenormal" in download mode
Click to expand...
Click to collapse

ShaDisNX255 said:
There are two possible reasons why OEM unlock is not on your phone
1) Either the bootloader is not unlockable for this phone (very common for U.S. phones)
or
2) You have RMM lock.
What is this?
You can read all about it here:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
It says "kg state=checking" and frp lock off. Nothing about rmm lock.

yah2000 said:
It says "kg state=checking" and frp lock off. Nothing about rmm lock.
Click to expand...
Click to collapse
Then most likely your bootloader will always be locked and no way of unlocking
Too bad

Flash combination file then you can do it if you need to run repairs etc or whatever else you have in mind...
- Go to settings
- Go to About Phone
- Go to Software information
- Tap Build number 7 times to activate developer options
- Return to settings
- Select developer options
- Activate OEM Unlock

yah2000 said:
it's not there.
Click to expand...
Click to collapse
Mine isnt there either.

Anyone know this problem ??

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

Unlocking Bootloader

So lately, I tried to unlock bootloader of my Samsung Galaxy M30 with One UI Core 2.0. As I had read in many guides that after successful unlock, the option of unlocking OEM will be grayed out. But when I enabled it, it asked for my device PIN, then Samsung account password and switched off automatically. After factory reset, it booted up but the OEM unlock option was still blue and togglable. It read Bootloader already unlocked!
I'm confused because there was no 'device lock' mode in download mode, no need to 'long press power up to unlock Bootloader in download mode' or 'no gray toggles'.
On Download Mode I could see "OEM lock: OFF" . Does it mean that my Bootloader is unlock.

Azamsm said:
So lately, I tried to unlock bootloader of my Samsung Galaxy M30 with One UI Core 2.0. As I had read in many guides that after successful unlock, the option of unlocking OEM will be grayed out. But when I enabled it, it asked for my device PIN, then Samsung account password and switched off automatically. After factory reset, it booted up but the OEM unlock option was still blue and togglable. It read Bootloader already unlocked!
I'm confused because there was no 'device lock' mode in download mode, no need to 'long press power up to unlock Bootloader in download mode' or 'no gray toggles'.
On Download Mode I could see "OEM lock: OFF" . Does it mean that my Bootloader is unlock.
Click to expand...
Click to collapse
You are bootloader unlocked. Check the guides on this forum, and also the TWRP thread.
Guides:
1. https://forum.xda-developers.com/galaxy-m30/how-to/guide-flash-gsi-samsung-m30-t4126133
2. https://forum.xda-developers.com/galaxy-m30/how-to/guide-galaxy-m30-recovery-edl-modes-t4020231
3. https://forum.xda-developers.com/ga...m-android-10-q-stock-rooted-firmware-t4026819
TWRP:
1. https://forum.xda-developers.com/galaxy-m30/development/m30lte-twrp-3-3-1-samsung-m30-t3931510

hello, urgent help me. I have a samsung M30 which I flash with an android 10 binary 6 rom. and after the tactility of my phone no longer works. I want to bring the system back to android 9, but I can't.
please give me any solution, waiting for your answer

Question Locked phone stuck in Fastboot mode

Hey everyone!
I was updating to the latest Android beta to try to get the Move to iOS app to work. The update seemingly went fine and I was using my phone (on reddit lol) and suddenly it powered off.
Now when it starts I get a black screen that asyas "Fastboot Mode". My phone isn't unlocked so I haven't done anything funky with the firmware.
I'm afraid I've lost everything on the phone
Here's a picture of what the phone shows:
https://imgur.com/oBpGFGX

Well, the fact you can boot into fastboot is good news
Before we talk about possible actions:
- what ROM exactly were you coming from ? Was that rooted or with a custom kernel ? Was the device unlocked ?
- what ROM exactly have you been flashing ? By using which method ? Any additional steps you did while/after flashing this ?

s3axel said:
Was the device unlocked ?
Click to expand...
Click to collapse
Besides @adamkparker's statement below, the screenshot shows the bootloader is locked, unfortunately.
adamkparker said:
My phone isn't unlocked so I haven't done anything funky with the firmware.
Click to expand...
Click to collapse
You should never install Betas without having the bootloader unlocked. Is OEM unlocking at least enabled in Developer Options (I know you can't get in there right now, but was it enabled before the phone stopped being able to boot to Android)? If OEM unlocking is enabled, even with the bootloader locked now, you can try Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
If OEM unlocking isn't enabled, there's probably nothing you can do to fix the phone - you'll have to RMA it.

Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader

fil3s said:
Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader
Click to expand...
Click to collapse
You can sideload OTA updateds without USB debugging enabled. It's really the only way forward for op.