S7 Stuck on "Erasing" After failed ODIN - AT&T Samsung Galaxy S7 Edge Questions & Answers

Today I was trying to revert back to stock firmware and flashed the files in this thread:
https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-stock-sm-g930a-ph1-odin-files-t3458890
The flash failed, on the phone it game an eMMC error that says:
SW REV CHECK FAIL : [about]Fused 4 > Binary 2
[1] eMMC write fail: ABOUT
No other flashes were working after that even other stock images I tried. I held down the power button and I am now stuck with a blue android "erasing" screen that pops up every few seconds followed by some commands that go by too fast to see.
Is my phone dead? is there anything I can do?
EDIT: Wasn't going into boot loader properly and was able to flash new firmware

Related

Galaxy Note 4 flashing issue

HI XDA,
I am using Galaxy Note 4 (SM-N910G)
1st STAGE
Suddenly in my phone's recovery menu says "drk verification failed",
If i install firmware vis Kies or ODIN it says"write flash memory failed"
2nd STAGE
I flash new Firmware and PIT file(get from some web) via ODIN3_v1.85.
But phone was not worked properly.
When i open recovery boot menu it says"Installing System updates"(5 min)
then after select "wiping menu" or "reboot" it takes 10 min.
3rd STAGE
I flash via Smart switch Emergency Recovery mode but it says above errors.(But it working properly compered to above condition but have same errors)
4th stage
I flash official ROM(AP) and Boot Loader(BL) vis ODIN3_v3.11.
Started properly but same screen says"Installing system updates" and all that.
Sometimes says "NO COMMAND" for a bit sec and goes to recovery menu.
Note: Phone is not rooted
What should i do to solve this issue?
I think that may issue again rise from PIT file?(It seems partition line in recovery menu)
is there any way to remove partition made by PIT file?
What should happen if i check "re-partition"(Not given PIT file) or "Nand Erase All" while flashing with ODIN?
I have BL,AP,CP,CSC for that phone.
Thanks in advance.

N910F couldn't do normal boot

Hi All,
I have a note 4 n910f on stock 5.1.1 unrooted and stock recovery.
The problem happened before when I'd lock the phone, I wont be able to unlock it or turn it back on. For me to boot it up I would have to remove the battery.
Then on its reboot, an error would pop up stating: "could not do normal boot mmc_read failed"
Later on I installed CPU Awake and the problem would no longer happen when locking the phone.
The next problem came when I turned it off once. I couldnt boot it back up again. I took the battery out and placed the phone in the freezer for about 10 minutes (i remember reading it somewhere) then I was able to boot it up, still with the same error but it is able to boot normally.
Any advice? Is this more likely a hardware issue?
Thanks
This a emmc issue.
Flash the recovery firmware.
https://mega.nz/#F!QIMmFRIT!Ns3AM-n0FUoMqOOWUif9ng
Go to note4/511 and download all files except apq8084.
Load all thr files in their respective slots(ap, cp, csc, bl and pit).
Enable repartion in odin.
Reporting Via N910G

S7 edge sw rev check fail device 2 binary 1

So I tried to downgrade from android 8 to android 6 and I got the sw rev check fail device 2 binary 1 it loaded the cp file but failed everything else now when I turn on the phone it's just stuck on the logo screen, I can access Odin mode and stock recovery which is reporting 6.0.1 any ideas here anyone?

Recovery does not get flashed alongside stock rom

Backstory:
Received the message "Custom binary blocked by FRP lock" when restarting my phone. I had a custom ROM installed so this was probably why, but I had flashed no-verity-opt-encrypt previously so I don't know why I randomly got this message.
Tried to flash the latest Android 8.0.0 stock firmware from sammobile, successfully flashed through Odin but when the phone boots it keeps looping into recovery, followed by "No command".
When I try to access the recovery settings by pressing power+up it comes with:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
Along with a bunch of lines saying failed to mount /system and dm-verity failed.
I've tried flashing many different stock ROMs but only the factory binary combination ROM is able to boot up. Therefore, I cannot turn off FRP lock. I am struggling to find out why, even though Odin successfully flashed the whole stock BL, AP, CP and CSC, the recovery cannot be opened.
Any ideas would be greatly appreciated.
Edit: Managed to fix it through a YouTube video by Mr.Lee
Try downgrading to nougat or marshmallow. That should remove FRP.
Sent from my SM-G935FD using Tapatalk
I've tried but I cannot find any marshmallow/nougat version which does not result in a SW REV CHECK FAIL error, my kernel only accepts Oreo or higher it seems.

G930V will not boot no matter what. please help

I have a co-worker's G930V that decided it wanted to only boot to the 'no command' recovery thing (not the menu, just blue with no command'), it's devolved to the point where he doesn't care about the data on it, just trying to get it working.
Info:
It's FRP locked (he knows the login, so this isn't important)
It's on binary 10 (can ONLY flash firmware CSF2 as far as I can tell)
Things I've tried and outcomes
Smartswitch: 'unsupported device'
Verizon's tool: 'Unsupport dev_type'
Odin flashing BL/AP/CP/CSC anything other than CSF2: 'SW REV CHECK FAIL'
Odin flashing BL/AP/CP/CSC for CSF2: 'recovery booting' followed by it rebooting and sometimes getting to a screen with a percentage bar that just says 'Error' (attached)
Odin flashing PIT/BL/AP/CP/CSC: same as non put odin
Odin flashing PIT/BL/AP/CP/CSC and NAND ERASE: same thing
I was able to get it to get to the encryption failed screen once by flashing just AP after a NAND ERASE PIT/BL/AP/CP/CSC.
I also got it to show "Custom Binary blocked by SECURE BOOT' by only flashing official firmware...
Update: There are other weird things that happen... I got odin to flash the latest G930U firmware and the same thing happens, I've also seen the grey circle with a lightning bolt screen leading me to believe its a battery issue.
IT WAS A BATTERY ISSUE, Tested with an S6 battery and once I flashed the Verizon firmware it booted right up.

Categories

Resources