Database Users

[Q] 1337 S4 Root unsuccessful please help

I attempted to do my first root via the tutorial: ibtimes.co m/android-442-kitkat-released-samsung-galaxy-s4-canada-while-odin-flashable-update-availabl
follow all instructions to the key, and ran into these errors:
1. FAIL! as soon as I pressed Start ( i did have the blue light)
2. second attempt started successfully but stopped 3/4 way through and received a invalid percent of drawing download error
Im trying to flash a telus canada samsung s4 that had the 4.4.2 update stock.
what can i do?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I337MVLUFNC1_880525_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I337MVLUFNC1_880525_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> AP_I337MVLUFNC1_880525_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_OYA_I337MOYAFNC1_880525_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/006> Added!!

lock1nout said:
I attempted to do my first root via the tutorial: ibtimes.co m/android-442-kitkat-released-samsung-galaxy-s4-canada-while-odin-flashable-update-availabl
follow all instructions to the key, and ran into these errors:
1. FAIL! as soon as I pressed Start ( i did have the blue light)
2. second attempt started successfully but stopped 3/4 way through and received a invalid percent of drawing download error
Im trying to flash a telus canada samsung s4 that had the 4.4.2 update stock.
what can i do
Click to expand...
Click to collapse
what i would do would be to downgrade to mk2 from i assume your on the NB1 build of 4.4.2
root using the saferoot methood or what i used was the kingo root methood, you can google kingo.
then flash a "already rooted" rom version of kitkat. i belive ShoStock rom is very close to stock but has some cool changes,
i am on the at&t network, i havent figured out quite yet how to flash shostock on my phone but ive been busy the past few days and havent been able to do any searching,
ill subscribe to this forum for you so you'll have someone watching for your post
anyone else have any ideas?

mejakola said:
what i would do would be to downgrade to mk2 from i assume your on the NB1 build of 4.4.2
root using the saferoot methood or what i used was the kingo root methood, you can google kingo.
then flash a "already rooted" rom version of kitkat. i belive ShoStock rom is very close to stock but has some cool changes,
i am on the at&t network, i havent figured out quite yet how to flash shostock on my phone but ive been busy the past few days and havent been able to do any searching,
ill subscribe to this forum for you so you'll have someone watching for your post
anyone else have any ideas?
Click to expand...
Click to collapse
thanks for the reply.
at this point, any firmware version of stock would do. Can i flash a stock 4.3 rom through, or is that too risky?

mejakola said:
what i would do would be to downgrade to mk2 from i assume your on the NB1 build of 4.4.2
root using the saferoot methood or what i used was the kingo root methood, you can google kingo.
then flash a "already rooted" rom version of kitkat. i belive ShoStock rom is very close to stock but has some cool changes,
i am on the at&t network, i havent figured out quite yet how to flash shostock on my phone but ive been busy the past few days and havent been able to do any searching,
ill subscribe to this forum for you so you'll have someone watching for your post
anyone else have any ideas?
Click to expand...
Click to collapse
By what he said he's on an I337m, different from the AT&T I337. Not only will the Safestrap method not work, it's more work than he needs.
lock1nout said:
thanks for the reply.
at this point, any firmware version of stock would do. Can i flash a stock 4.3 rom through, or is that too risky?
Click to expand...
Click to collapse
I don't know how downgrading goes, I believe you can flash a 4.3 though. I'd make sure that your 4.4 ODIN is a full download and the MD5 matches if there is one where you downloaded it. Also, when you retry the root, try just using the link to CF Auto Root from its thread in one of the development sections.
Sent from my GT-I9505 using xda app-developers app

DeadlySin9 said:
By what he said he's on an I337m, different from the AT&T I337. Not only will the Safestrap method not work, it's more work than he needs.
I don't know how downgrading goes, I believe you can flash a 4.3 though. I'd make sure that your 4.4 ODIN is a full download and the MD5 matches if there is one where you downloaded it. Also, when you retry the root, try just using the link to CF Auto Root from its thread in one of the development sections.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
im currently downloading the stock rom for my phone and region and carrier from the samsung updates site. I going to try a 4.4 first. I did not see a MD5 file listed along with the zip.
Can you explain to me a little more on how to 'link to CF Auto Root'?

lock1nout said:
Can you explain to me a little more on how to 'link to CF Auto Root'?
Click to expand...
Click to collapse
You need to find the thread for your phone for cf auto root and there will be a clickable link for you and will take you to chainfires Google plus page with the correct files

mejakola said:
You need to find the thread for your phone for cf auto root and there will be a clickable link for you and will take you to chainfires Google plus page with the correct files
Click to expand...
Click to collapse
I follow the instructions for the CF-Auto boot. Every seems to load up fine until i got the the samsung boot screen after recovery mode and stuck there. I tried a cache wipe and even a factory reset and it still sticks at the boot screen. I also tried to reflash the cf auto boot to not avail.

im back to stock, thanks to everyone for their help.

[Q] Odin flash back to stock failing due to

EDIT: Sorry for the bad title. Derp.
So my phone, AT&T Galaxy S4, is running into problems. It was running rooted MK2 firmware with Safestrap 3.72 installed on top. I was trying to flash Paranoid Android 4.6 Beta 5 onto the device, but the device would, upon booting to the intro screen, give some message about com.android.phone not working or something. This message would constantly throw itself up no matter how many times I would tap "okay." Anyways, onto the other stuff. I was tired of the bad flashing and decided to try to wipe Data in the separate button with Safestrap's recovery. While the wipe was running, the phone shut down and went into this state...
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Accompanied by an image of a phone connected by a large dotted line to a computer monitor with a large yellow warning sign in the middle. In the upper right is...
HTML:
ODIN MODE
PRODUCT NAME: SGH-I377
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Download mode is ordinary but the phone will not flash correctly. I have tested multiple cables and USB ports along with Odin 3.07 and 3.09, as well as the All-in-One and 4-part MK2 Odin files, but nothing works. They all output this:
HTML:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_ATT_I337ATTEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I've heard something about a PIT file which can save me and also that Best Buy can flash my phone back to stock. Any hope in these avenues?

If try flashing the nb1 tar file. You can find it in the general forum. A pit file isn't going to do you any good
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If try flashing the nb1 tar file. You can find it in the general forum. A pit file isn't going to do you any good
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So just flash the .tar file using Odin's PDA slot? Not the PIT file in this NB1 post?

Razznak said:
So just flash the .tar file using Odin's PDA slot? Not the PIT file in this NB1 post?
Click to expand...
Click to collapse
Yes, PDA slot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yes, PDA slot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well it is currently downloading at less than 100 KBps, so the download time is going to be something like 12 hours. I will post back when it is downloaded.
Never mind. I have the same file downloaded from when I flashed the MK2 Odin file a while ago.

Razznak said:
So just flash the .tar file using Odin's PDA slot? Not the PIT file in this NB1 post?
Click to expand...
Click to collapse
The fail auth indicates that you have a newer boot loader than the one being flashed. That means you have to flash NB1. You don't need the pit file. Just ensure that re-partition is unchecked in Odin.

I flashed the NB1 tar and everything seems good. Took a while to boot, but it hit the Ready2Go screen and all seems well. Will report back when I try to restore my backup I made before trying to flash the custom ROM.

Razznak said:
I flashed the NB1 tar and everything seems good. Took a while to boot, but it hit the Ready2Go screen and all seems well. Will report back when I try to restore my backup I made before trying to flash the custom ROM.
Click to expand...
Click to collapse
I've hit a problem. After restoring the backup on the NB1 recovery using Safestrap 3.72 (same as when I made the backup), the phone won't boot. Instead, it stays on the looping part of the boot animation for a while until it just shuts itself off.
I should note that on the NB1 OS I used Odin to flash yesterday, the Wi-Fi would not activate.

Razznak said:
I've hit a problem. After restoring the backup on the NB1 recovery using Safestrap 3.72 (same as when I made the backup), the phone won't boot. Instead, it stays on the looping part of the boot animation for a while until it just shuts itself off.
I should note that on the NB1 OS I used Odin to flash yesterday, the Wi-Fi would not activate.
Click to expand...
Click to collapse
I realized that I actually flashed the MK2 .tar file in Odin, that was my problem. Flashed the NB1 file and had to use Towelroot to get root, but I am back to where I was with my backup.

Stuck in a boot loop even after flashing to stock from odin.

I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.

I'm in the same situation exactly. At the moment I'm trying to download UK 5.1 to play with odin once again.

did you manage to fix it?

BettlePimp said:
I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.
Click to expand...
Click to collapse
It looks like your problem is that you forgot to turn off the samsung activation lock before flashing. If you forgot what that is see this I have not used this feature on my phone; however, I would suggest wiping with odin then flash the official stock ROM for your phone that you previously had on it when it did work, hopefully it will boot then login to you samsung account when it asks you about the reactivation lock. There are some activation lock bypass methods out there if you do a quick google search. Hopefully this will point you in the right direction.

The reactivation lock is indeed on. "Reactivation Lock(KK): On"
I have no way of turning it off since I'm stuck in a boot loop no matter what firmware I flash through Odin.
Any other suggestions?

I have same problem on my SM-910H
This problem was after updating 5.1.1 and isntallind micro-sd card (128gb)
In 4-5 days after this, bootloop began.
I deisntalled micro sd, checked it in computer for mistakes, fixed it and after this phone worked fine.
Today same problem, but when I deisntall micro-sd my problem does not go away.
I downgraded phone to 4.4 - does not help
Data wipe, cache wipe etc - does not help...
Waiting for solution from proffesionals (
update^
I've found 4 file Factory firware and tried to falsh it
What does Odin say:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Do this, it worked for me. In ODIN, just AP/PDA Autoroot md5 file. It will not be successful and you will get "FAILED" message. Disconnect the phone from PC, pull out battery. Reinsert the battery and boot.

The same happened to me.

To all with this problem. My history:
1. Suddenly my stock device go in bootloop
2. Tried to flash it with official software it does not help
3. Tried to flash it with 3 or 4 file service firmware - did not help
4. Service center (not official, that was service center of my internet market) falshed it with some firmware and sad do not update it. It helped for 2 days.
5. They replaced the motherboard. Only this can help.
So, if you have bootloop in your stock device - try to falsh it with firmware if it does not help - take it to service center and say that they do not spent their and your time and change device or mother board.
Now its ok, working fine.
Wrote it because I spent a lot of time to repair it and maby it will help to some one.

SM-G550T1 boot loop "Custom binary is blocked by FRP Lock"

I had used TWRP to install SuperSU to root. This seemed successful, but a day or two later the phone had powered itself off, and on power-up loops displaying the tiny red "Custom binary is blocked by FRP Lock" message. The phone will boot into download mode, but won't enter recovery mode.
I tried repeating the install of TWRP using ODIN 3.12, but now that fails. Tried installing factory images (\BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 etc.) w/ ODIN, and that fails too.
Is this an indication I don't have the latest image files? ODIN messages below:
<ID:0/004> 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/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​

Made some progress
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.

BHarris said:
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
Click to expand...
Click to collapse
what worked? and what firmware. I have 2 on5's one sm-G-550T and a sm-g550T1 that both ended up with the "custom binary blocked by FRP lock" on the same day..
Please help!

I just tried a bin I downloaded from S U site and it didn't work. Gotta love the On5 lol.

Custom Binary Lock
The same happened to me: i have not found a complete solution, the closest i get to anything is; i put the On5 in Odin3 v3.12 and select the AP option and putting the recovery.tar file and running it. it goes good till its done and the result is Custom Binary (recovery) blocked by FRP lock in green letters. but still no success. i have tried trwp recovery, the home.tar file, each file by them selves and having trouble. i may not be an expert at this type of programimng but i pick things up quickly if there is any solution to my problem please let me know. thx............ by the way i have also tried kies and wont connect to it as well

Same Problem FRP Blocked Bootlooping
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!

SeleneKnightress said:
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
Click to expand...
Click to collapse
You need to reinstall the firmware using Odin. Then, when you root again, you need to make sure you have oem unlock and usb debugging on in the developer options. Not having those on and rebooting when rooted cause the custom binary problem.

Bricked S7 Edge? AT&T

Hey folks, not quite sure where to turn from here or if this phone just goes to the dump...I was looking originally to unlock the AT&T S7 Edge I have and give it to a coworker who is on Verizon. Come to find this is a much larger task than I anticipated.
Device info: Galaxy S7 Edge AT&T SM-G935A
I attempted to follow the guide which started here: https://forum.xda-developers.com/verizon-s7-edge/how-to/odin-stock-nougat-firmware-t3570156
I downloaded the Samsung drivers, Odin v3.12.3 Patched, and the corresponding VZW firmware which I was under the impression was correct, from https://updato.com
I loaded Odin and the phone, ran the installer, and it looked kosher. The device passed, and it began to reboot. However, after that, it got stuck in the nightmare of recurring boot. I entered recovery mode, cleared cache and tried doing a factory reset, to no avail. Device keeps rebooting. Tried re-flashing firmware, no luck.
Where I got to:
On the downloading screen on the Edge:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-6935U <- (this seems wrong given it was AT&T, but I could be misinterpreting as I requested to have the device unlocked from AT&T and the person attempted activating on Verizon before all this)
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B8(2,1,1,1,1) K8 K8
SECURE DOWNLOAD: ENABLE
If I attempted to rerun any of the dozen or so firmware versions I've tried, I always got the following two errors:
In Odin:
<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..
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the device:
SW REV CHECK FAIL : [aboot] Fused 8 > Binary 4
After several hours I managed to get the phone semi-working.
I installed the G935UUEU8CRJ2 firmware from the web. It's the only one it would take as far as I can tell.
However there are two issues:
1. The device keeps restarting after 1-2 minutes of being powered on.
2. The firmware seems to be somehow Sprint? That doesn't make sense...
Android version: 9.0.0
Samsung Experience version: 9.0
Baseband version: G935UUEU8CRJ2
Kernel version: 3.18.71-13710210
Build number: R16NW.G935UUEU8CRJ2
Knox version: 3.1
I've tried running the factory reset from the GUI, but that didn't fix the restarting. Using the reset cache and factory wipe also did not fix the issue. Furthermore when booting into recovery mode initially it attempts to do a system update, then up pops the dead android with x's for eyes and the notorious yellow triangle, yet I can still access recovery mode after a few seconds.
Any suggestions?

Try this: https://www.mediafire.com/file/bzgzxqwafgpsk4c/G935AUCS8CRJ2_StockROM.zip/file

Leone/kyleproxx said:
Try this
Click to expand...
Click to collapse
There's a password on the file.

Update: I found the password. The ROM worked. It's back to AT&T. That solves my softbricking issue, but the original idea to switch it to Verizon is still at hand.
Is there any way to successfully do this?

Leomacomp said:
Update: I found the password. The ROM worked. It's back to AT&T. That solves my softbricking issue, but the original idea to switch it to Verizon is still at hand.
Is there any way to successfully do this?
Click to expand...
Click to collapse
I dont know what to do to switch to verizon

Leone/kyleproxx said:
I dont know what to do to switch to verizon
Click to expand...
Click to collapse
No worries. I actually found the correct VZW ROM (For any of those looking in the future it's: G935VVRU8CRJ3-StockROM-G935V-(-BIT
I loaded this using "Odin 3.13.1 Patched" (The SHA256 bypass). It installed successfully and works now on Verizon's network.
Thanks for the assist!

Leomacomp said:
No worries. I actually found the correct VZW ROM (For any of those looking in the future it's: G935VVRU8CRJ3-StockROM-G935V-(-BIT
I loaded this using "Odin 3.13.1 Patched" (The SHA256 bypass). It installed successfully and works now on Verizon's network.
Thanks for the assist!
Click to expand...
Click to collapse
Your Welcome :good:

Leomacomp said:
There's a password on the file.
Click to expand...
Click to collapse
Hello mate can you plz post the file pass TIA :good:

fabian108 said:
Hello mate can you plz post the file pass TIA :good:
Click to expand...
Click to collapse
The password is www.samkey.org/forum
Ps: and yes the actual website name is the password.

Thanks for solving my issue
I found this thread searching for a way to restore my AT&T branded Samsung Galaxy S7 Edge(SM-G935A), which I thought I might have bricked since it was stuck in a boot loop. Using the stock rom I found on this thread, I was able to get the phone going again. I spent many hours searching and trying different roms, and this was the only one I could get to work. It was FRP locked, but I knew the password. Just could not get past the loop to enter it.
Thus, I wish to say thank you for posting this thread, without it I would still be looking at a boot loop!

friends will have one for bynario 9 I have the same problem please