Database Info

HELP!! Custom Binary Blocked by FRP

Hi
I tried to change my firmware by flashing a stock firmware from the STOCK FIRMWARE thread.
I got an error msg saying Custom Binary Blocked by FRP and I am not able to boot up now.
Before you ask me
The phone's model is G955-F (it is network locked to 3IE)
I have tried to restore using smasung smart switch it gives me the same error
I have tried used odin to restore the stock firmware which was in device before.
Can someone please help me?

rishab_s said:
Hi
I tried to change my firmware by flashing a stock firmware from the STOCK FIRMWARE thread.
I got an error msg saying Custom Binary Blocked by FRP and I am not able to boot up now.
Before you ask me
The phone's model is G955-F (it is network locked to 3IE)
I have tried to restore using smasung smart switch it gives me the same error
I have tried used odin to restore the stock firmware which was in device before.
Can someone please help me?
Click to expand...
Click to collapse
That's probably because you hadn't unlocked your bootloader. The Odin restore method will work, I have done it myself, make sure you select all of the files required in Odin. Sammobile have the 3IE firmware, get version G955FXXU1AQDD

daveuk87 said:
That's probably because you hadn't unlocked your bootloader. The Odin restore method will work, I have done it myself, make sure you select all of the files required in Odin. Sammobile have the 3IE firmware, get version G955FXXU1AQDD
Click to expand...
Click to collapse
I have already tried that.

rishab_s said:
I have already tried that.
Click to expand...
Click to collapse
This could sound like a really dumb suggestion but remove your google account and retry. Could it be the factory reset protection?
Sent from my SM-T810 using Tapatalk

I returned it, will be getting a refund and will buy another one

I have the exact same problem with my SM-G955F
It has FRP lock on it
It originally could boot up, but then the google screen would ask for a password
I then went to try and flash TWRP on it which did not work
I then tryed to install the samsung stock firmware for android 8.0.0 which brings up "Custom Binary(RECOVERY) Blocked by FRP Lock"
I dont know the password, so could not enter one
I only have access to the Download screen on the phone
Flashed AP "AP_G955FXXU1CRB7_CL12993656_QB17006520_REV00_user_low_ship_meta.tar.md5"
ON PHONE SCREEN IN DOWNLOAD MODE: KERNEL REV. CHECK FAIL. DEVICE:11, BINARY:1
What can i do to remedy this ?

Trying to Restore Phone to Stock (and a few other questions)

Hello!
I want to make my phone completely stock again. (Or as close as possible if completely stock isn't possible)
I unlocked, installed TWRP, and then rooted my phone yesterday (thanks to shashank1320's guide which made it very simple), but quickly found out that safetynet will prevent me from downloading and playing certain games on the Google Play Store.
After poking around online, it seems that even switching over to Magisk instead of using SuperSU will leave intermittent gaps in time where the app will be inaccessible due to the new workaround eventually being blocked.
So I want to go back. But like a derp, I forgot to create a backup beforehand.
So far I've unrooted through the SuperSU app itself, and flashed the BOOT.img and RECOVERY.img from Dazed No More's links in the Honor 6x Repository here.
After this is where I'm not sure what to do.
I think I need to find a factory system image to flash (and the vendor.img)?
I've seen a few threads saying that putting the UPDATE.APP in a dload folder into the phone and have the phone run the update worked (This did not work for me, although I'm not sure I have the right files; I downloaded it through a tech guide site here). I extracted the system.img and vendor.img from the update.app off that website using the Huawei Update Extractor, but I am afraid of flashing them in case they are the incorrect ones. But what if they are correct? Would I be able to recover if they are not?
Also, should I download and use unSU?
I know there is this guide on the front page right now. I've downloaded the Huawei Firmware Finder, but I... don't know how to use it. I narrow it down to the model number and that is where I get stuck. How... do I use it?
Some other basic questions I have in addition to this are:
Would I just have to flash the system.img and vendor.img through adb and then it will be stock again?
Would there still be leftover SuperSU files in my phone? I want to remove every trace of it. Would flashing be enough?
Am I even on the right track? And if not, where should I go from here?
Is the term "ROM" here firmware? Are the two terms interchangeable?
Ultimately, I would want to flash stock and then lock the bootloader again.
Thank you very much in advance. I appreciate it.
Edit: Wow I forgot to put any information, sorry about that.
Honor 6x
Model Number: BLN-L24
Build Number: BLN-L24C567B360
EMUI version: 5.0
Android version: 7.0

If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.

shashank1320 said:
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
Click to expand...
Click to collapse
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?

Faifie said:
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Click to expand...
Click to collapse
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.

shashank1320 said:
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
Click to expand...
Click to collapse
Okay, since those have been flashed with stock, that means I'm set to re-lock the phone! Will get around to it sometime tomorrow c:
Thank you so, so much ^^

How to install Oreo ROM?

Hi! I'm really humbly sorry, I'm new to this stuff, so I have to ask you...
I have a Galaxy S8+ Duos (SM-GD955FD). I bricked it once or twice trying to root it. So I had to flash a sammobile.com ROM...
Now this is done, I have a successfully rooted phone with with the Baseband version G955FXU1AQH3 and the irritating "security notice" (since I was not able to install Magisk, and the NotifyClean app doesn't work either).
I would like to flash the latest Oreo and root it. I also heard good things about the Oreo ROM by alexega.
So: I'm on AQH3 rooted. What can I do?
Thank you for your patience.

If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.

josegon30 said:
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
Click to expand...
Click to collapse
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...

andifla852 said:
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
Click to expand...
Click to collapse
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.

Just rooted the new Oreo ROM with TWRP. Works just fine, thank you.
So, what are the advantages of the Oreo ROM by alexega compared to XXU1CRAP?

josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.

juange said:
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
Click to expand...
Click to collapse
Just follow the steps from the link in my previous repply. As it's an original software, it won't trip knox or void your warantee.

hi, does anybody knows how to install the oreo firmware using odin but without changing the csc I already have?

josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?

costafabiof said:
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
Click to expand...
Click to collapse
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.

josegon30 said:
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
Click to expand...
Click to collapse
Did not work.
I can not find out where I went wrong.

developer11 said:
Android.com.pl **** you
Little cocksucker
Click to expand...
Click to collapse
Translation?

costafabiof said:
Did not work.
I can not find out where I went wrong.
Click to expand...
Click to collapse
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.

josegon30 said:
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
Click to expand...
Click to collapse
That did not work out. But thank you for your attention.

Stuck with lost IMEI after rooting

Hi guys,
yesterday I rooted my galaxy S7 sm-g930f.
Everything worked fine and in a few minutes later I was back on stock fw with twrp and magisk root. But unfortunately I lost my IMEI and have no backup of this.
I read that I can resolve it by flashing factory binary.
Can anyone guide me through the steps I have to do? I think I'm able to manage it but wondering if there are any files I do need for my fw version or can i simple download any factory binary?
Thanks in advance
Catarrer

Flash firmware with a newer modem version compared to the one in the custom rom you were using (not factory/combination). Use the same CSC, the stock recovery might be required to apply CSC.
If that doesn't work, wipe data (backup photos and all that).
Backup EFS in TWRP, nothing else unless sure.

Hi Bryan48765,
Thanks for your reply.
I'm downloading atm the newest fw which is available for my device. (May be take a while with 2k dsl...)
I'm going more concrete about the steps I did:
I activated the dev options, switched on the oem unlock and then switched to download mode.
Installed the latest twrp with the latest Odin version.
First I rooted my device then with chainfires supersu, but it doenst show up as rooted (rootchecker) so I flashed back a boot loader for my device which I downloaded here. Unfortunately i don't know any more which one...
After flashing the vootloader I installed magisk and everything was fine... and then a few hours later i recognised that mobile network isn't working. A few looks later I saw that there was no imei... so I don't know if it was working before flashing the boot loader or the error occurred afterwards.
I'll try tomorrow to flash the downloaded fw.
Do I get the single csc file for my current version or do I need to download the whole fw? (Takes about 5h)
Thanks in advance
Cayarrer

Thank you!
I'm now back to stock fw and have my imei back! Thank you so much!
At weekend I will try to root again. Do I need to pay attention to anything to not lose my imei again?
I would follow these steps:
Flash latest twrp for my device without auto reboot, boot directly into recovery and flash there the no-verity file and then the magisk. Am I right or do I need some more or less?
You guys at sea are so amazing! Thank you!

Catarrer2 said:
Thank you!
I'm now back to stock fw and have my imei back! Thank you so much!
At weekend I will try to root again. Do I need to pay attention to anything to not lose my imei again?
I would follow these steps:
Flash latest twrp for my device without auto reboot, boot directly into recovery and flash there the no-verity file and then the magisk. Am I right or do I need some more or less?
You guys at sea are so amazing! Thank you!
Click to expand...
Click to collapse
Backup the EFS, and store it in the cloud (not public), maybe encrypt the zip it is stored in. Only if a lot of firmware changes and data wipes don't return the imei, restore the backup. The restoration could also affect some modem settings, battery wear info, and it might not be restored correctly.
Unlock the bootloader before flashing the latest twrp. RMM serms to not apply here.
If the phone is encrypted (should be visible in the security settings) twrp might show that it "failed to mount /data", and it's normally where the root zip is stored. Alternatively, move the root zip and others to the external sdcard, though with root+encryption there might or might not be a risk for a type of brick.
Encryption is disabled by formatting /data and flashing a zip that disables it.
no-verity-opt-encrypt might already be in magisk but flash it anyway and if it fails return to the stock kernel ("boot" in twrp)

S7 edge SM-G935F remove root/ back to stock

Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks

Vinni777 said:
Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks
Click to expand...
Click to collapse
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader

kpwnApps said:
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader
Click to expand...
Click to collapse
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.

Vinni777 said:
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.
Click to expand...
Click to collapse
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void

kpwnApps said:
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void
Click to expand...
Click to collapse
Thanks mate. I managed yesterday to flash on latest software and everything works perfectly apart Sam Pay and Sam Health Offcourse android pay and etc works fine.