Database Info

Custom Binary Blocked By FRP Lock - after regular boot

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

remove rmm state

visit this link https://halabtech.com/remove-rmm-prenormal-a320f-j701f-etc/
use miracle box to remove rmm state ...
put phone itno download mode and connect with computer via usb . then open miracle box
go to samsung tab ... then select Reset Reactivation / EE Locks
then click start .. wait for 1 minute .. ist done ...
then flash Stock ROm or Custom Rom
tools link http://www.techeligible.com/2018/04/03/download-miracle-2-58-with-loader/

Thank you very much I used miraclebox to remove rmm and root my oreo 8.1 j7 pro (j730gm, same exynos chipset) without problem
I got 'open port' error in miraclebox at first but it was solved after installing virtual serial port driver

A720F not work

bluechipmunk1225 said:
Thank you very much I used miraclebox to remove rmm and root my oreo 8.1 j7 pro (j730gm, same exynos chipset) without problem
I got 'open port' error in miraclebox at first but it was solved after installing virtual serial port driver
Click to expand...
Click to collapse
Hi, how do you create a virtual serial port?

I just googed virtual serial port driver, installed and it worked

full tutorial please?

It works!
This method actually worked in removing the rmm state in my J701F.

Do I have to download stock rom or it's optional?

virtual serial port
bluechipmunk1225 said:
I just googed virtual serial port driver, installed and it worked
Click to expand...
Click to collapse
link pls

If i got one of these 'miracle box' things, would this work on my SM-G960W(samsung galaxy s9, snapdragon, Canada, Koodo)?

FalsAlarm said:
If i got one of these 'miracle box' things, would this work on my SM-G960W(samsung galaxy s9, snapdragon, Canada, Koodo)?
Click to expand...
Click to collapse
you just have to take the risk

qasimsansi3 said:
visit this link https://halabtech.com/remove-rmm-prenormal-a320f-j701f-etc/
use miracle box to remove rmm state ...
put phone itno download mode and connect with computer via usb . then open miracle box
go to samsung tab ... then select Reset Reactivation / EE Locks
then click start .. wait for 1 minute .. ist done ...
then flash Stock ROm or Custom Rom
tools link http://www.techeligible.com/2018/04/03/download-miracle-2-58-with-loader/
Click to expand...
Click to collapse
is it mandatory to flash firmware after removimg rmm from miracle

abd96iq said:
is it mandatory to flash firmware after removimg rmm from miracle
Click to expand...
Click to collapse
yes

It works
It works for me very well, even my smj701d was not shown in the list from miracle box. I choose a similary one and
when done my bootloader option was visible.
Guess everyone can try it too, i really guess there is nothing can happen.

meyshah said:
A720F not work
Click to expand...
Click to collapse
You managed to bypass rmm state prenormal? If so, please tell us how!

Samsung Galaxy S7 - SM-G930F FRP Lock Android 8 Problem

Hello, I have since 1 week the problem to unlock the Galaxy S7 SM-G930F. Since my little brother does not have the e-mail and password anymore, and so we can not get in the phone, after a factory reset, Google wants to verify the I but what about the data we have is no longer possible. That's why I've tried everything the FRP lock somehow but everything fails ... I've already tried that with the binary 2, but does not work, the download mode tells me the following error:
sw rev. check fail (bootloader) device: 5 binary: 2
And now I do not know what else to do, I've already tried to downgrade to Android 7 or Android 6, but it does not work, Odin always says FAIL.
I hope you can help me somehow, otherwise I just do not know how to continue.
Download Mode Details:
ODIN MODE
PRODUCT NAME: SM-G930F
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
AP SWAEF: B:5 - K:3 - S:4
Click to expand...
Click to collapse
Sorry for my bad English. Greetings WhizKek

Try an application called FRP Hijacker

bwian444 said:
Try an application called FRP Hijacker
Click to expand...
Click to collapse
Not work's because is a Fake this Program :-/ Or u have a Something link for me what works`?

WhizKek said:
Not work's because is a Fake this Program :-/ Or u have a Something link for me what works`?
Click to expand...
Click to collapse
ok. Might have been Android Toolkit by John Esmail.
It was one or the other. I had custom binary blocked by frp lock.
Phone is now working.

WhizKek said:
Hello, I have since 1 week the problem to unlock the Galaxy S7 SM-G930F. Since my little brother does not have the e-mail and password anymore, and so we can not get in the phone, after a factory reset, Google wants to verify the I but what about the data we have is no longer possible. That's why I've tried everything the FRP lock somehow but everything fails ... I've already tried that with the binary 2, but does not work, the download mode tells me the following error:
sw rev. check fail (bootloader) device: 5 binary: 2
And now I do not know what else to do, I've already tried to downgrade to Android 7 or Android 6, but it does not work, Odin always says FAIL.
I hope you can help me somehow, otherwise I just do not know how to continue.
Download Mode Details:
Sorry for my bad English. Greetings WhizKek
Click to expand...
Click to collapse
You cannot downgrade the boot loader, your phone is version 5 (Device 5) and the firmware you are flashing is version 2 (binary 2) . 5 to 2 is not possible.
There are many guides how to bypass FRP lock on Oreo, you will have to find one that works. Try YouTube.

cooltt said:
You cannot downgrade the boot loader, your phone is version 5 (Device 5) and the firmware you are flashing is version 2 (binary 2) . 5 to 2 is not possible.
There are many guides how to bypass FRP lock on Oreo, you will have to find one that works. Try YouTube.
Click to expand...
Click to collapse
I did not understand your answer at all, you may like to see my YouTube progress, all I found are fakes. There, people show that you should put the SIM card in and out again and that should work, but it does not.

i have thesame problem
bwian444 said:
ok. Might have been Android Toolkit by John Esmail.
It was one or the other. I had custom binary blocked by frp lock.
Phone is now working.
Click to expand...
Click to collapse
what version you used? not working in my phone same model

Not sure. Deleted everything. Although used usb debugging fix as well.

WhizKek said:
Hello, I have since 1 week the problem to unlock the Galaxy S7 SM-G930F. Since my little brother does not have the e-mail and password anymore
sw rev. check fail (bootloader) device: 5 binary: 2
you simply have an incorrect combination file, more specifically the version number is incorrect if you boot the phone into recovery mode first it will show you a firmware version looking something like G930FXXU5ASD2 the parts you need to pay atterntion too are the u5 and the 2 at the end the u5 is bootloader version you CANNOT down grade find a combo rom with same bootloader version and flash that then open the app "factory ime" and punch in *#0808# select ap and dm+modem+adb , reboot phone run your choice of frp program i usually get mine from techelegible website after u run frp program reinstall 4 file stock firmware do flashing using either prince comsey odin or odin 3b i get firmware from androidfilehost usually good luck happy hacking
Click to expand...
Click to collapse

How To Guide 100% successfully unlock the Bootloader of your ROG Phone5/5s

Success is disgusted by some people, and will not share any files for free in the future.

Once again you proved it bro. Amazing job will test now and confirm.

Working perfectly tested and rooted. Steps are easy to follow.
1) Download the ENG firmware and flash it following the steps.
2) Then follow this post and the commands to extract asuskey4 and add ISN to the asuskey4.
3) Flash WW ROM back to the phone.
4) Use Unlock tool and then done.

by far one of the best contributions of the forum, I don't usually comment, but I had to thank you

This is huge! The answer everyone with Tencent WW phones were looking for! Thank you

Could anyone please elaborate step 1 (flashing the ENG firmware provided)?
My phone enters edl mode and I see port 9008 in the device manager.
What should I do next?

arjun_m4 said:
Working perfectly tested and rooted. Steps are easy to follow.
1) Download the ENG firmware and flash it following the steps.
2) Then follow this post and the commands to extract asuskey4 and add ISN to the asuskey4.
3) Flash WW ROM back to the phone.
4) Use Unlock tool and then done.
Click to expand...
Click to collapse
yes,very easy

Can NOT flash ENG firmware..
Method # 1 : "0-update_image_EDL.bat" does not even start
Method # 2 : ERROR_UNSUPPORTED_TYPE
Method # 3 : Download Fail:FireHose Fail: FHLoader Fail: process fail
SOS guys! I am in deep sh*t!!

I cant find the SSN in the device.txt ... Only ISN is available .. ?

JazonX said:
I cant find the SSN in the device.txt ... Only ISN is available .. ?
Click to expand...
Click to collapse
You can see SSN on our phone when you boot up ENG firmware just type urself to the editor.
Find the address mentioned and start typing from first 0 u will see the HEX changing and then verify it's correct and save

aimsjahan said:
Can NOT flash ENG firmware..
Method # 1 : "0-update_image_EDL.bat" does not even start
Method # 2 : ERROR_UNSUPPORTED_TYPE
Method # 3 : Download Fail:FireHose Fail: FHLoader Fail: process fail
SOS guys! I am in deep sh*t!!
Click to expand...
Click to collapse
Can you check if your phone is being recognized as EDL maybe the drivers are installed wrong. I can verify that the files provided works 100% and you have to use left side type c of the Asus not the bottom.

JazonX said:
I cant find the SSN in the device.txt ... Only ISN is available .. ?
Click to expand...
Click to collapse
SSN can be seen on the homepage of the mobile phone after flashing the ENG firmware, or on the packaging box of your mobile phone.

Asuskey4 software download link please

Thanks, @johnny886! Btw, can you change your post to "General" instead of "Question", and pin it to this forum so people would use it as a reference in the future?

arjun_m4 said:
Can you check if your phone is being recognized as EDL maybe the drivers are installed wrong. I can verify that the files provided works 100% and you have to use left side type c of the Asus not the bottom.
Click to expand...
Click to collapse
My ROG5 is being shown in Device Manager as Qualcomm 9008. So I guess it has entered in EDL mode.

aimsjahan said:
My ROG5 is being shown in Device Manager as Qualcomm 9008. So I guess it has entered in EDL mode.
Click to expand...
Click to collapse
Could you reinstall the drivers I have faced issues like this before with other Qualcomm devices. Reinstall Qualcomm drivers it should work. And remember to install with disable signature enforcement.

Akkaya34 said:
Asuskey4 software download link please
Click to expand...
Click to collapse
I think you haven't figured out how to do it. Please read the steps carefully before proceeding. . .

arjun_m4 said:
Could you reinstall the drivers I have faced issues like this before with other Qualcomm devices. Reinstall Qualcomm drivers it should work. And remember to install with disable signature enforcement.
Click to expand...
Click to collapse
Appreciate your response mate! I will try again after reinstalling QCOM drivers. Could you please share that driver you are using?
Also, my PC does NOT detect ROG5 when using the official USB-C on both end cable. I have to use another cable with USB in one end and USB-C in the other end. Do you think that might be an issue?

With lost imei , imei=0 , I correct imei , SN in asuskey4 but it not unlock

nguyenhung9x2018 said:
With lost imei , imei=0 , I correct imei , SN in asuskey4 but it not unlock
Click to expand...
Click to collapse
The asuskey4 should contain SSN and ISN then only it will unlock. Make sure it's there and how come you lost your IMEI I tried this for 2 separate devices and I didn't face any issue.

NEED N976V U7 emergency_download / DEAD-BOOT / DEAD-FIX / DEBUG EMERGENCY / 9008 / UnBrick / firehose programmer / loader PLEASE

Hi all,
I need a N976V U7 (USB only) DEAD-BOOT file / DEAD-FIX file / DEBUG EMERGENCY / 9008 / UnBrick / firehose programmer
The SM-N976V is a Verizon variant of the Note 10+ 5G positioned for the US market.
PLEASE PLEASE PLEASE !!!
Thank you.

Network_Pro said:
Hi all,
I need a N976V U7 (USB only) DEAD-BOOT file / DEAD-FIX file / DEBUG EMERGENCY / 9008 / UnBrick / firehose programmer
The SM-N976V is a Verizon variant of the Note 10+ 5G positioned for the US market.
PLEASE PLEASE PLEASE !!!
Thank you.
Click to expand...
Click to collapse
you dont need that as far as you can get into EDL mode you can flash with miracle tool box

So the Miracle Tool support SM-N976V SW Rev . bit7 (U7) ? I didn't find it specifically mentioned anywhere. In the EDL mode the Qualcomm sm8150 requires the firehose programmer. For other models this file seems to available so there is hope that for this model it can also be obtained from GSPN USA probably or from a guy who knows a guy who knows a guy who passed by a Samsung building once wink wink.

Network_Pro said:
So the Miracle Tool support SM-N976V SW Rev . bit7 (U7) ? I didn't find it specifically mentioned anywhere. In the EDL mode the Qualcomm sm8150 requires the firehose programmer. For other models this file seems to available so there is hope that for this model it can also be obtained from GSPN USA probably or from a guy who knows a guy who knows a guy who passed by a Samsung building once wink wink.
Click to expand...
Click to collapse
am telling you from experience it happened to my device i bricked it and i used miracle tool crack with just stock rom i did the EDL i just selected scatter file etc and i flashed and that was it
Anyways Good luck unbricking

Which update was it? I think the problem is the bit7 / U7 the firehose for that is another one if it worked for previous versions.

Gudaji said:
am telling you from experience it happened to my device i bricked it and i used miracle tool crack with just stock rom i did the EDL i just selected scatter file etc and i flashed and that was it
Anyways Good luck unbricking
Click to expand...
Click to collapse
Gudaji please give more info how did you do it exactly? Which 'scatter' file did you write to the device ?

Network_Pro said:
Gudaji please give more info how did you do it exactly? Which 'scatter' file did you write to the device ?
Click to expand...
Click to collapse
Okay,
I unpacked the firmware got the scatter file put the device in edl mode (with pins) and flashed the device .
But make sure you watch legit tutorials on YouTube how to get miracle tool box crack

Gudaji said:
Okay,
I unpacked the firmware got the scatter file put the device in edl mode (with pins) and flashed the device .
But make sure you watch legit tutorials on YouTube how to get miracle tool box crack
Click to expand...
Click to collapse
I've deleted your other post in this thread for the same reasons I already provided you here:
[RELEASED] TWRP FOR REDMI 12C/Poco C55
So I've started development for device trees, TWRP and custom for Redmi 12C (earth) and by the end of may we should also have a rom and custom recovery for our Redmi 12C. So stay tuned
forum.xda-developers.com
Please read my message as a friendly warning!
Regards
Oswald Boelcke
Senior Moderator

Which firmware and which scatter file? It won't work with wrong ones. More specifics please.
Did you have a pre-made scatter file, that you have made before bricking/EDL ?
It is important to be precise.

Network_Pro said:
Which firmware and which scatter file? It won't work with wrong ones. More specifics please.
Did you have a pre-made scatter file, that you have made before bricking/EDL ?
It is important to be precise.
Click to expand...
Click to collapse
Your stock rom it is in your stock rom just unpack it or use ODIN to unbrick

Odin does not see the phone because the phone is in 9008 EDL mode and the driver for that one is from Qualcomm. Odin wants a mode and driver from Samsung. For the Samsung download - Odin mode to work, the later Boot stages need to load. Those are messed up by wrong etoken bypass for the wrong Update version or wrong BL or tripepd knox erasure of the entire flash or something of that sort.
In the stock ROM I do not know which file you can call a scatterfile? Is it the PIT file which is used for formatting?
This is the 'stock ROM' correct ? https://samfw.com/firmware/SM-N976V/VZW/N976VVRU7HWB2

Well for sure the Miracle Box has a huge collection of loaders in the distribution, as well as XML files. Very interesting.
@Gudaji, it seems, however that with U7 there may be needed a new loader. The update "bit" is somehow set inside the CPU, which, from my understanding, prevents older loaders from working?

Network_Pro said:
Well for sure the Miracle Box has a huge collection of loaders in the distribution, as well as XML files. Very interesting.
@Gudaji, it seems, however that with U7 there may be needed a new loader. The update "bit" is somehow set inside the CPU, which, from my understanding, prevents older loaders from
Click to expand...
Click to collapse
First of all do you have miracle tool box?
If so go to the Qualcomm tab and you will se flash tab under and then you select the files from your “extracted” firmware and flash while in EDL mode

The "Miracle Box Update 3.39 to 3.40 only for PS" informs me there is a new version and does not start. Maybe I do not have the right one.

Network_Pro said:
The "Miracle Box Update 3.39 to 3.40 only for PS" informs me there is a new version and does not start. Maybe I do not have the right one.
Click to expand...
Click to collapse
There is a bypass for it but you have to look for it

I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.

Network_Pro said:
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Click to expand...
Click to collapse
Reply in my pm asap

Network_Pro said:
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Click to expand...
Click to collapse
First off how did you brick your device

Spammed the download mode with some wrong files. older etoken bypass, vbmeta disabled, KG disabled , eng. files, modem from other model, boot from other model, twrp recovery not sure which exactly was a successful flash and which were rejected due to checksum mismatch.

Network_Pro said:
Spammed the download mode with some wrong files. older etoken bypass, vbmeta disabled, KG disabled , eng. files, modem from other model, boot from other model, twrp recovery not sure which exactly was a successful flash and which were rejected due to checksum mismatch.
Click to expand...
Click to collapse
hayahe sorry your mobile is dead kek
MIRACLE TOOLBOX IS YOUR 1 AND ONLY SOLUTION IF YOU DONT WANT TO PAY ANYONE IVE GIVEN YOU GUIDE IN YOUR PM SO GOODLUCK KEK