Hey.
Has anyone been able to get the U firmware working on a Tmobile s7 edge? I got an error along the lines of "sw rev check fail fused 3 binary 2".
Thanks.
Sent from my SM-G935T using Tapatalk
Are you on the latest security update? I think the U firmware is patched up to May or so, these device bootloaders won't allow downgrading, maybe with the eng boot you can flash it, but from what I've been reading there's no going backwards, only flashing of the same updates or future.
Dark Nightmare said:
Are you on the latest security update? I think the U firmware is patched up to May or so, these device bootloaders won't allow downgrading, maybe with the eng boot you can flash it, but from what I've been reading there's no going backwards, only flashing of the same updates or future.
Click to expand...
Click to collapse
Ok, so if the U firmware gets updated, will i be able to flash it then?
Thanks.
Sent from my SM-G935T using Tapatalk
I would assume so since they usually have the base the same, the V and other software versions are able to use it, so we should be too once it's on the same update level.
Dark Nightmare said:
I would assume so since they usually have the base the same, the V and other software versions are able to use it, so we should be too once it's on the same update level.
Click to expand...
Click to collapse
Awesome, thank you!
I'll just have to figure out when the U firmware gets updated to the July patch. I'm a bit surprised that T-Mobile is ahead of the U firmware. Any idea why that is?
Sent from my SM-G935T using Tapatalk
I think we're all surprised really, lol, but they missed us on the May patch, so we jumped straight to our current update. U isn't as popular as the carrier versions in the US, so that may also explain the slower updates.
Dark Nightmare said:
I think we're all surprised really, lol, but they missed us on the May patch, so we jumped straight to our current update. U isn't as popular as the carrier versions in the US, so that may also explain the slower updates.
Click to expand...
Click to collapse
Oh. I was thinking of flashing U to get quicker updates, I didn't think they would be slower. I heard N is dropping today, and I want it ASAP.
Sent from my SM-G935T using Tapatalk
nahtnam said:
I heard N is dropping today, and I want it ASAP.
Click to expand...
Click to collapse
I want a blonde with a large chest and a butt that tastes like french vanilla ice cream. Don't expect N for a few months.
entropism said:
I want a blonde with a large chest and a butt that tastes like french vanilla ice cream. Don't expect N for a few months.
Click to expand...
Click to collapse
Of course, but I'd rather wait 3 months than 5.
Sent from my SM-G935T using Tapatalk
Dark Nightmare said:
Are you on the latest security update? I think the U firmware is patched up to May or so, these device bootloaders won't allow downgrading, maybe with the eng boot you can flash it, but from what I've been reading there's no going backwards, only flashing of the same updates or future.
Click to expand...
Click to collapse
Ok, so it looks like the August patch just dropped for the U firmware. So theoretically, will I be able to flash that now?
Also, in firmware zips, I always see a CSC and a HOME_CSC. What is the difference? Which should I use if I want to have a full and complete flash?
Thanks.
Sent from my SM-G935T using Tapatalk
nahtnam said:
Ok, so it looks like the August patch just dropped for the U firmware. So theoretically, will I be able to flash that now?
Also, in firmware zips, I always see a CSC and a HOME_CSC. What is the difference? Which should I use if I want to have a full and complete flash?
Thanks.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Please let us know how flashing the new August U firmware goes for you. It does look like the new U devices are now on the V2 bootloader.
I have an official SM-G935U and after the update it says on the bootloader page RP SWREV: B2(2, 1, 1, 1, 1) K1 S1. My hope is that at some point I can flash the official T-Mo firmware to my G935U if the G935U falls behind in updates again.
CSC will wipe the device. HOME_CSC will not wipe the device, from what I understand.
tublah said:
Please let us know how flashing the new August U firmware goes for you. It does look like the new U devices are now on the V2 bootloader.
I have an official SM-G935U and after the update it says on the bootloader page RP SWREV: B2(2, 1, 1, 1, 1) K1 S1. My hope is that at some point I can flash the official T-Mo firmware to my G935U if the G935U falls behind in updates again.
CSC will wipe the device. HOME_CSC will not wipe the device, from what I understand.
Click to expand...
Click to collapse
Isn't the T-Mobile firmware on version 3 bootloader? That means the flash from T-Mobile to U won't work. BTW, I've already flashed from U to T-Mobile. I would not recommend flashing the Tmobile firmware because I still don't think it's possible to go back to U.
Sent from my SM-G935T using Tapatalk
nahtnam said:
Isn't the T-Mobile firmware on version 3 bootloader? That means the flash from T-Mobile to U won't work. BTW, I've already flashed from U to T-Mobile.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Not sure. What do your device show when you boot to download/bootloader mode?
EDIT: are you saying that you have an official SM-G935U that you flashed to T-Mobile's firmware and are now stuck on T-mobile's firmware -- and that you're trying to get back?
tublah said:
Not sure. What do your device show when you boot to download/bootloader mode?
EDIT: are you saying that you have an official SM-G935U that you flashed to T-Mobile's firmware and are now stuck on T-mobile's firmware -- and that you're trying to get back?
Click to expand...
Click to collapse
I get: AP SWREV: B3(2, 1, 1, 1, 1) K1 S2
EDIT: I have a Verizon S7 Edge which I flashed U firmware onto. Then I flashed T-Mobile's firmware and now I'm stuck. I want to get back to U.
nahtnam said:
I get: AP SWREV: B3(2, 1, 1, 1, 1) K1 S2
EDIT: I have a Verizon S7 Edge which I flashed U firmware onto. Then I flashed T-Mobile's firmware and now I'm stuck. I want to get back to U.
Click to expand...
Click to collapse
Ah, then yeah - it looks like everyone aside from T-mobile are on V2 still. Sorry to have gotten your hopes up!
tublah said:
Ah, then yeah - it looks like everyone aside from T-mobile are on V2 still. Sorry to have gotten your hopes up!
Click to expand...
Click to collapse
No problem. Hopefully the U firmware will eventually upgrade to bootloader version 3. I'm kind of scared that it may never be updated because T-Mobile updated it with the July patch, and the U firmware is already at August.
nahtnam said:
No problem. Hopefully the U firmware will eventually upgrade to bootloader version 3. I'm kind of scared that it may never be updated because T-Mobile updated it with the July patch, and the U firmware is already at August.
Click to expand...
Click to collapse
I tried to flash the latest U firmware on my G935T without success though. It stuck at the beginning and I had to restore it using "Switcher". It might happened because I checked "re-partition in Odin.
mishastr said:
I tried to flash the latest U firmware on my G935T without success though. It stuck at the beginning and I had to restore it using "Switcher". It might happened because I checked "re-partition in Odin.
Click to expand...
Click to collapse
When did you try doing this?
Yesterday, about 1 p.m. EST
It looks like mine has BL 3 when the U firmware comes with BL2.
It's really sad but there is no way to flash it on my device.
God, this is a little infuriating. Why is the T-Mobile variant the only one on this new version of bootloader? This T-Mobile S7 is now officially more locked down than even the Verizon or AT&T variant, that's insane.
Related
I have a g930a with the basband version G930AUCS4APK1 and I have done all OTA updates.
Is it still rootable? Am I on the new bootloader?
Root???
FreshIce21 said:
I have a g930a with the basband version G930AUCS4APK1 and I have done all OTA updates.
Is it still rootable? Am I on the new bootloader?
Click to expand...
Click to collapse
THAT is an EXCELLENT question...
FreshIce21 said:
I have a g930a with the basband version G930AUCS4APK1 and I have done all OTA updates.
Is it still rootable? Am I on the new bootloader?
Click to expand...
Click to collapse
go to the root thread, follow the instructions and give it a shot. That's really the best way to find out...just make sure you have the APK1 firmware on standby in case it doesn't turn out well.
SantinoInc said:
go to the root thread, follow the instructions and give it a shot. That's really the best way to find out...just make sure you have the APK1 firmware on standby in case it doesn't turn out well.
Click to expand...
Click to collapse
Pretty much this. Backup files you don't want to lose, download the stock Odin files, and give rooting a shot. Worst case, you just gotta flash stock back via Odin. You may be able to flash an earlier firmware via Odin and root from there. Though I doubt Odin would let you. If I were you, I'd download all the applicable files, backup my data, wait until I've got a good chink of time ithat I don't need my phone and start playing around with it. I had all sorts of complications rooting mine s{ I was phone-less for like an hour
SantinoInc said:
go to the root thread, follow the instructions and give it a shot. That's really the best way to find out...just make sure you have the APK1 firmware on standby in case it doesn't turn out well.
Click to expand...
Click to collapse
where can i find the apk1 firmware?
FreshIce21 said:
where can i find the apk1 firmware?
Click to expand...
Click to collapse
Sammobile.com
Just search by your phones model #.
SantinoInc said:
Sammobile.com
Just search by your phones model #.
Click to expand...
Click to collapse
They don't have any firmware for the att model just USB drivers
Any way to extract the firmware from my phone??
Update 12/6/16
I downgraded to the U firmware (G930UUEU4API3) following the steps here: http://forum.xda-developers.com/att-galaxy-s7/how-to/g930uueu4api3-firmware-download-t3481159
I then rooted using Max Lee's directions and I have root! Haven't tried rooting directly from APK1 firmware
I successfully rooted my G930AUCS4APK1 using princecomsy how to.
http://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538
I'm still trying to learn the nomenclature....so, i'm assuming by the PK1 one part of the version that it is new than PI3?
Just wasn't sure about UUE part. Sorry, noob in this dept.
But, wanted to at least share that I had successful root with OP baseband.
Now to figure out how to make the battery last more than 10hrs and respond a little quicker.
The V15 fix hasn't seem to do much in comparison to stock OTA.
Hope this helps.
bweegn said:
I'm still trying to learn the nomenclature....so, i'm assuming by the PK1 one part of the version that it is new than PI3?
Just wasn't sure about UUE part. Sorry, noob in this dept.
Click to expand...
Click to collapse
(for the others that may not know too)
The last three characters of the release are the ones that matter.
* The P indicates the year (P=16th letter of the alphabet, 2016)
* The K indicates the month (K=11th letter of the alphabet, November)
* The 1 represents the release number (to allow for more than one release each month)
Keep in mind that once you flash a newer firmware on the S7, you cannot go back to an older one. Odin will not let you flash it. Even if you could, it would most likely trip the KNOX flag.
I got the unreleased nougat update 10 days ago from jimmy vb8 and I'm preparing to go back to stock i have all the right files but I'm worried ill brick my phone help
Also I need the pk1 file
Have you even searched for anything to do with your post? I can understand being worried, but theres only about 5 threads that contain the PK1 files.
loganbeck14 said:
I got the unreleased nougat update 10 days ago from jimmy vb8 and I'm preparing to go back to stock i have all the right files but I'm worried ill brick my phone help
Click to expand...
Click to collapse
if you are on the unreleased build, it's the same build AT&T released via OTA, you are on the official build.
Ok I heard that qa6 is the latest and I'm on qa4 will i still get future updates
loganbeck14 said:
Ok I heard that qa6 is the latest and I'm on qa4 will i still get future updates
Click to expand...
Click to collapse
you should, have you tried checking for updates on your device?
Yes
micallan_17 said:
you should, have you tried checking for updates on your device?
Click to expand...
Click to collapse
Is this true? AT&T's OTA for the S7 (Flat) is the same version that I got from the unreleased 7.0 thread?
I bricked my phone trying to go back to PK1, AT&T is sending a warranty replacement but my Wife's phone has this update too. Had I known I wouldn't have even touched it!
So in other words I should be able to receive any future OTA updates right? I should just leave my wife's phone alone?
I appreciate any help.
Thanks!
thegreenfamily04 said:
Is this true? AT&T's OTA for the S7 (Flat) is the same version that I got from the unreleased 7.0 thread?
I bricked my phone trying to go back to PK1, AT&T is sending a warranty replacement but my Wife's phone has this update too. Had I known I wouldn't have even touched it!
So in other words I should be able to receive any future OTA updates right? I should just leave my wife's phone alone?
I appreciate any help.
Thanks!
Click to expand...
Click to collapse
Hi,
If you sideloaded QA4 (or any build) you must Odin back to APk1 and then you can take the att over the air update. Otherwise, it will always say that you are up to date when you check on your phone.
Read the posts in this discussion (although it is for S7 Edge)
https://r.tapatalk.com/shareLink?ur...share_tid=3548594&share_fid=3793&share_type=t
OFFICIAL Nougat files for S7 Edge with February security build BQA6
If you have never updated other than using the att software update function on your phone then the Nougat 7.0 update should be available right now.
Sent from my SAMSUNG-SM-G935A using Tapatalk
---------- Post added at 11:05 AM ---------- Previous post was at 10:52 AM ----------
burrzoo said:
Hi,
If you sideloaded QA4 (or any build) you must Odin back to APk1 and then you can take the att over the air update. Otherwise, it will always say that you are up to date when you check on your phone.
Read the posts in this discussion (although it is for S7 Edge)
https://r.tapatalk.com/shareLink?ur...share_tid=3548594&share_fid=3793&share_type=t
OFFICIAL Nougat files for S7 Edge with February security build BQA6
If you have never updated other than using the att software update function on your phone then the Nougat 7.0 update should be available right now.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
Sorry meant PK1 (not APk1 since you don't have an Edge).
Check out this discussion thread too:
https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168/
Sent from my SAMSUNG-SM-G935A using Tapatalk
Thank you very much! I've got the files, hopefully I can unbrick my damn phone. I have the teal screen triangle of death (Download mode only) and boot loop when I try to get into recovery or just boot the phone normally when I tried to flash the wrong files...
Odin to the rescue hopefully.
thegreenfamily04 said:
Thank you very much! I've got the files, hopefully I can unbrick my damn phone. I have the teal screen triangle of death (Download mode only) and boot loop when I try to get into recovery or just boot the phone normally when I tried to flash the wrong files...
Odin to the rescue hopefully.
Click to expand...
Click to collapse
Be sure to tell me how it goes im planning on flashing back to pk1 once I know that Samsung didn't disable it
loganbeck14 said:
Be sure to tell me how it goes im planning on flashing back to pk1 once I know that Samsung didn't disable it
Click to expand...
Click to collapse
All worked well! This unbricked my phone and I am now running official AT&T Android 7.0
Thanks again to everyone for their help, it really means a lot!
thegreenfamily04 said:
All worked well! This unbricked my phone and I am now running official AT&T Android 7.0
Thanks again to everyone for their help, it really means a lot!
Click to expand...
Click to collapse
Congrats! Must be a big relief!
Wow since it seems like everyone is succeeding in downgrading I'm gonna odin back tonight
loganbeck14 said:
Wow since it seems like everyone is succeeding in downgrading I'm gonna odin back tonight
Click to expand...
Click to collapse
I thought I was screwed, the members of this forum REALLY helped me out. You should have NO issues downgrading and installing the AT&T OTA 7.0 update.
[Removed]
Hi All,
I'm a little confused as to where us U firmware users stand with Nougat. I've seen differing reports of what the known plan is with this. I believe some are saying we're waiting for Verizon to release it to the 935u, otherwise I'm reading that we're on a quarterly update schedule and won't be seeing anything until April.
I bought my 935V from VZW and flashed over to unrooted U firmware - actually by using the normal flash method and then doing a firmware restore from verizon's utility to get full unroot. Not exactly a typical method, but it gave me peace of mind knowing everything is completely stock U.
Everything is running great so I'm not in urgent need of an update for any reason, but would like to see some new features.
Lemme know if anyone has any clues here as for what to expect. Thanks in advance!
Not exactly sure what you mean by going full "unroot".. unless you ment, you wanted the U firmware for a smoother "root" can you please clarify bubby?
---------- Post added at 05:56 AM ---------- Previous post was at 05:51 AM ----------
Action123 said:
Hi All,
I'm a little confused as to where us U firmware users stand with Nougat. I've seen differing reports of what the known plan is with this. I believe some are saying we're waiting for Verizon to release it to the 935u, otherwise I'm reading that we're on a quarterly update schedule and won't be seeing anything until April.
I bought my 935V from VZW and flashed over to unrooted U firmware - actually by using the normal flash method and then doing a firmware restore from verizon's utility to get full unroot. Not exactly a typical method, but it gave me peace of mind knowing everything is completely stock U.
Everything is running great so I'm not in urgent need of an update for any reason, but would like to see some new features.
Lemme know if anyone has any clues here as for what to expect. Thanks in advance!
Click to expand...
Click to collapse
But anyway, lol. You are correct of the U FW being released somewhere around April. Verizon isn't responsible for U firmware, Samsung is.. I'm actually surprised Verizon released before U
vsn4 said:
Not exactly sure what you mean by going full "unroot".. unless you ment, you wanted the U firmware for a smoother "root" can you please clarify bubby?
---------- Post added at 05:56 AM ---------- Previous post was at 05:51 AM ----------
But anyway, lol. You are correct of the U FW being released somewhere around April. Verizon isn't responsible for U firmware, Samsung is.. I'm actually surprised Verizon released before U
Click to expand...
Click to collapse
Good to know. Thanks.
I had to root in order to flash U FW, but the root process we have for GS7 is really process heavy and battery draining. I wanted an unrooted version of the U firmware with no bullsh*t and good battery life so I unrooted and restored using the software tool.
Action123 said:
Good to know. Thanks.
I had to root in order to flash U FW, but the root process we have for GS7 is really process heavy and battery draining. I wanted an unrooted version of the U firmware with no bullsh*t and good battery life so I unrooted and restored using the software tool.
Click to expand...
Click to collapse
Ah Gotcha, sorry I misunderstood the op. Maybe give the T or V carrier FW a spin till U gets released? I haven't upgraded yet but am tempted. Been using stang 5.0 rom and been pretty impressed. I'd say I would recommend it even with the faults of the eng boot.
I also believe I seen a "no root no bull**** playstore Nougat rom" by jkruse, or something to that effect. If that's something your into
Lots of cry babies over in the Samsung forums. I can see why everyone is so upset but Samsung never promised faster updates for unlocked variants over carrier models. I'm content waiting at least until April for the nougat release of the 935u. Screw Verizon bloat. It's not worth putting up with it for Nougat.
There are some articles with Samsung's new commitment for monthly security updates on unlocked devices. This should mean that the 935U will get Nougat this month with March security update.
junear said:
There are some articles with Samsung's new commitment for monthly security updates on unlocked devices. This could mean that the 935U will get Nougat this month with March security update.
Click to expand...
Click to collapse
Fixed.
Expect nothing. Never get disappointed.
Magnus_CA said:
Lots of cry babies over in the Samsung forums. I can see why everyone is so upset but Samsung never promised faster updates for unlocked variants over carrier models. I'm content waiting at least until April for the nougat release of the 935u. Screw Verizon bloat. It's not worth putting up with it for Nougat.
Click to expand...
Click to collapse
Well, sorta agree with you. I'm patiently waiting for the U update to 7.0, but in the mean time I'm running the Verizon update on a backup device. I can't really enjoy 6.0.1's UI after having Grace UX.
G935U Nougat (G935UUEU4BQD2) is now available!
check samfirm and sammobile for downloads of firmware G935UUEU4BQD2 (7.0)!
jtash01 said:
check samfirm and sammobile for downloads of firmware G935UUEU4BQD2 (7.0)!
Click to expand...
Click to collapse
Smart Switch PC can also do an in-place update to 7.0. It's the April security patch.
I've downloaded the nougat U firmware and can't get it to install over the latest VZW firmware, the one that came out in the last few days. Has anyone been able to, if so please outline your steps.
I have U firmware on Verizon s7 edge works as charm. Use latest Odin to install the firmware
seemcity said:
I have U firmware on Verizon s7 edge works as charm. Use latest Odin to install the firmware
Click to expand...
Click to collapse
which is latest odin I've tried 3.10 3.11 3.12
gunnyman said:
I've downloaded the nougat U firmware and can't get it to install over the latest VZW firmware, the one that came out in the last few days. Has anyone been able to, if so please outline your steps.
Click to expand...
Click to collapse
I would flash the full Odin package for U 6.0 and then use Smart Switch PC to update to 7.0.
http://updato.com/firmware-archive-select-model?record=08ABA51C2C6F11E7963AFA163EE8F90B
Can anyone on an UDP confirm if you can tether the unlocked software of the 935u on 7.0 nougat now that it is out?
RyanEJ25 said:
Can anyone on an UDP confirm if you can tether the unlocked software of the 935u on 7.0 nougat now that it is out?
Click to expand...
Click to collapse
Yes i have the original UDP and the tethering option works. How ever i cant get the verizon video calling to work??
So from what I'm getting, to install (if I'm on Verizon Nougat), flash Unlocked 6.0 first, then smart switch to 7.0? Also, I read that someone had been having issues with using LTE while in a phone call, can anyone confirm? And what happened to all the other fix files, since I remember the first time flashing the unlocked software required more subsequent flashes as well.
I'm not seeing anything anywhere, I just want to get xprivacy working tbh.
sirtweak0 said:
I'm not seeing anything anywhere, I just want to get xprivacy working tbh.
Click to expand...
Click to collapse
I don't think so yet. No eng img to help root the phone. I have been watching for one also.
Sent from my SAMSUNG-SM-T377A using Tapatalk
freeop said:
I don't think so yet. No eng img to help root the phone. I have been watching for one also.
Sent from my SAMSUNG-SM-T377A using Tapatalk
Click to expand...
Click to collapse
Thank you, I'm always looking
https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Jkruse just posted his root method for Oreo across Carriers. All credit goes to him. This was posted in the last 24hrs via the safestrap thread.
I have Samsung Galaxy s7 edge sm-g953a when ever I try to update my phone firmware through OTA it's always said your software is update while I am currently on 6.0.1 October 2016 update. how i can update my phone to 7 or 8 android version?
Waiting for replying.
[email protected] said:
I have Samsung Galaxy s7 edge sm-g953a when ever I try to update my phone firmware through OTA it's always said your software is update while I am currently on 6.0.1 October 2016 update. how i can update my phone to 7 or 8 android version?
Waiting for replying.
Click to expand...
Click to collapse
Switch to the U firmware. AT&T firmware won't update without a valid AT&T SIM.
jshamlet said:
Switch to the U firmware. AT&T firmware won't update without a valid AT&T SIM.
Click to expand...
Click to collapse
Has 1000% to do with the firmware. Has everything to do with the bootloader. The bootloader is locked and cannot be unlocked so perm root is unattainable on the 935A or U firmware.
Does anyone have an ODIN compatible update for the One UI 2 beta that would work for the US factory unlocked S10+ (SM-G975U1)? I saw a T-Mobile only update.zip, but that only works on T-Mobile locked ones.
lightmastertech said:
Does anyone have an ODIN compatible update for the One UI 2 beta that would work for the US factory unlocked S10+ (SM-G975U1)? I saw a T-Mobile only update.zip, but that only works on T-Mobile locked ones.
Click to expand...
Click to collapse
It appears the aren't releasing it for U1 yet. As long as your csc is part of the OYN multi-csc then you can use U firmware and use the update.zip on here.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
It appears the aren't releasing it for U1 yet. As long as your csc is part of the OYN multi-csc then you can use U firmware and use the update.zip on here.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
Not familiar with the term "OYN multi-csc", however I can and have flashed different carrier ODIN packages onto my US Unlocked S10+. I assume that means mine is apart of the multi-csc. Mine is "VZW/VZW/XAA", a factory unlocked s10+ bought from Samsung's website with a Verizon SIM in it.
lightmastertech said:
Not familiar with the term "OYN multi-csc", however I can and have flashed different carrier ODIN packages onto my US Unlocked S10+. I assume that means mine is apart of the multi-csc. Mine is "VZW/VZW/XAA", a factory unlocked s10+ bought from Samsung's website with a Verizon SIM in it.
Click to expand...
Click to collapse
VZW is part of it. It should work just fine then. Just make a Smart Switch backup first
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
VZW is part of it. It should work just fine then. Just make a Smart Switch backup first
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
If I'm currently on G975U1ES2BSIE, I assume I can't just flash that update.zip file because it says you must be coming from BSI4. Is it safe to ODIN flash the BSI4 version and then recovery flash the update.zip? Also, in a screenshot on the update.zip thread, it said the source version was G975USQS2BSI4, yet the firmware I have been using has always started with G975U1..., so can I even use the update.zip at all?
lightmastertech said:
If I'm currently on G975U1ES2BSIE, I assume I can't just flash that update.zip file because it says you must be coming from BSI4. Is it safe to ODIN flash the BSI4 version and then recovery flash the update.zip? Also, in a screenshot on the update.zip thread, it said the source version was G975USQS2BSI4, yet the firmware I have been using has always started with G975U1..., so can I even use the update.zip at all?
Click to expand...
Click to collapse
You would have to flash BSI4 U firmware via odin first then update zip after full boot. U1 beta has been delayed now untill who knows when. So basically we're stuck with bloat if we want the beta until further notice.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
You would have to flash BSI4 U firmware via odin first then update zip after full boot. U1 beta has been delayed now untill who knows when. So basically we're stuck with bloat if we want the beta until further notice.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
Thank you for reminding me about the bloat from U firmware.... ewww.... Will definitely hold out until more information about the U1 beta comes out, especially considering that someone will likely release the update.zip for it, rendering their limited beta unlimited.
I'm curious about this as well. Didn't the release the u1 beta yesterday? If so does anyone have the update.zip we could apply locally?
spidey44 said:
I'm curious about this as well. Didn't the release the u1 beta yesterday? If so does anyone have the update.zip we could apply locally?
Click to expand...
Click to collapse
You on BSIE?
lightmastertech said:
You on BSIE?
Click to expand...
Click to collapse
I'm on BSIC (thought that was the latest U1 version)
I was on BSIE and had to downgrade to BSIC in order to take the beta update. Even though I registered, wasn't sending it and as soon as I downgraded back to BSIC the beta update came through.
tgee0907 said:
I was on BSIE and had to downgrade to BSIC in order to take the beta update. Even though I registered, wasn't sending it and as soon as I downgraded back to BSIC the beta update came through.
Click to expand...
Click to collapse
Hmm so I'm not able to grab it while on BSIC; any chance you have the update.zip file
I have the U1 (512 unlocked Snapdragon). I flashed the T-Mobile U image (downloaded using Frija, then flashed with Odin), and then saved the ota zip to an SD card and flashed that update via recovery. Haven't had any issues, yet. While I'm not a fan of the T-Mobile boot screen and default ringtone, the only bloat I've identified is the Name ID, T-Mobile, and Visual Voicemail apps, which all appear to be uninstallable. It also added the video call function to my dialer, which I'll probably never use but it's neat that it exists...
I say all that because you could just install the T-Mo firmware to your VZW phone and get away with a updating to the beta and uninstalling the bloatware, if you're ok with having the T-Mobile boot screen (ideally, you won't see it much anyways).
Just a thought.
spidey44 said:
Hmm so I'm not able to grab it while on BSIC; any chance you have the update.zip file
Click to expand...
Click to collapse
Let me get home tonight and I'll extract it
The U1 version of the oneui 2.0 beta was released yesterday and apparently still being released for many users hopefully someone has the logics to make the update zip out of it and pass it along. Not everyone wants to go through completely wiping their phone and swapping unlocked firmware for a carrier one just to test the beta.
phishfi said:
I have the U1 (512 unlocked Snapdragon). I flashed the T-Mobile U image (downloaded using Frija, then flashed with Odin), and then saved the ota zip to an SD card and flashed that update via recovery. Haven't had any issues, yet. While I'm not a fan of the T-Mobile boot screen and default ringtone, the only bloat I've identified is the Name ID, T-Mobile, and Visual Voicemail apps, which all appear to be uninstallable. It also added the video call function to my dialer, which I'll probably never use but it's neat that it exists...
I say all that because you could just install the T-Mo firmware to your VZW phone and get away with a updating to the beta and uninstalling the bloatware, if you're ok with having the T-Mobile boot screen (ideally, you won't see it much anyways).
Just a thought.
Click to expand...
Click to collapse
That's not how it works. You won't have tmobile bloat. The firmwares now are all inclusive so it will install bloat depending on your installed sim card. Example, I installed it on my AT&T S10+ and got AT&T bloat. If you install on your tmobile S10, you'll have tmobile bloat.
jpcdeux said:
That's not how it works. You won't have tmobile bloat. The firmwares now are all inclusive so it will install bloat depending on your installed sim card. Example, I installed it on my AT&T S10+ and got AT&T bloat. If you install on your tmobile S10, you'll have tmobile bloat.
Click to expand...
Click to collapse
Assuming that's the case, why not just do the entire install and setup without a SIM, then plug the SIM in after it's complete?
I used that trick on the VZW Pixel and Pixel 2 and was able to avoid them force-locking the bootloader.
phishfi said:
Assuming that's the case, why not just do the entire install and setup without a SIM, then plug the SIM in after it's complete?
I used that trick on the VZW Pixel and Pixel 2 and was able to avoid them force-locking the bootloader.
Click to expand...
Click to collapse
Between here and Reddit it's been asked several times if that works and there hasn't been a real answer yet. Yes though, that is the case. It's been that way since one of the major updates on the S8 firmware back when it was still a flagship. The bloat and carrier files it installs are carrier dependent. That's why the total download size of firmware went way up.
tgee0907 said:
I was on BSIE and had to downgrade to BSIC in order to take the beta update. Even though I registered, wasn't sending it and as soon as I downgraded back to BSIC the beta update came through.
Click to expand...
Click to collapse
Im thinking thats why I wasn't ever able to join the beta. Downloading BSIC now and hopefully installing that will make it possible to officially join the U1 beta. After going back to U firmware i remember all the things that made me switch back to U1 last time lol.
Sent from my Samsung SM-G975U using XDA Labs
jpcdeux said:
That's not how it works. You won't have tmobile bloat. The firmwares now are all inclusive so it will install bloat depending on your installed sim card. Example, I installed it on my AT&T S10+ and got AT&T bloat. If you install on your tmobile S10, you'll have tmobile bloat.
Click to expand...
Click to collapse
Why are there separate S10+ firmware downloads for AT&T, Sprint, T-Mobile and Verizon which have different Home_CSC partitions if the Samsung firmware works like you say? Shouldn't all the Samsung S10+ firmware be U1 (the firmware that comes installed on the carrier free version of the S10+) if the carrier bloat is installed via the inserted SIM?