Develop Bugs

[Q] Didn't know you couldn't downgrade 4.3 Now im stuck?

I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD

Johnnysauur said:
I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD
Click to expand...
Click to collapse
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.

andyistic said:
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.
Click to expand...
Click to collapse
You wouldn't happen to have a dl link for official would you?

Johnnysauur said:
You wouldn't happen to have a dl link for official would you?
Click to expand...
Click to collapse
Start up Kies (no cellphone connected), then go to Tools / Firmware Upgrade
It will ask you for the model number, so put that in.
Then it will ask you for either the serial number or MEID, so put that in, too.
Then it should download a big-ass android package (around 1.5 gigabytes).
After the package is decrypted, copy it from the temp directory to some safe place on your local hard drive.
Use Odin in Download Mode to install this package.
The package should end with .tar.md5

If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen

FallenZen said:
If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen
Click to expand...
Click to collapse
I downloaded the mk3 modem, and flashed it in odin, it fixed the softbrick. i rooted it with cf-auto and it went through no issue. disabled knox no problem, and now got cwm working.

[Q] Need wifi help AT&T S3

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.

Galaxy A3 FRP Unlock

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

Odin flash gets: Device:2 Binary:1

Hi Guys,
When trying to downgrade/flash below firmware via Odin I'm getting error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 2, BINARY: 1
Or if BL disabled following some recommendations:
KERNEL REV. CHECK FAIL. DEVICE:2, BINARY:1
Current version: (got via OTA)
G960FXXU2BRG6
Service provider OXM_XEF_00_0025 ... XEF/XEF, XEO/DBT - but this has probably nothing to do with that.
Returning to:
DBT-G960FXXU1BRE5
History of the phone is that I've received it on Saturday (manufactured on May 21), dual SIM + SD Card was working, got notification about OTA, and did proceed (silly me), got message that "no downgrade" will be possible - thought that it is for normal user, not the one with Odin magic, though have a feeling it has something to do with that. It was unusual message though thought it is something new on S(, but not really blocking me to downgrade with Odin.
Is there any way to downgrade? I really need to do that as thanks to Samsung I cannot use dual SIM + SD Card, described here:
https://forum.xda-developers.com/ga...o-sim-card-t3822368/post77193881#post77193881
Thanks!

When trying to downgrade/flash below firmware via Odin I'm getting error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 2, BINARY: 1
same problem, my S9 Plus is AFG cant intall only can update with DBT file but his current AFG no

Make sure you're using ODIN 3.13.x
You cannot downgrade the bootloader you can only flash firmware with an equal or higher BL version
G960FXXU2BRG6 <<< BL version 2
Check in Download mode what version yours says

*Detection* said:
Make sure you're using ODIN 3.13.x
You cannot downgrade the bootloader you can only flash firmware with an equal or higher BL version
G960FXXU2BRG6 <<< BL version 2
Check in Download mode what version yours says
Click to expand...
Click to collapse
Many thanks, that makes sense. I do remember message prior OTA apply "you won't be able to downgrade" but thought it was meaning that normal user won't be able to downgrade unless Odin would be used. Tough luck.
The worst part is that this is the first "U2" version for S9, so there's no path for me.
One more question - when "BL" was deselected and I've left only AP, CP, CSC - it resulted in message:
KERNEL REV. CHECK FAIL. DEVICE:2, BINARY:1
It is still in effort to downgrade the rest outside of BL, but does it seem I'm stuck on this firmware as the lowest on my phone now?
On technical side, these are all partitions on internal SDcard/memory. Why would it not be possible to overwrite it? Is it re-partitioning thing or something else? I'm trying to understand from where the limitation comes.
p.s. did some reading on bootloader process of Samsung and whilst it is clever and nice for Common Criteria, it should be possible to unlock it as in the past (Superboot tool). The good bootloader lecture is here: https://www.sciencedirect.com/science/article/pii/S1742287618300409 (S7 based).

Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/

batfink1 said:
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
Click to expand...
Click to collapse
What are risks using that Odin version and pushing AP?
Should I try to push BL too?
Apologies if I'm overly cautious it is that I don't want to brick the phone.

Honestly, I'm a take your balls in your hand kind of guy.
I'm a computer technician and if I spent all my time wringing my hands being cautious I'd never get anything done.
It's pretty hard to HARD BRICK these phones as long as you don't go faffing around with the partitions option in Odin.
God I've brought mine to the brink of death and back again.
Just out of curiosity, do you have a way of taking a photo of your Odin/Download mode screen... I'll try to post mine.
I'm rooted and running a customised stock based rom on BRE5

My Odin screen

batfink1 said:
Honestly, I'm a take your balls in your hand kind of guy.
I'm a computer technician and if I spent all my time wringing my hands being cautious I'd never get anything done.
It's pretty hard to HARD BRICK these phones as long as you don't go faffing around with the partitions option in Odin.
God I've brought mine to the brink of death and back again.
Just out of curiosity, do you have a way of taking a photo of your Odin/Download mode screen... I'll try to post mine.
I'm rooted and running a customised stock based rom on BRE5
Click to expand...
Click to collapse
Well... sometimes it is better to be safe than sorry... (at least this is my take), like with that unfortunate upgrade.
If you're that brave, why don't you upgrade to the latest one and then try to downgrade?
Attached is Download mode screenshot.

batfink1 said:
My Odin screen
Click to expand...
Click to collapse
Interestingly, your model shows 6GB, mine 4GB, but it doesn't matter...
Thanks... I'll debating if to give it a shot with that custom Odin version. Did you try it? Should BL be included?

I said brave, not freaking insane... Mine is rooted and working perfectly
I honestly DON'T want to go through the 17 days of possibly having to wait for the RMM STATE again haha
---------- Post added at 06:25 PM ---------- Previous post was at 06:21 PM ----------
Mines an S9+, they have 6 gig compared to the S9 which only has 4 gig.
I didn't try it, no.. I just know the modded version exists.

I'm having the same problem
Hi guys I'm having the same problem with kernel rev check fail.
I had a brand firmware and tried to make it no-brand, but something went wrong.
Now when trying to flash a no-brand firmware, Odin stops during system.img
What can I do? Do I have to reinstall the same branded old firmware that I had?
Thanks!

Ma5terDevil said:
Hi guys I'm having the same problem with kernel rev check fail.
I had a brand firmware and tried to make it no-brand, but something went wrong.
Now when trying to flash a no-brand firmware, Odin stops during system.img
What can I do? Do I have to reinstall the same branded old firmware that I had?
Thanks!
Click to expand...
Click to collapse
Just a thought - your non-brand might be of an older release than branded software. In worst case you're stuck on working branded soft?

i tried, i doesn't work either with/without BL
batfink1 said:
Have you tried the patched Odin 13.3.1
https://www.google.com.au/amp/s/for...id/software/patched-odin-3-13-1-t3762572/amp/
Click to expand...
Click to collapse
i tried, i doesn't work either with/without BL selected. so i guess the modified odin did not fit for the new firmware.

I Tried
Me too being the grab your balls by the hand person that likes to boldly go where no man has gone before, attempted the patch version of Odin on my s9 in an attempt to put the TMO firmware on to get RCS chat. Using BL AP CL and CSC all did not work. I got the same stupid message regarding the downgrade. I then tried AP and CSC alone. Same issue. Finally, I tried just CSC. It gave a similar error but it was difference in the sense that it says [cache]fused 2 > Binary 1.
It's super annoying that you can't move from u1 to u (unlocked to carrier) without having to do all this crap.

Hey all, dunno if you resolved the kernel error but I was getting the same thing on my S8 (SM-G950F) and ended up checking if anyone at the Samsung store could fix it (they could). Have a look at this post I wrote up, hopefully it's somewhat useful.
https://forum.xda-developers.com/showpost.php?p=77580177&postcount=18

Same problem I got. No matter if I use modded or normal ODIN... Even if I do not flash Boot, I got the message Kernel Rev. check fail...
To me, this is almost criminal from Samsung... I pay 800 Euro for the phone and I like to run a different system. I think there is no law against using a Computer (which in fact it is) with an Operating system of my choice.
To me, a restriction of "liberty".

joe535 said:
Same problem I got. No matter if I use modded or normal ODIN... Even if I do not flash Boot, I got the message Kernel Rev. check fail...
To me, this is almost criminal from Samsung... I pay 800 Euro for the phone and I like to run a different system. I think there is no law against using a Computer (which in fact it is) with an Operating system of my choice.
To me, a restriction of "liberty".
Click to expand...
Click to collapse
ODIN is a Samsung INTERNAL tool, you're not even meant to be using it
And you do have the freedom to run whatever OS you want, you have that choice the day you choose to buy a new phone, otherwise read the smallprint, pretty sure you agreed to Samsungs terms when you bought the phone
I don't get why people buy Samsung phones knowing how locked down they can be, knowing they don't run vanilla Android, knowing about KNOX, and then complain when they can't do anything with them.... if I wanted to mod my phone without any problems I wouldn't be buying Samsung

Anyway, honestly I accidentally updated my spare S9 to U2 forgetting it can't be rolled back and I had a little bit of trouble finding a firmware that ran fine with gravity box, but now I'm running a custom BRI3 rooted with magisk running gravity box where 99% of features work including lock screen security.
So unless the U2 bootloader is effecting you in some way... Does it matter if you can't roll back.

Well, the hardware of Samsung I actually do like.. But the software policy I do not.
For sure, never again I will buy Samsung

Having issue flashing with Samsung S9 SM-G960F

Long story short I rooted my phone with Magisk, fully unrooted then me being stupid I went into settings and turned off OEM Unlock it had to wipe the device since then had this FRP lock, Now i was told only way to fix this is to flash with the default software since this i've run into problems with ODIN when loading the files into the phone it gets stuck on recover.img on Odin and on the phone it says sw rev check fail bootloader device 2 binary 2.
If you guys can help fix I would be so happy
Thank you

gilescore said:
Long story short I rooted my phone with Magisk, fully unrooted then me being stupid I went into settings and turned off OEM Unlock it had to wipe the device since then had this FRP lock, Now i was told only way to fix this is to flash with the default software since this i've run into problems with ODIN when loading the files into the phone it gets stuck on recover.img on Odin and on the phone it says sw rev check fail bootloader device 2 binary 2.
If you guys can help fix I would be so happy
Thank you
Click to expand...
Click to collapse
Make sure you're not trying to downgrade the bootloader, has to be the same version or higher that you're flashing
Download mode look for BL:1 or 2 or 3, and pick a firmware with that number or higher as shown below
G960FXXU2BRJ3 << Version 2

Thanks man thats fixed it
*Detection* said:
Make sure you're not trying to downgrade the bootloader, has to be the same version or higher that you're flashing
Download mode look for BL:1 or 2 or 3, and pick a firmware with that number or higher as shown below
G960FXXU2BRJ3 << Version 2
Click to expand...
Click to collapse
Thank you so much

gilescore said:
Thank you so much
Click to expand...
Click to collapse
No probs :good: