Hey, guys! This is my first time posting, so I apologize if my post is missing some key details or isn't of quality in some other way.
I am currently looking into installing LineageOS onto my Samsung Galaxy A7 (SM-A720S); on the LineageOS installation documentation, it said to make sure that my device was running Android Oreo (Android 8.0). Since my device had Android Pie (Android 9.0) installed, I downloaded the Android 8.0 stock ROM for my device and region from SamMobile, and I also downloaded Odin v3.14.1 (un-patched as I am using a ROM for the same region) from the XDA forums.
Furthermore, I turned on developer settings on my phone and enabled OEM unlocking and USB debugging. Attempting to flash Android 8.0 onto my device resulted in the following error message:
SW Rev. Check Fail (Bootloader) Device: 5 Binary: 3
Click to expand...
Click to collapse
From poking around in the forums, I learnt that this means there is a mismatch between the bootloader version and the binary I am trying to flash. Is there any way to either downgrade the bootloader in order to be able to flash Android 8.0 or is there some way to trick the device/odin into thinking that the Android 8.0 has a binary of 5?
I really want to try LineageOS. so I would appreciate any advice on how to work around this issue.
That was a slight oversight on my end, because there aren't many A720S users. Your pie bootloader is fine, you can flash lineage.
Related
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
Hi guys, I recently purchased a refurbished S9+ without knowing the model and it turned out to be a SM-G965U. After a failed software update ("Your current software isn't supported. Visit a service centre"), I've been trying to find a way to update the phone to 'official' Android 10. Does anyone know if this is possible or is the phone locked to Android 9?
'OEM Unlock' is missing from developer settings which (I think) means it can't be rooted with any common method. But is it possible to flash the phone with an official, working version of Android 10?
I'm willing to use any method required (within reason) to update the phone to a working version of Android 10. I'm aware of the "Extreme Syndicate" root method but the bugs / missing features rule it out for me. I intend to get a refund for the phone if it can't be updated to Android 10 so I'd really appreciate any answers to my questions.
Thanks!
You can manually update your phone by using Odin, and download the latest firmware available by using Frija
B1nz said:
You can manually update your phone by using Odin, and download the latest firmware available by using Frija
Click to expand...
Click to collapse
That's good news. Just to confirm, I can manually update with Odin WITHOUT unlocking OEM in the develop settings? Thanks for replying.
Just confirming that I successfully updated to Android 10 using Odin. The CSC I used is for an American carrier and the phone tries to register on its network but that's easily disabled. Had to be done after every reboot but it's a small price to pay for a working phone....
Hello Guys, I'm currently stuck on G965USQU3ZRLG
I made use of firmware.science to update my S9 plus to this point, but it seems there's no further firmware update for G965USQU3ZRLG to the next update file. Kindly assist, thank you.
I currently have an Unlocked Z Fold3 purchased directly through the Samsung US site.
Model: SM-F926U1
Baseband version: F926U1UEU1CVC5
I would like to downgrade to Android 11 to see if it resolves the no service issues with T Mobile the update caused. Does anyone know if this is possible?
Yes. Download android 11 package and use Odin
domineus said:
Yes. Download android 11 package and use Odin
Click to expand...
Click to collapse
I thought I needed an unlocked bootloader for this? If its that easy is there a way to prevent getting the update to 12?
No, Odin flashes the Android firmware.
Unlocking the bootloader gives the ability to install TWRP, custom ROMs, and delve into the system folder easily. Odin flashes firmware. However, once you update a bootloader, you cannot roll that back...if I remember correctly.
was the bootloader updated in the Android 12 update? if it was that means flashing Android 12 really wouldn't change anything or may not even be possible?
Hi everyone,
for a customer project we have created a custom build of LineageOS 18.1 for SM-P610 and I have an image that is complete with our signage software.
I used to be able to flash these devices following the official installation instructions from the LineageOS page https://web.archive.org/web/20211002124915/https://wiki.lineageos.org/devices/gta4xlwifi/install
Now this doesn't work anymore. On some devices, I can't even unlock the bootloader. This has been discussed elsewhere and I have tried all the tricks from manipulating the datetime to logging on with a google or even a samsung account.
But even on the devices where I could onlock OEM, I can't seem to install the LineageOS recovery. I always get the error message "Only official released binaries are allowed to be flashed (RECOVERY)". FAP LOCK is OFF and OEM LOCK is OFF(U).
It says in the LineageOS install instructions that I must have the latest official Android 11 firmware installed. Previously, I would simply OTA update to this firmware, but nowadays, OTA goes directly to Android 12. So I tried downloading the only available Android 11 firmware from sammobile and flashing it in Heimdall. But unfortunately, I still get the same error message.
Can anybody please tell me which version of the Samsung bootloader I need exactly to install this version of the LineageOS recovery: lineage-18.1-20220112-recovery-gta4xlwifi.img?
Bonus question: Does anybody still have this firmware version mirrored somewhere?
edit: I have downloaded a newer recovery from the internet archives: lineage-18.1-20220504-recovery-gta4xlwifi.img
Now a get a different error message: "Custom binary(RECOVERY) blocked due to remaining installment balance".
Can somebody tell me what this means?
Do you really need LineageOS recovery specifically? Perhaps you may have better luck with the TWRP Recovery and then flash the OS through that instead. It was successful on my Galaxy S4 Mini.
Pelii said:
Do you really need LineageOS recovery specifically? Perhaps you may have better luck with the TWRP Recovery and then flash the OS through that instead. It was successful on my Galaxy S4 Mini.
Click to expand...
Click to collapse
Tbh I don't know. So how would that work? I Install the TWRP recovery (how?) and then I proceed to install the LineageOS image?
Well, looking at TWRP's website and the forums here, there's actually no build for your model specifically, so it seems you're out of luck on that one.
I suppose what's left is to just keep trying different sources of LineageOS recovery, because neither of the errors you described so far look like anything you can fix from your end.
Update: I have found what seems to be the exact Samsung firmware that was the latest one at the time:
https://samfrew.com/de/download/Galaxy__Tab__S6__Lite__-Wi-Fi-__/0kd5/DBT/P610XXU2DUL9/P610OXM2DUL9/
I'm currently downloading.
Also, I have been able to bring one of the really old devices to exactly this firmware state by OTA by cycling through 3 consecutive incremental updates. I was pretty excited to bring it into download mode, only to see this strange error "Custom binary(RECOVERY) blocked due to remaining installment balance" yet again.
I'm in a bit over my head, so apologies if some of this doesn't make sense.
I have a Galaxy S9 that I want to install Android 9 on. For context, I'm an app developer and I have a bug that's been reported to be only on Android 9 - and emulators aren't reproducing the issue.
Unfortunately, it has Android 10 already installed on it, and so far as I can tell, installing Android 9 requires rooting the device.
At first, I tried directly installing an Android 9 firmware onto the phone using Odin - this gives the error "sw rev. check fail(bootloader) device 17 binary 7".
I then installed TWRP - which worked, but now I don't know what I need to do to actually get Android 9 onto the device... any help would be appreciated!
wwnsw said:
I'm in a bit over my head, so apologies if some of this doesn't make sense.
I have a Galaxy S9 that I want to install Android 9 on. For context, I'm an app developer and I have a bug that's been reported to be only on Android 9 - and emulators aren't reproducing the issue.
Unfortunately, it has Android 10 already installed on it, and so far as I can tell, installing Android 9 requires rooting the device.
At first, I tried directly installing an Android 9 firmware onto the phone using Odin - this gives the error "sw rev. check fail(bootloader) device 17 binary 7".
I then installed TWRP - which worked, but now I don't know what I need to do to actually get Android 9 onto the device... any help would be appreciated!
Click to expand...
Click to collapse
Short of installing a custom ROM, I'm not sure what else you can do. I would suggest a GSI but they all seem to be Android 10 and up, unless you want to try something like this.
V0latyle said:
Short of installing a custom ROM, I'm not sure what else you can do. I would suggest a GSI but they all seem to be Android 10 and up, unless you want to try something like this.
Click to expand...
Click to collapse
Thanks - by `custom ROM`, do you mean something like LineageOS? Or are you saying I'd have to build something from source?
(I think the answer here is probably to just get a phone that hasn't/can't been upgraded past Android 9)
wwnsw said:
Thanks - by `custom ROM`, do you mean something like LineageOS? Or are you saying I'd have to build something from source?
(I think the answer here is probably to just get a phone that hasn't/can't been upgraded past Android 9)
Click to expand...
Click to collapse
I mean anything in .zip or .img form. It could be anything from a very slightly modified version of the Android 9 system+kernel for your device, to a full blown GSI.
The reason you can't use Odin to flash the original Android 9 firmware is because of an anti-rollback mechanism in the bootloader.
Since you're a developer, I would suggest finding a developer friendly device, like a Pixel. They have zero bloatware on them - they're meant to be the pure vanilla Android experience. The Pixel 2 launched with 8.0, and you can find it for less than $100. Just make sure you don't get a carrier branded device.