Related
My cousin just got me a new S7 Edge from Shanghai/Hong Kong/Singapore, somewhere like that where he goes for holidays.. Two problems.
First.
It's not remembering the wifi password after a restart. I checked and this seems to be an issue after rooting. Checked, its not rooted BUT it has a "custom" firmware on it.
When the phone boots up, it says Custom with an unlocked logo on it. In download mode, it says custom instead of official. Smart Switch doesn't support this phone model. SM-G935V.
Second issue.
What is the phone model? On the box it says SM-G935F. On Smart Switch and Internal it detects it as SM-G935V. In download mode its says SM-G935A. Checked with CPU Z, its a Snapdragon 820. So, it's obviously the U.S Verizon model that I got. I tried using odin to restore firmware for SM-G935F and V, it gives me. FAIL! SHA256 is invalid. Trying the Samsung G935X_QC_Rooted_Boot.tar method gives the same error code.
In Root Checker, the bootloader is G935AUCS4API2, that's for AT&T. Display and other firmware infos that I'm not familiar with are for G935VVRU2APB5, and that's for verizon. What is this bull****?
How do I fix this? Everything works fine. Except the wifi issue and the "custom" firmware that's on it that's not updating or giving me the ability to root to fix the wifi issue.
Download Samsung info from playstore check your pda, csc, etc... Save screen shots of those as wrong things might happen later, check updato for that specific firmware, double check that firmware csc with yours, flash using odin then reroot
Sent from my SM-G935F using Tapatalk
Alright. I found this thread and this software seems to work on this shanghai phone with a At&t bootloader and a verizon model and firmware. Weird thing. Its now working. Wifi issue fixed. So now, I'll try and flash an international firmware on it to see how of it works. Will update.
Update: Found this. Installed it and it worked. No carrier bloatware or bootscreen. Great. Hopefully this will help anyone in the future with the same issue.
Hi,
I am trying to update my Samsung S6 Edge + (5.1.1 lolipop) to Nougat 7.0.
Phone Specs:
Android: 5.1.1
Baseband: G928AUCU2AOJ1
Build Number: LMY47X.G928AUCU2AOJ1
I have downloaded Nougat firmware SS-G928AUCS4CQB2-to-U4EQC6-UP.
But I can't update my phone to Nougat. I have read many post on net about updating the phone. But its not working.
I have tried Odin different version, 3.10.6, 3.10.7, 3.12.3 but non able to update the phone.
The lower version of Odin mostly crashes when Start button is clicked. I have to close Downloading screen and again go to Downloading screen on phone to go a little further but it isn't doing anything.
Mostly it stuck at 'Nand write Start' and freezes for every.
I have download the PIT file as well to use in Odin, but nothing.
I am on Windows 10, using high quality USB cable, also tried different USB ports. But update process not completing.
So please tell me what to do, is there any better Nougat Firmware that i should use (for SM-G928A)?
Btw, do i have to root my phone, that is what I have not done, is it necessary? If it is please guide be the proper way for s6 edge+.
I am really looking to some help here.
Thanks in advance.
gurupak said:
Hi,
I am trying to update my Samsung S6 Edge + (5.1.1 lolipop) to Nougat 7.0.
Phone Specs:
Android: 5.1.1
Baseband: G928AUCU2AOJ1
Build Number: LMY47X.G928AUCU2AOJ1
I have downloaded Nougat firmware SS-G928AUCS4CQB2-to-U4EQC6-UP.
But I can't update my phone to Nougat. I have read many post on net about updating the phone. But its not working.
I have tried Odin different version, 3.10.6, 3.10.7, 3.12.3 but non able to update the phone.
The lower version of Odin mostly crashes when Start button is clicked. I have to close Downloading screen and again go to Downloading screen on phone to go a little further but it isn't doing anything.
Mostly it stuck at 'Nand write Start' and freezes for every.
I have download the PIT file as well to use in Odin, but nothing.
I am on Windows 10, using high quality USB cable, also tried different USB ports. But update process not completing.
So please tell me what to do, is there any better Nougat Firmware that i should use (for SM-G928A)?
Btw, do i have to root my phone, that is what I have not done, is it necessary? If it is please guide be the proper way for s6 edge+.
I am really looking to some help here.
Thanks in advance.
Click to expand...
Click to collapse
Try this :
https://docs.google.com/uc?id=0B4sOy1rlqVoYcVZIWUN6U0h5VUE&export=download
Thank you for the firmware. I am trying it on phone now. But it is everytime stuck on File Analysis:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
I am using Odin 3.12.3. What is blocking it?
Best regards,
Is there any other way then Odin to install the firmware on s6 edge plus?
I recently discovered the hard way that S7s have version fuses. These prevent you from installing certain older firmwares. This is convenient for Sprint as it prevents you from switching your SM-G930P to another carrier.
If you look at a Samsung firmware's release ID, such as G930UUEU4BQJ5, look at the 5th place from the right, in this case a 4. That is what I'm calling the firmware version.
I am on Sprint, and that carrier incremented its firmware version to 5 starting with QJ3 (Nov. 12, 2017). See https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/ for a firmware list.
A few weeks after that, I tried changing my phone from the Sprint SM-G930P to the unlocked SM-G930U. If you check https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/, you'll see that all variants of the U were and still are on firmware version 4. Also, T-Mobile is on 4, Verizon is on 4, and AT&T is on 4. (Why is AT&T's SM-G930A not on sammobile.com?)
Anyway, I got this error during the SM-G930U firmware install: SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4.
Not appreciating what this meant at the time, I managed to get the CP (modem software) from the SM-G930U on my phone as I tried the four files one at a time. It turns out you can put some older software on the phone. However, you need to have your current firmware around so that you can put things back if they don't work. Unfortunately for me, the firmware download for SM-G930P (Sprint) QJ3 didn't become available for about a week after I did this. I couldn't use a prior Sprint firmware because all before QJ3 had a lower firmware number. While the phone worked fine with this version mismatch, I had to endure repeated Knox security warning messages.
I since put the phone back on the SM-G930P firmware (once QJ3 became available for download!), and everything's happy now. No warranty fuse issues or anything, and I'm two OTA releases newer now than QJ3.
A more detailed write-up is here: https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/
I may not be searching on the right keywords, but I can't find anyone else reporting this. As mentioned at top, it's really convenient for Sprint that it incremented its firmware version. This lock out Sprint S7 owners from switching to another carrier. I can assure that you really need to change firmware to do that: I switched to T-Mobile for one month over the summer but kept the Sprint firmware on the (unlocked!) Sprint phone. Several bands were missing until I switched to the T-Mobile firmware. For now, Sprint S7 owners cannot do that unless there is some way to increment the firmware version number, but even then, I'd guess we'd have trouble installing the other carrier's OTA updates.
All US model S7s (Snapdragon) have locked bootloaders, this is why you cannot downgrade to older firmware
*Detection* said:
All US model S7s (Snapdragon) have locked bootloaders, this is why you cannot downgrade to older firmware
Click to expand...
Click to collapse
Is that version number (5 digit from right on version string) really for the bootloader version?
novasource said:
Is that version number (5 digit from right on version strong) really for the bootloader version?
Click to expand...
Click to collapse
Not sure what the numbers / letters mean in firmware versions
But that's the reason you can't downgrade
*Detection* said:
Not sure what the numbers / letters mean in firmware versions
But that's the reason you can't downgrade
Click to expand...
Click to collapse
Still, you typically don't downgrade to switch carriers (I didn't going from VZW to T-Mobile, for example)
(I was avoiding a network lock due to shens of the previous owner of the handset -hence the move to the UnCarrier from BigRed) - I also gained VoLTE and wi-fi calling; neither of which I could have kept on BigRed for some rather odd reason).
PGHammer said:
Still, you typically don't downgrade to switch carriers (I didn't going from VZW to T-Mobile, for example)
Click to expand...
Click to collapse
You are generally correct when it comes to Android software version (occasionally, you may need to jump back a minor Android release or two if the carrier you're going to isn't as up to date on releases as the carrier you're coming from).
However, Android software is just one of four files in a firmware package. The problem is the version number embedded in the firmware package itself, which might correspond to the bootloader version. This number prevents Sprint S7 owners from going to any other firmware: at this point as it appears that Sprint is the only one whose firmware (or bootloader?) version is at 5. All others appear to be 4 or lower.
The 4 and the 5 is the binary correct? I'm assuming that because that's where Odin always has the problem when I was pointlessly trying to root my SM-G935P on QL1 firmware.
Brianmagoon said:
The 4 and the 5 is the binary correct? I'm assuming that because that's where Odin always has the problem when I was pointlessly trying to root my SM-G935P on QL1 firmware.
Click to expand...
Click to collapse
The 4 and 5 are numbers I see in the firmware version strings that may correspond to the bootloader version. Regardless, if you've installed a firmware with a 5 in that version digit, then you cannot install any firmware with a lower version. So if you are on a Sprint-branded S7 and up to date, then you cannot install any other firmware until they also have a 5 in the firmware version string.
Yeah that sucks. I was really looking forward to rooting this beast. Looks like that won't be happening any time soon
Nobody incremented their bootloader revision except Sprint.
Everyone is still on bootloader 4 (VZW/ATT/TMO)
Sprint is now on bootloader 5
Also, none of this is a downgrade, they released identical versions with different bootloader revision
Example
Latest Sprint software
G930PVPU5BQL1
Latest OEM software
G930UUES4BQL1
They are basically identical softwares
This was done intentionally to stop unbranded G930U flashing which also results in European LTE bands 3/7/20 to be enabled
Sprint does not want these items to leave the United States.
sins07 said:
...
Also, none of this is a downgrade, they released identical versions with different bootloader revision
...
This was done intentionally to stop unbranded G930U flashing which also results in European LTE bands 3/7/20 to be enabled
Sprint does not want these items to leave the United States.
Click to expand...
Click to collapse
Confirms my suspicion, if you are sure the binaries are functionally the same.
Sadly I just picked up a sprint 7 edge last night with oct 1 2017 patch ..I neglected to do my homework on this device and of course its on 5b ..does anyone know the possibility or likeliness that other carriers would feel the need to go to 5B
Sincerely,
A screwed buyer
So question.. how did you manage to get the image for the S7 930P? I tried two different 930U images and now left with a cycling device. I can't seem to download the 930P image using sammobile. I've tried 4 different sites. Some say free downloads for 2gb or less and the image size is 2.3gb. Any working link would be greatly appreciated.
Hey Guys, I have the tmobile version and went through this when the phone first came out. I am rather certain that number does correspond to the bootloader version. At the time I wanted to install the U firmware on my stock tmobile phone and couldn't because tmobile version had a higher bootloader version. At the time tmobile was the only one with the higher bootloader iirc. Eventually all the carriers, including U, caught up to tmobile and I was able to downgrade.
Hey, would you gents mind helping me out. I had a failed root attempt, and ****s been a little crazy with my 930p. Currently I get this while trying to get back to anything which will make my phone work. I understand about the SW versions, and F sprint for that. However, would any of you be so kind as to simply tell me which files I need to get this thing to not be in a constant state of boot loading either in recovery or anything else. I get this on the download screen SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4 while Odin says this:
<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> emmc_appsboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth
tonysak said:
Hey, would you gents mind helping me out. I had a failed root attempt, and ****s been a little crazy with my 930p. Currently I get this while trying to get back to anything which will make my phone work. I understand about the SW versions, and F sprint for that. However, would any of you be so kind as to simply tell me which files I need to get this thing to not be in a constant state of boot loading either in recovery or anything else. I get this on the download screen SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4 while Odin says this:
<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> emmc_appsboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth
Click to expand...
Click to collapse
Had the same issue. After much trial and error (and a few boot loops and soft bricks) I was able to get the phone back to factory with firmware G930PVPU5BQL1 from another site (not sure if I'm allowed to link, but it has the words Samsung and firmware in the address, and it's a .org). Make sure you factory reset and wipe cache afterwards in recovery (hold power, home, volume up), and I'd recommend flashing the CSC rather than HOME_CSC to avoid duplicates in the settings menu. I unchecked auto reboot in Odin to make it easier to get to recovery without having to watch the whole install like a hawk. Also, don't sweat it if you get "Installing system update" and then "No command" when you boot into recovery mode. Just wait for a few minutes and it'll take you to the recovery menu. After the factory reset and cache partition wipe, you should be able to reboot and be have a squeaky clean install. YMMV but it worked for me. Good luck.
jessemcstew said:
Had the same issue. After much trial and error (and a few boot loops and soft bricks) I was able to get the phone back to factory with firmware G930PVPU5BQL1 .
Click to expand...
Click to collapse
Wanted to say thanks. I've been struggling with this issue for a couple of weeks on and off as I play with this S7. Really frustrating to be on my like 8th firmware download and still running into issues prior to the above.
Now that I have the phone back up and running, anyone know how to move to stock non-sprint android given the issues with the sprint bootloader? My preference would be to debloat and de-gaps but from all the reading in the past week or so it doesn't sound likely.
My hope was that given the rollout of oreo now that someone would have a v5 bootloader for sm-930U (generic S7 - non carrier version)
schmism said:
My hope was that given the rollout of oreo now that someone would have a v5 bootloader for sm-930U (generic S7 - non carrier version)
Click to expand...
Click to collapse
Your hopes are likely dashed.
1. Every US carrier has updated to Oreo and none of them have updated the bootloader to v5, except for Sprint. So if you have the latest Sprint firmware, you can't switch to anything else.
2. As of this writing, the US unlocked version (SM-930U) still has not been updated to Oreo. There is no announcement when it will be released. And there is no reason to think it will be v5.
Friends, until there is an upgrade to the bootloader of the G930U Firmware, i believe it is not possible to convert the sprint device with binary 5 to G930U
At the moment, what seems to work is doing it via flashfire. There is a tutorial posted on the youtube link here
No Samsung Apps
borispavlov said:
Friends, until there is an upgrade to the bootloader of the G930U Firmware, i believe it is not possible to convert the sprint device with binary 5 to G930U
At the moment, what seems to work is doing it via flashfire. There is a tutorial posted on the youtube link here
Click to expand...
Click to collapse
Yes, but you will see on their linked site that Samsung Apps will not run on this version. Probably should wait if you care about this.
Android o just got released for the snapdragon s7! For anyone who wants to try it just flash the latest att firmware in Odin and then follow this guide.
https://www.xda-developers.com/how-...id-oreo-on-the-att-samsung-galaxy-s7-s7-edge/
I'm running this right now and it runs great(so far).
Newest att firmware(G930AUCS4BRA1 7.0):
http://www.mediafire.com/file/w34d7kwkx33rudc/G930AUCS4BRA1.zip
Mirror: https://drive.google.com/file/d/1OyuqyUWavoLFgHm44wBPErGRfapdwyQi/view?usp=sharing
Prince Comey Odin(for flashing att firmware)
https://androidfilehost.com/?fid=24591023225177749
Ota updates:
https://forum.xda-developers.com/at...ate-ss-g930aucs4bqj2-to-u4bqk2-t3716713/page1
oreo update:
https://samsung.firmware.science/download?url=48782/1488/SS-G930AUCS4BRA1-to-U4CRC1-UP(SS-G930AUCS4BRA1-to-U4CRB9-UP)
https://drive.google.com/uc?id=1GrWaV21O_loNsZzPIcy6YlhgIX4UJRh6&export=download (G930AATT4BRA1_to_G930AATT4CRC5)
Thanks to @MastahMatt for uploading the G930AATT4CRC5 firmware
https://drive.google.com/file/d/1aS-C2Qs0033hFNsKw_8Hm0wcIOnbP_kw/view?usp=drivesdk (D1)
https://drive.google.com/file/d/1OMYnr9HL2AecmxGUQjGp4tJt5j3vwUUI/view (D4)
https://drive.google.com/open?id=1x_si51aVVipoc9YdPcOohYzsrnP1bBJn (D6)
HOW TO FIX THE HEART RATE SENSOR:
Go into Samsung health click the heart rate tab (not measure) and select the 3 dots in the corner and click quick measure then turn it on.
- found this in a comment by joshua jesse
Recovery/returning to 7.0:
odin SM-G930U_1_20170516105039_fspus9jwu3_fac.zip (with prince comsey odin)
download verizon wireless software upgrade tool, restore to U variant firmware it offers (in this case BRA1)
odin G930VVRS4BRA1_G930VVZW4BRA1_VZW
- thanks @djh816 for the recovery guide.
Misc info:
There is a really annoying bug, whenever you touch the heart rate sensor it lights up.
This is only for snapdragon variants of the s7 (should work on most snapdragon variants).
I've been running this for a bit now and its still running smooth!
This thread is in the wrong section.
Screenshots in next post.
@jrkruse released an Oreo ROM (https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3757884).
There is a way to bypass a factory reset when updating through an ota (https://pastebin.com/pNKQrfva).
Screenshots:
turnert said:
Android o just got released for the snapdragon s7! For anyone who wants to try it just flash the latest att firmware in Odin and then follow this guide.
https://www.google.com/amp/s/www.xd...reo-on-the-att-samsung-galaxy-s7-s7-edge/amp/
I'm running this right now and it runs great(so far).
Click to expand...
Click to collapse
this work on verizon variant?
turnert said:
Android o just got released for the snapdragon s7! For anyone who wants to try it just flash the latest att firmware in Odin and then follow this guide.
https://www.google.com/amp/s/www.xd...reo-on-the-att-samsung-galaxy-s7-s7-edge/amp/
I'm running this right now and it runs great(so far).
Click to expand...
Click to collapse
But can you use the phone (as a phone) afterward on VZW? Or must you leave your (VZW) SIM out of the phone?
PGHammer said:
But can you use the phone (as a phone) afterward on VZW? Or must you leave your (VZW) SIM out of the phone?
Click to expand...
Click to collapse
I haven't tried mine is blacklisted.
You can still take it another carrier - mine was blacklisted on VZW; however, I took it to T-Mobile (Tracfone uses both tower providers - which is why it works), so you could take it either to T-Mobile directly, or to Tracfone and use a T-Mo nano-SIM. However, you need a proper T-M firmware - and this is not it.
PGHammer said:
You can still take it another carrier - mine was blacklisted on VZW; however, I took it to T-Mobile (Tracfone uses both tower providers - which is why it works), so you could take it either to T-Mobile directly, or to Tracfone and use a T-Mo nano-SIM. However, you need a proper T-M firmware - and this is not it.
Click to expand...
Click to collapse
Then I will give it a try with my T-Mobile simcard
ebravo01 said:
this work on verizon variant?
Click to expand...
Click to collapse
Yes
Geekbench 4:
turnert said:
Yes
Click to expand...
Click to collapse
No work for my, i have 7 error status.
ebravo01 said:
No work for my, i have 7 error status.
Click to expand...
Click to collapse
Probably means your not on the newest version of the att firmware. I couldn't find the newest version of the art firmware so I manually updated to the newest version
The Deadly Oreo Cookie on the UnCarrier - Just How Tasty Is It?
turnert said:
Probably means your not on the newest version of the att firmware. I couldn't find the newest version of the art firmware so I manually updated to the newest version
Click to expand...
Click to collapse
I started with BQE1, then applied all the updates from there to BRA1 (in order) via SD card (which is the easiest way, despite the number of such updates - seven altogether not counting the Oreo OTA). Each update will wipe your data, so don't bother to go through the new-customer steps in between; instead, simply reboot back into recovery and apply the next update in the series. Also, if you have a carrier OTHER than AT&T, make sure your SIM is not in the phone and don't put it back INTO the phone until after you apply the Oreo OTA - why take chances?
PGHammer said:
I started with BQE1, then applied all the updates from there to BRA1 (in order) via SD card (which is the easiest way, despite the number of such updates - seven altogether not counting the Oreo OTA). Each update will wipe your data, so don't bother to go through the new-customer steps in between; instead, simply reboot back into recovery and apply the next update in the series. Also, if you have a carrier OTHER than AT&T, make sure your SIM is not in the phone and don't put it back INTO the phone until after you apply the Oreo OTA - why take chances?
Click to expand...
Click to collapse
I had to do the same thing, took me about 2 hours to do. would you mind linking the updates for anyone else trying to do it?
turnert said:
I had to do the same thing, took me about 2 hours to do. would you mind linking the updates for anyone else trying to do it?
Click to expand...
Click to collapse
The list of updates are in the AT&T Samsung S7 forum (which is where I found them); the two hours is correct, too. While I started with a full charge, the two-hour stretch sapped half the charge in addition to the two hours of time. It is (altogether) seven updates (not counting the Oreo OTA). Starting from BQE1 (where I began) the Updates are to (in order) U4BQF3, U4BQG1, S4BQH1, S4BQJ2, U4BQK2, S4BQL1, AND S4BRA1.
PGHammer said:
I started with BQE1, then applied all the updates from there to BRA1 (in order) via SD card (which is the easiest way, despite the number of such updates - seven altogether not counting the Oreo OTA). Each update will wipe your data, so don't bother to go through the new-customer steps in between; instead, simply reboot back into recovery and apply the next update in the series. Also, if you have a carrier OTHER than AT&T, make sure your SIM is not in the phone and don't put it back INTO the phone until after you apply the Oreo OTA - why take chances?
Click to expand...
Click to collapse
Well sh-t. I tried last night to Odin BRA1 and then throw the Oreo update.zip on my SD card and I kept getting some error in recovery saying something like "Unable to apply update from external storage". Trying to select ADB gave me a similar error. So I had to immediately go back and restore all my stuff. I think I'm just going to wait for someone to make a convenient method for us to get to Oreo on Verizon.
How is it though?
How do i roll back to Verizon stock or 930U? I was on Verizon 930U and installed latest at&t but Oreo update failed. I cannot go back to any 930U or Verizon stock. Only AT&T flash via Odin works.
For Verizon Stock install I get this error in Odin
<ID:0/009> Odin engine v(ID:3.1207)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
For 930U i get the below error.
<ID:0/009> FAIL! Model dismatch fail
Click to expand...
Click to collapse
matrixddl said:
How do i roll back to Verizon stock or 930U? I was on Verizon 930U and installed latest at&t but Oreo update failed. I cannot go back to any 930U or Verizon stock. Only AT&T flash via Odin works.
For Verizon Stock install I get this error in Odin
For 930U i get the below error.
Click to expand...
Click to collapse
That is an error I have seen myself - it means that your download that you are trying to install has issues (that was the case with with my attempted download of the full BRA1 firmware); it is why I wound up going the multiple-OTA route instead. If you truly want to go back to SM-G930V, download the latest such via updato.com (faster than SamMobile by far).
---------- Post added at 11:53 PM ---------- Previous post was at 11:39 PM ----------
DildoMaster said:
Well sh-t. I tried last night to Odin BRA1 and then throw the Oreo update.zip on my SD card and I kept getting some error in recovery saying something like "Unable to apply update from external storage". Trying to select ADB gave me a similar error. So I had to immediately go back and restore all my stuff. I think I'm just going to wait for someone to make a convenient method for us to get to Oreo on Verizon.
How is it though?
Click to expand...
Click to collapse
The ODIN BRA1 had issues for me as well - which is why I went how I went (BQE1 and the seven OTAs). No - it's not easy (it takes two hours and - from a full charge - it will easily eat half the charge even if you stay connected to a PC for MTP - which is what I did). Still, it's as smooth as, if not smoother than, Project_L V.4 (which is what it replaced) which I did not expect (even though it's not a fusion firmware, which L is). Also, it confirms what I had seen in O elsewhere; O is quicker than N on the same hardware. Also, I'm not looking to "fire" the Cookie any time soon - it would, at this point, require an UnCarrier-specific version of the Cookie for the S7 to displace it, as this AT&T version works just fine, even though it is technically working on the *wrong* carrier (I have my Tracfone/UnCarrier nano-SIM in my phone, and only lost VoLTE - which I never used; you can get Vo-WiFi back via a Settings option).
PGHammer said:
That is an error I have seen myself - it means that your download that you are trying to install has issues (that was the case with with my attempted download of the full BRA1 firmware); it is why I wound up going the multiple-OTA route instead. If you truly want to go back to SM-G930V, download the latest such via updato.com (faster than SamMobile by far).
Click to expand...
Click to collapse
I used the same 930U to flash from 930V. How could it be corrupted?
Is downgrade possible? Because latest at&t installed today is from Feb 18 and 930U/930V are from Jan 18.
matrixddl said:
How do i roll back to Verizon stock or 930U? I was on Verizon 930U and installed latest at&t but Oreo update failed. I cannot go back to any 930U or Verizon stock. Only AT&T flash via Odin works.
For Verizon Stock install I get this error in Odin
For 930U i get the below error.
Click to expand...
Click to collapse
Use the prince Comsy version of Odin
turnert said:
Use the prince Comsy version of Odin
Click to expand...
Click to collapse
It worked. Thank. Should i use prince Comsy Odin for future/930U flashes also?
I have a TracFone S8+. I recently flashed it with the Verizon combination and stock firmware. Now, whenever I'm trying to flash it to anything, I either
get stuck at SetupConnection for a while before getting "All threads completed success 0 / failed 1", or
get the Complete(Write) error
I tried the method where I click the start button before immediately entering download mode. That did nothing. I also tried flashing it again with both Verizon and Tracfone files. Neither succeeded. I used different versions of Odin, as well as the Prince and the new patched editions. My phone is working fine, but I'm worried that problems may arise by not having the original carrier's firmware, esp. when I still have TracFone as my carrier.
gladiatorland said:
I have a TracFone S8+. I recently flashed it with the Verizon combination and stock firmware. Now, whenever I'm trying to flash it to anything, I either
get stuck at SetupConnection for a while before getting "All threads completed success 0 / failed 1", or
get the Complete(Write) error
I tried the method where I click the start button before immediately entering download mode. That did nothing. I also tried flashing it again with both Verizon and Tracfone files. Neither succeeded. I used different versions of Odin, as well as the Prince and the new patched editions. My phone is working fine, but I'm worried that problems may arise by not having the original carrier's firmware, esp. when I still have TracFone as my carrier.
Click to expand...
Click to collapse
Nothing bad should happen service wise. A lot of tracphone uses Verizon towers. As long as you download the TracFone apps.
Ok first off.
The combination is a multi carrier firmware. It is test firmware from Samsung not the carrier. So when you flashed that and then switched to Verizon that set Verizon as the CSC.
What you are looking for is a TracFone CSC from your current firmware version 5th digit back from far end is a 1 through 5. That determines the revision. This could cause a Odin failure. If it's lower than current.
So now that's some what explained.
If you can find that revision of firmware's CSC file you can flash that in Odin with your tracfones sim installed and it should revert back to TracFone if you think it's nessicary. If your on the newer 8.0 firmwares you need that modded Odin 3.12b I think. Those firmware are in a different file type. Not .tar files. So that will cause a fail too.
I'm always around if all those check out we can go from there:good:
There is also a dialer code to select csc but I think hidden menus are disabled on Verizon.
Lss all the firmwares are identical for all the us models. They all have identical hardware.
Pretty much what determines anything is the csc file
Thank you for your help! It's invaluable.
Okay, so I found Verizon's firmware to be G955UOYN2CRB9. However, Tracfone's is G955USQU5CRL2. If the number before the C is indeed the bootloader version, then that means I'm trying to upgrade from 2 to 5. Is that possible?
gladiatorland said:
Thank you for your help! It's invaluable.
Okay, so I found Verizon's firmware to be G955UOYN2CRB9. However, Tracfone's is G955USQU5CRL2. If the number before the C is indeed the bootloader version, then that means I'm trying to upgrade from 2 to 5. Is that possible?
Click to expand...
Click to collapse
Yes. You just can't go back to the revision 2 firmware after. You can upgrade just not downgrade
TheMadScientist said:
Yes. You just can't go back to the revision 2 firmware after. You can upgrade just not downgrade
Click to expand...
Click to collapse
Okay, now I'm seriously boggled. When I go to Software Update section in settings, it tells me that the current version is indeed G955USQU5CRL2/G955UOYN5CRL2/G955USQU5CRL2. Even though the last successful flash was Verizon. Do you know what could've happened here!? And why I still get an error when I flash the phone with TracFone firmware?
I have a Verizon phone with Verizon firmware and the 5th digit from the right is a 5. It appears you have Verizon firmware flashed on your phone
Sent from my SM-G950U using Tapatalk
djm1947 said:
I have a Verizon phone with Verizon firmware and the 5th digit from the right is a 5. It appears you have Verizon firmware flashed on your phone
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
Interesting. When I visited SamMobile's page for G955U, I found that PDA associated with TracFone as well.