Hi XDA-Community.
I want to root my Galaxy S8 Plus based on the new Android 9.0.
In Download-Mode it shows me
OEM Lock: On
FRP Lock: On
KG-State is not shown anymore.
Means that im in "Jail" and had to wait those 168 hours before flashing TWRP etc? Or it's a new Samsung Thing?
Thanks in advance! And sorry for bad English, im from Germany!
Andreas96 said:
Hi XDA-Community.
I want to root my Galaxy S8 Plus based on the new Android 9.0.
In Download-Mode it shows me
OEM Lock: On
FRP Lock: On
KG-State is not shown anymore.
Means that im in "Jail" and had to wait those 168 hours before flashing TWRP etc? Or it's a new Samsung Thing?
Thanks in advance! And sorry for bad English, im from Germany!
Click to expand...
Click to collapse
Can't say for sure if your kgstate is missing that it's turned off/disabled as this is a new issue.
In your post from 2 days ago from this thread look back about 9 posts the OP has some updated news regarding this.
https://forum.xda-developers.com/sa...ide-root-install-twrp-samsung-t3747535/page49
As for the OEM lock you can wait for it to show up or try the date method ( or variations of it ) to get the option in developer menu. Note: Rebooting your phone resets your up time.
If you do try it I would recommend downloading your firmware first if you come across the official binary error you can re-flash and start from scratch again.
Just for reference on my S8 I flashed UK (BTU) firmware and updated to pie beta and had TWRP and root in about 5 min.
Related
A week ago I bought a used s7 edge. The original owner had done a factory reset. My first thing was to flash the latest local stock rom, bootloader, and modem. Then I installed TWRP and then rooted. All great. After a few days, I got tempted by the new Nougat betas.
OK, so now I've got a huge mess. I updated to the Minotaur 7.0 beta (nice rom) and got it nicely set up. I'm quite sure that I enabled OEM Updates in Developer Options. I was trying a manual setup of the APN and it wasn't working. So I thought a reboot might solve it. When I rebooted, I got a black screen with a little red message at the top - Custom binary blocked by FRP lock.
So I have spent the afternoon on the Internet only to learn that Google and Samsung created that lock so that stolen phones cannot be easily put into service. If OEM updates are checked, that disables the lock. I don't know what happened but I have a phone with a black screen that won't boot. It will go into download mode so I will try to flash a stock rom.
OK, that worked. I lost 2 days set up but the rom is booting.
Samsung Galaxy S5
Exodus CM12 5.1.1
Boeffla kernel
Apex Launcher
Hi.
Download the official firmware for your S7 and flash it with Odin. That should solve the problem.
ByronXg said:
Hi.
Download the official firmware for your S7 and flash it with Odin. That should solve the problem.
Click to expand...
Click to collapse
Yes it did! I was very worried that the stock rom was MM and so I was going backward. But it worked! And now I am all set up again. Just wish I knew what triggered that so I could avoid it in the future....
Sent from my SM-G935F using XDA-Developers mobile app
Did you tilt the option about OEM unlock in develop settings? Also try to flash without setting any PIN or fingerprint in the official rom
How do I do this process with a Claro brand phone? I do not know what firmware to select, the list has every country but Unites States.
rachel10105 said:
How do I do this process with a Claro brand phone? I do not know what firmware to select, the list has every country but Unites States.
Click to expand...
Click to collapse
You can use the European firmware on it.
hi
after open oem lock we cant install twrp 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
hossputer said:
hi
after open oem lock we cant install twrp 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
Click to expand...
Click to collapse
For some reason, Samsung has started to lock the bootloaders with the updates for 2017 A-series. Same for A520.
Everyone, Good Night,
I am trying to downgrade my S8 (SM-G950FD) to Nougat, however I am getting the error "SW REV. CHECK FAIL. DEVICE: 2. Binary: 1", I changed from Roms and still get this error at the moment of flash
I searched the internet for some solution, but I did not succeed in any
Any solution guys?
"Sorry for my bad English!"
marceloesplucio said:
Everyone, Good Night,
I am trying to downgrade my S8 (SM-G950FD) to Nougat, however I am getting the error "SW REV. CHECK FAIL. DEVICE: 2. Binary: 1", I changed from Roms and still get this error at the moment of flash
I searched the internet for some solution, but I did not succeed in any
Any solution guys?
"Sorry for my bad English!"
Click to expand...
Click to collapse
Error is caused by flashing ROMs with an earlier bootloader version number. ie ver 2 to 1 which can"t be down graded. On the firmware file name the 5th number from the right is the bootloader version no.
Sent from my Samsung Galaxy S8 using XDA Labs
Would this cause problem with a non-flashed (but ADB enabled) S8? I want to try Oreo but in case it ****s my battery I want to be able to downgrade.
I tried everything too. Seem like Samsung really making sure you can't downgrade from V2 bootloader.
OgreTactic said:
Would this cause problem with a non-flashed (but ADB enabled) S8? I want to try Oreo but in case it ****s my battery I want to be able to downgrade.
Click to expand...
Click to collapse
Only in respect to bootloader version
Try looking for Oreo with bl ver 1 so you can revert back to noughat if needed.
Sent from my Samsung Galaxy S8 using XDA Labs
I think you would get same error.
spawnlives said:
Only in respect to bootloader version
Try looking for Oreo with bl ver 1 so you can revert back to noughat if needed.
Sent from my Samsung Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
Sorry if this question has been asked before...
I have an S8 G950F running DBT pie, I have successfully switched on OEM Unlock, but when I enter download mode I still see RMM state renormal.
Can I still root in this situation? If no, how do I go about removing RMM prenormal.
Thanks.
virux1 said:
Sorry if this question has been asked before...
I have an S8 G950F running DBT pie, I have successfully switched on OEM Unlock, but when I enter download mode I still see RMM state renormal.
Can I still root in this situation? If no, how do I go about removing RMM prenormal.
Thanks.
Click to expand...
Click to collapse
Have a read through this thread. Also in the first post very top is a link to an updated issue ( in the same thread last page )
Since pie.is not released in my region yet I ended up having to flash UK firmware to test the pie beta updates. I did not have any trouble with installing TWRP,Root or Xposed. All with no issues.
But read this thread first before proceeding.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Alright thanks
Hello,
I have a samsung galaxy s10+ and I would like to downgrade android 11 to 10
I unlocked the bootloader but i cant get any stock ROM flashed that has binary version under 14 (E)
This is the closest I could get with Odin: https://samfw.com/firmware/SM-G975F/SIO/G975FXXSEFUJ2
Is there any way to bypass the binary lock?
This is the firmware I want: https://samfw.com/firmware/SM-G975F/SIO/G975FXXS9DTK9
Tried flashing it both from download mode and from bootloader, i get SW REV CHECK FAIL DEVICE 14 BINARY 9 error (or something like that I dont remember)
My phone is not network or carrier locked and any of that bs
I found an old thread where an user claimed to have successfully bypassed the lock but it is from 2017.. https://forum.xda-developers.com/t/5-1-1-rom-sm-a310f-twrp-downgrade.3614602/page-2
Is it possible for me to downgrade my current device? Literally no stores in my area have galaxy s10+ on stock right now and probably won't , I bought this phone 1.5 years ago
Thanks everyone
Edit:
I found another similar post which is also very old and I doubt it has any useful information for now https://forum.xda-developers.com/t/...amsung-bootloader-from-sw-rev-3-to-2.3650483/