[Samsung Galaxy S7 Questions and Answers] Eiji.exe:
Whatsup guys, i'm new to xdadev, i'm loving how elaborate and informative all these threads are as well as the community.

Long story short, i got an S7 Tmobile here (i found it, it was blacklisted google locked and all sorts of ****ed)

So i replaced the screen and it looks brand new.

As far as google lock and the blacklisting, i went to a guy who basically did his magic and he wont tell me what he did exactly but i'll ASSUME, he did a flash ROM ?

When it boots it says Android Custom Rom or some****.

It was working fine despite it being kind of laggy.

left it on the table for a week, now that i want to turn it on, it's stuck on the T-Mobile Screen, and i hear a repetitive buzzing sound every minute or so. (is this a brick or a bootloop?)

Anyways, i go to the boot options menu (Power, volume down, and home), and I run Odin as admin, and followed through as instructed. (Yes, I've tried BOTH versions of Odin)

and i made sure I used the right custom firmware (its the T-Mobile Samsung Galaxy 7) (Not edge)

On my phone screen I get this:

ODIN MODE (HIGH SPEED)

Product name: SM-G930T

Current binary: Samsung Official

System Status: Custom

FRP Lock: OFF

Warranty Void: 0x0

QUALCOMM SECUREBOOT: ENABLE

RP SWREV: B4(2, 1, 1, 1, 1) K1 S3

SECURE DOWNLOAD: ENABLE

SW REV CHECK FAIL : [system]Fused 3 > Binary 2

(all of that is on my phone screen)

_________________________

Now for my Odin Screen:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin engine v(ID:3.1203)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> boot.img

<ID:0/003> FAIL! (Auth)

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

______________________________

Does anyone have any solutions?

I'm only attempting the unroot in hopes that i can simply get past the tmobile screen to get the phone running so I can sell it.

**UPDATE**

So i've been playing around with it. I tried 'kies' (Smart Switch.. i think? correct me if im wrong) and tried the emergency software recovery/ initialization but it asks for a Model Name and i guess i'm a really low scrub noob but i can't even get past that part.

It'd be cool if someone can pass me the model name (i swear i had it and i can't even find it now on google, maybe its because i'm running on no sleep and filled with frustration and rush, i gotta get this phone sold by tomorrow)

But yeah, so the Kies method is on pause.

So now I'm trying to do a hard reset through recovery mode (Power, Vol up, Home).

Here's what I have:

Android Recovery

MMB29M.G930TUVU3APG1 (lmfao i think i just figured out the model number here <(G930TUVU3APG1) >_<

samsung/heroqltetmo/heroqltetmo

6.0.1/MMB29M/G930TUVU3APG1

user/release-keys

Use Volume up/down and power.

[then the menu of what i can do]

and on the bottom:

Supported API:3

dm-verity verification failed...

So I try 'Wipe data/factory reset' and here's what I get:

-- Wiping data...

Formatting /data...

Formatting /cache...

-- Set Factory Reset done...

-- Copying media files...

-- preload checkin...

E: failed to mount /preload (No such file or directory)

Data wipe complete.

And basically when I reboot the system, it shows

Samsung Galaxy S7 Custom (Unlock icon),

Then the android loading (installing system update...)

and back to the recovery menu.

What could have caused this?

I was playing around with Odin earlier as well and i feel as though i mightve ****ed it up because i played with options like NAND Erase All and Re-Partition.

Could that be why?

or does it have to do with something called KNOX? I have no clue what KNOX is but based off what i read off other threads, there's a knox count or something to whether it's 0 or 1 or some****

and FRP unlock/bypass may have something to do with it?

Again, keep in mind that i let someone else do something to this phone (no clue what that person did in practice, but ill assume a custom flash rom and frp unlock to bypass google cloud lock and also clean imei from blacklisting)

All this stuff is beyond my knowledge so i'm sorry if i sound extra ignorant but im trying haha.

Anyways, enough of my ranting.

Help me get this phone up and running ASAP and you'll be rewarded a small incentive. ($10-$15 Paypal)

Thank you!