***EDIT*** The problem was that I was trying to flash firmware that wouldn't work on my bootloader version, I was running version 3, and the firmware I tried were all version 2. You can check the bootloader of firmware by starting at the right side of the firmware number, and counting back 5 spots.
Trying to get root, so I am downgrading the firmware, I have had nothing but trouble with it thus far, though. Any help would be appreciated.
SM-G955U - US Cellular Version
G955USQS3CRE2
Bootloader Version 3
Android 8.0.0
History of the phone, tried rooting quite a while ago, softbricked it, then went back to stock rom no problem. Flash forward a few months later, used the SamFail and PartCyborgRom method to have root, did not have mobile data, though, so I went back to stock, again. I was told after a bit that updating the modem would have fixed that issue, but oh well. Now, I want to use the SamFail mehtod to have root again, and fix the modem issue in the phone. I am trying to downgrade the firmware so that this will work.
However nothing is working properly.
List of all firmwares I have tried:
USC-G955USQU1AQDE-20170505162155
USC-G955USQU1AQD9-20170421124057
SM-G955U_1_20170504154313_jk5541apkz_fac
SM-G955U_1_20170620081840_8g9ali6ocz_fac
SM-G955U1_1_20170428100826_id2grime7e_fac
I have uninstalled the Samsung Drivers, rebooted and reinstalled, same for ADB. I have enabled USB Debugging. I can not enable OEM Unlock, locked bootloader.
For the Odin settings I have tried loading just AP. Then All of them. Then everything except for BL. Then all except for CSC.
The options I have checked are Auto Reboot and F. Reset Time.
This is the Odin Log:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4429 M
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what it says on my phone in DL mode:
CARRIER: USC
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF
WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE
RP SWREV: B3(1.1.1.1.1) K2 S3
SECURE DOWNLOAD: ENABLE
DID 205EBC0B1B52
SW REV CHECK FAIL : (boot)Fused 2 > Binary 1
My phone still works just fine, have not bricked it trying all of these. I am open to all suggestions at this point. I know I had the stock firmware at one point in time, and I am trying to find it at any cost.
KimJongIan said:
Trying to get root, so I am downgrading the firmware, I have had nothing but trouble with it thus far, though. Any help would be appreciated. SM-G955U - US Cellular Version......
Click to expand...
Click to collapse
I don't have this device and there's really not much on the forum regarding the US Cellular variant for your device.
Your best bet is to take a look at the following link to a very good forum that's specific for US Cellular devices.
http://teamuscellular.com/Forum/forum/481-samsung-galaxy-s8/
I don't often recommend members to another forum unless it's a much better solution for what's needed.
When i used to have a US Cellular device (like my older Galaxy S4 that's long gone now) I used to use that forum and it was extremely helpful there.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Related
Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<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 am kind of out of options here. Any suggestions?
Auth means you are using the wrong tar fille. Make sure you use the MI1 file if you took the latest update
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Ablac said:
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Did you get it to work? I made the same mistake with SafeStrap, and now I can only boot to the download screen.
I'm downloading the ROM you linked, but it will take another two hours.
EDIT:
Download finished. How do I install it? I was expecting a .tar or .md5 to use with ODIN, but the link contains a zipped .img
Did it work?
Ablac said:
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
alexbmex1 said:
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
dlist said:
Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<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 am kind of out of options here. Any suggestions?
Click to expand...
Click to collapse
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
All done
artjef said:
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
Click to expand...
Click to collapse
Beautiful ROOT! It is back. Thank you very much for the link. Worked like a charm.
Not sure if anyone has done this, I didn't see anything, so here goes: I OTA updated to Official OG6 and didn't like that my music wasnt displaying the info on my Bluetooth stereo, so downgraded to NK2. It was pretty simple, Get the official NK2 Odin package, Modem, and Bootloader, put them in the correct locations in Odin 3.0.9 and untick auto-reboot, flash and pull battery for 30 seconds, put battery back in and 3button boot into recovery, wipe data and cache and reboot. If you see the white T-Mobile background pull battery and 3button back into recovery wipe data and cache and reboot...profit!
Thanks for this. Worked like a charm.
Been a while since I've ran a Kit Kat ROM, but it's gooooood to be back. I forgot how much I like the mostly dark theme of Kit Kat vs the mostly white theme of Lollipop (gross). FOF6/FOG6 ROMs worked pretty good the first couple of days after flashing them and then it was just downhill from there all the way to lagville with my phone anyway. It would freeze up for 5-20 seconds multiple times a day. Seemed to have bad timing with it too. It would happen when using GPS or when getting a phone call or while needing to text someone.
Glad somebody else got to use it. I've already been back and forth a few times....I'm an og flashaholic!
Sent from my SM-G900T
I'm getting ready to do this tonight. I'm seeing way too much lag with OG6. Where did you get the files? Can you provide a link to the right post? I just bought this S5 as I came from an ATT S5. There we just found the full ROM placed it into the AP slot and away we went.
This should get you started
http://forum.xda-developers.com/showthread.php?p=59132750
Sent from my SM-G900T
Yea I just took my wife's s5 and gave her my old note 3, (I have a note 5 now), because the lag is terrible on OG6. I will definitely be going to KK tonight or tomorrow it's so unbearable. The s5 was a bad a$$ on KK and its time to go back until M gets dropped.
Sorry to bump an old thread. I saw a link to this. I am getting error in Odin3_v3.10.7
UJsed AP slot, only auto-reboot and F. Reset Time are checked
Phone: stock FOF6, booted once, USB debugging enabled
Tried both ROM and both failed.
G900TUVU1ANCH_G900TTMB1ANCH_G900TUVU1ANCH_HOME
G900TUVU1DOB1_G900TTMB1DOB1_G900TUVU1DOB1_HOME
G900TUVU1CNK2_G900TTMB1CNK2_TMB
Error are shown below.
If OP has success with OG6, I'd think OF6 has no issue. The only thing I can think of is that I'd have to flash bootloader and modem at the same time. Is that the issue?
Thanks
Thanks
On the phone:
PRODUCT NAME: SM-G900T3
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
SECURE CHECK FAIL: aboot
Odin:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I download and used LL for about 3 days. Man, that doggone lag.....it's almost like watching paint dry. LL was awfully written. KK is a beast on my S5.
So I was given this phone that is stuck in download mode and am having quite a few problems getting it flashed with odin.... it seems to fail every time. not sure on the original android version it was rooted on .. The only information I was given is that it was rooted at one point and then they did a factory wipe getting it stuck in download mode... Seeing as Im new to this whole scene any help would be much appriciated
Tried 3 different firmwares from a post here
and also tried to get kies to recognize the phone .. It will not ,It is stuck at connecting
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update:
On download screen : sw rev check fail....
If i have to choose a certain version of the firmware is there anyway to check the version I need without having to turn on the phone?
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Matthew M. said:
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Click to expand...
Click to collapse
fuse 0 binary 5
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
You should go back to kies and see what version it flashed. That way if this ever happens again you can download that version and flash it through odin
Deleted
Serioussamuel said:
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
Click to expand...
Click to collapse
Can you explain how you did this? I am running into a similar problem and neither a firmware upgrade nor a kies initialization is working.
Same problem here, I also don't know what my phone bootloader or firmware, I'm also stock in download mode...hope someone can answer and help us...
so i am attempting to flash stock ATT firmware to my s7 edge from sprint. the phone is unlocked, fully paid for and has no issues. i went through developer mode and unlocked the bootloader and checked usb debugging. i keep getting sw rev check fail s7 edge fused 5 > binary 4 and it fails just after reaching <ID:0/003> hyp.mbn.
the thread looks like this.
<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> apdp.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> hyp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help, thanks. P.S. done quite a few roots and mods including the legacy os 14 but the samsung flagships are always tricky.
Hi, is your phone working fine when you flash the same version of OS what you had before ?
SM-G935P
the phone is originally sprint, it was working, had it unlocked, put it on att, last time it did that i got stuck in recovery bootloop and i had to "flash" stock sprint firmware. sad thing is it didn't fully flash to the original but it got it out of the loop, i suppose because whatever the file or system block is that stops it at hyp.mbn there is all that is needed to be fixed. in short yes it works fine. but i do not like the sprint bloatware and i need to at least get the att modem on the phone so that i can get proper signal
I think the only way to remove sprint bloatware is to root your device , and uninstall all that bloatware with root Uninstaller.
Do some research how to do that and look if is safe or not .
I can't provide anything here because is not tested and I don't want to bring your device in BRICK state .
SM-G935P has just firmwares for Sprint , so if you try to flash DBT unbranded firmware I think you will got Bootloop , I don't know because I don't have that device to make test .
from what i understand the only firmware you can flash is unlocked firmware, essentially SM-G935U from my days of research on it.
I'm really not sure , but if you think about flashing that firmware look with 5 files repair 5 file is .pit to wipe completely os and reflash that new one .
I think is better to search for people who has experience with that , to knows better what is risk and what not .
Hello all,
I am hoping someone brilliant on here has gone through this and can help me as I have tried other suggestions on this forum but have not found any success. I have a Verizon Galaxy S6 Edge phone (SM-G925V), but my carrier is T-Mobile. The phone is carrier unlocked as it works with T-Mobile using their APN settings (although the reception is not great). I want to flash the newest T-Mobile stock firmware onto my Verizon phone so that I can have access to T-Mobile's full spectrum of radio bands.
When I try to flash the latest T-Mobile 7.0 firmware onto my Verizon phone from Sammobile using Odin 3.13.1, I always receive the following fail message:
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 3526 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have installed drivers, updated Kies, and made sure to kill the Kies process prior to running Odin. I have tried doing this using older versions of Odin (including Prince Comsy), on a laptop and desktop using USB 2.0 and 3.0. I have even tried the plug-in, volume up and start sequence mentioned in another thread - all without success. Is this even possible? Should I be using another process? or am I forever doomed to have subpar reception?
Final thought in doing some research: does this have anything to do with a locked bootloader? Verizon phones does not include the option in Developer Options for OEM unlock so unfortunately I can't test this.
Any help would be greatly appreciated!
Hi,
I saw your "How Can I Flash T-Mobile Stock Firmware onto Verizon S6 Edge Phone?" post from 9/12/18.
I am in the same boat with a SM-G925V. Were you able to solve this? Can you point me in the right direction?
Thx,
Dean
DeanONH said:
Hi,
I saw your "How Can I Flash T-Mobile Stock Firmware onto Verizon S6 Edge Phone?" post from 9/12/18.
I am in the same boat with a SM-G925V. Were you able to solve this? Can you point me in the right direction?
Thx,
Dean
Click to expand...
Click to collapse
I have not found a solution and have basically given up. It seems like Verizon S6 Edge phones come with a locked bootloader and no option for OEM unlock which means you can't flash another carrier's firmware.