So I have been having alot of trouble trying to get my S5 to have root capabilities and ended up soft bricking the thing. I have Odin V3.09 and the stock firmware and it keeps giving me the chain of messages everytime I try to reflash it:
<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)
My phone is A Galaxy S5 verizon version (SM-G900V) running on 5.1 (I believe). I use this phone everyday and need help ASAP.
Verizon bootloader will be locked, I read someone had unlocked it, but never saw anything more come of it
btw919 said:
So I have been having alot of trouble trying to get my S5 to have root capabilities and ended up soft bricking the thing. I have Odin V3.09 and the stock firmware and it keeps giving me the chain of messages everytime I try to reflash it:
<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)
My phone is A Galaxy S5 verizon version (SM-G900V) running on 5.1 (I believe). I use this phone everyday and need help ASAP.
Click to expand...
Click to collapse
Before you do this open your phone, take battery out and note down your serial number.
What I always try at this stage is Kies. Download Kies 3, click Tools > Firmware Upgrade/Initialization and it will ask for your model number and serial number.
Go through with it. It should download the latest stock firmware for your device and it should ask you to plug your phone in and put it in download mode & press next.
This method has recovered me from the worst situations so I hope it works for you!
Shaolin36 said:
Before you do this open your phone, take battery out and note down your serial number.
What I always try at this stage is Kies. Download Kies 3, click Tools > Firmware Upgrade/Initialization and it will ask for your model number and serial number.
Go through with it. It should download the latest stock firmware for your device and it should ask you to plug your phone in and put it in download mode & press next.
This method has recovered me from the worst situations so I hope it works for you!
Click to expand...
Click to collapse
It worked! Thanks for the help!
Related
Running Samsung-SGH-I337 Galaxy S4 AT&T with 4.2.2, rooted and encrypted of course, I've been trying to flash a custom recovery such as CWM via ROM Manager and also TWRP via GooManager as well as other attempts to get the custom recovery working. When ROM Manager or GooManager tries to set things up it says it works, but when I reboot into recovery mode it actually goes into Download/Odin mode instead. Even if I use the volume up method of getting into recovery mode (download mode is volume down) it goes to download mode instead. I've even rebooted to recovery mode via adb, still goes to download instead. What?
Try flashing it with Odin.
I haven't found a TWRP method that works for the ATT I337 via ODIN. Not sure how that would make a difference either though.
i dont about twrp why not use Philz Touch CWM ?
i can send your a link, pm me if you're interested
I tried flashing the version from here: goo. im/devs/philz_touch/CWM_Advanced_Edition/jflteatt but it fails every time. I've tried different verions of the ATT CWM Advanced Edition as well as different versions of Odin. I've read maybe it had something to do with a locked bootloader? Haven't been able to find much good information on that for my phone.
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<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)
Parad0x86 said:
I tried flashing the version from here: goo. im/devs/philz_touch/CWM_Advanced_Edition/jflteatt but it fails every time. I've tried different verions of the ATT CWM Advanced Edition as well as different versions of Odin. I've read maybe it had something to do with a locked bootloader? Haven't been able to find much good information on that for my phone.
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<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)
Click to expand...
Click to collapse
have you tried other versions of Odin?
Hi,
I'd like to remember you that you have a specific forum for your device
http://forum.xda-developers.com/galaxy-s4-att
People there should be of better help than here .
~Lord
XxLordxX said:
Hi,
I'd like to remember you that you have a specific forum for your device
http://forum.xda-developers.com/galaxy-s4-att
People there should be of better help than here .
~Lord
Click to expand...
Click to collapse
Thanks, I didn't realize I had to look at "All" forums to find my device's forum since the default is just "Top Devices" and didn't see it. If this can be moved please do.
I've been reading and from what I've gathered, since I have MF3 firmware my bootloader is locked down and my only bet is to use Safestrap. I'll be looking into this.
Edit: Also I use encryption which is apparently not a good idea with Safestrap so I'm probably SOL. Awesome.
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
So there was a game promotion that if you had an S6/EDGE, you would get free content in that game. The only way (to me) that I could get it was change my ro.device.model number to appropriate S6 model number to fake having an S6/EDGE. I rooted my Note 4 (SM-N910P) using chainfire's auto-root. Everything went fine inthe rooting process. I downloaded the application that changes my build.prop (In play store it is titled "build.prop editor"). So I changed the ro.device.model to SM-G920F. I restarted my device so the game could notice that I "had" G6/EDGE. I was stuck in a bootloop. All I see is the Samsung logo. I can access download mode (power home voldown) and recovery (power home volup). I was freaking out that I was stuck in a bootloop. Then someone else in the reddit thread (reddit dot com/r/hearthstone/comments/3dkwew/how_to_get_the_samsung_s6_3_packs_and_card_back) said that he tried it on his Note 4 and he also got the same bootloop but he fixed it by reverting back through stock. I downloaded stock Note 4 4.4.4 firmware and flashed....
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
savev1 said:
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
So there was a game promotion that if you had an S6/EDGE, you would get free content in that game. The only way (to me) that I could get it was change my ro.device.model number to appropriate S6 model number to fake having an S6/EDGE. I rooted my Note 4 (SM-N910P) using chainfire's auto-root. Everything went fine inthe rooting process. I downloaded the application that changes my build.prop (In play store it is titled "build.prop editor"). So I changed the ro.device.model to SM-G920F. I restarted my device so the game could notice that I "had" G6/EDGE. I was stuck in a bootloop. All I see is the Samsung logo. I can access download mode (power home voldown) and recovery (power home volup). I was freaking out that I was stuck in a bootloop. Then someone else in the reddit thread (reddit dot com/r/hearthstone/comments/3dkwew/how_to_get_the_samsung_s6_3_packs_and_card_back) said that he tried it on his Note 4 and he also got the same bootloop but he fixed it by reverting back through stock. I downloaded stock Note 4 4.4.4 firmware and flashed....
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
Click to expand...
Click to collapse
try download diffrent firmware
try wipe data/cache (volum up+power button +home button) if you cant access it .try rooting your device and then install recovery then wipe(cache data) and try flashing stocks firmware again
it may also be bad cable try diffrent one
reinstall kies 3(after unistalling it first)
use diffrent odin (3.04 ECT)
and try kikat firmware i believe its just firmware issue (try russian kitkat if your device varient is supported )
savev1 said:
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
Click to expand...
Click to collapse
No youre not screwed(shouldnt be).
And No, dont continue to flash KitKat firmware or youre going to be wasting time and continually disappointed, no matter how many times you download it.
Once you get to a certain bootloader, youre not able to downgrade to prior(kitkat in this case) bootloaders. Flash the LATEST stock.tar through Odin and start all over.
xxSTARBUCKSxx said:
No youre not screwed(shouldnt be).
And No, dont continue to flash KitKat firmware or youre going to be wasting time and continually disappointed, no matter how many times you download it.
Once you get to a certain bootloader, youre not able to downgrade to prior(kitkat in this case) bootloaders. Flash the LATEST stock.tar through Odin and start all over.
Click to expand...
Click to collapse
Ummm, okay could you possibly link my to the current tars? I have tried flashing everything from kitkat to lollipop. (I was originally on the BOB7 lollipop build).)
From what I've read (hence why I am scared) is that my eMMC chip is broken and cannot be written to...
savev1 said:
Ummm, okay could you possibly link my to the current tars? I have tried flashing everything from kitkat to lollipop. (I was originally on the BOB7 lollipop build).)
From what I've read (hence why I am scared) is that my eMMC chip is broken and cannot be written to...
Click to expand...
Click to collapse
Well, lets hope that isnt the case and stick to what we do know. That message you received points to one thing, Trying to Odin a .tar firmware that contains an older bootloader that people with OE1 and up bootloaders cannot downgrade to.
OF5 Stock tar.
http://forum.xda-developers.com/note-4-sprint/general/of5-tar-t3158006
FYI SM-N910P Forum
http://forum.xda-developers.com/note-4-sprint
xxSTARBUCKSxx said:
Well, lets hope that isnt the case and stick to what we do know. That message you received points to one thing, Trying to Odin a .tar firmware that contains an older bootloader that people with OE1 and up bootloaders cannot downgrade to.
OF5 Stock tar.
http://forum.xda-developers.com/note-4-sprint/general/of5-tar-t3158006
FYI SM-N910P Forum
http://forum.xda-developers.com/note-4-sprint
Click to expand...
Click to collapse
It worked! It worked! I pressed thanks bro ^.^
savev1 said:
It worked! It worked! I pressed thanks bro ^.^
Click to expand...
Click to collapse
Lol. Np bro. Glad it worked. Thats what the community is here for.
Get your phone situated and the way you like it (launchers or what have you) and make a backup in recovery and youll be good to go.
Note 4 sm-n910f
savev1 said:
It worked! It worked! I pressed thanks bro ^.^
Click to expand...
Click to collapse
I've been had the same problem having this error
----------------------
UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
-----------------------
and I badly need to flash to stock since I am using custom and having problem with my sim not being detected .
but i just cant seem to get it flashed once more like i did the first try with a stock rom ?
would you suggest me to download several stock rom in sammobile and try all.
I am having the same problem with N910W8 getting emmc write fail
Does anyone know where I can find the stock firmware for my at&t galaxy s7 SM-930A APB4? I found APB5 but ODIN won't flash it as it's saying its the incorrect matching firmware. I have searched far and wide trying to find the firmware for my phone. It's like I somehow managed to snag the most niche phone on the planet with no stock firmware. Thanks!
PB5 should flash fine. Try a different odin
This is what I get when I try to flash APB5
<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> 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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And then on my Galaxy s7 it says "SW REV CHECK FAIL : [system]Fused 3 > Binary 1
iscream612 said:
This is what I get when I try to flash APB5
<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> 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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And then on my Galaxy s7 it says "SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Click to expand...
Click to collapse
A quick search I ran found that it seems you may be trying to downgrade. What version were you on prior to this? It sounds like you were either on a T-Mobile firmware or on the latest PI2 firmware (Based on that "Fused 3"). If you don't remember but you haven't taken any updates since you got it, could you provide the date you got it? Then I could help. Thanks.
SkyAttacksX said:
A quick search I ran found that it seems you may be trying to downgrade. What version were you on prior to this? It sounds like you were either on a T-Mobile firmware or on the latest PI2 firmware (Based on that "Fused 3"). If you don't remember but you haven't taken any updates since you got it, could you provide the date you got it? Then I could help. Thanks.
Click to expand...
Click to collapse
I was on the newest Sept bootloader update. With the help of a couple people I was able to flash the unlocked firmware.
http://forum.xda-developers.com/att-galaxy-s7/how-to/please-shed-light-att-s7-root-failures-t3481904
Joe3681 is currently uploaded the Sept AT&T firmware so soon I should be able to flash back to at&T and be all set.
Thanks!!
AT&T
Galaxy S7
Android security patch level: Sept 1, 2016
Baseband version: G930AUCS4API2
Build number: MMB2M.G930AUCS4API2
I attempted to root my phone with the guide you can find by The Unlockr (David Cogen)
I followed the steps exactly but unfortunately it would freeze on AT&T symbol...
So I tried flashing stock firmwares with no luck. So I wiped data/restored factory settings and fortunately my phone runs. However I keep getting a popup saying "Security Notice: Unauthorized actions have been detected." Which I am assuming means I tripped KNOX. =(
Is there a way to remove this trip? Does anyone know a firmware that SHOULD flash properly on my phone?
Here is the error I get when I try to flash the 2 firmwares I have found (G930AUCS2APF2, G930AUCU1APB5)
<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> 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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help you can provide..
iscream612 said:
AT&T
Galaxy S7
Android security patch level: Sept 1, 2016
Baseband version: G930AUCS4API2
Build number: MMB2M.G930AUCS4API2
I attempted to root my phone with the guide you can find by The Unlockr (David Cogen)
I followed the steps exactly but unfortunately it would freeze on AT&T symbol...
So I tried flashing stock firmwares with no luck. So I wiped data/restored factory settings and fortunately my phone runs. However I keep getting a popup saying "Security Notice: Unauthorized actions have been detected." Which I am assuming means I tripped KNOX. =(
Is there a way to remove this trip? Does anyone know a firmware that SHOULD flash properly on my phone?
Here is the error I get when I try to flash the 2 firmwares I have found (G930AUCS2APF2, G930AUCU1APB5)
<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> 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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help you can provide..
Click to expand...
Click to collapse
You may be on a newer bootloader which is why you are receiving the pit file error when flashing lower firmware
Sent from my SM-G930P using XDA-Developers mobile app
iscream612 said:
AT&T
Galaxy S7
Android security patch level: Sept 1, 2016
Baseband version: G930AUCS4API2
Build number: MMB2M.G930AUCS4API2
I attempted to root my phone with the guide you can find by The Unlockr (David Cogen)
I followed the steps exactly but unfortunately it would freeze on AT&T symbol...
So I tried flashing stock firmwares with no luck. So I wiped data/restored factory settings and fortunately my phone runs. However I keep getting a popup saying "Security Notice: Unauthorized actions have been detected." Which I am assuming means I tripped KNOX. =(
Is there a way to remove this trip? Does anyone know a firmware that SHOULD flash properly on my phone?
Here is the error I get when I try to flash the 2 firmwares I have found (G930AUCS2APF2, G930AUCU1APB5)
<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> 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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help you can provide..
Click to expand...
Click to collapse
The september patch has a new bootloader which means you can't downgrade below API2. And no, you didn't trip knox. That notification pops up regardless when the security log detects that the phone is rooted, So you should be fine. API3 G930U firmware flashes perfectly and works really well, I recommend using it.
G930U Firmware >
http://forum.xda-developers.com/att...4api3-firmware-download-t3481159#post69147585
VenomMOD said:
The september patch has a new bootloader which means you can't downgrade below API2. And no, you didn't trip knox. That notification pops up regardless when the security log detects that the phone is rooted, So you should be fine. API3 G930U firmware flashes perfectly and works really well, I recommend using it.
G930U Firmware >
http://forum.xda-developers.com/att...4api3-firmware-download-t3481159#post69147585
Click to expand...
Click to collapse
You are the man, thank you so much! And big thanks to joe3681 for paying/uploading the firmware for us! :good:
VenomMOD said:
G930U Firmware >
Click to expand...
Click to collapse
Also, what firmware is this? Custom? From another carrier? It's definitely different than my old at&t firmware..
iscream612 said:
Also, what firmware is this? Custom? From another carrier? It's definitely different than my old at&t firmware..
Click to expand...
Click to collapse
It's the firmware of the Unlocked S7 variant, which is Official Samsung firmware. No AT&T bloat or anything.
Performance and battery life have gotten better on this Firmware, and no overheating either.
VenomMOD said:
Performance and battery life have gotten better on this Firmware, and no overheating either.
Click to expand...
Click to collapse
I really do enjoy the idea of no bloat and better performance/battery life. Theres just some things that I will miss, like at&t advanced text messaging..
Hi all,
I have a S7 Edge - SM-G935F (UK) - that I think had/has a software/firmware issue. It would boot and be ok if left idle but after about 5 minutes of use it would crash and reboot.
I connected to Smart Switch and it tried to update the software to the latest version but due to the device crashing after a few minutes, this failed. Then I was left with the blue error screen advising a software update has failed and to use the Firmware Recovery mode on Smart Switch. So I tried this and this fails at either 5% or 16% referencing an issue with the device.
Then I tried flashing the stock firmware in ODIN and this fails almost instantly with the following log entries:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> modem_debug.bin
<ID:0/004> Home Binary Download
<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> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help or is it done for??
Thank you
Anyone, please?
lemons55 said:
Anyone, please?
Click to expand...
Click to collapse
Have you taken a look here: https://forum.xda-developers.com/galaxy-s7/how-to/guide-onelatest-stock-fw-csc-root-t3702963 ? It might be of use. If that fails, report back in. Now I think of it, report back anyway.
On top of the problem you got, i got the problem that when i open "smart switch", or Kies, none detects the phone, supposedly i should be able to recover it with the emergency thingy..
Anyway i can get to download mode, but it also fails and im using XEU-G935FXXU2ERGE
MartyHulskemper said:
Have you taken a look here: https://forum.xda-developers.com/galaxy-s7/how-to/guide-onelatest-stock-fw-csc-root-t3702963 ? It might be of use. If that fails, report back in. Now I think of it, report back anyway.
Click to expand...
Click to collapse
Hey, I've only just logged back in to check this forum - the link you shared no longer works, would you happen to know of another link that may help? I still have the problem - left this device as a dead in the water project!
Thanks a lot