Hi all,
I have an S6 that I am trying to downgrade. It is on 6.0.1 but reboots randomly multiple times a day. I downloaded 5.0.2 stock firmware for Bell and tried to flash via Odin but receive the following error:
sw rev. check fail device 4 binary 1
Not 100% sure what it means. I think the device 4 means that it has been updated and can't be reverted to a lower firmware. If I am wrong, hopefully someone can correct me or provide some guidance. I have already tried clearing the cache and using smart switch to reload the os.
Model is G920W8.
Yeah, I'm on the same boat. I would love an expert to correct me if I'm wrong, but I think once you are past a certain revision of Marshmallow there's no turning back and you basically have to stick with your firmware or move on to a newer one.
You can't downgrade 5.0.2 or 5.1.1 anymore.
Damn, I thought so. If anyone else has ever resolved the random reboot I would love to hear about it. It's such a pain.
Related
Hey guys,
I have been using a 5.0.2 rooted firmware for the longest time possible and it is time for my to update my firmware because of certain battery issues.
How should I go about updating it? I did supersu's full unroot and tried the original software update but I still get the error message saying that my firmware is modified.
Tried out smart switch restore+update but after downloading the firmware and putting my phone to download mode, it gets stuck at 0%, not sure if its my wire issue because its a 3rd party wire, lost all my original wires so far with no more ideas I can come up with.
I am currently downloading my firmwares from sammobile which is taking ages, with the risk of the download corrupting halfway through. Can I flash a 6.0.1 stock firmware on my 5.0.2 and magically everything will work and my phone will be on 6.0.1 and then I can proceed to root it again? My download mode shows that I am using official samsung firmware but its custom. Or do I need to find a 5.0.2 stock firmware then flash it and update from there? I can't find my region's 5.0.2 anymore because its too old, I'm from Singapore by the way.
Any help is greatly appreciated, have been trying for 6 hours to get this to work so far and frankly I dont think I want to go through the trouble of rooting once I update to 6.0.1 because of this cumbersome process just to try and minimize battery drain.
Fixed the issue, smartswitch works, the usb I was using was plugged through my keyboard, not straight to my motherboard so transferring of files couldn't happen
I bought a refurbished Galaxy Note 5 and have used it on TotalWireless for a few days before I noticed the Note 5 should be on BPF4. When I received the phone it was already on BPD4, my wife's phone upgraded from a 5.1.1 firmware and went through the full chain to BPF4 previously. Will an ODIN flash back to a 5.1.1 firmware allow my phone to pass where it is stuck currently?
Thanks
NeoandGeo said:
I bought a refurbished Galaxy Note 5 and have used it on TotalWireless for a few days before I noticed the Note 5 should be on BPF4. When I received the phone it was already on BPD4, my wife's phone upgraded from a 5.1.1 firmware and went through the full chain to BPF4 previously. Will an ODIN flash back to a 5.1.1 firmware allow my phone to pass where it is stuck currently?
Thanks
Click to expand...
Click to collapse
Why don't you just download BPF4 and flash via odin? I'd make sure you didn't receive a fake phone before you flash anything as long as the phones real you can just flash it yourself in odin and setup the network to use the right settings from Totalwireless. The only reason I mentioned a fake phone is because someone else wanted to do the same thing and ended up with a phone that he couldn't find the firmware for because it was fake and after trying to flash Verizon firmware which failed he had no way to go back!
It's definitely a genuine Note 5. I was trying to locate the PF4 firmware to flash via ODIN, but the only ones I could find were several 5.1.1 firmwares and the PD4 firmware I was already on, do you have a link to a full PF4 firmware? Must have had research failure or something, haha. I finally decided to try the Verizon Upgrade Assistant and it was able to update me to the latest PF4 firmware no problem.
Download Samsung Smart Switch for PC.
You won't get OTA updates unless you have an active Verizon sim card.
Using Smart Switch to update is much easier than Odin.
I'll try Smartswitch when the next OTA comes out. I was actually surprised how well the Verizon software worked to fix the issue. In the past I always ignored the software install portion of USB connection. Guess it serves a purpose now.
Hi everyone, there is this really strange issue with my phone, if i try to update it to the latest Nougat version it will update but will reboot and work for about 30 seconds before it restarts, the phone works well if i stay on the android version I have now (7.0 May 2017 update) but if I update it even just by one version it will continue to have this issue which forced me to restore it back via Odin. Also when I go into my settings and have a look at my storage I notice that it only says that it has 16GB storage capacity which isn't true. I was wondering if anyone out there has had this issue before or knows how to fix any of mine any information would be greatly appreciated. Before anyone asks, no my phone has never been rooted, I have tried factory resetting, I have tried other firmware's from different carriers, I have tried most things but nothing seems to work, please help. Thanks.
So it's updating via OTA and having problems or you're manually flashing to newer versions? And when you flash you're using all 4 firmware files and no just AP?
Hello everyone, I searched here and found several discussions on this problem, but didn't found a solution.
My friend gave me a G920F with a bootlop problem (stock Samsung ROM), it also has a broken recovery which doesn't load at all. I can only go into Download Mode. The fact is, downloading the latest available firmware for ITV, dated 30th March if I remember well, with Nougat, I get the error message on the phone: SW REV CHECK FAIL: DEVICE 6, BINARY 5. Now, how the hell is possible that the phone has a bootloader version greater than the latest firmware available to download?My friend told me she updated the phone few days ago, so it could clearly be the 30th March, which is also the firmware I'm trying to install with ODIN. Anyone could help? I can't really figure it out.
Hi, I've got the same problem. I had stock Nougat on my G920F. Never rooted. Then I recieved a call form unknown caller and the phone crashed. Now it's in a bootloop. I can't access recovery menu, only download mode. Odin fails to push the latest software and I get "SW REV CHECK FAIL: DEVICE 6, BINARY 5" on the phone. I've tried SmartSwitch but it doesn't support G920F anymore. I tried to find sth in here but the only solution I found is to get AOKP, which is dead with no download link. Please help.
I have the same problem. I installed TWRP and LineageOS and want to go back to stock. I downloaded firmware for the phone, start it in Odin and it says in Download screen on the phone: "[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY 5". I Googled it and only found that I'm possibly flashing older bootloader than what I already have. I updated my phone when it was on stock like 2 days ago.
I will try and download newest firmware I can find, 4/4/2018. and see if it works then.
-------------------EDIT--------------------
It worked! I downloaded a ROM from sammobile from 4/4/2018, can't remember which one exactly but it doesn't matter and I didn't get any issues. Everything works fine now.
pilicar said:
I have the same problem. I installed TWRP and LineageOS and want to go back to stock. I downloaded firmware for the phone, start it in Odin and it says in Download screen on the phone: "[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY 5". I Googled it and only found that I'm possibly flashing older bootloader than what I already have. I updated my phone when it was on stock like 2 days ago.
I will try and download newest firmware I can find, 4/4/2018. and see if it works then.
-------------------EDIT--------------------
It worked! I downloaded a ROM from sammobile from 4/4/2018, can't remember which one exactly but it doesn't matter and I didn't get any issues. Everything works fine now.
Click to expand...
Click to collapse
so it works?!
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.