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 .
So i think i have completely ****ed up, hopefully you guys can give me some insight
I was on the process of properly rooting a samsung s7 that i got since the root checker said that it was not properly root.
i decide to fallow this guide
https://forum.xda-developers.com/ve...ot-guide-verizon-s7-s7-edge-sm-g930v-t3411015
But i after flashing the ENG using Odin
the phone just keep restarting, over and over, it also does the samething in recovery mode.
Notes:
The phone was displaying Custom unlock login screen (Before Flash)
Also it was 6.0.1 update
and I got the the 7.0 update, to flash the ENG
If there is anything you guys can advice, ill appreciate.
If it can go in downloading mode you can flash stock firmware and try rooting again.
What I have:
I have a Samsung Galaxy S7 SM-G930W8 device. It has been rooted and unrooted previously, as well as flashed with official samsung stock ROM. I also have just performed a factory reset from recovery mode recently.
What I am trying to do:
I am trying to root it properly and flash LineageOS on it. I am aware as to how to do this based on the guides here, but I run into a problem early on...
Problem:
I cannot seem to enable OEM unlock. It automatically disables right after I try to enable it.
Other potential problem:
When I try reboot to bootloader via adb command ".\adb reboot bootloader", it just restarts my device normally
Question:
If I can connect my device to Odin and attempt to flash LineageOS do I risk bricking my device given it's current circumstance? Or is this all I can try now?
I'll provide any additional information/images if needed. I just feel like I am repeating the same troubleshooting over and over again without any progress.
Thanks
Just ended up doing it assuming that it was unlocked (felt quite risky wiping everything and installing old zips)... Everything seems relatively functional and rooted. I'm a little uncertain whether or not I should update magisk as I don't feel like creating a new problem on it for myself just yet.
It may be not easy for some users. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Flashing Instructions
Make sure the bootloader unlocked
Enter Download Mode
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing twrp-3.5.2_10-0-a52q.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key until red warning "This phone is not running Samsung's official software..." disappears. Then release all keys. It will take more time than usual until TWRP recovery appears.
Install Kakarot-UNI-1-A52-2021-05-13-23-11.zip
Install Disable_Dm-Verity_ForceEncrypt_20210320.zip
Install Magisk-v23.0.zip, Swipe to confirm Flash ( Ignore this if you don't want to root it )
Format data
Select Reboot to System
Setup the phone
Done!
Rooting
Connect Phone to Internet
Install Magisk and Open it. Magisk will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done
Recommended to Watch This Video!
Download and Terms
The phone bootloader must be unlocked, if not read How to unlock bootloader Galaxy A52
Download TWRP twrp-3.5.2_10-0-a52q.tar
Download Disable_Dm-Verity_ForceEncrypt_20210320.zip
Download Kakarot-UNI-1-A52-2021-05-13-23-11.zipsafetynet-fix-v1.1.1.zip
Download Magisk-v23.0.apk stable Rename to Magisk-v23.0.zip
Credits to:@RealVelosh for TWRP 3.5.2
@neel0210 for Kakarot Kernel
Thanks a lot, this is what I was looking for an updated guide on how to root these great phones! Will this work with the July 1 security patch update?
kidkree1 said:
Thanks a lot, this is what I was looking for an updated guide on how to root these great phones! Will this work with the July 1 security patch update?
Click to expand...
Click to collapse
Yes, it works
So I have been looking into rooting as well. And dozens of threads are mistakenly assuming OEM unlock is an available option under Developer Options on this phone. It's not there. So anything after that is not going to happen. I am referring to the A52 5G US version with the 750c Snapdragon chipset.
The only supported option is paying ransom for a 3rd party unlock as far as I can tell.
Anyone tried this version on A52 5G version? Simply cant find any root methods for my device.
Faakarna said:
Anyone tried this version on A52 5G version? Simply cant find any root methods for my device.
Click to expand...
Click to collapse
This method should work, unless you have the U.S. variant in which case you won't be able to use any method until you unlock the bootloader (paid services afaik)
So ive been rooted for a few weeks now and was successfully passing safetynet. But now out of nowhere CTS started failing, i cant pass it anymore even without magisk. Anyone having the same issue?
Simon1511 said:
So ive been rooted for a few weeks now and was successfully passing safetynet. But now out of nowhere CTS started failing, i cant pass it anymore even without magisk. Anyone having the same issue?
Click to expand...
Click to collapse
Yes, a few people are having this issue. Seems that Google pushed something out that detects current known bypass methods.
ShaDisNX255 said:
Yes, a few people are having this issue. Seems that Google pushed something out that detects current known bypass methods.
Click to expand...
Click to collapse
Urg. Is there a fix for that? Or do i need to re-lock my bootloader (since it still fails even without magisk)
Simon1511 said:
Urg. Is there a fix for that? Or do i need to re-lock my bootloader (since it still fails even without magisk)
Click to expand...
Click to collapse
Well this is quite new as in it started to fail today (for me) so I think people are scrambling right now to get a fix. I haven't read anyone that has fixed it yet.
ShaDisNX255 said:
Well this is quite new as in it started to fail today (for me) so I think people are scrambling right now to get a fix. I haven't read anyone that has fixed it yet.
Click to expand...
Click to collapse
Ok, thanks. Was just curious if relocking BL could fix it
Magisk Hide has been removed from the main server, so it won't pass CTS now. There is a fix, please search!
Hi! I did everything according to instructions, but I don't get past step 5.
After pressing and holding Volume Down + Power Key, when the screen went blank I quickly pressed and held Volume Up + Power key, got the Red Warning, but instead of going away it stayed and I got a few lines with green background:
RPMB fuse set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x00C)
FRP LOCK: OFF
OEM LOCK: ON (U)
KG STATUS: CHECKING
WARRANTY VOID: 0x1 (0x30C)
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B1(1,1,1,1,1,1) K1 S1
SECURE DOWNLOAD: ENABLE
HDM STATUS: NONE
DID: [16 digits]
That's it. Never went further.
HELP PLEASE! Thanks!
P.S. - I've made sure the bootloader is unlocked.
FlugHund said:
Hi! I did everything according to instructions, but I don't get past step 5.
After pressing and holding Volume Down + Power Key, when the screen went blank I quickly pressed and held Volume Up + Power key, got the Red Warning, but instead of going away it stayed and I got a few lines with green background:
RPMB fuse set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x00C)
FRP LOCK: OFF
OEM LOCK: ON (U)
KG STATUS: CHECKING
WARRANTY VOID: 0x1 (0x30C)
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B1(1,1,1,1,1,1) K1 S1
SECURE DOWNLOAD: ENABLE
HDM STATUS: NONE
DID: [16 digits]
That's it. Never went further.
HELP PLEASE! Thanks!
P.S. - I've made sure the bootloader is unlocked.
Click to expand...
Click to collapse
Did you figure out how to fix this?? I have the same issue!
Hello guys, so I was rooting my phone and I had just ended loading the "A52_MagiskPatched_AndroidHowTo.tar" AP thing via Odin. Instead of taking me to the recovery and is stuck at this screen.View attachment 5474237
I can still load into the download screen, but that's all.
If any one has any solutions please reply, I am sure I did all the steps, but now I'm doubting myself is there a way to revert it or something?
If someone can help me I promise to give a small compensation!
Discord: Non Sense Speaks#4580
DID YOU FIND SOLUTION TO THIS? I HAVE SAME LOGO ISSUE AND WANT TO REMOVE BOOTLADER UNLOCKED RED ALERT
I have samsung sm-a525f android 12 OUI 4.0 security patch 1 dec 2021, i've read this tutors n find that if we want to root the device we must install TWRP before rooting it. Now, i have a question, why must we install the custom recovery before doing that root session? Why cant we just flashing the root files using the stock recovery ? thank you.
frenxl said:
I have samsung sm-a525f android 12 OUI 4.0 security patch 1 dec 2021, i've read this tutors n find that if we want to root the device we must install TWRP before rooting it. Now, i have a question, why must we install the custom recovery before doing that root session? Why cant we just flashing the root files using the stock recovery ? thank you.
Click to expand...
Click to collapse
Because you can't flash root files using stock recovery, they're unofficial files.
Hi! I have a new Samsung Galaxy A52 (SM-A525M variant, Latin America). Anyone tried this method on the "M" variant yet? I've already unlocked the bootloader successfully.
More data:
A525MUBU4AUJ3
nov. 2021 security update
I can debloat it with ADB, but I love root.
Thanks in advance to this great community!
EDIT: I want to thank explicitly ShaDisNX255 for the guide and help in succesfully rooting my phone!
Hi. I accidently updated my J3 to android 9 and since then, the phone works like my old Samsung S4 mini. Everything is lagging, in short phone is just unusable. I know that trying to downgrade via odin you get anti rollback protection because of the bootloader so is there any other way how to downgrade it to older version? I don't care if it's easy or hard way, i just want to make this phone usable. Maybe flashing older rom with keeping new bootloader? I heard someone did that once to A7 2018 but never published this rom.
I downgraded my SM-J330F (with unlocked bootloader) from Pie (9) to Nougat (7) using Odin.
To unlock the bootloader on a J3 is very easy. Go to Developer Options and activate OEM unlocking. That's it.
If it's somehow missing, use this:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
You can find a how-to here:
Unlock Bootloader on Samsung Galaxy J3 2018? OEM Unlock!
Hey, there in this guide, I will show you the easiest method to Unlock Bootloader on Samsung Galaxy J3 2018. This smartphone was recently launched, and in
www.rootingsteps.com
my thread may help you
[A320FL] Downgrade Android 8 to 6.0.1
So i just succeded in downgrading my A3 by flashing boot.img and system.img through OrangeFox recovery, theres not much more to it(and magic probably). The phone initially didn't boot and just bootlooped not even showing the boot animation only...
forum.xda-developers.com