Had no idea the dev options needed to be left ON regardless after rooting, or it rejects the custom binary? Would have thought the FRP lock would have been bypassed with the rooting. Can't enter twrp recovery neither.
And to be 100% clear, phone is rooted. Dev option was unticked w/o realizing it'd retroactively lock the phone as it detects the non-oem firmware and refuses to boot, refuses recovery, refuses flashing.
Can I somehow flash a stock firmare via Odin and NOT get the wrath of FRP? I found the stock firmware for the phone from Samsung's site. For some reason, the firmware.zip is like 1.4gb? Do I need to strip out a file for the recovery image assuming it'll accept it? Or just select the entire thing in Odin?
OK, flashed the 2.5gb (unzipped it had THAT much bloat) factory Samsung firmware, which took about 2.5 minutes vs. like 4 sec for the root .img :silly: and phone boots back up w/o issue, all personal stuff is intact, and unsurprisingly it adds all the bloatware back that I just deleted earlier.
So, if you accidentally turn off the dev options or I'm assuming the OEM unlocker specifically on your J7, and the phone refuses to boot as it's retroactively detecting "custom binary", OR if you happen to accidentally truly delete an important app and/or it can't be brought back with 3rd party apps, going to Samsung's firmware section, finding your EXACT phone/model/software numbers including the most recent OS and security upgrade to it i.e. 7.1.1 in my case, flashing it with Odin (site said to use most recent, so used v3.13.1) will restore the phone, unrooted of course. But it's better than a paperweight.
Related
Hi there,
I have a Samsung Galaxy Tab A6 (SMT-580) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
dottech .org/200476/how-to-install-twrp-recovery-on-samsung-galaxy-tab-a-sm-t580/
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Hi. Have you got it fixed yet? You need to download and flash stock firmware for your model and flash it in odin. Once it's done you have to enable oem unlock before you flash twrp. Let it be enabled as long as you you have twrp, root or anything custom.
Skickat från min SM-A310F via Tapatalk
ok, I read this is the place for noobs, so, I too got myself into a FRP LOCK on my Galaxy Tab A6 sm-T280. I use the tablet strictly for flying my drone for surveillance around the rural location where I live. It was having some connectivity problems, so I rooted it to hopefully get enough horsepower to run the DJI Go app. That didn't work so I did a wipe/factory reset, had a problem with the password, and here I am.
I am researching, and gathering the required tools to fix it.
I finally found some guides that are basic enough for me to understand.
I found numerous sites to download the stock rom, but not sure which ones are safe. Suggestions? Also, I am not sure about the country code for the firmware. I am in the USA, and I don't see it listed anywhere. Does it matter? This android stuff is all new and confusing to this old man. I am determined to get this tablet fixed, and would appreciate any and all advice. Thanks, Gary
edit: Will this rom work? : T280XXUOAPL1 using XAA for theCSC? Is xaa the default/generic for U.S.A. ?
Hi guys, i have a galaxy s7 of a customer that doesn't absolutely remember email and password for his google account connected to the phone(and so it's OEM Locked).
i tried to follow many guides on the forum but this happened:
i can't root the phone (because the FRP is locking the Flash),
nor install 6.0.1 (because of the error "sw rev check fail device 2 binary 1")
i can't use bluetooth method to skip setup guide (it was fixed in 6.0.1)
i can't use RealTerm because it can't make me save the number to proceed the guide(also fixed in 6.0.1)
what can i do? how do i bypass the FRP? or how do I downgrade to 6.0.1?
Downgrading can be a problem caused by the bootloader, make sure you try to flash a stock ROM with the same version bootloader as shown with this number
G930FXXU2ERD5
The customer would have had to enter a secondary / recovery email while making that Google account, tell them to check their other email addresses for confirmation emails around the time they set up the phone, then they can find the email address of the google account and reset the password to that email address
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
LaHunnid said:
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
Click to expand...
Click to collapse
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
*Detection* said:
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
Click to expand...
Click to collapse
I did that and it didn't brick
LaHunnid said:
I did that and it didn't brick
Click to expand...
Click to collapse
AP is the system / OS, you're telling OP to flash a new version of Android (AP) with an old bootloader, in order to downgrade to 6.0.1, your method would not downgrade anything other than bootloader & modem and old bootloader with new OS will almost certainly brick
To downgrade you need to flash old bootloader (BL) & old Android 6.0.1 (AP), and probably old modem (CP), CSC is the only thing left
And as already stated, downgrading the BL is the problem that prevents most people from downgrading in the first place
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Massive thanks
S6unbricker said:
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Click to expand...
Click to collapse
I've been absolutely stuck for days trying to sort out the bloody FRP lock on an S7 (SM-G930F) that had been gifted to my wife by my father-in-law where he hadn't removed the accounts before passing it over.
My wife then did an update that the phone requested when it started up and that went wrong at which point I get involved and factory reset it...oh BIG mistake... and that's where my problems started made worse by the fact my father-in-law couldn't remember which account he had setup on the phone....or even the password to possible accounts!! I consider myself to be well versed in all things tech but I had absolutely no idea FRP existed and was absolutely baffled when i saw the message on the screen after flashing the stock firmware (G930FXXU2DRB6) that was on there according to the recovery mode. I've been trying so many different things over the past week all current methods failed...then I came across this one...which had seemed to be blocked by admins but I was able to click on the link in the 2nd post and grab the password from the readme in the first, which i must admit made it a bit dubious and not sure why @S6unbricker felt the need to do that but there's no issues it doesn't go to a stupid survey site or anything it just goes to a text file on mega which has one line and that's the password!
I followed the method to the letter and, to my surprise and joy, it's actually worked a treat...the S7 is no longer a paper weight!!!
Massive thanks to @S6unbricker :good: ...any chance of re-posting but without the password on the file or putting the password in the post?
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
deshaney said:
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
Click to expand...
Click to collapse
From my experience the combination roms (which I presume you are referring to when you say eng bootloader) didn't solve my issue. Yes I could get them on the phone and boot into them, change the settings or use adb but obviously I don't want the factory binary to stay on there so as soon as I flashed it back to the current firmware, back to square one!
Most poeple advised to use HOME CSC instead of CSC when flashing from combination rom back to stock but I couldn't get odin to flash with HOME CSC.
No I'm referring to the boot.img file. Combination ROMs don't enable su access via she'll.
Samsung s7
Ok I know this is an old Post but I'm brand new to Odin and all the unlock lingo.. can anyone explain to me how to downgrade to bypass the frp on my Galaxy I just bought , I'm very tech savvy just need a walkthrough any help would be greatly appreciated
Samsung Crown SM S767VL
I keep auto updates turned off. Somehow last night out of no where my phone started a software update. Now I have even more junk than before and no way to disable anything. Also phone keeps popping up "Sim card Updating" completely knocking me offline etc. How can I go back to the previous software do I have to root? Thanks for any advice!
Lee96008 said:
Samsung Crown SM S767VL
I keep auto updates turned off. Somehow last night out of no where my phone started a software update. Now I have even more junk than before and no way to disable anything. Also phone keeps popping up "Sim card Updating" completely knocking me offline etc. How can I go back to the previous software do I have to root? Thanks for any advice!
Click to expand...
Click to collapse
If you took the update and installed. It probably updated the bootloader. If that happend you probably can't down grade. The bootloader can't be down graded and judgeing by what my phone did It won't let you flash the other parts of the rom If they don't match the bootloader. I have a tracfone sm-s767vl useing straight talk
Signing boot images for Android Verified Boot (AVB) [v8]
Various Android devices support Android Verified Boot (AVB). A part of this is more commonly known as dm-verity, which verifies system (and vendor) partition integrity. AVB can however also verify boot images, and stock firmwares generally...
forum.xda-developers.com
Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.
I'm on the latest version of android.
A little birdie gave me a neat set of files and I was able to successfully flash them, RES OK!
................But..............
When booting, android complains about the vbmeta file and says, "you have flashed custom firmware, the device is now locked. Please contact your service provider"
I was a bit worried at first but just flashed the stock image and I was up and running again.
The flash was supposed to enable the OEM Unlock option but the security put in place on the device prevents the system from even booting.
Can anyone shed light if I am close or if this is futile?
Thanks
**EDIT** - Without unlocked bootloader, flashing anything is useless, successfully or not.