Related
Hi all,
I have this model
Phone: SM-G955F
Android version: 7.0
Build number: NRD90M.G955FXXU1AQDD
I haven't touched anything or updated anything in at least 6 months and the work has been working fine.
I did update yesterday the "Samsung music" app however, not sure if that has anything to do with my problem.
This morning I got a message "Please restart your device, some apps are overloading the system".
So I did a reboot and now the device won't start.
I hate the red message "Custom Binary Blocked By FRP Lock" and the device stays turned off.
I didn't touch anything, so what on earth caused this?!
OEM Lock appears to be ON. FPR Lock is also ON now.
I had the phone rooted when I bought it but I'm using stock firmware.
Also, haven't had any issues in over 6 months so this I am very curious what could cause this to suddenly happen.
I read some guides that I have to re-flash stock firmware again, but I don't see how that will prevent the issue from happening again
Please help
I downloaded Odin and then what looks like the latest stock firmware.
Not sure how that is going to help. I had stock firmware before too
Hum. What can you boot into, recovery (is it stock recovery)? download mode? will it boot to setup in system, as it should if you have an FRP happening.
I had a nightmare of a day yesterday.
Downloaded the latest stock rom and flashed it using Odin. That worked fine.
Then I added TWRP and the phone got soft-bricked because apparently TWRP is not compatible with any of the latest firmware versions (who knew!)
Then I spent hours looking at hacks and found that Notorious zip that you can flash after getting into TWRP via the old BL/smash Start on Odin trick
Then phone showed verification error with the only option to Wipe all data (which I didn't want to do)
Then I managed to reflash the latest stock rom and leave it unrooted for now.
It's a learning experience but I don't like the high stress levels.
The most important thing is that I did nothing to cause the FPR lock and I'm now afraid it might randomly happen every few months
nkomp18 said:
I had a nightmare of a day yesterday.
Downloaded the latest stock rom and flashed it using Odin. That worked fine.
Then I added TWRP and the phone got soft-bricked because apparently TWRP is not compatible with any of the latest firmware versions (who knew!)
Then I spent hours looking at hacks and found that Notorious zip that you can flash after getting into TWRP via the old BL/smash Start on Odin trick
Then phone showed verification error with the only option to Wipe all data (which I didn't want to do)
Then I managed to reflash the latest stock rom and leave it unrooted for now.
It's a learning experience but I don't like the high stress levels.
The most important thing is that I did nothing to cause the FPR lock and I'm now afraid it might randomly happen every few months
Click to expand...
Click to collapse
Generally for the 955F (Exynos, yes?), it's a pretty straight forward process. Yes, you do have to make sure you have the correct TWRP . . .
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
once you flash TWRP, right at the end, or just before then end of the flash, press Vol up, Bixby and power to boot directly into TWRP. Should work just fine. If not, usually re-flashing TWRP and a direct boot to recovery works. Sometimes it take a few times to get the key pressing/timing down.
Yeah, you are right, it can feel pretty stressful.
hi, did you finally fix this problem? I have a s9+ stock firm, got TWRP and rooted and has been using it for a couple of months without issue, including reboot. but today I was using a bank app it kept stopping itself, so without further thinking I restarted the phone and got the red FRP lock on the screen. tried getting into TWRP but said it's blocked by FRP lock. then using ODIN I reflashed the same stock firm, got into the phone, everything is there except root, and of course Titanium works no more!
my question is, if anyone is reading this, is the TWRP still there or not? in order to find out I'll have to flip the OEM lock off and tried to get into TWRP, but would that trigger a factory reset? but if the TWRP is not there anymore, in order to root I'll have to do a system wipe. either way it gonna be troublesome. and besides, what's to prevent its happening all over again?
I'd appreciate any help! thanks))
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Matty1993 said:
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Click to expand...
Click to collapse
thanks Matty! now that I think about it I might have turned OEM unlock off because some bank app suddenly stopped working and I was trying to guess what went wrong.
Matty1993 said:
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Click to expand...
Click to collapse
hi i need your help, i have a samsung galaxy s7 and it's locked by frp (sorry for my english but i'm italian), i try to install official firmware by odin but it say an error sboot.bin fail! (with bt file) and say recovery.img fail! (with ap file), now i understand that my bootloader il blocked by oem block, there is a way to unlock by odin mode or others? i can't have access to recovery or phone.
please help me i'm desperate!
corvasce03 said:
hi i need your help, i have a samsung galaxy s7 and it's locked by frp (sorry for my english but i'm italian), i try to install official firmware by odin but it say an error sboot.bin fail! (with bt file) and say recovery.img fail! (with ap file), now i understand that my bootloader il blocked by oem block, there is a way to unlock by odin mode or others? i can't have access to recovery or phone.
please help me i'm desperate!
Click to expand...
Click to collapse
You need to flash the correct bootloader version to your device IE check the binary number on the firmware file and compare to what is listed on download mode
File binarys have the letter U? example is
G930FXXU2ARA1 or G930FXXU3ARA1
Take note of the number
Now in download mode on the device
Find AP SWREV B: ? An example is
AP SWREV B:2 K:0 S:0
The 2 signifies it's a bit 2 bootloader so the firmware package needed for this device would be for example G930FXX"U2"ABCD
all you have to do is match them up,
AP SWREV B1 = U1 or S1
AP SWREV B2 = U2 or S2
AP SWREV B3 = U3 or S3
As for the flash error message " custom binary blocked by frp lock" means someone has tampered with the firmware, I'd assume you didnt get it from sammobile ? or it's not made for model number check the backing to your S7 model number is located at the bottom in small writing
Will be G930"F" for example also compare the letter to the binary file to make sure your flashing the correct model,
Also what version of odin3 are you using to flash as 6.0 to 7.0 binaries can be flashed with V3.12 as the binary files don't use .lz4 compression however 8.0 binaries do use .lz4 compression this is a new type of compression so requires Odin3 3.13.1 as this odin3 has the capabilities to read and flash the .lz4 binaries to the device
And I'm not sure if your aware but the factory binaries dont have OEM unlock in them to remove the FRP however there is a way that I know how to do it on this particular model but it will vary the B:? In download mode and to if a combination rom is available for your binary number COLOR="Silver"]
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
[/COLOR]
snooyy said:
thanks Matty! now that I think about it I might have turned OEM unlock off because some bank app suddenly stopped working and I was trying to guess what went wrong.
Click to expand...
Click to collapse
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Matty1993 said:
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Click to expand...
Click to collapse
thanks mate yes I got my data back, but re-root it would mean loosing them so I'm running without the root now. good thing is Netflix, prime vedio, bank stuff are all working, bad thing is no titanium(
Matty1993 said:
You need to flash the correct bootloader version to your device IE check the binary number on the firmware file and compare to what is listed on download mode
File binarys have the letter U? example is
G930FXXU2ARA1 or G930FXXU3ARA1
Take note of the number
Now in download mode on the device
Find AP SWREV B: ? An example is
AP SWREV B:2 K:0 S:0
The 2 signifies it's a bit 2 bootloader so the firmware package needed for this device would be for example G930FXX"U2"ABCD
all you have to do is match them up,
AP SWREV B1 = U1 or S1
AP SWREV B2 = U2 or S2
AP SWREV B3 = U3 or S3
As for the flash error message " custom binary blocked by frp lock" means someone has tampered with the firmware, I'd assume you didnt get it from sammobile ? or it's not made for model number check the backing to your S7 model number is located at the bottom in small writing
Will be G930"F" for example also compare the letter to the binary file to make sure your flashing the correct model,
Also what version of odin3 are you using to flash as 6.0 to 7.0 binaries can be flashed with V3.12 as the binary files don't use .lz4 compression however 8.0 binaries do use .lz4 compression this is a new type of compression so requires Odin3 3.13.1 as this odin3 has the capabilities to read and flash the .lz4 binaries to the device
And I'm not sure if your aware but the factory binaries dont have OEM unlock in them to remove the FRP however there is a way that I know how to do it on this particular model but it will vary the B:? In download mode and to if a combination rom is available for your binary number COLOR="Silver"]
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
[/COLOR]
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Click to expand...
Click to collapse
thanks for answer, in odin mode it say rp swrev b3 k1 s2, where can i find the frmware with my binary number?
corvasce03 said:
thanks for answer, in odin mode it say rp swrev b3 k1 s2, where can i find the frmware with my binary number?
Click to expand...
Click to collapse
No worries so you have a bit 3 bootloader what does the model number say also in download mode ?
I'll provide you the link to the correct firmware to download that will be 100% official
matty1993 said:
no worries so you have a bit 3 bootloader what does the model number say also in download mode ?
I'll provide you the link to the correct firmware to download that will be 100% official
Click to expand...
Click to collapse
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
corvasce03 said:
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
Click to expand...
Click to collapse
Yep sweet also what region are you in also so I can make sure the firmwares modem is also region appropriate as they all run on different frequencies other than that that's all the info I need my friend product name is model number you have the same model as me I have G930F also give me two seconds and I'll get the link for you for the correct firmware, as for frp lock your very much quite lucky the warranty void is only "warranty void 1 (0×030c)
If it were : 1 (0×500b) youd be royally screwed for some reason combination roms will not boot on any Knox tripped S7 with : 1 (0×500b) but will boot on any Knox tripped device with : 1 (0×030c) I know this as I have a variety of S7 as I run a phone repair shop and have tested on tripped devices with Knox tripped as both
---------- Post added at 05:34 PM ---------- Previous post was at 05:27 PM ----------
corvasce03 said:
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
Click to expand...
Click to collapse
Not sure what region you are but here the link to the S7 G930F pages just scroll down select your country and the select the first available firmware that appears with a U3 or S3 when you have selected your region,
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
Matty1993 said:
Yep sweet also what region are you in also so I can make sure the firmwares modem is also region appropriate as they all run on different frequencies other than that that's all the info I need my friend product name is model number you have the same model as me I have G930F also give me two seconds and I'll get the link for you for the correct firmware, as for frp lock your very much quite lucky the warranty void is only "warranty void 1 (0×030c)
If it were : 1 (0×500b) youd be royally screwed for some reason combination roms will not boot on any Knox tripped S7 with : 1 (0×500b) but will boot on any Knox tripped device with : 1 (0×030c) I know this as I have a variety of S7 as I run a phone repair shop and have tested on tripped devices with Knox tripped as both
---------- Post added at 05:34 PM ---------- Previous post was at 05:27 PM ----------
Not sure what region you are but here the link to the S7 G930F pages just scroll down select your country and the select the first available firmware that appears with a U3 or S3 when you have selected your region,
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
Click to expand...
Click to collapse
ok thanks i try to download it and update you if it go or not
corvasce03 said:
ok thanks i try to download it and update you if it go or not
Click to expand...
Click to collapse
Hey mate no it will 100% work just select your country all firmware from sammobile is guaranteed to be 100% official I use them myself, the only thing however is you need to make an account but the good news its 100% free to make an account but then there another little downfall download speeds are a little slow in free subscription but well worth the wait as I guarantee it will work
Matty1993 said:
Hey mate no it will 100% work just select your country all firmware from sammobile is guaranteed to be 100% official I use them myself, the only thing however is you need to make an account but the good news its 100% free to make an account but then there another little downfall download speeds are a little slow in free subscription but well worth the wait as I guarantee it will work
Click to expand...
Click to collapse
thanks!!!!! it workk it's beautiful!!! thanks thanks thanks!
OK someone please help. I'm having this same issue, except I got a galaxy s6, however when I boot into download mode and plug cable up it recognizes the driver as a modem or sometimes I get it to show up in ports but its named USB serial device, so I'm unable to flash anything through odin. I tried plugging my wife's galaxy s7 up to PC through download mode and her phone doesn't even show up as a USB diagnostic port....I'm seriously stumped on this and having a hell of a time trying to find any info on this My dumbass had stay awake checked at the time and when I went to turn it off I must have accidently unchecked the OEM unlock option resulting in.....a good headache lol....thanks for ur time guys.
corvasce03 said:
thanks!!!!! it workk it's beautiful!!! thanks thanks thanks!
Click to expand...
Click to collapse
No problem mate glad I could help
---------- Post added at 01:56 AM ---------- Previous post was at 01:49 AM ----------
jfoley420 said:
OK someone please help. I'm having this same issue, except I got a galaxy s6, however when I boot into download mode and plug cable up it recognizes the driver as a modem or sometimes I get it to show up in ports but its named USB serial device, so I'm unable to flash anything through odin. I tried plugging my wife's galaxy s7 up to PC through download mode and her phone doesn't even show up as a USB diagnostic port....I'm seriously stumped on this and having a hell of a time trying to find any info on this My dumbass had stay awake checked at the time and when I went to turn it off I must have accidently unchecked the OEM unlock option resulting in.....a good headache lol....thanks for ur time guys.
Click to expand...
Click to collapse
Hey mate i run a phone repair shop it's got nothing to do with the phones it's the computer or drivers
#1 What version of Odin are you using, you should be using the latest I use 3.13.1 as it supports new .lz4 compression for 8.0 oreo firmware,
#2 did you install the latest Samsung drivers.exe because if you didnt the information is not on your computer to read samsungs devices all the information to communicate to the device is stored in these drivers,
If you havent this is your problem, go to Google type in "latest Samsung USB driver.exe download" or check the forums here for it also, download it and simply open the exe and install the drivers,
Reboot and now try, if you still have the same issue what USB cord are you using, try an original Samsung USB cable or decent branded one,
If there error still persists what version of windows are you using,
Thanks
Hello.
(backstory, boring) So, in efforts to root my device, after successfully doing it (or so I thought), I clicked the restart button on the "your phone has been modified, restart to undo process" notification from samsung. My phone had a message that the custom binary had been blocked when restarting. After a while I fixed it just by installing stock firmware from the internet, but not the original from Claro as it didn't have any of the bloatware.
(question) I'm trying to install the recovery now but I keep getting "custom binary(recovery) blocked due to remaining installment balance" on the download section for Odin, and it obviously fails.
OEM Lock: OFF
FRP Lock: OFF
So what is the problem? I already tried installing all the stock files from the firmware I found, but no success.
Any suggestions?
Thanks in advance,
Estebandido1232
Estebandido1232 said:
Hello.
(backstory, boring) So, in efforts to root my device, after successfully doing it (or so I thought), I clicked the restart button on the "your phone has been modified, restart to undo process" notification from samsung. My phone had a message that the custom binary had been blocked when restarting. After a while I fixed it just by installing stock firmware from the internet, but not the original from Claro as it didn't have any of the bloatware.
(question) I'm trying to install the recovery now but I keep getting "custom binary(recovery) blocked due to remaining installment balance" on the download section for Odin, and it obviously fails.
OEM Lock: OFF
FRP Lock: OFF
So what is the problem? I already tried installing all the stock files from the firmware I found, but no success.
Any suggestions?
Thanks in advance,
Estebandido1232
Click to expand...
Click to collapse
same problem, also Claro Puerto Rico, custom binary(recovery) blocked due to remaining installment balance, OEM Lock: OFF
FRP Lock: OFF, on android oreo (8.0) dont show OEM unlock option, spend more than 10 days and it does not appear, I can not downgrade to nougat (7.0) I've tried several versions, but all give DRK error, so I have to go back to Oreo (8.0) the last thing I tried was to install COMBINATION_FA70_G955FXXU1ARA1_CL12792727_QB16458742_REV00_user_mid_noship.tar.md5 which is based on 7.0 to see if Could you activate OEM unlock, but without any results, any help?
WalterSilverio said:
same problem, also Claro Puerto Rico, custom binary(recovery) blocked due to remaining installment balance, OEM Lock: OFF
FRP Lock: OFF, on android oreo (8.0) dont show OEM unlock option, spend more than 10 days and it does not appear, I can not downgrade to nougat (7.0) I've tried several versions, but all give DRK error, so I have to go back to Oreo (8.0) the last thing I tried was to install COMBINATION_FA70_G955FXXU1ARA1_CL12792727_QB16458742_REV00_user_mid_noship.tar.md5 which is based on 7.0 to see if Could you activate OEM unlock, but without any results, any help?
Click to expand...
Click to collapse
I'm able to upgrade/downgrade. I've moved past it and decided not to root it. So I installed 8.0 stock rom for PR signals.
I recently bought an unlocked s8+ which was from Claro, and am getting the same error. This error started popping up after I did a factory reset. The phone was never registered with Claro before, and has a clean IMEI. Does anyone know what could be done to stop this message?
mrh4ck said:
I recently bought an unlocked s8+ which was from Claro, and am getting the same error. This error started popping up after I did a factory reset. The phone was never registered with Claro before, and has a clean IMEI. Does anyone know what could be done to stop this message?
Click to expand...
Click to collapse
I have not found a problem since then. I'm trying now to get the phone working with a Stock Firmware. Downloaded the file from sammobile. I'll let you know how it goes.
Hello friends, did anyone manage to figure this out? im quite mad as ive never seen pre-normal state for RMM. I waited 10 days and no oem ever showed up. I too get this error and can not flash twrp. If anyone has managed to fix this, please help me out if possible. Thanks.
I had...have, actually, the same problem. I bought this phone on Ebay for the express purpose of rooting and running cfw. But when i try to install anything custom i get that same message that a balance is owed on this device. I even tried contacting Claro to inquire about paying the balance.
Long story short, I ordered another Exynos s8 and made sure it wasn't from Puerto Rico or Claro first.
WalterSilverio said:
same problem, also Claro Puerto Rico, custom binary(recovery) blocked due to remaining installment balance, OEM Lock: OFF
FRP Lock: OFF, on android oreo (8.0) dont show OEM unlock option, spend more than 10 days and it does not appear, I can not downgrade to nougat (7.0) I've tried several versions, but all give DRK error, so I have to go back to Oreo (8.0) the last thing I tried was to install COMBINATION_FA70_G955FXXU1ARA1_CL12792727_QB16458742_REV00_user_mid_noship.tar.md5 which is based on 7.0 to see if Could you activate OEM unlock, but without any results, any help?
Click to expand...
Click to collapse
I sold my US version and bought this Exynos version on eBay specifically so I could root. In developer options OEM unlock was missing. I tried flashing TWRP anyway and got the "custom binary blocked due to balance owed on the phone". I never got the pie update and any firmware I tried to install other than the one that came on the phone failed. I ended up just buying a different phone and made sure it was not Claro.
Well I pulled this one out today and flashed a non claro pie firmware. SM-G955FXXS8DTC6. Amazingly it passed. When I got the phone on the OEM unlock toggle was there and I got excited. I flashed the latest TWRP an it failed and I got that same annoying notification about the outstanding balance. But I do have OEM unlocked now at least. That's progress. There has to be a way around this
Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.
I want to flash TWRP onto my S8+ but im being blocked by the RMM. FRP and OEM is off but the RMM stays on prenormal. I have tried everything to my knowledge and what i have seen on XDA but no luck.
Is it even possible to bypass this?
My phone currently has the FEB 2020 security patch, is this a problem?
Please Help
Bylie said:
I want to flash TWRP onto my S8+ but im being blocked by the RMM. FRP and OEM is off but the RMM stays on prenormal. I have tried everything to my knowledge and what i have seen on XDA but no luck.
Is it even possible to bypass this?
My phone currently has the FEB 2020 security patch, is this a problem?
Please Help
Click to expand...
Click to collapse
Rmm/KG locks have been around since Oreo.
Generally to change KG and/or Rmm states takes 7 days ( 168hrs ) of ON Time with Internet Connection. Times may vary with devices.
While I have not tried them there are various threads on how to change the state.They may or may not work.
There are PC apps, like chimera, which also claim to be able to change the state.
I can't really recommend any one particular thread to try except for waiting for the time limit to expire. As I said some of the methods work for some but not others.
Flashing of stock firmware will reset these locks.
And only way to view these locks is in Download Mode.
spawnlives said:
Rmm/KG locks have been around since Oreo.
Generally to change KG and/or Rmm states takes 7 days ( 168hrs ) of ON Time with Internet Connection. Times may vary with devices.
While I have not tried them there are various threads on how to change the state.They may or may not work.
There are PC apps, like chimera, which also claim to be able to change the state.
I can't really recommend any one particular thread to try except for waiting for the time limit to expire. As I said some of the methods work for some but not others.
Flashing of stock firmware will reset these locks.
And only way to view these locks is in Download Mode.
Click to expand...
Click to collapse
The RMM state is now gone after the 168hrs as you said, which is awsome. I checked this morning. I unlocked the OEM and went to download mode, wasnt even showing. I'll try and flash TWRP later. I hope it doesnt gove me the "Official Binaries Only" error
spawnlives said:
Rmm/KG locks have been around since Oreo.
Flashing of stock firmware will reset these locks.
And only way to view these locks is in Download Mode.
Click to expand...
Click to collapse
I'm rmm locked here and need root. Are you sure flashing stock firmware will reset the locks?
BrMBr said:
I'm rmm locked here and need root. Are you sure flashing stock firmware will reset the locks?
Click to expand...
Click to collapse
Yes. Flashing stock firmware will relock OEM and KG and/or RMM state. Basically start the process again.
Note: Some phone can vary with times to be able to modify your phone. ie: my phone if I update firmware I can modify my phone as soon as I give it internet connection ( no sim ) using Wi-Fi.
spawnlives said:
Yes. Flashing stock firmware will relock OEM and KG and/or RMM state. Basically start the process again.
Note: Some phone can vary with times to be able to modify your phone. ie: my phone if I update firmware I can modify my phone as soon as I give it internet connection ( no sim ) using Wi-Fi.
Click to expand...
Click to collapse
Thanks for the clarification. I got locked after march security patch. I did all the stuff I found (date, reboots, etc) and nothing. I'll wait then.
I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?
eddieofny said:
I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
Try with patched odin, not normal odin.
TheWorldYT said:
Try with patched odin, not normal odin.
Click to expand...
Click to collapse
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
Oh, you have to use BROM, which involves opening up phone. You can search a tutorial how to do BROM mode in your phone.
eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
If the bit version of your phone is 3, flash the earliest bit 3 U package files. Then after flash bit 3 U1 package.
When flashing the U package just leave off the user data file. Must be using patched modded odin.
If you are bit 4, then you will be out of luck for a while.
I only know this because I ran into this same issue and that is how I resolved it on bit 3.