Related
Hello everybody,
I usually find my answers in the specific phone related forums. But this time I'm stuck.
A friend of mine bought a Samsung Galaxy J7 (SM-J700F to be specific) in India. After using his phone there he came back home to Israel.
His phone didn't worked here for some reason and he went to a phone lab which flashed his ROM to stock Israel ROM.
They called him in the middle of the process and asked him what was his Google account thet he signed to while the first setup. Unfortunately, he cant remember his email address.
I took the phone to try bypassing the frp lock.
After a small search I realized I need an otg cable, which I bought.
I received the cable (1.5 mounths wait) and tried the otg cable method with no success.
After some experiments I successfully managed to open the settings menu. Pressed factory data reset and after a restart it stopped on recovery menu with the yellow message "dm-verity verification failed".
Well, this is annoying. I realized I need to flash the stock ROM again(Dated 01/16). So I did And the message dissapperd.
Back to the FRP lock issue. I did the process again and it didn't stopped in the recovery mode this time and I could see the Android logo with a little erasing.. Under it. Finally I thought.
I was wrong.
The FRP lock is still there! Dammit.
It is time to pull the big guns.
I thought I will flash the OLDER version of the stock ROM. Dated 09/2015 I Understand google updated the FRP lock protection on January 2016. Is the downgrade OK? I don't know if a downgrade is possible on Samsung phone.
And if you have an idea how to bypass this. Please share it.
Thank you so much!
Hello epopcop
I try so hard for three days like ure problem
The issue not from odin or pc
Th problem from samsung you cannot downgrade any update
So maybe u use software sysgem update and install it on ure device
So you cannot use any old firmware
(You shloud last updated firmware)
Link
Sorry just search in androidfilehost make a search for j700f and download the 2016 firmware
I cannot post links sorry
Use it and live ure life happy
Wishes
Long story short. I'm helping out my colleague who got her phone locked. We ended up factory resetting it, but she's not the most technical, so it seems that every time she's gotten a new phone over the years, she's just created a new gmail-account and forgotten about it.
Then FRP kicked in. Shouldn't be a problem if she just knew her account.. We've found out that she's got at least three accounts, but none of them works. I figure she's got another one, but not one that she could remember. So I have to bypass FRP somehow, otherwise this phone will be an expensive useless brick. :/
It seems it's on build MMB29K.G930FXXU1BPJE.
It's recently updated, so any bypass I've found seems to have been patched. It's usually a good thing, but in this case (she can blame herself, though..) it's a bit sad.
I've tried to downgrade using Odin, but for some reason it fails. I've haven't been able to enable OEM-unlock or enable Developer options.
Any help is appreciated!
She should have some record of which account she used, creating a Google account should ask for a backup email address for recovery, so one of her accounts should have the details of the one she's forgotten
Otherwise unfortunately this could just as easily be "I stole a phone and want to know how to bypass FRP"
Octoplus box and your problem is solved.
*Detection* said:
She should have some record of which account she used, creating a Google account should ask for a backup email address for recovery, so one of her accounts should have the details of the one she's forgotten
Otherwise unfortunately this could just as easily be "I stole a phone and want to know how to bypass FRP"
Click to expand...
Click to collapse
I know. At first she couldn't remember the gmail, and after we checked against her phone no. we found two accounts. Checking against her work e-mail, I found another. Unfortunately it was none of them.
vatvedt said:
I know. At first she couldn't remember the gmail, and after we checked against her phone no. we found two accounts. Checking against her work e-mail, I found another. Unfortunately it was none of them.
Click to expand...
Click to collapse
All I can suggest is look for tutorials on YT for bypassing FRP for whichever security update that phone was on / downgrade with ODIN to one that has a tutorial (Try leaving out the BL part of the flash if it's failing, and use CSC, not HOME_CSC)
You should definitely be able to downgrade a G930F, I just did with mine from 7.0 Nougat back to 6.0.1 using ODIN 3.12.3
You don't need OEM Unlock or Dev Options / USB debugging for flashing stock with ODIN
*Detection* said:
All I can suggest is look for tutorials on YT for bypassing FRP for whichever security update that phone was on / downgrade with ODIN to one that has a tutorial (Try leaving out the BL part of the flash if it's failing, and use CSC, not HOME_CSC)
You should definitely be able to downgrade a G930F, I just did with mine from 7.0 Nougat back to 6.0.1 using ODIN 3.12.3
You don't need OEM Unlock or Dev Options / USB debugging for flashing stock with ODIN
Click to expand...
Click to collapse
Thanks, I'll give it another try later tonight.
Following this video (https://www.youtube.com/watch?v=KRUp09bXnDA&feature=youtu.be) I didn't have to downgrade anything other than the account manager on 6.0.1 through an .apk. That way I could bypass FRP on the October security patch. She was so happy, and I told her to keep it to this one @gmail-account.
So, problem solved! Thanks for the replies!
Nice one :good:
Hi guys, I thought I just got a heck of a deal when I picked up a 64gb Note 5 for only $75 today off of the app LetGo (kinda like craigslist). The guy I bought it from was very nice and showed me that everything on the phone was in working order and let me use it myself to test it out. I gave him $75 and brought it home only to factory reset it and Google Account lock it in the process. I believe it is currently on 5.1.1, no idea what security update. I tried the FRP bypass that uses Realterm as well as the wifi disconnect method and neither worked. Realterm doesn't seem to be sending the commands to the device. It instead just displays the command I sent in green lettering and nothing else. I am really getting hopeless now. The guy I bought it from wont answer my texts or calls so i can't get his gmail account or anything. I doubt it is stolen or anything due to the fact he gave me the box with the charger, s pen tips, sim tool, and everything. And yes, I checked and the serial number on the box does match the one on the phone. I am about to attempt to use odin to update it to 6.0.1 and see if the Realterm method works then. Does anyone have any ideas? It is for Sprint if that matters. Is it possible to root or flash a custom rom or anything to get passed this? Any help will be so greatly appreciated. This day started out so exciting and now is truly disappointing.
Thanks guys.
Ok, I got it figured out! I had to use odin and downgrade to N920PVPU2AOI6. Then downgrade bootloader to SM-N920P_OK3_BOOTLOADER. Then was able to insert a flash drive with the Google Bypass USB OTG.apk app on it into my phone. It automatically opened My Files when inserted, then I installed to app and bypassed it. The only thing now is in Download mode it still says "FRP lock: On" Although it seems to be fully functional and currently has my google account on it.
mxkevin117 said:
Ok, I got it figured out! I had to use odin and downgrade to N920PVPU2AOI6. Then downgrade bootloader to SM-N920P_OK3_BOOTLOADER. Then was able to insert a flash drive with the Google Bypass USB OTG.apk app on it into my phone. It automatically opened My Files when inserted, then I installed to app and bypassed it. The only thing now is in Download mode it still says "FRP lock: On" Although it seems to be fully functional and currently has my google account on it.
Click to expand...
Click to collapse
Greetings and welcome to assist. Glad you got your phone working, there are several guides on bypassing FRP on xda that may remove this message if you want to try them
Regards
Sawdoctor
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.
Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.