So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<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> 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> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anybody???
I'm sure you're tired of walking noobs through this crap, but I'm sure you can sympathize the idea of suddenly losing access to your smart phone. Does anyone have any ideas on what to try next? I've read for hours and tried dozens of tutorials and I'm just not getting anywhere. FRUSTRATING AS HELL!!! I can stop a heart attack or a tension pneumothorax in my sleep, but trying to program a damn smart phone correctly... you might as well tell me to try to fly.
ERDOC76 said:
So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<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> 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> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I finally figured it out. Thanks for all your help!
:good: but what was your solution?
edit: I think you didn't get much attention because your title likely turned people off -- it's kind of petty to call attention to someone's background if it's not part of the discussion. I saw you had another post where you didn't do that, and got help, so :good:
chill,
Procrastinatron
What's with the title of your post? We don't need that BS on these forums.
ERDOC76 said:
So I tried to root using an old youtube tutorial
Click to expand...
Click to collapse
You'll be fine man go to sammobile look up your G930V in firmware. You can get your current or update to oreo (no root method for oreo yet) unzip
Make sure you have all samsung drivers and adb uninstall kies maybe reboot your computer and make sure your cable is mtp compatible not just a charging cable. Reboot into download mode flash the BL, AP, CP, and CSC .md5 files in their respective Odin slots. Let recovery do its thing first boot will take some time.
Rooting is even quicker and easier so if you're still confident in yourself look up the methods here on here xda. G930V, G930A, G930T, G930U and G930P pretty much use the same root methods as far as nougat goes.
this is probably the biggest thread all credit to those guys that developed it and shared the files, this is probably the best place to start before you discover safestrap and what mods you can actually do (dual speaker ect.). Rooting, like everything else in life is always at your own risk
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Related
Good morning all.
I need to unroot (or just put stock firmware back on my device). I have Cyanogen 11, and i need to swap phone numbers on my phone. The code Sprint wants me to enter does not work with Cyanogen mod so i need to put stock firmware back on the device so sprint can have me put in the codes they need to change the phones telephone number.
Long story short, i have done a lot of research on Google and on here, and i am running into a problem.
First i am using the original (actually i have tried three different ORIGINAL (white) Samsung) USB Cable, i have tried several different USB ports.
I've have downloaded my drivers (actually had them from when i rooted in the first place), i have odin (several different versions, tried them all same result), and stock firmware .tar.md5.
The problem is after i click START in odin, it does its thing for like 10 seconds, then reports a FAIL, this is what Odin reports (this report is from using an Odin v3.185, i have tried v3.07 and 3.09 as well, same end result, but the oden report is slightly different, as it checks the MD5 in the other versions when you enter the file into Odin, vs checking the MD5 when you hit start):
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> aboot.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the PHONE itself, i get a sliver of the progress bar, and in the upper top left some red text that's very difficult to read, but it says something like:
START [ZZ4.1440]
SV REV. CHECK FAIL : found : 4 . Binary : 1
It says all that in red... i have a suspicion THAT is the problem (my phone) and not Odin.
Any help on this would be appreciated, as this is a WORK phone that i need to get the new number ported to before i give it back to my work! LOL
Thanks in advance.
(After previewing my post in the forum.... WOW that's an OLD signature! LOL please disregard the sig info!)
You're trying to Odin an outdated tar. Go to www.sammobile.com and download the NG2.tar.
Thank You! That worked.
I was under the impression that i had to go back to an older version, then update to the latest version. <Shrug>
Anyhow, the first flash went to about 97,98%, then failed. I cleared everything i was doing on the computer (I was running 6 instances of an MMO i play at the same time on the one computer, plus some other stuff that was taxing my computer), RE-Flashed in ODIN, successful Flash. First boot hung at yellow sprint screen. I Pulled the battery, cleared cache, reset (in recovery), and it was a Success! So again, thank you kindly, i knew i just needed a nudge in the right direction. =)
CASE CLOSED. Heh.
I am trying to install the original stock firmware using Odin but keep getting the Secure Check Fail: PIT when I try to install the ROM.
On the phones download screen it has the following (prior to install attempt)
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: CUSTOM
FAP LOCK: ON
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD: ENABLE
In the Odin log I see:
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I only select the AP tar file I get SECURE CHECK FAIL: boot
instead of the PIT.
I added all 4 tar files in ODIN, BL, AP, CP, CSC.
This is a VZW phone.
Any help getting this to boot would be appreciated. Thanks.
You're simply trying to flash the wrong firmware/pit.
And you're in the wrong section, head over there: Verizon Samsung Galaxy S7 Edge
Well I'm searching everywhere and people keep not answering or saying it's the wrong firmware....
I tried two different downloads of the firmware....It's the PE1 for my verizon s7 edge.
I extracted both, have tried with and without the vzw s7edge pit, multiple different cords and ports.
And same issue. I wish every reply would not be...wrong firmware.
Use Samsung own app to restore firmware. Download and install smart switch ,go to emergency software recovery and initialization, device initialization and there put ur model and SN from the back of ur phone..and it will download the right firmware that came with the phone and will install it. Hope it helps
Hey guys,
I'm kinda lost here, I bought this phone a few months ago on a black friday sale in the US.
A few weeks it started bootlooping (the 'preboot logo' kept flashing) it got worse and worse. Remember, I never tried to root, install a custom recovery/OS, nothing!
The only way to get it out of the bootloop was to do a factory reset or sometimes a clear dalvik. But it got worse and worse, and booting into recovery was getting harder and harder...
5 factory resets further, and dozens of dalvik clears, it it bootlooping again!! And it is now impossible to boot into recovery, only download mode.
So I reinstalled the os through odin using these files: https://forum.xda-developers.com/att...4eqc6-t3596180
When that didn't work, I used these files: https://forum.xda-developers.com/att...build-t3576469
Same bootloop, and still impossible to boot into recovery via power+vol up+home.
You might ask, why don't you repair it under warranty?
Well, I live in france and samsung france refuses to even touch an american device!
Ps: here are the options I had ticked in odin:
1st time: F reset and re-partition
2nd flash: NAND erase, F reset and re-partition
3rd flash: bootloader update, NAND erase, F reset and re-partition
Here is a log, md5 checks included, in case you wonder:
<ID:0/006> 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..
<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/006> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> userdata.img
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I would greatly appreciate your help as I'm lost,
Many thanks in advance,
nxss4
which model do you have? you might have erased your EFS And imei and did you use a pit file when you flashed?
MjdHa or MjdHa1 said:
which model do you have? you might have erased your EFS And imei and did you use a pit file when you flashed?
Click to expand...
Click to collapse
Hello, and thank you for replying!
Yes, I used a pit file, it's a G928A (att).
I saw this was a risk when using nand erase all, but I just want it to show some signs of life again before doing hardware repairs.
I will very probably buy a new motherboard anyway. If possible I'd like to put a G928F motherboard into my G928A, this should be possible, right?
In this case I could install samsungs stock firmware and have better developer support.
Thank you in advance,
Try flashing su..... I guess you have drk damaged
You can simply send the device to USA's Samsung's warranty repair center.. Of course Samsung France won't touch it, they're only familiar with devices that originated from France and no where else..
Samsung USA won't touch a French device or any others that wasn't originally one from here, since they won't have the resources or knowledge to fix it.
It just makes sense this way, especially with phones like the S6, which have 16 or so variants, that differ mostly due to region/carrier specs. Not to mention access to all the various firmware for each specific phone/carriers..
It just wouldn't be cost effective or sensible if each repair center worldwide has the ability to repair a different regions device, considering they may get a handful of handsets for repair from other regions.
Its kind of silly to think otherwise...
At this point however, not sure whether your device still falls within their warranty restrictions w/ all the flashing you've done?
Too bad, Id go w/ the warranty claim every time, if it's available, heck some of us pay extra money to have extended coverage, as a "safety net.."
InkTry install twrb using download mod after that wipe every thing and then install any coustom rom after installing the rom make sure install DM virety zip this important step after that hit reboot and see if loop again
The second way is to install the stock firmware and then go into download mod and install twrb after that reboot to recovery again and then install DM virety zip and when finish hit reboot and see if loop
I hope works for u
"Only officially released binaries..." error and I can't flash the stock firmware
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<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/005> Odin engine v(ID:3.1100)..
<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> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<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 complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,
twinsniper said:
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<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/005> Odin engine v(ID:3.1100)..
<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> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<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 complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,
Click to expand...
Click to collapse
For starters use latest Odin 3.13.1 it supports the lz4 compression.
Device 3 binary 2 error means you are trying to flash early version firmware use the same or later version firmware
Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.
twinsniper said:
Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.
Click to expand...
Click to collapse
Glad you got sorted out.
I am aware of the new firmware with ver3 bootloader it has been out for a while. Samfirm is probably the best for latest versions. I am using XSA (Australian unbranded) firmware i try not to use branded firmware like Telstra,Optus or Vodafone.
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