My wife has an S10e on T-Mobile (US). I have a T-Mobile S10+. My S10+ has received all updates without a problem and I'm currently running Android 10, One UI 2.0 and my latest update was installed on March 19, 2020. My wife's S10e's last update was installed all the way back on May 21, 2019! Her phone is still running Android 9 (Pie) and One UI 1.1.
When I try to search for software updates through her phone's settings menu, the phone says that her software is up to date. Obviously that's not true, as it hasn't received so much as a security patch for about 11 months! T-Mobile released Android 10 (One UI 2.0) for the S10e months ago, and it should've been pushed out to her device.
I've downloaded the latest official T-Mobile S10e firmware from Sammobile.com here: https://www.sammobile.com/samsung/galaxy-s10e/firmware/SM-G970U/TMB/download/G970USQS3CTB6/324698/
I downloaded and launched Odin on my laptop, put her phone into Download Mode, unzipped the contents of the compressed folder that I downloaded from Sammobile.com, loaded the BL, AP, CP, Home_CSC and USERDATA files from the download to their respective slots in Odin, connected her device to my laptop (Odin detects it on COM0 and the blue box indicates as much) and then clicked the Start button in Odin.
The end result, every time, is "<OSM> All threads completed. (succeed 0 / failed 1)"
Can anyone help me figure out what I'm doing wrong? I'm trying to avoid having to completely wipe and factory reset her phone, as that would be a huge pain in the butt for her, and a flash via Odin would certainly be ideal, if possible. Am I missing a step?
I appreciate any help you can provide. Thanks very much in advance!
Never mind. Third attempt worked for whatever reason.
Related
Hi
Apologies for what is quite a basic question for I'm just trying to get things straight in my head before proceeding.
I have a UK retail S7 G930F, current running stock
Build G930FXXU1DQC4
Baseband G930FXXU1DQC2
Despite the fact this build only has Android security patch level February 2017, and the latest build is from 2018, my device and Smart Switch insist I am up to date, I want to actually make this the case while remaining on stock firmware.
I have used Odin to flash Galaxy phones before but not since I had a Note 2 and Note 3 so I'm a little rusty.
I have Odin 3.13.1 and the zip download from sammobile for build G930FXXS2DRAA for the same CSC region I'm currently on which is XEU.
All the guides for Odin flashing say to only use the AP file and option in Odin. However as my BL, CP and CSC will all be older as well, and I'm simply going from stock to stock can I (or should I) also flash these parts as well?
Thanks.
I need more information. 6 mm and 7 nougat use the same BL and require no upgrade where if you were on lollipop somehow you would need the bl. Please DO NOT run off and start flashing things like BL without help from here first. I have bricked a samsung device so bad I had to replace the motherboard, so I learned the hard way.
Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.
y2kgecko said:
Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.
Click to expand...
Click to collapse
I get that a lot. I upgraded my s7 to latest n release today and it worked ok.
So, do I just flash AP or everything?
y2kgecko said:
So, do I just flash AP or everything?
Click to expand...
Click to collapse
You need to flash all 4 files: BL / AP / CP / CSC
I do recommend that you flash CSC* and not HOME_CSC*. That way you will reset the phone to factory defaults and it will be ready for future OTA updates.
Backup your files first that you think are important and then start from scratch to configure the phone, install your apps, update the ones on the phone.
Ok. I got an AT&T Galaxy Note 8 back in early-mid 2018. The first thing that happened when I booted it up and connected to a wifi hotspot was that it downloaded the latest update.
That was the last update I received.
I am trying to install Android P onto my device through Odin (Using 3.13.1B PatcheD). I tried OTA first, but when checking for updates, it says that my phone is up to date. I am currently on build U4CRD7.
I called AT&T and they told me that I have to contact Samsung to download the update, and also that it could be a hardware issue (?) and to possibly send it in to Asurion. After that, I called Samsung, and they told me I had to take it to the closest Best Buy. Now, I don't have a way to travel the ~30 miles to the closest one. So, I decided to try Odin. (I have used Odin before, so I am somewhat familiar with it)
I downloaded firmware version U7DTC1_USC from a post here on the forums. I placed all files in the correct areas, went to download mode, tried flashing, and failed. I've gotten three different fails. I changed cables and ports and failed. I tried downloading firmware version U7DSK3 and flashing that one, thinking I might have skipped too many updates (if that is a thing... I've read conflicting information). Failed.
The last failure was a "Complete(Write) operation failed"
Besides taking an expensive rideshare to the nearest Best Buy, is there something that I am missing in trying to update this phone? Could it be a hardware issue? Have I missed too many updates? Do I need to progressively update my phone? (I don't need answers to all these questions, just the most relevant answer please)
If I have posted this in the wrong area, I am sorry. This is my first post on XDA, and I usually don't post in forums anywhere, I just lurk and look for answers to my questions. I haven't been able to find a matching problem.
Edit:
More digging and I found this in another thread.
MrMike2182 said:
...You need to manually update it yourself to the next update version which I think is ... using Odin and then it'll be able to do it on it's own.
Click to expand...
Click to collapse
In further replies, he suggests updating to the firmware version that I am currently at. What is an "update version?" Do I need to just go one firmware update up? Do I need to go one BL version up?
Phone successfully updated
So, I downloaded firmware version U5DSC1, dug up my 10 year old laptop and switched from the patched version to the normal Odin3 3.13.1.
I don't know which change allowed the update, but I was able to update.
After U5DSC1, I had no problem updating to U7DTC1 through Odin (though the system update feature on the phone still did not pick up any updates after U5DSC1).
G-Man Cometh said:
So, I downloaded firmware version U5DSC1, dug up my 10 year old laptop and switched from the patched version to the normal Odin3 3.13.1.
I don't know which change allowed the update, but I was able to update.
After U5DSC1, I had no problem updating to U7DTC1 through Odin (though the system update feature on the phone still did not pick up any updates after U5DSC1).
Click to expand...
Click to collapse
Your problem was simply because you were trying to use the patched version of Odin and should have just used the newest updated version of Odin. There's no reason to use the patched Odin to flash the normal firmware. People use the patched Odin when they're flashing modified firmware.
Edit: By the way, if it's an AT&T device and you're using say a T-Mobile or Verizon sim card it will not update unless you put an AT&T sim card back in it. It's apparently picky like that. For instance let's say it had AT&T firmware on it and you have a Verizon(or other) sim card in it, the phone is expecting to find and download the AT&T firmware for updates the problem is that Verizon(and others) do not carry AT&Ts firmware they only have their own versions of firmware that's the reason some people don't get updates.
( Main question below at the end in Bold Italic ) ...... So here's what happened.
I was using ( probably Sept 2020 ) Security Patch on my phone and everything was well. Then there were 2 software updates from Samsung, both were security updates. I initially didn't upgrade to October update, because the phone was already nearing 4 years from launch and I did have a bit of experience with Samsung where I felt it sometimes got slower especially in end updates , and this update was given in one month from sept update which was weird for a 3.5 year old phone, but later January 2021 Security update was also out and I decided to upgrade to at least October patch. Upon upgrading to October Update my Sensors stopped working ( - Iris scan, accelerometer, gyroscope , light sensor - they just turn on for a sec and stop working, I still believe it isn't a fault with Sensor microcontroller,. So I then did all the steps like clearing cache partition, etc as described in various threads & forums. None helped and finally I upgraded to January patch and yet the problem isn't gone.
The bootloader has been upgrader to some 'B' version as from what I can say from my current PDA Version G950FXXSBDUA3 which was earlier G950FXXSADT1I . So That was bootloader version A I assume. Before which there has been One Bootloader version 9 - which I prefer to downgrade to and then turning off auto update system from dev options.
----------------------------Main Question ------------------------------------------------------
So my main doubt was :- If I Download the July firmware which has those 4 files in it, not load the old bootloader file and then flash it via ODIN, will KNOX TRIP ? will it be 0x1 ? Because I want to continue using Samsung Pay , Samsung Health , Secure Folder and other apps. P.S. Do share if you have done anything like this on any other Samsung phone ( after 2014 - when e-fuses were introduced in them ) and did it trip KNOX ?
**I don't remember, but I did it trip on a Galaxy Note 3 when I was a kid. Can't experiment much with ODIN. Before it used to be one PDA file, now I am wondering if flashing only AP file works ?
---------------------------------------------------------------------------------------------------
Got some part of my answers. Odin won't flash older firmware - at least if you don't turn on OEM Unlocking in Developer options, and it prevents Knox from tripping. I won't try OEM Unlocking as of now. I tried loading only the old AP file and not the bootloader file, and it failed ( got suck in middle ), then I tried all 4 files of old firmware, and still, it failed. So overall got the answer can't downgrade without tripping KNOX as of now. There is something like a developer bootloader or so, but I don't know about that.
Hi all !
Hope everyone have a great day, i have got a samsung galaxy A6 US variant TMB, (SM-A600T) with android version 9, I was trying to root the phone but didn't have the knowledge that this phone can't be rooted because of locked bootloader which can't be unlock with any procedure. So i gave up and just updated my phone to the latest version available of PIE . (Android 9), To tell you more, before it was also on the same version of android 9 but earlier date. I have not updated a whole version of android but just to a latest date of android 9, Android 10 is also available for this phone but i haven't done that yet. The main problem with my phone is that before this update i just needed to charge my phone once in 24 hours, and now after update i need the same phone with same demands to charge it 3 times in 24 hours, Did every optimization for battery, unused apps, extra apps uninstalled, just one google account left, synchronization is off, NFC and near scanning is off, Bluetooth / Wifi is off, GPS is off. Auto update for apps and system software is off. Battery saving mode is enabled, clear cash has been done, factory reset is already done with flashing this version of android with odin tool, and etc every other thing has been tried with no luck, please don't advise for these things as the main problem for me is just the android version itself which i have newly flashed. Because of locked bootloader i can't flash back my older version of android 9 with odin tool, phone gives error of bootloader :
sw rev check fail device 2 binary 5​something like above after many tries the same result. tried my old firmware with the new bootloader but still no luck. (Same error). Any help or suggestions will be greatly appreciated. I am thinking what if i extract the AP of the new flashed firmware and replace the system.img.lz4 with my old firmware's system.img.lz4 to trick the phone and reflash with the new firmware but old system image file, Can this be done ? or i may brick my phone for ever ? what if i take my phone to the outside market and request a z3x flash for the old firmware version ? will that work ?
Please give any accurate solution i really want my old phone back, this locked bootloader has become a really annoying thing for me. I will never buy a phone like this which bootloader's can't be open again. Or if i wasn't able to flash this to my old version i will never use android again in my life, Better option will be to buy an iphone after 17 years of android use.
Thanks in advance.
Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?
*I do not have any backups from Android 12 stable.
You tried flashing official firmware for U device right? You were using CSC file or HOME_CSC to preserve data?
Going back from beta to stable means wiping data, phone will factory reset when you flash back the stable firmware and you should use the CSC file (not HOME_CSC)
Yeah... I know how to operate Odin3... It literally says right there I tried flashing multiple stable builds and each time it fails with AUTH error. Tried HOME and regular CSC....
I have the same phone. I have not gone back to stock U firmware from beta. But I have gone from beta to stock U1 firmware. I believe once you go back to stock U1 Android 12. You can flash back with Odin not patched to U firmware.
zlib1 said:
Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?
Click to expand...
Click to collapse
Any chance you still have the flashing zip file for beta 1 s908?
The link for beta 1 in this post isn't working
If you do can you send it to me please?
Thanks