Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
chewtoy0 said:
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
Click to expand...
Click to collapse
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
mrd0pe said:
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
Click to expand...
Click to collapse
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
chewtoy0 said:
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
Click to expand...
Click to collapse
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Your S/N is on the rear of the phone it can be a pain to see but it is there. Use smart switch to restore the firmware. Just click emergency firmware restore.
It is? The IMEI is there but I didn't see the SN. Also my phone is black so that doesn't help.
I will have another look.
mrd0pe said:
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Click to expand...
Click to collapse
I did that. No dice.
I had the same issue as you. Used the same rom and disabled developer options. I downloaded stock firmware.. flashed it with odin. It actually took 2 tries. The first time I could see only 1/4 of the screen. The second time i flashed stock firmware from another country and it worked. You might actually have to do a hard factory reset if you cant unlock your phone.. for some reason. Then I let kies do its magic because I could then see my S/N. Right now I still feel my phone slightly different. Messenger is unstable for some reason also.
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
chewtoy0 said:
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
Click to expand...
Click to collapse
Try to flash Nougat firmware, as that was what your custom rom was on right? I dont think it really matters though as I downgraded from stock 7.0 to stock 6.0.1 via odin without errors... But you can try
As an absolute last resort I would try to check the "re-partition"-tab and provide odin with a .pit file, then load everything (BL, AP, CP...) with stock firmware <<<< do this at your own risk, if you are not careful, your phone will be bricked
I am trying to flash MM back to it .
I'm not sure I want to mess with the re partition table...But it's already soft bricked.
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Matty39856 said:
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Click to expand...
Click to collapse
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
chewtoy0 said:
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
Click to expand...
Click to collapse
I'm not sure then. Have you tried flashing the latest unlocked version for your region? I remember on my s6 I had a similar problem that was caused because I was trying to flash a lower version of Android than what I previously had. So ended up flashing the latest unlocked version BTU for my region and it worked. Sorry I can't be of more help. It looks like the latest firmware is still 6.0.1 that's why it's blocking it from downgrading.
Was sent a PM by a person. Was skeptical at first, but in 10 minutes using TeamViewer, they fixed the issue by reflashing the device (as well as repartitioning it properly). I can't thank them enough.
This is the person on Facebook...
Unlock Network FRP Lock Remote Service
Related
Can anyone help? I spent a big chunk of my hard earned money on a refurbed S6 for my daughter, she's had it about a week (she's Pokemon mad btw). The latest update for Pokemon Go came out and now she's blocked from the game as it appears the phone has been rooted. If I'd known, I wouldn't have bought it. Anyway, for the last 2 days my partner and I have been trying to unroot it. We've used various versions of Odin to no avail. I had a lot of trouble finding the right firmware because it looks like the phone was Polish according to the version and CSC numbers, and tbh I'm still not sure if we're trying the right one. Software is 5.1.1. right now. I've tried installing SuperSU but it won't run, it just crashes the phone and forces a reboot. We've tried manually unrooting with a file manager but the su files we need to delete reappear seconds after they're deleted. I'm at the end of my tether, does anyone have any ideas?
You won't be able to unroot it until you flash stock firmware. I don't know if the game checks the knox status.
Give this a go
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Enjoy
Unforunately my partner spent almost all night trying to flash the firmware. According to him it 'nearly' worked, however, I now have a phone stuck in a boot loop. :crying:
Run emergency recovery on Smart switch
ccalixtro said:
Run emergency recovery on Smart switch
Click to expand...
Click to collapse
Do I need to have smart switch installed on the phone for this to work?
amber_1978 said:
Do I need to have smart switch installed on the phone for this to work?
Click to expand...
Click to collapse
No, run it on your pc.
Thanks, I'll give it a go after work.
ccalixtro said:
No, run it on your pc.
Click to expand...
Click to collapse
Smart switch won't work, says it doesn't recognise the device
I think I would give original firmware of your country and odin a try. One of possible ways is to download all needed files from the site of sammobile.
For me this way works every time when I stuck in boot loop. Odin functionates when you are in download mode. Switch off your s6, then start by pressing home-, powerbutton and Volume down at the same time.
Then start Odin on PC, then connect USB and so on.
Greetz JG
amber_1978 said:
Smart switch won't work, says it doesn't recognise the device
Click to expand...
Click to collapse
When you select emergency recovery theres an option where you have to write the device model and the serial number
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
fahad999 said:
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately I've tried Kies already and I can't get it to work at all. I get a message telling me my device is not compatible and the whole thing just stops. I'll give it another go though, no harm in trying. Thanks
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
socal87 said:
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
Click to expand...
Click to collapse
Really? Did you do the latest update in the game and it still worked ok? This phone has definitley not been used for location spoofing by us and I'm pretty sure there were no apps of that nature on the phone. I downloaded a root checker when everything went wrong the other day, it said the phone was rooted. I'm totally at a loss tbh. Right now it's still in a boot loop. Trying to flash it with Odin as we speak.
Just an update. Tried Smart Switch. Tried the model and serial numbers on the back of the phone case, these weren't recognised so I went to the recovery screen and hit the home button and got a completely different set of numbers. Different IMEI, model number, you name it. I'm assuming this is why Odin won't work, I'm looking for the wrong firmware? I obviously have Frankenstein's phone. No idea what to do now.
Best thing to do is to flash TWRPP and try to flash a custom stock rom through the TWRP recovery which does not have root installed..... If that doesn't work try to find a generic stock firmware for Odin, meaning a firmware that can run in any country..... If all else fails update it to 6.0.1 stock firmware. Try the closest firmwares to your location.
And if you do manage to get to the Samsung logo let the phone sit there for a good 10 minutes even if it reboots....
When I bricked my Samsung I used masiks custom 6.0.1 rom based on stock, but had all the links to bootloaders cscs radios and what not so giv that a shot if you can find it.
---------- Post added at 12:08 AM ---------- Previous post was at 12:05 AM ----------
Link to rom that helped me http://forum.xda-developers.com/galaxy-s6/development/masik-marshmallow-1-0-jan-20-2016-t3297961
do you have lucky patcher playstore installed ?
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^
Hey all,
I tried rooting my Galaxy S7 today with Odin 3.11.1 and I thought it all went fine, it said it passed and that it was successful. However when it starts to boot it gets no further than the boot screen which says "Samsung Galaxy S7" and then "Powered by Android" at the bottom. There isn't an unlocked padlock on the screen either which I thought there was meant to be. Any help would be much appreciated and at this point I am more than happy to just go back to stock firmware and forget rooting even exists.
SM-G930F
G930FXXU1DQD7
You can flash stock from updato.com and ODIN 3.12.3 or newer
*Detection* said:
You can flash stock from updato.com and ODIN 3.12.3 or newer
Click to expand...
Click to collapse
Is that guaranteed to fix my problem then and bring it back to stock?
Lethal_Trousers said:
Is that guaranteed to fix my problem then and bring it back to stock?
Click to expand...
Click to collapse
Nothing is a guarantee when you flash devices with custom stuff and break them
But flashing stock is guaranteed to take you back to stock obviously, so long as it flashes successfully (It will not reverse KNOX 0x1 though, good chance you've tripped KNOX already)
Seems you have reservations about flashing stock, but quite happy to try rooting the phone using an outdated ODIN?
Try downloading a stock firmware from sammobile (make sure to find the right model and android version), extract it and then flash it with odin (assuming that you can still enter download mode). File is quite large to download, but Internet Download Manager (IDM) could speed up the process by 4-5 times. As for rooting, I have an S7 myself and I managed to successfully root it using Odin and chainfire's auto root file. However, I was also stuck in your situation the first time I tried and had to factory reset before trying again. Can't remember the cause though.
The easiest way is using samsung smart-switch.
There is a menue "emergency-recovery" or similar.
Follow the instructions and it will automatically download the actual firmware and flash it.
Good luck
Hey guys, I really screwed up big time with my S7. My model is the SM-G930F. I have numbered my mistakes below so it is easier to follow.
1) I wanted to root my phone, so I followed the guide for HighonAndroid on youtube.
2) Fast forward, got TWRP and flashed Magisk root v16 and samsung anti-root removal 2.4.
3) Restarted phone and got this message along the lines of "integrity of phone has been damaged... please factory reset"
4) I advanced factory reset, and also accidentally ticked the software reset as well :crying:
5) Phone is bricked, and stuck in bootloading error. Cannot be turned off, it would just continue to recycle the Samsung S7 screen on repeat until put into TWRP mode...
6) Can only assess download mode and TWRP mode
If you are still following, this is where I am stuck ATM. I just want a working phone at this point...
7) Download official 7.0 nougat software for my phone model.
8) Odin the firmware over however the message stays stuck at this: https://imgur.com/a/UMQPw
9) Cry
If anybody can help that will be great, thanks!
Looks like Odin is not signing a com port to the phone.
Drivers are installed? Tried different usb cables and usb ports?
audit13 said:
Looks like Odin is not signing a com port to the phone.
Drivers are installed? Tried different usb cables and usb ports?
Click to expand...
Click to collapse
The phone stays connected, but the second I flash my phone just reboots.
You're not flashing BL, CP, and CSC?
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Beanvee7 said:
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Click to expand...
Click to collapse
Yes I got the file from sammobile. I have tried flashing the 4 files however alas, it again just reboots my phone. I will follow up with an image when I get home and try it out again.
Beanvee7 said:
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Click to expand...
Click to collapse
Yeah here we go: https://imgur.com/a/FF0Rd
Still does not work. It continues to reboot. Tried different computers the phone will just reboot. Is there any hope left? I can access TWRP, meaning is it possible to restore/flash a backup from another user?
You can try Smart Switch which is the official method of a factory flash.
Otherwise for Odin if I recall correctly the latest firmware will chuck a fit if you aren't flashing the right firmware for your country, since the DRAG bootloader is meant to be more locked down.
You could also try different Odin versions maybe https://forum.xda-developers.com/showthread.php?t=2711451
You could try a stock ROM flash via zip like super stock or superman choosing clean install. Would be easier than trying to orchestrate a backup from someone.
Is there any errors that I have now seem consistent with anybody else's issue? Something like I might be flashing the wrong firmware into my phone, as a result the phone just reboots in download mode?
I have tried using both the new and old versions of odin and it still has the same result.
I am using the phone model SM-G930FZDAXSG
Really thanks a lot guys. Just having you guys readily available took a lot of stress off my chest. Someone cares
The issue has just been resolved! Yey. The problem was not running odin in administrator mode. As a result, my phone would just reboot instantaneously after flashing.
Good day everyone. I am totally new to this and on here but hope is something I came with and will always be a part of my beliefs.. I did flash my Samsung S7 SM-G930F a couple of times with different kind of custom ROMS and I guess I upgraded the bootloader by doing so... So now I was in TWRP mode and without thinking, I started to change the DATA format and immediately switched it off when I realized what exactly I'm doing and now it's stuck. It can switch on only with a charger and by force but I am capable of getting into download mode. I am trying to flash a stock ROM but it keeps on failing cause of the bootloader. When I use the PIT file, it shows successful though. But nothing more happens. Any help would be appreciated. Thank you in advance.
Andre369 said:
Good day everyone. I am totally new to this and on here but hope is something I came with and will always be a part of my beliefs.. I did flash my Samsung S7 SM-G930F a couple of times with different kind of custom ROMS and I guess I upgraded the bootloader by doing so... So now I was in TWRP mode and without thinking, I started to change the DATA format and immediately switched it off when I realized what exactly I'm doing and now it's stuck. It can switch on only with a charger and by force but I am capable of getting into download mode. I am trying to flash a stock ROM but it keeps on failing cause of the bootloader. When I use the PIT file, it shows successful though. But nothing more happens. Any help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
I don't own an S7 so maybe not much help.
From screen shot above try using Odin version 3.13.1 or higher.
Can you post a screen shot of download mode and Odin when it fails
If you can still get into download mode there should be a line saying AP SWREV: B:? K:? S:? or something similar.
The B:? is your bootloader version number. You will need to flash firmware with this number or higher.
spawnlives said:
I don't own an S7 so maybe not much help.
From screen shot above try using Odin version 3.13.1 or higher.
Can you post a screen shot of download mode and Odin when it fails
If you can still get into download mode there should be a line saying AP SWREV: B:? K:? S:? or something similar.
The B:? is your bootloader version number. You will need to flash firmware with this number or higher.
Click to expand...
Click to collapse
Thank you for the response I managed to get it fixed. I used odin 3.14 instead and I wiped it with the NAND option and started from scratch. I used the pit file and flushed the bootloader first with repartition, then did the AP separete, and thats how I went on. After all, I'm back again. Thank you for trying, much appreciated.