Related
Hey guys i am trying to use odin to downgrade from android 4.3 to Android 4.1.1 but for some reason it keeps on failing in odin. And now i am stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". How do i know if i have the correct stock file? I downloaded 4.1.1 from here: http://www.sammobile.com/firmwares/1...e=TLS#firmware.. why is it keep on failing? i have checked and kies is off and i am using the original samsung cable odin recognizes the phone but it "fails"
please help
Do you have an AT&T s3? If you do, you cannot downgrade the 4.3 bootlaoder using desktop Odin and there is no stock AT&T 4.3 ROM.
kaboose786 said:
Hey guys i am trying to use odin to downgrade from android 4.3 to Android 4.1.1 but for some reason it keeps on failing in odin. And now i am stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". How do i know if i have the correct stock file? I downloaded 4.1.1 from here: http://www.sammobile.com/firmwares/1...e=TLS#firmware.. why is it keep on failing? i have checked and kies is off and i am using the original samsung cable odin recognizes the phone but it "fails"
please help
Click to expand...
Click to collapse
Be thankful Odin failed because if it hadn't you probably would have had a bricked phone on your hands now. Like the senior member already advised, you can't downgrade the bootloader on the 4.3 to an older system. Desktop Odin tries to flash most partitions which is why it failed. If I may ask, why are you trying to downgrade to 4.1.1? If it's to free unlock the phone, you may be advised that there haven't been conclusive results on the viability of this process. It's possible to downgrade the system itself without downgrading the bootloader by flashing with other methods apart from Odin. I'm not aware, however, that anyone's been able to unlock even after this.
It's unlikely you'd be able to use Kies to recover from the phone's current situation as Kies will likely try to update to 4.1.1. If it isn't booting or working normally, you may try doing a hard wipe from recovery. If your phone still has warranty left on it, you may try an authorized service center. I am also assuming you are using an AT&T phone? You may be able to get it fixed at Best Buy
Ok, so I've had wifi issues for awhile with this thing, but apparently the 4.3 update sent it over the edge. (I just updated it last week, since I was out of the country when the update issued).
The issue is, I cannot connect to any wifi, other than my home. Before the update, I could connect to non-home wifi only through various router setting changes, that required admin access to the router. After the update, no matter what I've tried with regards to routers, my home router is the only one I can connect to, and the signal strength is pretty bad on my phone, while it shows very strongly for any other device.
I've tried all the suggestions in just about every thread I could find. I've done several factory resets, I've tried the *#0011# thing. I've tried using static IP addresses. But the phone will do one of two things. After I click connect, after selecting a network, it will say Saved. Or it will try to connect and then go back to Saved, or eventually give the Authentication error.
I'm not 100% familiar with how android is setup, but is there a specific file that I could try to install that might affect this? (Like a driver)
Would replacing the antenna be helpful, or maybe the chip on the mb? Or are those options too extreme?
Any ideas are appreciated.
Nobody has any ideas for me?
Please, I'll try anything.
Still looking for help. Thanks!
Did you try re flashing the firmware? Might be a bug in the software. You'll lose all your data but its worth a shot. I've seen a similar issue like this before on the S III and that took care of the problem.
Brian9391 said:
Did you try re flashing the firmware? Might be a bug in the software. You'll lose all your data but its worth a shot. I've seen a similar issue like this before on the S III and that took care of the problem.
Click to expand...
Click to collapse
Do I use odin to reflash....it's basically like installing a rom, right?
NwFl Griz said:
Do I use odin to reflash....it's basically like installing a rom, right?
Click to expand...
Click to collapse
Yes, you will use Odin to complete this process.
Few things you should consider though, by doing this it will completely reset your phone to a point as if you just un-boxed it (or a factory reset). I am uncertain about the fact that it may hinder you the ability to receive further OTA updates. Like i said I don't know exactly on that one but that will most likely be stated in a thread that you receive the firmware from. Also, this may be a good opportunity for you to root your phone if it was not previously. Doing this could be as simple as downloading one file vs. another to use in Odin. The choice is yours as there are threads regarding both Stock Rooted and Stock non rooted firmwares. Another thing, consider which version you want. Im guessing 4.3? I was once told going down a version on android (i.e. 4.4 to 4.2) could brick a device... also unclear on that. try doing some research if you wish.
If you have the AT&T 4.3 bootloader on your phone, do not use Odin to try and flash any stock ROMs as this may brick your phone. The 4.3 bootloader cannot be downgraded and attempts to do so with probably brick your phone.
Boot into download mode and tell us what it says on the download screen.
audit13 said:
If you have the AT&T 4.3 bootloader on your phone, do not use Odin to try and flash any stock ROMs as this may brick your phone. The 4.3 bootloader cannot be downgraded and attempts to do so with probably brick your phone.
Boot into download mode and tell us what it says on the download screen.
Click to expand...
Click to collapse
I have rooted this device, so when i boot into download mode, I get the android guy with the words "downloading do not turn off target" underneath him. In the top right it says:
Odin mode
product name: SGH-i747
custom binary download: Yes (2 counts)
current binary: custom
system status: custom
qualcomm secureboot: enable
warranty bit: 1
bootloader rp swrev:2
audit13 said:
If you have the AT&T 4.3 bootloader on your phone, do not use Odin to try and flash any stock ROMs as this may brick your phone. The 4.3 bootloader cannot be downgraded and attempts to do so with probably brick your phone.
Boot into download mode and tell us what it says on the download screen.
Click to expand...
Click to collapse
I replied above...still waiting to ensure I don't brick this thing.
Hey,
So I had a friend ask me to unlock her S3, no biggie, I did it with another one (That hadn't been updated and was running 4.1.1 or something)
Following instructions online, I tried to upload a .md5 file via Odin but had the wrong version of Odin, and it failed to load. Now my download screen is showing SW REV CHECK FAIL : Fused 1 > Binary 0
As well, turning the phone on only results in "There was a problem updating the Firmware. Please run recovery mode in Kies."
Which is all fine and dandy, except Kies doesn't connect to the phone. It freezes on "Connecting..." and does not go any further.
Any help? I found another thread about it and am trying to use philz through Odin 3.07 and then flash through an external HDD the CM11.
Do you remember what stock ROM was on the phone before you used Odin?
Does the download screen say anything about warranty bit?
audit13 said:
Do you remember what stock ROM was on the phone before you used Odin?
Does the download screen say anything about warranty bit?
Click to expand...
Click to collapse
No clue.
Says Warranty Bit : 0
This five minute thing is a tad annoying...
Would be good to note, it is still under Warranty, and samsung offered to have it sent and fixed, however the phone is kind of needed ASAP.
I'm pretty tech-saavy, but I use Apple products generally and this is a touch foreign to me.
Odin failed to write Philz, just says WriteFail
This leads me to believe that the phone has least a 4.3 loader on the phone; therefore, you cannot unlock the phone using the free method as there is no way to get the stock 4.1.1 modem on your phone.
Is it an i747 from ATT? If it is, there is no stock ROM that can be flashed in Odin to restore the phone as ATT never released a full firmware flash for 4.3 or 4.4.2.
Any warranty left on the phone?
audit13 said:
This leads me to believe that the phone has least a 4.3 loader on the phone; therefore, you cannot unlock the phone using the free method as there is no way to get the stock 4.1.1 modem on your phone.
Is it an i747 from ATT? If it is, there is no stock ROM that can be flashed in Odin to restore the phone as ATT never released a full firmware flash for 4.3 or 4.4.2.
Any warranty left on the phone?
Click to expand...
Click to collapse
She doesn't even care if it's unlocked anymore, as long as we can get it working again.
I'm in Canada, so I'm assuming it is AT&T.
I believe the old OS was Jellybean 4.3. There is warranty, however she doesn't want to wait the length needed for that.
Brad90 said:
She doesn't even care if it's unlocked anymore, as long as we can get it working again.
I'm in Canada, so I'm assuming it is AT&T.
I believe the old OS was Jellybean 4.3. There is warranty, however she doesn't want to wait the length needed for that.
Click to expand...
Click to collapse
Wait, you have an i747m or i747? Big difference as cross-flashing the bootloader could hard brick the phone.
audit13 said:
Wait, you have an i747m or i747? Big difference as cross-flashing the bootloader could hard brick the phone.
Click to expand...
Click to collapse
SGH-i747M
I don't like the sounds of Hard Brick...
Brad90 said:
SGH-i747M
I don't like the sounds of Hard Brick...
Click to expand...
Click to collapse
Are you sure? Is that what it says at the top of the download screen? If it does, this is easier to fix.
audit13 said:
are you sure? Is that what it says at the top of the download screen? If it does, this is easier to fix.
Click to expand...
Click to collapse
"odin mode"
product name : Sgh-i747m
You can download the full firmware for the phone from sammobile.com. Search for the sgh-i747. The search results should inlcude the 4.3 and 4.4.2 firmware for the i747m. Make sure you match the firmware with the carrier.
If the phone had the 4.4.2 ROM, you cannot flash the 4.3 ROM.
audit13 said:
You can download the full firmware for the phone from sammobile.com. Search for the sgh-i747. The search results should inlcude the 4.3 and 4.4.2 firmware for the i747m. Make sure you match the firmware with the carrier.
If the phone had the 4.4.2 ROM, you cannot flash the 4.3 ROM.
Click to expand...
Click to collapse
I'll assume there's no way to check, should I try one before the other? Will doing so screw it up further?
How much warranty is left on the phone? I'm asking because there are different ways to restore the phone.
audit13 said:
How much warranty is left on the phone? I'm asking because there are different ways to restore the phone.
Click to expand...
Click to collapse
I'm not overly sure when she purchased it.
Samsung support said the IMEI was still covered by Warranty and to just send it in, but if there's a way to do it today I would like to.
Well, to be as safe as possible, you could try flashing the 4.4.2 Kit Kat ROM from sammobile for her carrier. You may have to register to download the ROM.
Who is the carrier?
Koodoo is her carrier, i'm download both the 4.3 and 4.4.2 at the moment.
So try the 4.4.2 first?
If you go with the 4.4.2 and it flashes properly, you will not be able to go back to 4.3. I recommend using Odin 3.07.
If you try to flash 4.3 and it fails, this tells me you probably have the 4.4.2 bootloader and modem on the phone.
Whenever you flash a ROM, there is always the possibility that something will go wrong. Just be prepared to deal with any possible issues. Don't panic, we're here to help.
When using Odin, do not check anything except F.Reset Time. When you see the word Reset in the status windows, disconnect the USB cable, pull the battery, boot into recovery, wipe cache and data, reboot the phone.
audit13 said:
If you go with the 4.4.2 and it flashes properly, you will not be able to go back to 4.3. I recommend using Odin 3.07.
If you try to flash 4.3 and it fails, this tells me you probably have the 4.4.2 bootloader and modem on the phone.
Whenever you flash a ROM, there is always the possibility that something will go wrong. Just be prepared to deal with any possible issues. Don't panic, we're here to help.
When using Odin, do not check anything except F.Reset Time. When you see the word Reset in the status windows, disconnect the USB cable, pull the battery, boot into recovery, wipe cache and data, reboot the phone.
Click to expand...
Click to collapse
Okay. So going to test with 4.4.2 once it's done downloading.
I had Auto Reboot checked before. When I turn on the phone, I can either set it in Downloading... mode or the error screen, I have absolutely nothing else. Is that the recovery screen I should be using?
To use Odin, you must boot into download mode.
When the file downloads, open Odin, connect the phone in download mode, click on the PDA button, browse to the downloaded 4.4.2 file, select it, click start.
How long does it sit on ID:0/003> SetupConnection..
Before it says reset? I'm attempting this with 4.4.2 under PDA with only F. Reset Time checked.
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Frank-95 said:
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Click to expand...
Click to collapse
1.install KIES
2.press tools
3.press frimware upgrade and installation
4.device id is your device model and serial number can be found under battery
5. allow kies to download and install the image
Video link for more help : https://www.youtube.com/watch?v=LqoX7wNhotk
good luck
Edit: please remember to enable OEM unlock in developer options next time
Kies cannot link to the device in the downlaod mode unfortunetely
Frank-95 said:
Kies cannot link to the device in the downlaod mode unfortunetely
Click to expand...
Click to collapse
try using smartswitch and see if it detects it
-are drivers installed
-does the pc recognize the phone ?
So, I had already tried with Smartswitch, but it says device not supported and does not link at all.
Moreover yes, the computer could read the phone before the frp lock, and even now, odin can detect it in download mode.
Kies just loads for some minutes and then says "unable to link to the device"
EDIT: no sorry kies raises "the device does not respond"
ok we need to flash using odin , i assume you can't access recovery but if you tried and it worked, look at the top of the screen it must show a code like
<your A3 model> followed by <your country> followed by <frimware date>
If you couldnt, we can use an updated version for your model , please provide us with the model if u can.
I can only acces to odin mode. Via that, I have the following text:
Product name is: SM-A310F
Current binary: Custom (it was rooted)
System status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warranty Void: 1
RP SWREV: B:2 K:0 S:0
I am sure that the phone had Vodafone pre-installed applications, and looking at mrcrab.net there exist these possible stock firmware:
Android 5
Android 5
Android 6
Android 6
I only fear that if I mistaken the version I will obtain a wipe of my data, which are not vital but are important to me
Actually there is no way to avoid the reset as we don't know anything about the PDA version, install the drivers type in google "USB Samsung drivers"
It must show developer.Samsung.com/....
I'm on phone so I can't provide it as a link, install the drivers and try again, else we will get the latest version
I already have samsung usb drivers, and odin can succesfully detect the phone in download mode; Kies cannot, though
Anyway, if you open one of the links I posted, isn't the PDA shown in the line:
OS Version : A310FXXU1AOLE (chosen one as example)
In that website there is every stock firmware by model, android version, and mobile operator. I know two out of three, and those 4 links are the 4 possible choices regarding android version. If I picked the right one, would I avoid the data reset, wouldn't I?
EDIT: What, if I did how it is explained here with the latest version? I mean download android 6 last upgrade, extract it, rename .tar.md5 in .tar and flah it with odin? Would it be any risk of loosing data?
Hello,
.MD5 lets odin checksum the rom loaded to it to make sure it's not corrupted, however if you are sure of two main things:
that the frimware you are flashing isn't a downgrade as downgrading flashs a old bootloader which gets you in some kind of troubles possibly a brick, to avoid that, grab the latest version
and the second thing you must make sure of is that the file isn't anyway corrupted.
if you think it's all ok, then you can proceed as of i tried it once and it saved a device.
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Frank-95 said:
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Click to expand...
Click to collapse
The build number must be the same regarding the android version, so to keep the files it must be the same as the one in the phone, else a wipe will be performed.
The problem is that you want your data, that maybe lost if we don't have the exact same build.
Just grab the latest marshmallow or nougat -, but the data would be lost then.
Do a hard reset in case something went wrong.
I was able to unlock the phone a mantain the data! Thanks
I have a special problem with an old Samsung Galaxy A3 2016 SM-A310F (Android 7.0 Nougat)
on which the correct combined file cannot be obtained
I have tried perhaps all FRP removal options without success
A310FXXS5CSH3
Recently I rooted my S9 and installed Lineage OS but I didnt like it and decided to swap back to the stock OS. I used Frija to get the .tar.md5 files for Odin but once I select all the files and hit start the log in Odin loads up to system.img then stops and I get the SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6 error on my phone. Any idea on how to fix this? I'd really appreciate some help as I'm going to be travelling soon and I need my phone for it and I'd prefer not to use Lineage OS. Thanks in advance.
Do you have an At&t branded phone? SM-G960U?
I am having a very similar problem. A customer came in and was having issues with device. I told them to back up, wipe, and update device. That didn't work so I tried a full flash with ODIN. Now I can't get the phone to boot at all and it says, "Secure Check Fail : Modem" and "Unauthorized software visit nearest AT&T blah, blah,..)
I think it is because AT&T has pushed out the latest update(OCT. 18th), but the Odin files are not out yet. According to:
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U
G960USQS7CSI5 is the latest FW. If you google it, there are only four results.
Yep, the problem was the phone was on the latest FW. Newer firmware was just uploaded a few days ago.
I flashed:
G960USQU7CSJ2_G960UOYN7CSJ2_CHA
and now I'm booting again.
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
ma777 said:
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
Click to expand...
Click to collapse
^^^^ this ^^^^
the Odin error is telling you that youre trying to flash a revision of the bootloader than was last installed on the phone. to to sammobile.com/fimrwares and get the one with the correct bootloader for your specific phone and flash that.
also download the firmware with the frija tool or samfirm. trust me, its literallt 5x faster than a direct download from the site. The 5 min it takes to get samfirm up and running is worth it, believe me on that.
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Youdoofus said:
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Click to expand...
Click to collapse
Getting no help was meant I hadn't Posted asking Questions, I read everything ya'll put up and I was able to do it on my own without continuing to ask, so Yeah I did get help here but not by asking only reading what is available
downgrade samsung sm-g570m
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
pol1345 said:
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
Click to expand...
Click to collapse
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
TheMadScientist said:
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
Click to expand...
Click to collapse
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
Like 99.9%. That's what that error is. The bootloader is blocking downgrade
pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
yes, if you get a firmware version matching the one last installed on your device, itll go right thru and boot just fine. Goodlock is finally working on all modules for A10 as well. Maybe we will see more development occur with this shutdown going on. Let us know if you run into any trouble, the error you were getting is totally resolvable!
at the end I give up on it..! my internet 2 slow 4 go downloading & trying rom after rom.! i am from venezuela.
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
I have S20+ running Android 11 with U7 Binary. I tried downgrading to Androi 10 which has Binary U5. Now I have downloaded the Binary U5 file. But in some video, he is telling that you should download the Binary File with the same number as it is currently installed in your phone, which in my case is U7. So? Am I supposed to download U7 Combination Binary file and flash it in order to downgrade to Android 10
OR
Should I flash the U5 Combination File and flash the Android 10 AP, CSC, BL, HOME ???
Someone has Combination file to G960F with bootloader SF (Version 15)?