S20 Ultra FRP Locked - Samsung Galaxy S20 / S20+ / S20 Ultra Questions &

Recently my relative purchased used S20 Ultra 5G (Region SKZ). After the factory reset the phone is locked on FRP . I am not able to get in touch the person from whom my uncle bought the phone.
I could have approached official Samsung gallery but since the phone is used there no invoice nor the guy who sold provide original one. Now stucked in hard place and dont know what to do.
However I did following things as a way around.
1. Used frp hijacker by hagard tool but since the model is new one there is no frp support for s20 ultra in that.
2. Used Samfirm to open browser method but no luck there either the Tool is not able to Open browser event action .It is failing.
3. Did try to capture screen shot way too but new updates are blocking to take screenshot.
4.Tried to flash combination file with pit file but getting 'Please get approval for binary files (bootloader). --this is most success way but kinda stucked at this step.
Not sure what can be done..
Please share if any way around on latest security update on FRP.
PDA : G988BXXU5BTJ3 currently installed. let me know if any other details required.

dhirajp3003 said:
Recently my relative purchased used S20 Ultra 5G (Region SKZ). After the factory reset the phone is locked on FRP . I am not able to get in touch the person from whom my uncle bought the phone.
I could have approached official Samsung gallery but since the phone is used there no invoice nor the guy who sold provide original one. Now stucked in hard place and dont know what to do.
However I did following things as a way around.
1. Used frp hijacker by hagard tool but since the model is new one there is no frp support for s20 ultra in that.
2. Used Samfirm to open browser method but no luck there either the Tool is not able to Open browser event action .It is failing.
3. Did try to capture screen shot way too but new updates are blocking to take screenshot.
4.Tried to flash combination file with pit file but getting 'Please get approval for binary files (bootloader). --this is most success way but kinda stucked at this step.
Not sure what can be done..
Please share if any way around on latest security update on FRP.
PDA : G988BXXU5BTJ3 currently installed. let me know if any other details required.
Click to expand...
Click to collapse
Did you try the @ method?
Edit; nvm, it is an old method.
Did you flash full firmware? Idk if that matters...

twismo1 said:
Did you try the @ method? -- which method?
Edit; nvm, it is an old method.
Did you flash full firmware? Idk if that matters...
-- this is will not solve tried this also
Click to expand...
Click to collapse

Related

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

tab s4 locked by user .... how can I unlock it ?

I have a tab S4 that is locked by the previous owner.
and I don't know the person to get the google account or password.
Any thoughts on how to unlock it
I can reset to factory default, but it keeps asking for the previous person account and password.
can I install a new rom and get past the user lock ?
https://forum.xda-developers.com/galaxy-tab-s4/how-to/how-to-bypass-google-account-lock-sm-t3893933
thanks for the link. I am not sure which of the roms I should use .... should I use the latest one ?
I purchased a tab s4 on ebay with the locked by user problem.
I followed this thread :
https://forum.xda-developers.com/galaxy-tab-s4/how-to/how-to-bypass-google-account-lock-sm-t3893933
I am able to install the combination firmware, but am unable to install the stock firmware listed there ... odin 3.13.1 will not load it, repeatedly fails
Is there a combination firmware of the stock firmware that I can install?....( does that even make sense)
All I want is a working tablet .. don't need root or anything else.
Although if rooting it will help I could probably do that, but I am afraid of bricking it!
Edit : follow up, I got it working I needed a later firmware and it loaded fine
This is the firmware dated 12/2018
https://drive.google.com/file/d/1hvf4ge2o0UkzOcAzEjKFkuEzrJP1OTjK/view?usp=sharing

Error when installing stock OS: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6

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)?

Help rooting note 10+ N975F/DS please

Hi all,
It's a couple of days I am trying to root my note10+ however even looking very simple I can't go over the bootloader.
Following the istruction I have:
downloaded firmware accordingly
patched with magisk
unlocked bootloader
unlocked developer mode and toggled OEM unlocking option
When using odin I get the error on phone "blocked by OEM lock" even if it is ulocked on the mobile, I've tried everything!
Any idea please?
Attaching photo as the only doubt I have is on the bootloader screen where I can read on top "odin by xxx"
Thank you in advance
which instructions did you follow?
can you please give me instructions on my smn975u
slinger198569 said:
can you please give me instructions on my smn975u
Click to expand...
Click to collapse
It's not nice to hijack someone else thread.
https://forum.xda-developers.com/t/...sh-twrp-snapdragon-only.4195891/post-84012015
w41ru5 said:
which instructions did you follow?
Click to expand...
Click to collapse
Hi w41ru5, thank you for your reply
I've been searching around, at the end I could manage to unlock properly the bootloader and root with a custom ROM my mobile, harder than expected to find proper files for this model
got stuck bootload, on twrp, some bootloop, stuck after magisks update, but finally is ok now
did you find a solution? I manage to root tricking the lz4 files which is the new type of extension in Android and for this you can not root in a normal way. I followed this guide
Fix Oreo Firmware Installation Issue in Odin for Samsung Devices - DroidViews
Android Oreo has finally made its way to Samsung's latest S series flagships, the Galaxy S8 and S8+. The Oreo update brings with it the usual Android Oreo features such as Picture-in-Picture, redesigned Settings app, etc. It also brings with it Samsung Experience 9.0 which is but a fancier name…
www.droidviews.com
After having the 4 stock files modified without lz4 you must flash them with Odin.
After you take the modified AP file and patch it with Magisk.
Then you flash again stock using the patched AP file and the rest of modified files but you must not select autoreboot in Odin. When the flashing is done you must exit download mode and imediatelly enter in Recovery mod but better use this guide
How to Root Samsung Galaxy Note 10 and Note 10+
In this tutorial, we will show you how to unlock the bootloader and then root Samsung Galaxy Note 10/Note 10+ using Magisk. This guide supports Exynos variants of the Galaxy Note 10 and Note 10+ with…
www.thecustomdroid.com
This methods do not work for me now. I am in the latest R update 07 and it seems dont work. I am serching how to root my phone now...

Categories

Resources