So, I've done this before, and I've never bricked a device until now.
I tried installing a custom rom for my Galaxy S3 on Verizon, but when I restarted, it says this:
System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.
I can't get into clockwork, or any bootloader. Any attempt to do anything brings this screen up.
Now, I can get into the Odin downloader. (Power, volume down and home). But, I can't figure out how to get a Rom to load. This is where I am stuck. I have downloaded a few roms, all stock, but none of them want to be recognized. I have no idea where to go. I've been downloading stuff for 5 hrs and nothing has worked, so now Im going to the forumns. Any help is appreciated.
I have the Verizon i-535 Galaxy SIII.
You did not brick your phone you failed to unlock your bootloader. There are 2 guides in the android dev section for rooting.
http://forum.xda-developers.com/showthread.php?t=1974114
Odin back to stock and next time after rooting make sure to use EZUnlock 1.2 to unlock the bootloader BEFORE loading a ROM
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 yesterday I got this Samsung Galaxy S III that was I535 but had a I9300 4.1.2 Firmware in it. (I don't know how was it there) It had been rooted. I don't know about the bootloader if it was locked or unlocked.
I wanted to install the official firmware for i535 so I used Odin to flash I535's official 4.4.2 (downloaded from sammobile.com) and it worked fine. I then used towelroot v3 apk to root the phone and it got rooted again, then I used safestrap 3.71 to install custom recovery and that too went well.
I then flashed a zip to get Motolora Cricles widget, although that didn't install properly but my phone was still working fine until then. Then I used EZUnlock14 to unlock my bootloader and the app supposedly decraled that my bootloader was "now" unlocked, again I couldn't confirm because that's when the problem starts.
After closing that app I plugged in my phone through usb cable to my laptop and had been using it for facebook and texting. Then I turned off my phone and it never turned on back again.
When I connect it to the PC now, it is not recognized and Device manager shows QHSUSB_DLOAD device
I hope somebody can help me with that.
well, ya dun messed it up. But its fixable. For future reference, never try a bootloader unlock app, thats what messed yours up. Those apps only work on 4.2.2 bootloader phones and have caused many a headache for lots of folks. Lemme grabe you a link quick.
here ya go. this will get it fixed for ya
http://forum.xda-developers.com/showthread.php?p=68239621#post68239621
I tryed rooting this Verizon J7V. Apernetey they hate unlocked boot loaders sadly well I used obm whatever that PC flashing app is called. I flashed my rom it seemed like it rooted! Nope failed no brick though. Ah brings me back to my Wii and WiiU and 3DS and XBOX 360 modding days... and Vita too. Well rooting is hard so after doing that on the PC I booted up. I factory rested to fix Google play store error 491, but now I have this as a notification "Unothorized actions have been detected" from "securetyLogAgent" and it says "Secerity notice". It was still there after i tried factory reset. Tryed doing what it said before and after reset. No fix whatsoever, I just want to root and unlock bootloader, kingroot and most 1 click root no PC are no nos I want better battery life, no ads in games, and no bloatware. I don't like ya Verizon, you are as bad as Nintendo nowadays. That app said success but I tryed a bloatware removal app and it said "Root access not granted" something like that, my phones warntey is already up. If there's a way to to root I can try. All I need is a nand backup right to fix? I just wanna be smarter.
The phone is powered by an Exynos 7 SoC, running Android 8.
In phone's Android -> Settings -> Developer options check for OEM Unlock option is present. If not then phone's bootloader can't get unlocked, will say you can't install a Custom Recovery nor a Custom ROM.
BTW: To root a phone's Android phone's bootloader must NOT be unlocked.
Hint:
Add Samsung Galaxy J7 ( Verizon ) to this thread's title so mainly owners of such a phone get addressed.
Greetings My Brothers. I have a huge Problem. Sometimes ago I got a Samsung Galaxy S7 Verizon Model, thought it will be cool to have such a model, just come to think of it; Snapdragon 820 what else did I wanted again. And the phone started running Berserk. apps downloaded and installed from PlayStore don't work at all even WhatsApp does work properly. The phones freezes all the Time, it overheats all the time. So I made a decision. root, install custom recovery and install Custom Rom like lineage OS. I'm accustom to those stuffs like Odin, download mode, etc. I don't have any problem with a phone stock on boot loop, it's something I have been fixing, so I'm Used to It. My SM-G930V security level is High with its latest android version Oreo, the bootloader is locked. tried to unlock it with ADB and Command Prompt. It was a failure. tried to get some help On YouTube. Failed, all the videos I watched was about SM-G930F none of them talked about SM-G930V, I came across SM-G930V bootloader Unlocking, rooting and custom Rom but, it wasn't compatible with my SM-G930V. So let Me ask You Guys this question. Can I really unlock the bootloader, root the phone and Install a custom recovery, and A custom Rom??? If there is a slight chance or possibility of doing so, please Brothers help me out, because I am unable to use the phone to its full potential. Thanks. Michael.