So I have an Exynos S8+ (G955F) with bootloader v5. I have been trying to flash TWRP onto it to no avail.
I flashed Android Pie (9.0) and attempted to flash TWRP, but I get the "Only official binaries are allowed to be flashed(recovery)" error. I noticed both my RMM and KG states were "prenormal". So I attempted (many times btw) the RMM/KG bypass with the date change, update check, auto-date, update check, dev options, oem off and on, etc. I got the KG state to change to "checking" (made some progress I guess), but the RMM state stays at "prenormal".
One of my problems with the RMM/KG bypass is that it's shown as a RMM/KG bypass rather than a RMM AND KG bypass (to get both into "checking" or w/e). I don't know if I am reading too deeply into the meaning of the slash, but I am confused as to whether the bypass should be solving either one OR the other, rather than both (RMM AND KG).
But that's beyond the point. If someone could help me figure this out I would really appreciate it. I've been through thread after thread and I cannot seem to find anything else that will fix my problem.
Thanks in advance!
I was contacted by BIOKNOX and they offered to help me with my problem. Long story short, solved my problem. Thank you very much.
Fritzy8 said:
I was contacted by BIOKNOX and they offered to help me with my problem. Long story short, solved my problem. Thank you very much.
Click to expand...
Click to collapse
Share the solution, otherwise your post is useless.
w41ru5 said:
Share the solution, otherwise your post is useless.
Click to expand...
Click to collapse
Probably a spam paid site. More than likely
Related
I have a Samsung J320V or J36V which is on the Verizon network. I really want to root it to unlock the full potential of my phone and I understand it will void my warranty but I'll go ahead and do it anyway. When I follow the steps to root I get stuck at the Odin part which I have to click start and the TWRP file installs on my phone. But it fails and I get this message on my phone "SECURE BOOT FAIL RECOVERY"! I've looked everywhere for a solution but none of them work and I also enabled USB DEBUGGING and OEM UNLOCK. I also couldn't disable REACTIVATION LOCK because the feature is not on my phone and I also removed my Google account and Samsung account. If anyone could help you would be the real MVP and I would really really really appreciate it from the bottom of my heart! Even if you saw my post and can't help still thank you for taking time out of YOUR day and looking at my problem!
XpertSource said:
I have a Samsung J320V or J36V which is on the Verizon network. I really want to root it to unlock the full potential of my phone and I understand it will void my warranty but I'll go ahead and do it anyway. When I follow the steps to root I get stuck at the Odin part which I have to click start and the TWRP file installs on my phone. But it fails and I get this message on my phone "SECURE BOOT FAIL RECOVERY"! I've looked everywhere for a solution but none of them work and I also enabled USB DEBUGGING and OEM UNLOCK. I also couldn't disable REACTIVATION LOCK because the feature is not on my phone and I also removed my Google account and Samsung account. If anyone could help you would be the real MVP and I would really really really appreciate it from the bottom of my heart! Even if you saw my post and can't help still thank you for taking time out of YOUR day and looking at my problem!
Click to expand...
Click to collapse
Greetings and welcome to assist. I can see you have already asked this question here
http://forum.xda-developers.com/showthread.php?t=3497140
and here
http://forum.xda-developers.com/showthread.php?t=3435514
so I will close this one up. Please just make the one thread in future
Good Luck
Sawdoctor
I'm rooted via ODIN with TWRP. I got a browser hijacker that put my browser home page to some stupid ad, so I tried to get rid of it using the AVG antivirus program. That program recommended I disable "developer mode" on my phone ... and like a total idiot I followed their instructions.
Next time I tried to boot ... I get the "Custom Binary blocked by FRP Lock" message.
I am on vacation and I REALLY need my phone. I can't believe Samsung can just lock me out of my own phone like this. I can get into download mode. Do I try to reflash with Odin or what?
ANY help would be greatly appreciated ...
EDIT: forgot to mention I was on Nougat stock ...
Haints said:
I'm rooted via ODIN with TWRP. I got a browser hijacker that put my browser home page to some stupid ad, so I tried to get rid of it using the AVG antivirus program. That program recommended I disable "developer mode" on my phone ... and like a total idiot I followed their instructions.
Next time I tried to boot ... I get the "Custom Binary blocked by FRP Lock" message.
I am on vacation and I REALLY need my phone. I can't believe Samsung can just lock me out of my own phone like this. I can get into download mode. Do I try to reflash with Odin or what?
ANY help would be greatly appreciated ...
EDIT: forgot to mention I was on Nougat stock ...
Click to expand...
Click to collapse
No one is willing to advise me on this ... ?
Odin back to stock seems to be the only way forward? At the same android os level or higher?
flash back stock firmware and next time never disable oem unlock in developer options on rooted phone
Haints said:
No one is willing to advise me on this ... ?
Odin back to stock seems to be the only way forward? At the same android os level or higher?
Click to expand...
Click to collapse
You need to call T-Mobile and request that they help you because this FRP lock deals with stolen phones, which I'm not accusing you of. Just saying.. If you Odin back it's going to ask for the original Google account info and password and if you have that just enter it into the phone and then you'll be able to get back into the phone to enable it again. But if you don't have the Google account and password, that's a problem.
AntonPres said:
flash back stock firmware and next time never disable oem unlock in developer options on rooted phone
Click to expand...
Click to collapse
I just finished doing exactly as you describe when I checked back here to see if anyone had responded. So even though I had successfully reflashed my phone before I saw your advice, I still appreciate you're willingness to help and the fact that your solution is the correct one.
I've been rooting my phones for years and had never heard of the developer mode warning or run into FRP lock before. I won't forget either now, though.
In case anyone else runs into this issue:
I found my exact stock tmobile rom on sammoble ( sign up, use free download mode, takes forever but it is free) and downloaded the tar/mdf file.
Used Odin3 v3.11, select AP then find your tar/mdf file.
Put phone into download mode and when Odin recognizes it, hit start.
I thought it looped at the tmobile logo but it just took a while so be patient.
Not only do I have a fully working phone again, but contrary to what I had read--that the only way to defeat the FRP lock would entail losing all my data--I lost NOTHING. My phone is EXACTLY the way it was before, including the fact that Developer mode is now enabled AGAIN. How is that possible? I don't know, but I'm very very happy that all I lost was time.
you only lost root, flashing same version explains that you didn't lost your data
MrMike2182 said:
You need to call T-Mobile and request that they help you because this FRP lock deals with stolen phones, which I'm not accusing you of. Just saying.. If you Odin back it's going to ask for the original Google account info and password and if you have that just enter it into the phone and then you'll be able to get back into the phone to enable it again. But if you don't have the Google account and password, that's a problem.
Click to expand...
Click to collapse
When I Odin'ed back it didn't ask me for anything--my phone was exactly the way it was before.
Phone is not stolen. I bought it used off craigslist and had the seller meet me at a tmobile store to verify that it was clean before I bought it. I
This happened while I was on vacation and I really, REALLY needed a working phone. Called samsung and the first rep I spoke to in India--as soon as she heard "FRP Lock," she basically said: "You're ****ed." She also said it was my fault that I had a crippled phone because I never should have rooted it in the first place. When I argued that the root hadn't crippled my phone,--I'd been using it rooted for months with no issues--but that the FRP lock had crippled it, she said FRP lock wasn't Samsung's fault, but Google's fault, and if I needed a solution to FRP lock, I should talk to Google. Classic buck-passing mode. Like Google would have helped me.
Second rep I spoke to was much more helpful, even though she couldn't really help me. She eventually suggested I get the IMEI from tmobile, then send my phone into Samsung and they would fix it--at my cost, presumably.
Thanks to the power invested in me by the internet, however, I didn't have to find out what would have happened if I'd sent my phone to Samsung.
Happy, happy day, and good luck to anyone who runs into this issue in the future!
Haints said:
When I Odin'ed back it didn't ask me for anything--my phone was exactly the way it was before.
Phone is not stolen. I bought it used off craigslist and had the seller meet me at a tmobile store to verify that it was clean before I bought it. I
This happened while I was on vacation and I really, REALLY needed a working phone. Called samsung and the first rep I spoke to in India--as soon as she heard "FRP Lock," she basically said: "You're ****ed." She also said it was my fault that I had a crippled phone because I never should have rooted it in the first place. When I argued that the root hadn't crippled my phone,--I'd been using it rooted for months with no issues--but that the FRP lock had crippled it, she said FRP lock wasn't Samsung's fault, but Google's fault, and if I needed a solution to FRP lock, I should talk to Google. Classic buck-passing mode. Like Google would have helped me.
Second rep I spoke to was much more helpful, even though she couldn't really help me. She eventually suggested I get the IMEI from tmobile, then send my phone into Samsung and they would fix it--at my cost, presumably.
Thanks to the power invested in me by the internet, however, I didn't have to find out what would have happened if I'd sent my phone to Samsung.
Happy, happy day, and good luck to anyone who runs into this issue in the future!
Click to expand...
Click to collapse
What I meant by Odin back was you can get back into the phone and just re-enable the OEM unlock in developer settings and you won't have to worry about the FRP crap again.. And you're right I highly doubt Google would have given a crap and gave you the run around again.
Most of the time, I can bypass the frp on a galaxy s7 with no issues. I simply flash combination, use frp hard unlocker 3.0 provided by hardreset, then flash factory firmware. My problem lies with some devices only bootlooping once the factory firmware has been flashed. I can go in and flash the combination file with no issues, but I'm just tying to figure out what would cause this and how to get past it. Thanks for any info you may have.
VELEGIS said:
Most of the time, I can bypass the frp on a galaxy s7 with no issues. I simply flash combination, use frp hard unlocker 3.0 provided by hardreset, then flash factory firmware. My problem lies with some devices only bootlooping once the factory firmware has been flashed. I can go in and flash the combination file with no issues, but I'm just tying to figure out what would cause this and how to get past it. Thanks for any info you may have.
Click to expand...
Click to collapse
The firmware being updated and blocking the old FRP bypass method.
cooltt said:
The firmware being updated and blocking the old FRP bypass method.
Click to expand...
Click to collapse
Can you elaborate? thanks.
VELEGIS said:
Can you elaborate? thanks.
Click to expand...
Click to collapse
Sure,
So the whole point of FRP lock is to stop lost / stolen phones being factory reset and used again. However when you modify you may forget to turn it off (not a problem if you know email and password) then when the phone starts up with fresh firmware the FRP kicks in and you are locked out.
Others found an exploit to get round the FRP lock, combination rom's etc but with every new firmware update the exploit is closed and it no longer works. You have to wait until someone finds a new way around FRP lock for your specific device and since the S7 is now getting old, no one is bothered fixing the FRP lock problem anymore.
The easy solution is to always remove the google account before modifiying the device.
cooltt said:
Sure,
So the whole point of FRP lock is to stop lost / stolen phones being factory reset and used again. However when you modify you may forget to turn it off (not a problem if you know email and password) then when the phone starts up with fresh firmware the FRP kicks in and you are locked out.
Others found an exploit to get round the FRP lock, combination rom's etc but with every new firmware update the exploit is closed and it no longer works. You have to wait until someone finds a new way around FRP lock for your specific device and since the S7 is now getting old, no one is bothered fixing the FRP lock problem anymore.
The easy solution is to always remove the google account before modifiying the device.
Click to expand...
Click to collapse
I knew as much, I work for a company that buys electronics in bulk from places such as amazon or asurion for this very reason, the people who owned the devices and returned/sold them to these companies had not removed their google account. My job is to remove the frp as well as refurbish these devices for resale and so far i've had great success doing this. However, I've got a few devices every so often that fail to bypass. Are you suggesting that I should use as low of a binary as possible when doing frp bypasses? I believe these devices had binary 7. Combination flashed fine, linked up to adb and removed the frp lock, then when i flashed the stock firmware it would just bootloop. My goal is to maximize the amount of devices we can sell overall so any bit of information helps. Thanks.
I should also mention that I was taking note of the csc code before starting this process.
So I sold my s8+ g955fd seexynos to this guy for a really good price.
My s8+ was rooted with magisk and bootloader was unlocked.
But this guys wants it unrooted and wants the bootloader to be locked so that he can have the ota updates working. And if I fail to do so (which I am at the moment), I would have to return the money (which I dont want to).
I tried flashing stock rom (latest from Sammobile) from the scratch with Odin but still when I check with Intercept X app, it says bootloader unlocked. and I checked in developer options too, the oem unlock is greyed out and set to off and says "bootloader is already unlocked".
Could someone please guide me with working steps please? I am good with flashing and stuff.
I tried searching the s8+ forum but couldn't find anything helpful.
Need urgent help. :foldedhands:
Edit 1: now the OEM unlock is gone from developers options after flashing magisk again :scared:
Edit 2: After uninstalling magisk from magisk manager app
, phone went to bootloop. So I flashed stock rom "bl,ap,cp,csc" with odin again and the greyed out oem unlock is back with status "bootloader is already unlocked"
Any hint guys?
Just a hint would be enough!
Its a one way process from what I understand.
Anybody will want it locked because without it locked you cant use Knox or any of the payment apps that depend on Knox.
I could be wrong but this is what I feel.
RonChinoy said:
Its a one way process from what I understand.
Anybody will want it locked because without it locked you cant use Knox or any of the payment apps that depend on Knox.
I could be wrong but this is what I feel.
Click to expand...
Click to collapse
Already figured it out. I am sure that guy doesn't care about knox, but does care about ota updates
I bought a second-hand galaxy S10e that was advertised as being stuck on a boot loop. I fixed the boot loop by flashing with a stock firmware, but was greeted with an frp lock that I triggered in the process. I contacted the seller about it, but he said he bought it second hand himself and has no way of contacting the original owner. I've tried a couple things and thought this through, and I decided to ask here whether I missed anything.
First, is it possible to read the google email associated with the frp lock from the device in order to contact the last logged in owner? that would make this a lot easier if I could ask them to unlock it for me.
I assume this isn't possible, since I couldn't find anything about it. what are my other options? while recovering from the boot loop, I flashed a very recent firmware, so all of the 'frp bypass' tricks I see advertised don't work. I also wasn't able to flash a combination file.
Does anyone have any experience with this, and any ideas I could still try? Bought the phone for my wife, and I'd hate to see her angry :|
Solved with the help of @hainguyenthao
thank you!
drafthorsey said:
Solved with the help of @hainguyenthao
thank you!
Click to expand...
Click to collapse
Can you elaborate on how you achieved this? So I and others can follow the procedure too?