So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
TheofficialJonerockit said:
So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
Click to expand...
Click to collapse
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I read also
but I was just hoping that it wasn't true or that their was some way to intercept or clone its coding but install the real thing.
Well I guess I am gonna make this phone my test phone and see how badly I can screw it up by installing stuff and test software on it. LoL until it wont work anymore.
Has anyone tried Linux/Heimdall vs Windows/ODIN? I am just curious to try it myself as I gave up on Windows years ago. It also seems to me that since Android is a Google-based form of Linux, that a Linux user may have more success.. I will be attempting it myself as I cannot get my phone to update to Android Pie, or anything after the June 2019 version of Oreo and the security updates. Contacting Cricket nor Samsung is of any use as they are both reluctant to help anyone with any issue that doesn't include buying something (i.e. new warranty, new phone, new service upgrade, ect.), even though my phones are always purchased, not leased. Anyway.... I will be either flashing this old and busted thing or destroying it completely. Wish me luck.
Related
Hi All,
The short of a long story is that I just changed carriers and found out way late that I couldn't bring my Sprint phone to MetroPCS. So now I'm using the budget PCS On5 that came with the deal when we signed up.
I successfully loaded TRWP and then rooted however, I didn't know about FRP until it smacked me in the face. The root went fine but later SU prompted me to update the binary and when it did, it tripped factory reset protection and soft bricked my phone.
I want to reinstall stock OS on this phone but it appears that I have a software version that I haven't been able to find on the web yet. I found the stock rom for the MetroPCS On5 easily enough but it's Revision 0.0 and the box I have for the phone says REV0.4.
When I try to Odin Flash the REV0.0 version, I get SW REV CHECK FAIL DEVICE 2, BINARY 1 fail. So I guess I had the latest software on my phone and the phone thinks I'm trying to roll back using the 0.0 revsion.
My question is this, does anyone here have the stock rom for G550T1 REV0.4? Help!
If nobody does, maybe I can still fix this phone. I have a TRWP backup from the sister phone (same model same revision 0.4) that I'm using right now but I can't get back into TRWP on the soft bricked phone to recover that way to use the backup file.
Next I thought I might take the backup files and turn it into a rom and just flash that. However, with the tutorials I followed I kept running into problems. When I went to unpack the files per the tutorial, my rar software said that the file was corrupt. Maybe it is. but maybe not. It was my first time attempting to make a rom. If I can't find the software I need, could any of you Android geniuses help me get this backup into a flashable format?
I have to admit I'm daunted by the FRS in 5.0 and above. Is it defeatable? How do you root newer Android versions?
Thanks!
I did the same thing to my phone. did you get yours fixed?> if so could you provide me with the rom?
I haven't found the fix yet. Hopefully somebody will come through with a helping hand!
I finally got it figured out! So here is what i did and hopefully it will work for you.
1. I Odin flashed a good BL from the ROM REV0.0 floating around on the net. So at least I could now get into download mode.
2. Then I used Kies3 > Tools > Firmware Upgrade and Initialisation. It will ask you for your model number and then when you click ok it will ask you for a SN.
3. The trick is that Samsung doesn't put the SN that you need on the phone or the box. (personally, I couldn't find it on the phone either once I got it up and running) so go here: https://forum.xda-developers.com/android/general/root-samsung-galaxy-on5-t3435457/page46 and get a SN from post #454 and use that. (don't forget to say thanks)
4. Click Ok. Let it work, and max and relax.
Mine took about 10 minutes. Hopefully this will work for you too! Thanks XDA!
Help!
What is BL from the ROM REV0.0? I need your help, I have the MetroPCS On5 and I installed Reborn ON5 I want to go back to the MetroPCS ROM because the camera and the audio do not work and I tried to install the original ROM through Odin but it does not work I get an error. What I can do? I would like to use this method but I do not have very clear files needed.
You could help me bro, I'll thank you
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
solamente said:
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
Click to expand...
Click to collapse
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
DeadRatGames said:
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
Click to expand...
Click to collapse
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
solamente said:
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
Click to expand...
Click to collapse
Do I really need to wait 168 hours lol?
DeadRatGames said:
Do I really need to wait 168 hours lol?
Click to expand...
Click to collapse
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
solamente said:
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
Click to expand...
Click to collapse
How do I downgrade though?
DeadRatGames said:
How do I downgrade though?
Click to expand...
Click to collapse
At this time its impossible to downgrade from a binary 3 towards 2 or from 2 to 1.
You can only upgrade, Samsung has blocked the downgrading from a higher to a lower binary, therefore it is useless to try it with Odin, it won't succeed.
Maybe someone else knows a way around to downgrade, but I don't.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
BlackMesa123 said:
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
Click to expand...
Click to collapse
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
DeadRatGames said:
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
Click to expand...
Click to collapse
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
BlackMesa123 said:
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
Click to expand...
Click to collapse
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Reformat system.
DeadRatGames said:
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Click to expand...
Click to collapse
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
solamente said:
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
Click to expand...
Click to collapse
Ok. Thanks
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
same questions
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
amazing. youre the man. cheers.
samalderon said:
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
Click to expand...
Click to collapse
omg youre the best. thanks so much.
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number
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.
Was trying to flash to combination rom so I can bypass frp then flash back to stock. Accidentally flashed to latest firmware G970U1UES4DTG1 which is actually G970U1 firmware.
Is it possible to flash to an earlier firmware? I was getting " please get the approval to use factory binary( pit) " then for some reason flashed to higher firmware without realizing it like an idiot.
I tried to load the combination files but I keep getting Fused 4 > binary 2. the firmware currently loaded is newer than the combination file so it wont let me go to it.
Will there be binary 4 combination files coming out? is there anyway I can unlock the bootloader without getting into the phone? or any way to enable USB debugging with my computer? Any help is appreciated.
Also doesn't help its AT&T and apparently they dont release their firmware files publicly