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
XDA user since 2007.
These last months I used to have a custom rom on my encrypted note 5 with no issue.
Until last week.
The phone refused to start after a shutdown ("Custom Binary block by FRP lock" message)
Just a black screen with this red message, really so at first it was kind of a malware before I knew about this 5.1 android feature that lock the phone in case of being stolen or modified.
What is really interesting is that Google guys implemented this "feature" obviously without taking in account encrypted users. So the message asking for the google account never appeared.
Ok. I make backups, it is not a big deal and I will flash a new rom with ODIN.
But then I realize it is impossible. This feature is specially made for preventing fresh factory reset.
The new roms + kernels I tried to flash (from 5.1 to 6.0) always display this message :
( device does not have DRK (device root key ), contact to SW PL
please flash ENG binary then install DRK
So I am basically screwed, and my phone is absolutely useless like it was stolen. Expect I paid $700 for it.
Really pissed of against Google and Samsung !!
The option to avoid this mess was : OEM unlock, I strongly suggest you to activate it before trying custom roms.
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.
Hi everybody,
I just bought a S8+ with firmware G955FXXU5DSFB - Pie - pre-installed.
After a couple of days (and nights), the frustration piled up:
- barely managed to install TWRP
- RMM protection and "only official released binaries are allowed" messages that seem to come up again almost randomly
- still didn't manage to root
- what's worse - this bootloader downgrade issue (which I've just found out about) - the bootloader cannot be downgraded - is it for real ?
The final question - how can I install a custom Oreo/Nougat custom ROM if I have the BL v5 ?
I guess all the custom ROMS have lower bootloader versions. Does this mean I am stuck forever with stock Pie ? That would be a really bad.
Since when did Samsung turn so bad ? My previous phone was a Note 4 - I haven't been following the xda/Android news for the past 5 years.
Thanks a lot, and as always - xda-developers rule !
I managed to root the phone with Magisk.
I tried to flash Omega ROM, but the phone was stuck at boot screen.
Can someone pmease confirm that there's no way I can install cuatom ROM?
Thanks.
Unfortunately you are stuck to Pie forever, it's also the case for me, got my s8+ with Pie (BL5) and didn't even try to downgrade to Oreo, coz it's impossible
I'm using Alexis Rom with NX Kernel now, everything is perfect, smooth along with 6h30 screen on time
Hi, thanks for the reply. Isn't there any version of Oreo that has BL5 ?
Anyway, had I known this stuff beforehand, I would have never bought the phone. I am sorry that Samsung went so wrong, locking down their phones so brutally. I owned only Samsung smartphones, starting with SGS1; most likely this will be my last Samsung.
realn said:
Hi, thanks for the reply. Isn't there any version of Oreo that has BL5 ?
Anyway, had I known this stuff beforehand, I would have never bought the phone. I am sorry that Samsung went so wrong, locking down their phones so brutally. I owned only Samsung smartphones, starting with SGS1; most likely this will be my last Samsung.
Click to expand...
Click to collapse
No, no oreo firmware with BL5 :/
I got mine for free so I'm not that bothered Plus I'm still enjoying oreo on my s7 edge
It seems that, in fact, there is a way of downgrading: I have now Oreo running on the device with BL5.
Please see below post
https://forum.xda-developers.com/ga.../test-u1ara2-devbase-v5-0-encryption-t3752964
Hi a few months ago I switched from global to eu after some time I wanted to update miui to a newer version but an error appeared (check ss) I've already installed a few twrp, including the latest and several recovery versions available on the forum (orangefox)
Can somebody help me?
Did you format data before installing?
Yes i did it
Maybe you can try a fresh install with a miui 12 fastboot rom .
@alibei I will try and speak up
@csjneek @alibei
Hello, I found a solution to my problem, so if we have a screen lock (pattern / fingerprint), you should turn off the lock in time, it is a security that "prevents" deleting data from our phone. I personally do not believe that such a screen lock is able to prevent theft of the phone with an unlocked bootloader but somehow it works, also the update installed, you can close the topic
@csjneek @alibei
Hello, I found a solution to my problem, so if we have a screen lock (pattern / fingerprint), you should turn off the lock in time, it is a security that "prevents" deleting data from our phone. I personally do not believe that such a screen lock is able to prevent theft of the phone with an unlocked bootloader but somehow it works, also the update installed, you can close the topic