Database Info

[q] samsung galaxy s3 root accidentyl updated help

I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time

Same with mine I think it's called a bricked phone and think there is nothing we can do about it, hopefully someone has a solution

Might Work?
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Click to expand...
Click to collapse
I dunno if this will work for you. But I had the same message and when I booted in Download mode I just hit Cancel then rebooted and it worked?

If you flashed cyanogenmod, that means you're bootloader is unlocked, which is a good thing.
Can you get into CWM or TWRP? I don't have a samsung so i don't know about ODIN (i presume it's like flashtools for Xperia).
For as long as your phone vibrates (or does pretty much anything when you boot it up) your phone is not hardbricked, which is also good .
Try getting into CWM, shut down your phone completely, wait 5 seconds, then do: Volume Down + Home + Power key . This will get you into bootloader state and try reflashing your old backup, a stock rom or cyanogenmod.
First time with these softbricks is always the most fun ^^. Been there done that, i thought i spend 250 euro's on a phone that was broken .
Btw. Always make a backup for these kind of situations.

Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help."...
Click to expand...
Click to collapse
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.

Ok how do i get it?
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
Ok so is do i do the same thing as i was trying to flash or something like grab a kies file( the ones that take 2+ hours to download) and then flash or get to factory reset with the 4.3 file? if so do you know where i can grab a 4.3 update file to restore? please help me if you have skype or PM me? thanks

afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
I just recently ODIN flashed the latest 4.3 stock firmware for my TMO GS3 and then attempted to roll back to 4.1.2. It didn't brick my device, but it didn't work either. I would simply fail to install. I was able to reflash, through ODIN, the 4.3 stock firmware (actually used the root66 version). Then I was able to ODIN flash CWM recovery and install Dandroid 5.1, which is also a 4.3 based ROM. All is well now. I guess I simply can't go back to any previous 4.3 ROMs now, and I'm not sure about any AOSP ROMs. I may give a try at some point to see.

Possible method to SIM unlock on MK2 *must be rooted*

UPDATED 7.14.2014
Method 1 (rooted)
The easiest way you can use RegionLockAway for those on MK2 is to do this:
I did this on the stock MK2 ROM stock.
Since no one either bothered to look in the same forum for the modem thread here is a link to the modems:
http://forum.xda-developers.com/showthread.php?t=2496517
1. Root the phone on Stock MK2.
2. Download and install Safestrap.
3. Download MF3 modem.
4. Install the modem using Safestrap from the stock rom slot (what I did)
5. Reboot the phone, go to settings, and confirm you are on the MF3 modem. (this will not affect KNOX or bootloader)
6. Run RegionLockAway 1.3
7. Shut the phone down and insert any other carrier sim and turn the phone on, or leave the sim in after installing the MF3 modem, bypass the code unlock screen and then run RegionLockAway 1.3
8. Reboot and you should see it activate your carrier.
9. You can also flash back to MK2 if you like. (optional)
I can confirm it worked and the T-Mobile sim was accepted. There was no invalid sim prompt or unlock code prompt after doing this. I even flashed back to the MK2 modem and it still stayed unlocked.
Unfortunately the person I got the phone from had reported it stolen and when it went to activate on T-mobile is threw up the MM#6 code meaning the phone can't be activated due to bad IMEI. Apparently the guy who sold it to me assured me it would work on AT&T and everything was good. I had the phone maybe 5 days and after unlocking it later found out he reported it stolen. So yes I got scammed. Luckily I only paid $100 for the AT&T GS4. However for being honest on craigslist that I had a beautiful AT&T GS4 with Bad IMEI I was able to get $250 for the phone from a guy who fixes these problems...and that's all I will say to that. So now I have a Galaxy Note 1.
For those on KitKat 4.4 NB1 Here is more info from DroidDonX
DroidDonX said:
Downgrade from NB1 to MK2, and SIM Unlock SUCESSFUL!!
I got the CSC error too, but to get around that you have to flash the (modem) by flashing the CSC tar in ODIN. You should of got in the MK2 ODIN firmware folder.
It should say this:
CSC_ATT_I337ATTEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
Click to expand...
Click to collapse
Link is at the bottom of the post!!
Method 2 (posted by muniz_ri)
Alternatively, I337 owners can flash the MDL modem via Odin to re-gain access to the hidden menu(links to signed, odin flashable modems below) then follow the guide in the OP to unlock your phone. Once completed you can re-flash the MK2 modem. I tested this process on my own stock i337 running stock MK2 and it works but follow at your own risk. Also, my knox warranty flag has been tripped for a long time so I don't know if flashing the MDL modem will trip the flag or not. Someone else can chime in on that. Cheers:
MDL Modem: https://mega.co.nz/#!wpUUXQCS!Aws3S1HWW31WUnA1s4BavFsyoNU7fBTVaEvIzcd3t6M
MK2 Modem: https://mega.co.nz/#!pwESna5I!YK7EKG37xXIG1ReB-Z-mfSMoXNkXQ9t2EdMK9ofgJKg[/QUOTE]
To finish this method go to this thread:
http://forum.xda-developers.com/showthread.php?t=2285431
*muniz_ri has stated he is not sure whether this will trip KNOX or not*
**Method 2 has been confirmed to not trip KNOX by users**
Thanks to RockRatt and deadlysin9 for letting me know it was safe to just flash modems while on MK2 rooted
My method to root the AT&T S4 was saferoot
http://forum.xda-developers.com/showthread.php?t=2565758
For those who need to downgrade from 4.4.2 to 4.3
kali323 said:
CSC_ATT_I337ATTEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar
https://mega.co.nz/#!jgRVFaAB!6DeTpHAFqjjUzw1rBimo8Ge39l6vrZ1Z1A54FJMUjvI
Remember use the CSC slot in Odin
We are downgrading everything but the bootloader when downgrading from 4.4.2 to 4.3
Click to expand...
Click to collapse
Method 3 (For those on NC1 or higher) @NewToGalaxy
Link for the files needed:
https://www.dropbox.com/s/16fu4havwvbt59c/NC1unlock.zip
NewToGalaxy said:
Try this and let me know, BTW this works on SGH-I337 S4 on 4.4.2 Kit Kat w/ stock ROM and NC1 Modem:
1. Download and install the following programs, but do not open them: Regionlock Away v1.3, towelroot v3, BusyBox Free v1.22.1 and Terminal Emulator and Safestrap v3.72. You should also obtain a MF3 modem flash .zip and place it on your internal storage "sdcard" or external storage, just remember where it is. I believe you can have any SIM card that is an unauthorized carrier in your phone at this time. That is of course if you want to unlock your SIM. I personally did not do this but my friend did it and I have read in the XDA forums that you can do this in theory if you so desire.
2. I placed all of the apps mentioned in this post into a single folder for ease of access.
3. Open towelroot and click "make it ra1n."
4. Upon completion, your device should be rooted, no reboot is necessary at this time (takes 5-10 seconds MAX).
5. Your device is now rooted, now download and install SuperSU. Open it and give any program you run from here on out access by clicking "grant" upon opening.
6. Open BusyBox Free v1.22.1 and let it run until complete, I let it complete the smart install but you can click on "install" at the bottom if you want. (don't know if this is required, I just read about it on one of the xda forums or a YouTube video out there somewhere, at any rate, I had heard that you can run it and install everything that needs to be installed and I had heard that you will obtain your overall objective of unlocking your phone. :angel: Let an expert elaborate on this one...
7. Download and install Root Checker Basic. Open it and click on "verify root." You should see some text in green that states, "Congratulations! This device has root access!" You just verified you have root :victory:
8. Open Terminal Emulator and type "su" (but no quotations "", so just type su), then press enter/return.
9. This should give Terminal Emulator root access via SuperSU. Now type "setenforce 0" (again, without "", so just setenforce 0 and press enter/return).
10. You just allowed your device to open Safestrap without automatically crashing if you didn’t complete step 9. (step 9 must be accomplished every single time you wish to open Safestrap or when ever you seek to boot into Safestrap Mode. I made it a habit to type this in every time I turn on/reboot my device. Let’s hope one of the devs can come up with something to fix this so it is automated and we don’t have to physically type this in every time) *hint* *hint*
11. Now that you opened Safestrap, click on "Install Recovery." If I remember correctly, it will require you to boot upon completion of the installation. Don't remember but if it makes you reboot though, but when you first turn on your phone it will say that Safestrap is disabled and you can either enter "recovery" or "continue." If it does reboot and you get this, just click "continue" to boot normally. At this time, complete step 9 then open Safestrap and click on "reboot to recovery."
Alternate Option 11A. For whatever reason, if you did not reboot your device after clicking "install recovery," upon completion of installing Safestrap, click on "reboot to recovery." You have to click this every time you wish to reboot into Safestrap Recovery Mode. (I could be mistaken but this is the method I use to reboot into recovery each time) Check out my name, I am new to the Galaxy scene.
12. Now that you are in Safestrap, click on "Mount."
13. Mount the storage device you put the MF3 modem on by checking "System" if it is stored on the internal memory (example sdcard\download) or "Micro SDcard" if it is saved to your external Micro SD Card.
14. Back out of that screen and go to main scree in Safestrap.
15. Click on "Install."
16. Click on the actual .zip file for the MF3 Modem Flash file mentioned previously. This will flash your modem from NC1 to MF3.
17. :victory: Congrats, you now have an MF3 Modem.
18. Go to main screen in Safestrap. Click on "Reboot," then "System."
I stopped here on my device, but what my friend did on her device, she went on to unlock her SIM in the following steps. I have not done this and I cannot confirm this, maybe someone else can. But from reading threads on XDA, this in theory should work.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Now, for the 19th step, In case you missed the first step to place your unauthorized SIM in your phone, no fear, this is the time when you absolutely have to have it If you wish to unlock your SIM. In theory you can elect to open RegionLock Away and then click on "Region Unlock." I cannot confirm this for I have NOT done this but I have read that your device will reboot or you should reboot at this time. Your device should boot up normally, aside from the screen that says Safestrap is disabled in which you must click on "Continue" to boot normally or wait 10 seconds to boot normally. You should in theory have an unlocked SIM and now have access said network once your device boots up. If it did not work, Re-read this entire 19th step and the 2nd time around you should be good to go.
I hope this worked for you. I cannot confirm anything past the 18th step but in theory it should work for you. Let me know. :cyclops::cyclops:
Click to expand...
Click to collapse
Disclaimer
I am not responsible if you brick your phone. You should have some working knowledge about your phone as well as rooting and flasing. This is not a comprehensive guide. This is a workaround for those on MK2 firmware where in none of the secret codes to access the SIM lock will work.

Did this method last night. Worked like a charm. Tested my T-Mobile sim and all is good
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

This definitely works!! Thanks

Glad I can help. I was out of options since the unlock code I paid for was a bust.I wish I knew the phone had a bad IMEI. However my experiment worked and now can help others from having to pay for an unlock on MK2.
Anyone else if it worked post here. This should be stickied lol!!

bvzxa3 said:
The easiest way yo use RegionLockAway for those on MK2 is to do this:
1. Root the phone on MK2.
2. Download and install Safestrap.
3. Download MF3 modem.
4. Install the modem using Safestrap from the stock rom slot (what I did)
5. Reboot the phone, go to settings, and confirm you are on the MF3 modem. (this will not affect KNOX or bootloader)
6. Run RegionLockAway 1.3
7. Shut the phone down and insert any other carrier sim and turn the phone on, or leave the sim in after installing the MF3 modem, bypass the code unlock screen and then run RegionLockAway 1.3
8. Reboot and you should see it activate your carrier.
9. You can also flash back to MK2 if you like. (optional)
I can confirm it worked and the T-Mobile sim was accepted. There was no invalid sim prompt or unlock code prompt after doing this. I even flashed back to the MK2 modem and it still stayed unlocked.
Unfortunately the person I got the phone from had reported it stolen and when it went to activate on T-mobile is threw up the MM#6 code meaning the phone can't be activated due to bad IMEI. Luckily I only paid $100 for the AT&T GS4. However for being honest on craigslist that I had a beautiful AT&T GS4 with Bad IMEI I was able to get $250 for the phone. So now I have a Galaxy Note 1.
Thanks to RockRatt and deadlysin9 for letting me know it was safe to just flash modems while on MK2 rooted
Click to expand...
Click to collapse
Where to get these files? I have the stock MD5 modem for MF3. It can't be flashed using SafeStrap can it? Thanks
edit: I found the RegionLockAway 1.3 ... but cannot flash the Modem files from SafeStrap. I must have the wrong file format. It errors out on me with 3.71 SS.

Would this work on i337m. I know it would be a different modem but would i be able to.

MK2 Sim Unlock
Can I get the link for MF3 modem? I would like to update it back to mk2 after unlocking. Where I can get ODIN stock MK2 firmware?

vhicke said:
Would this work on i337m. I know it would be a different modem but would i be able to.
Click to expand...
Click to collapse
I don't know about the i337M because I never had one. I can only speak for the i337 AT&T. If the current firmware you're on does not work with regionlockaway, then you may have to flash a modem that regionlockaway will work on.

TheDogman said:
Where to get these files? I have the stock MD5 modem for MF3. It can't be flashed using SafeStrap can it? Thanks
edit: I found the RegionLockAway 1.3 ... but cannot flash the Modem files from SafeStrap. I must have the wrong file format. It errors out on me with 3.71 SS.
Click to expand...
Click to collapse
what firmware are you on?
and they should be in zip format

nics04 said:
Can I get the link for MF3 modem? I would like to update it back to mk2 after unlocking. Where I can get ODIN stock MK2 firmware?
Click to expand...
Click to collapse
Go back to the first post I put up a link.
You cannot use ODIN if you are on the MK2 firmware. Just flash back to MK2 modem after you perform the unlock.

Unlock the Safestrap method
Is this a permanent unlock or a bypass to the sim lock? Will the phone still be unlocked after safestrap is removed?
---------- Post added at 05:22 AM ---------- Previous post was at 05:18 AM ----------
Is this a permanent unlock or a bypass to the sim lock? Will the phone still be unlocked after safestrap is removed?
TheDogman said:
Where to get these files? I have the stock MD5 modem for MF3. It can't be flashed using SafeStrap can it? Thanks
edit: I found the RegionLockAway 1.3 ... but cannot flash the Modem files from SafeStrap. I must have the wrong file format. It errors out on me with 3.71 SS.
Click to expand...
Click to collapse

Only1Anonymous said:
Is this a permanent unlock or a bypass to the sim lock? Will the phone still be unlocked after safestrap is removed?
---------- Post added at 05:22 AM ---------- Previous post was at 05:18 AM ----------
Is this a permanent unlock or a bypass to the sim lock? Will the phone still be unlocked after safestrap is removed?
Click to expand...
Click to collapse
Safestrap has nothing to do with the unlock. Safestrap gives you the ability to "safely" flash modems lower then MK2 on the MK2 firmware (if that is what you are on). The app that does the actual work is regionlockaway 1.3. This is a permanent unlock.

This also worked for me. Great Post!

Simple and easy, decided to finally unlock today very smooth. Thanks for the hard work

Any benefits to flashing back to mk2?

ACardAttack said:
Any benefits to flashing back to mk2?
Click to expand...
Click to collapse
I believe for some it has better download speeds. Far as I know it also connects better to wifi. You can flash modems at will rooted and on safestrap to see which one works for you

NVM, mods feel free to delete, I can't seem to

Amazing, your the man!
Worked perfectly on my i337 (ATT). I am on Tmobile now and no issues so far.
:good::good::good::good::good:
bvzxa3 said:
The easiest way yo use RegionLockAway for those on MK2 is to do this:
I did this on the stock [email protected] ROM stock.
Since no one either bothered to look in the same forum for the modem thread here is a link to the modems:
http://forum.xda-developers.com/showthread.php?t=2496517
1. Root the phone on Stock MK2.
2. Download and install Safestrap.
3. Download MF3 modem.
4. Install the modem using Safestrap from the stock rom slot (what I did)
5. Reboot the phone, go to settings, and confirm you are on the MF3 modem. (this will not affect KNOX or bootloader)
6. Run RegionLockAway 1.3
7. Shut the phone down and insert any other carrier sim and turn the phone on, or leave the sim in after installing the MF3 modem, bypass the code unlock screen and then run RegionLockAway 1.3
8. Reboot and you should see it activate your carrier.
9. You can also flash back to MK2 if you like. (optional)
I can confirm it worked and the T-Mobile sim was accepted. There was no invalid sim prompt or unlock code prompt after doing this. I even flashed back to the MK2 modem and it still stayed unlocked.
Unfortunately the person I got the phone from had reported it stolen and when it went to activate on T-mobile is threw up the MM#6 code meaning the phone can't be activated due to bad IMEI. Luckily I only paid $100 for the AT&T GS4. However for being honest on craigslist that I had a beautiful AT&T GS4 with Bad IMEI I was able to get $250 for the phone. So now I have a Galaxy Note 1.
Thanks to RockRatt and deadlysin9 for letting me know it was safe to just flash modems while on MK2 rooted
Disclaimer
I am not responsible if you brick your phone. You should have some working knowledge about your phone as well as rooting and flasing. This is not a comprehensive guide. This is a workaround for those on MK2 firmware where in none of the secret codes to access the SIM lock will work.
Click to expand...
Click to collapse

Big thanks! Worked perfectly!
If you're going to T-mobile be sure you turn on roaming and reset your APN to help data connection...I also had to go in and edit the APN and change the Bearer setting to LTE (it was on unknown on default for some reason),...at least that helped me
Any reason to keep safestrap or regionlock on my phone after doing all this?

ACardAttack said:
Big thanks! Worked perfectly!
If you're going to T-mobile be sure you turn on roaming and reset your APN to help data connection...I also had to go in and edit the APN and change the Bearer setting to LTE (it was on unknown on default for some reason),...at least that helped me
Any reason to keep safestrap or regionlock on my phone after doing all this?
Click to expand...
Click to collapse
You can delete them both if you want. When I had my S4 I sold it with safestrap installed for the future user since it's the only way to install some custom roms

[Q] Need help With soft Bricked Galaxy S3 I535 Verizon Model

Alright guys so here is the whole story with how I "Soft bricked my GS3 I535 Verizon version 4.4.2
I rooted my phone with the application "Kingo Root". It worked flawlessly my phone was rooted and i was able to install SuperSU and rootchecker and a whole bunch of other great root only apps. After I realized how great rooting was I decided I wanted to change my ROM to cyanogen since that what most people seem to prefer for a rooted phone. I downloaded an earlier version of EZ UNLOCK app to unlock the bootloader to that I could access the bootloader to flash a new ROM. After I used the EZ UNLOCK and turned off my phone to get into the recovery IT WAS HARD BRICKED . Luckily though I found this thread here: http://forum.xda-developers.com/showthread.php?t=2581166 Which worked like a charm and had my device up and running again but was dependent on the new Ext SD card to boot up. When I got to the step where I was supposed to recover the Stock bootloader onto the device it seemed to work. I input the code in the Terminal that the instructions said to do with the debrick.bin file. (My file was actually a debrick.img disck image file) But I didnt think it mattered too much. After inputing the code and waiting for it to finish the process I tried to reboot to see if it would boot off of internal memory. Now it is stuck in a boot up loop AKA soft bricked i supppose. I cannot get into recovery as it is locked because of verizon stuff still.
At this point I have backups of everything I REALLY want to keep so If I can get to factory defaults even, that would absolutely fine.
PLEASE PLEASE HELP!
I apologize for the lengthy story but I feel the more info i give the easier it is for you to help.

Hi there,
Here is some threads about soft brick S3 Verizon: Help soft brick verizon galaxy s3
Read this guide: [GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
Also, please wait until mods will move this thread to the device specific forum.
Stand by
Thanks

R_a_z_v_a_n said:
Hi there,
Here is some threads about soft brick S3 Verizon: Help soft brick verizon galaxy s3
Read this guide: [GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
Also, please wait until mods will move this thread to the device specific forum.
Stand by
Thanks
Click to expand...
Click to collapse
Thanks man I'll be on standby

[Completed] Help please? Galaxy S4 i337

Okay, so apparently I screwed up greatly last night. I was trying to flash Android L 5.0.2 on my phone and after trying to flash it onto my device (using Safestrap) it did not work for some apparently reason (no md5) ,but before, I check summed the files if the codes matched and it did. So, I tried to restore and it failed and I accidentally pressed reboot and now I can't access Safestrap and stuck in a loop of the stock recovery mode.
It was running Kitkat 4.4.4
Safestrap 3.72
Phone: Rooted
Galaxy S4 SGH-i337
sorry for bad grammar, running sleepless atm

XDA Visitor said:
Okay, so apparently I screwed up greatly last night. I was trying to flash Android L 5.0.2 on my phone and after trying to flash it onto my device (using Safestrap) it did not work for some apparently reason (no md5) ,but before, I check summed the files if the codes matched and it did. So, I tried to restore and it failed and I accidentally pressed reboot and now I can't access Safestrap and stuck in a loop of the stock recovery mode.
It was running Kitkat 4.4.4
Safestrap 3.72
Phone: Rooted
Galaxy S4 SGH-i337
sorry for bad grammar, running sleepless atm
Click to expand...
Click to collapse
Here is the Safetrap discussion thread: Official AT&T S4 Safestrap Discussion Q/A by graydiggy.
If you register on xda, you can post your question there. best place to get help IMO.
Here is a guide how to unbrick your device: [GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3 by nkhater.
Hope this works in your case.
Good luck !

Thread closed. Thank you!

Hard bricking Galaxy S7

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 .