Related
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
NeoDJW said:
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
Click to expand...
Click to collapse
It's not possible since I bought it second hand.
Even if I had a warranty, in my country (Serbia) warranty for smartphones doesn't mean much, I think I could write PhD thesis easier than to make seller replace/fix smartphone with warranty
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Erik1805 said:
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Click to expand...
Click to collapse
Thanks but this will not fix my problem.
Have you tried this: http://pangu.in/frp.error.html
Bright.Light said:
Have you tried this: http://pangu.in/frp.error.html
Click to expand...
Click to collapse
No I didn't but the fact is it will not work.
There is currently no way to fix that. The only way would be to unlock FRP by some box, but it isn't released yet.
What I am asking here is true that Galaxy S7 could be hard bricked that easy? By steps I wrote in my first post.
My questions are partially answered in this article
But I still don't understand what's the problem with dm-variety if I flashed stock rom?
Is there are any other parts of the NAND that are not original/signed and that's why dm-verity fails?
If that's the case can they be backed up then reflashed with the Odin if I get into same problem with new phone?
Thanks
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
harshang2007 said:
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
Click to expand...
Click to collapse
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
mss1988 said:
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
Click to expand...
Click to collapse
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
harshang2007 said:
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
Click to expand...
Click to collapse
I don't have the phone anymore to confirm or to deny this. But the whole procedure in Kies and Smart Switch is the same. There are other people with the same problem too in this thread too, and they still didn't found the way to unbrick their devices.
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
I went through this procedure: http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 which gives a link to downloading the factory binary (of either version). It reinstated my IMEI which had been turned to a string of zeroes. I will say that when you reboot after flashing the factory binary it's pretty different looking so be prepared for that. I then went to Sammobile and downloaded the appropriate stock ROM for my s7 and flashed that with Odin. I flashed TWRP, formatted internal data when given the opportunity, flashed the no-verity-opt-encrypt.zip, and I was able to use my s7 again. At any rate, you might follow the guide at the link I gave you and see if it helps. As always, no guarantee is given or implied. It's just what I did.
Thanks man, but I can't flash the Factory binary, my FRP is unfortunately ON.
E pa brate nemoj se više onda igrati sa telefonom, nije to za svakoga,...
Mod Edit: Please post in English only:
Well, the brothers do not come then play with the phone, it's not for everyone
now phone detect usb ? i mean adb devices
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
wild guess....
Install dm-verity and force encryption disabler
Wipe Cache
install custom kernel
chandarakk said:
now phone detect usb ? i mean adb devices
Click to expand...
Click to collapse
There's no adb/fastboot access from Samsung recovery or Samsung download mode, as far as I know.
Just get your phone into downloadmode and then flash the stock firmware witch you can find on sammobile. I got also this problem, and then everything will be fine ?
did you try use Kies or Smart swticher to factory restore the phone ?
because as far as i know , even FRP is on , you can still flash stock firmware.
and , try local shop to find any place have z3x box or Octopus box .
I recently buy Samsung Galaxy J7 (2015) from a untrusted source, and when i wipe data, it need to enter the google account, i don't have the account, i've try all solutions on the internet but it don't help me, because OTG cable and SideSync solution are blocked on the new 5.1+ firmware, and i have to install the old 5.1 firmware but my phone is on 6.0, when install the old 5.1 firmware using odin and it said failed and stopped at cm.bin, i read on some forum, blog that because of the update has block downgrade, please help!
flash Custom recovery and stock flasheable man
so fine
seven4grindBR said:
so fine
Click to expand...
Click to collapse
Use Odin ?
Im new to android
p/s: Samsung don't have .zip stock rom, or if it have, please give me the link
~not really good at English
dangquoctrung123 said:
I recently buy Samsung Galaxy J7 (2015) from a untrusted source, and when i wipe data, it need to enter the google account, i don't have the account, i've try all solutions on the internet but it don't me, because OTG cable and SideSync solution are blocked on the new 5.1+ firmware, and i have to install the old 5.1 firmware but my phone is on 6.0, when install the old 5.1 firmware using odin and it said failed and stopped at cm.bin, i read on some , blog that because of the update has block downgrade, please !
Click to expand...
Click to collapse
Brother I have same problem, when I try to install Twrp by Odin it says FRP lock, but I fix this by simply formate mobile without setup google account then I am able to Install TWRP on it.
After that I flash 5.1(Lollipop) by TWRP.
It install successfully but when I sign in again in my google account from my device it gonna turned off.
And when I tried to turn on only model no is display (Not samsung logo) and at the top of the screen there is something like- "custom frp lock" display.
TWRP also not open, I already try some methods but Not working.
Please help me how to fix it?
I'm using J700F/DD I'm not able to bypass FRP lock. Using 6.0.1/MMB29K/J700FXXU2BPH4
I'm using J700F/DD I'm not able to bypass FRP lock. Using 6.0.1/MMB29K/J700FXXU2BPH4
I tried to root my 12 months old phone, it was not rooted correctly.
I tried to follow this http://forum.xda-developers.com/galaxy-j7/themes/how-to-root-twrp-install-xposed-t3328580
After this my phone working normal for 2 days, I dont want proceed further. But after a restart, its started to flash error "custom binary blocked by frp lock"
So I tried to upload the original samsung binary.
I tried to download & install J700FXXU2BPH4_J700FODD2BPH2_INS.zip from sammobile.com but unfortunately I cant unzip as it seems corrupted file.
I tired previous version J700FXXU1AOL2_J700FODD1AOL1_INS_(by_firmwarefile.com).zip too.
Anyone please point me to the correct direction.
thanks
J700FXXU1AOL2_J700FODD1AOL1_INS_(by_firmwarefile.com).zip (896M)
So simple. Just installed kies and installed the firmware. Wasted 6 hours
Hello..
I buyed a n915fy in bootloop from ebay...after flashing android 6.0.1 with odin the phone starts
But has Samsung reactivation lock..the seller says he cant remember and doesnt have any samsung account..well i have the original o2 invoice from him so its not stolen.
Can anybody help me to remove the reactivation lock?
I already contacted Samsung but they said i should contact the guy who sold it so i cant do anything now..:crying:
dante2903 said:
Hello..
I buyed a n915fy in bootloop from ebay...after flashing android 6.0.1 with odin the phone starts
But has Samsung reactivation lock..the seller says he cant remember and doesnt have any samsung account..well i have the original o2 invoice from him so its not stolen.
Can anybody help me to remove the reactivation lock?
I already contacted Samsung but they said i should contact the guy who sold it so i cant do anything now..:crying:
Click to expand...
Click to collapse
Google Samsung reactivation lock bypass...
joke19 said:
Google Samsung reactivation lock bypass...
Click to expand...
Click to collapse
well lol i did that..
but things like talkback ..doesnt work ..sidesync wont connect..so on.. so pls someone help..
Can someone please help me..
im trying another way where i did flash a combination file ....
should be done like :Enable ADB Mode and Activate USB Debug
After Done above Steps Download Following Files
com.sec.android.app.samsungapps_4.2.19.3-421903120_minAPI14 ( nodpi )_apkmirror.com.apk
Samsung service.apk
Move Those Files into Minimal ADB and Fastboot Folder
Install com.sec.android.app.samsungapps by Using ADB Commands
Then, Install Samsung service.apk using ADB Commands
NOW, Find the Samsung Account on the Screen – Activate Wi-Fi
so but if i try to install via adb it says:invalid apk file.. what am i do wrong?
pls help!!!
How about flashing a room from this forum, like mickey room and root it, perhaps will get reed of that pre installed software, I'm just guessing that.
Hello everyone
Here is new method to root all Samsung devices,twrp not needed.
First you need to download EFTSU tool: https://mega.nz/file/34lDEBqB#7mSv2SeYKP2kReheBk7q5AU582TZUdsJy6GL5sd7O-I
Then you need file from this website where you can find for your device and download it : https://eftsu.com/
After you downloaded this file put your samsung device in download mode *need oem unlock* then flash your file with eftsu tool.
Your device will reboot it and it will during boot ask to reset ,then reset it.
When it comes to system you need to download and install eftsu manager: https://mega.nz/file/Oo1yCSiQ#rWlMbcBiBHSzv5oMioyGxQZ0ynxqaeqz_Nfm4ze240c
And you are done.
You can also install root checker to see if it rooted.
jasmin811 said:
root all Samsung devices
...
*need oem unlock*
Click to expand...
Click to collapse
US/CA Sammys: hmmm...
The rest are rather easy to root with Magisk anyway.
AndyYan said:
US/CA Sammys: hmmm...
The rest are rather easy to root with Magisk anyway.
Click to expand...
Click to collapse
There is more supported devices besides samsung that will work just look at the website above eftsu.com
If there is no device model supported in the list,just tell me an will add it.
if you need any help with it,I can help you.
What I'm looking for is twrp working for M105G,because with M105F is also working but during boot it ask for password,even if i format data in twrp.
I have note10 plus SM-N975U Snap dragon that has the OEM toggle missing and tried everything to make it appear but no luck and without that i can't install anything or unlock the bootloader......Any tools or ideas to overcome my situation?
if no oem in developer option than you have to wait for 7 days .
Hello! I want to root my Samsung Galaxy A01 with firmware A015MUBS3ATL8, I found all the files that I should download, but no way to unlock the bootloader, I did all the guides and when it asks me for confirmation on the bootloader screen to unlock it, I affirm and the phone is formatted and it reboots, but when re-entering the bootloader it is still blocked
Sorry for my bad English, I'm using Google Translate
Please help.
My phone is SM-G955F with Exynos processor. Hungarian XEH code. The latest PIE is running on it. OEM does not allow unlocking. The slider can be turned on, but it also turns off immediately after enabling. What can I do to make OEM resolution work?
Thank you.
jasmin811 said:
Hello everyone
Here is new method to root all Samsung devices,twrp not needed.
First you need to download EFTSU tool: https://mega.nz/file/34lDEBqB#7mSv2SeYKP2kReheBk7q5AU582TZUdsJy6GL5sd7O-I
Then you need file from this website where you can find for your device and download it : https://eftsu.com/
After you downloaded this file put your samsung device in download mode *need oem unlock* then flash your file with eftsu tool.
Your device will reboot it and it will during boot ask to reset ,then reset it.
When it comes to system you need to download and install eftsu manager: https://mega.nz/file/Oo1yCSiQ#rWlMbcBiBHSzv5oMioyGxQZ0ynxqaeqz_Nfm4ze240c
And you are done.
You can also install root checker to see if it rooted.
Click to expand...
Click to collapse
Hi
Samsung Galaxy Note 10+ not supported?
OEM unlock still doesn't work.
bautigarzabal said:
Hello! I want to root my Samsung Galaxy A01 with firmware A015MUBS3ATL8, I found all the files that I should download, but no way to unlock the bootloader, I did all the guides and when it asks me for confirmation on the bootloader screen to unlock it, I affirm and the phone is formatted and it reboots, but when re-entering the bootloader it is still blocked
Sorry for my bad English, I'm using Google Translate
Click to expand...
Click to collapse
you need to ulock developer option in setting-about phone-build info and tap 7 times in it.
Ptreki said:
OEM unlock still doesn't work.
Click to expand...
Click to collapse
activate also usb debbuging
fazi78 said:
Hi
Samsung Galaxy Note 10+ not supported?
Click to expand...
Click to collapse
check if there is file for you model in website
jasmin811 said:
usb debbuging-ot
Nem, nem, nem, nem, nem
I activated it too, but nothing happens.
Click to expand...
Click to collapse
I have a samsung galaxy j4 +
I got it from a friend today.
The phone is after a hard reset (some dumbass did it)
Unfortunately, there is no access to google accounts because the accounts were from her husband and he died.
I keep searching and trying but can't root. Because Debug Usb doesn't go on.
And the computer doesn't read the phone after all.
Yes, I have drivers installed, various Odins, I also took your EFTSU, Fastboot and I do not read my phone anywhere. Nothing else is just loading.
Yup i trying Hard reset many many times...
Jerry3Tears said:
I have a samsung galaxy j4 +
I got it from a friend today.
The phone is after a hard reset (some dumbass did it)
Unfortunately, there is no access to google accounts because the accounts were from her husband and he died.
I keep searching and trying but can't root. Because Debug Usb doesn't go on.
And the computer doesn't read the phone after all.
Yes, I have drivers installed, various Odins, I also took your EFTSU, Fastboot and I do not read my phone anywhere. Nothing else is just loading.
Yup i trying Hard reset many many times...
Click to expand...
Click to collapse
try to frp unlock your phone,you have here on xda tuts how to do it,just search for it.
what do you mean nothing happened?
I can't unlock the OEM with either method.
did you follow the guide i wrote above?
First you need file downloaded from the website and with the eftsu tool flash it in download mode,the when phone is reseted and comes in system install eftsu manager and root checker and in root checker you have to see if it's rooted or not.