Database Users

Samsung Purposefully built in the download/recovery modes?

Did Samsung purposefully build in the recovery mode and download modes for us to be able to root and stuff?
Or were they for like Samsung's use only, and not all personal uses?

I don't know, but you have to appreciate the way Samsung doesn't lock their phones to the extent other manufacturers do.

ColorNapkin said:
I don't know, but you have to appreciate the way Samsung doesn't lock their phones to the extent other manufacturers do.
Click to expand...
Click to collapse
I mean they did start getting hardware locked vibrants out there later during the year and then on 2.2 they tried to make a barrier for us to not do the recovery reisntall packages because it checked the signature and other stuff... so.. they did TRY later on to stop us... but i'm asking if the modes were built for them to use, and if it was only for them, how can they be so stupid to make it so easy to get in because i'm sure some dev just looked at the system files and saw the download mode etc and adb'd it in there.

I'm sure it was initially meant for Samsung use only. If they didn't care about us rooting our phones it wouldn't void the warranty. At least they don't use encrypted boot loader's like Motorola has started to do. They make it pretty much impossible to flash a custom ROM.

xriderx66 said:
I mean they did start getting hardware locked vibrants out there later during the year and then on 2.2 they tried to make a barrier for us to not do the recovery reisntall packages because it checked the signature and other stuff... so.. they did TRY later on to stop us... but i'm asking if the modes were built for them to use, and if it was only for them, how can they be so stupid to make it so easy to get in because i'm sure some dev just looked at the system files and saw the download mode etc and adb'd it in there.
Click to expand...
Click to collapse
IIRC, in the case of the hardware locked vibrants, Samsung did admit that it was a manufacturer's fault there. All that got fixed by the JI6 update (if you didn't flash the fix beforehand).

Oniyuri said:
IIRC, in the case of the hardware locked vibrants, Samsung did admit that it was a manufacturer's fault there. All that got fixed by the JI6 update (if you didn't flash the fix beforehand).
Click to expand...
Click to collapse
Nope it wasn't fixed in ji6 not for me
And recovery comes in almost all phones.
Download mode was a bonus
Sent from my SGH-T959 using XDA Premium App

CrazyCharlie said:
I'm sure it was initially meant for Samsung use only. If they didn't care about us rooting our phones it wouldn't void the warranty. At least they don't use encrypted boot loader's like Motorola has started to do. They make it pretty much impossible to flash a custom ROM.
Click to expand...
Click to collapse
After I rooted and did an update a while back, I got some boot loops. Took it back to T-mobile and the rep asked me if I had rooted. He didn't mention anything about warranty and replaced it since I was under 30 days. Not sure if they don't care about root or if he was being nice.

muathib said:
After I rooted and did an update a while back, I got some boot loops. Took it back to T-mobile and the rep asked me if I had rooted. He didn't mention anything about warranty and replaced it since I was under 30 days. Not sure if they don't care about root or if he was being nice.
Click to expand...
Click to collapse
probably because you were on your 30 day thing, if you tell them you rooted, then their going to "black mark" you on your tmo acc so you don't get any more refurb. phones.

Now if they only release driver source..

Boot Loader Lock and alternate ROMs

Hello,
I am pondering the possibility to buy the Samsung Galaxy S II and have heard quite a few rumors that this phone will have a locked and encrypted boot loader making it impossible to use alternative ROMs.
I am sure hackers will take very little time in fixing this but am still wondering. Has anyone seen tangible claims of encrypted/lock boot compared to the I9000 (which I own atm).
Thanks!

Expansys has a 32 gb model listed as coming april 11th but pricing is not yet announced

galaxinho said:
Expansys has a 32 gb model listed as coming april 11th but pricing is not yet announced
Click to expand...
Click to collapse
Yes, no definite date. Doesn't answer my question though

FRLinux said:
Yes, no definite date. Doesn't answer my question though
Click to expand...
Click to collapse
Samsung's own website mentions encryption, but doesn't give enough detail for us to know if it'll be custom ROM friendly yet. I'm sure it'll take very little time once the phone is released to let you know, just hold tight until then!

Ayrlupine said:
Samsung's own website mentions encryption, but doesn't give enough detail for us to know if it'll be custom ROM friendly yet. I'm sure it'll take very little time once the phone is released to let you know, just hold tight until then!
Click to expand...
Click to collapse
Link please?
I suppose you are referring to the data encryption that Samsung mentioned in its splash page? I really doubt they would post information about a Locked Bootloader on their website as it really wouldn't do them any good publicity wise.

sarsh11 said:
Link please?
I suppose you are referring to the data encryption that Samsung mentioned in its splash page? I really doubt they would post information about a Locked Bootloader on their website as it really wouldn't do them any good publicity wise.
Click to expand...
Click to collapse
Yeah, I said encryption. Of course we have no idea about the bootloader until it's released or someone techy gets their hands on one! That's why I said we have to wait. Sorry if my post was ambiguous.

SamFirmware just tweeted, Samsung are using same ODIN for Galaxy S II, just with new .PIT file. So it will be flashable.

Broomfundel said:
SamFirmware just tweeted, Samsung are using same ODIN for Galaxy S II, just with new .PIT file. So it will be flashable.
Click to expand...
Click to collapse
Yes saw that but it doesn't mean it is flashable just like that until you see it working. Good start anyway.

FRLinux said:
Hello,
I am pondering the possibility to buy the Samsung Galaxy S II and have heard quite a few rumors that this phone will have a locked and encrypted boot loader making it impossible to use alternative ROMs.
I am sure hackers will take very little time in fixing this but am still wondering. Has anyone seen tangible claims of encrypted/lock boot compared to the I9000 (which I own atm).
Thanks!
Click to expand...
Click to collapse
There's already a running topic on this question found here.

Beards said:
There's already a running topic on this question found here.
Click to expand...
Click to collapse
Thanks spotted it afterwards.

FRLinux said:
Thanks spotted it afterwards.
Click to expand...
Click to collapse
No problem... Your not the only one who has started a topic and found later it's already running.
That link I passed you is actually a second topic on another which was started a day earlier here.
That means we now have three topics covering the same (although each will fragment as further posts are made).

Everyone has their needs/requirements for a phone but for me-personally to fulfill my individual desires and needs it would need to be unlocked 100%. Otherwise I will jsut have to keep my captivate
As I do not approve of manufacturers locking hardware that I paid for with my hard earned money and now own.

HappyBallz said:
Everyone has their needs/requirements for a phone but for me-personally to fulfill my individual desires and needs it would need to be unlocked 100%. Otherwise I will jsut have to keep my captivate
As I do not approve of manufacturers locking hardware that I paid for with my hard earned money and now own.
Click to expand...
Click to collapse
Seem the norm these days on android handsets but keep in mind that the mobile market has always liked a locked an tight device.
Sent from my GT-I9000 using Tapatalk

SE was from the very few to lock the bootloader with X10 and now they decided to unlock the simfree Arc, HTC locked their Incredible S in another hand
I don't think sammy will lock the bootloader,just a little security for the formalities that can be easily decoded by happy devs

vegetaleb said:
SE was from the very few to lock the bootloader with X10 and now they decided to unlock the simfree Arc, HTC locked their Incredible S in another hand
I don't think sammy will lock the bootloader,just a little security for the formalities that can be easily decoded by happy devs
Click to expand...
Click to collapse
Yes over time there is always a way. But that said, new devices tend to have better boot loader locking.

Has there been any update on whether the S2 have a locked bootloader?

monkley said:
Has there been any update on whether the S2 have a locked bootloader?
Click to expand...
Click to collapse
Search this very forum. Several threads opened about this but only speculations until someone has one and messes with it.

Locked bootloader...
So I see the chat regarding the locked bootloader on the sg2...I also see people on the forum actually have the device...could they some how check and see if it is locked?
I have been going round in circles looking for a new phone...finally decided on the sam sg2 to find out they are going down the same route as moto!
So, to all the happy owners of a shiney new sg2...whats the dealo!?!?!?

owners of the sgs2 in this forum? you must be mistaken lol...
sam locking the bootloader? who told you that nonsense?

they wouldnt dare to lock the bootloader. its 1 of many reason why sgs 1 succeeded as it did.
if they want sgs2 to be a successful device as well they wont lock the bootloader. it makes sense that the bootloader will be UNlocked.. but then again you can never tell... we might be like if we will find out its locked. followed by and then after we will unlock it. leading to

[N00B] I have an idea for downgrade

Ok, so I have an idea to like downgrade from mk2 or mf3... I am a noob to i337, so please explain to me WHY I can't do this before flaming :C
So we obv can't flash because of Samsung's locked bootloader and knox and stuff, but what if we were to completely wipe our phone. Not like a regular "I'ma factory reset my brick yo!" No no no, I mean completely getting rid of EVERYTHING. Modem, kernel, everything to make it as if you haven't gotten a single flash of ANYTHING on your phone, as if your phone is just getting it's software installed. THEN, we flash a MDL and everything for 4.1.2, or practically whatever came before mf3 (since my phone was shipped with that, I never really took the time to research what came before so I'm not sure what version is before). So, I'm thinking maybe someone has actually tried this, and thinking someone has not... Just want to find out if you can, and if you can't, why not.
Thanks
P.S: Wasn't sure whether to post in General or Q&A, so I posted it here

Because when your phone updated to mf3 or later it blows a q fuse that makes it impossible. It's beyond software. It's a hardware issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Ends said:
Because when your phone updated to mf3 or later it blows a q fuse that makes it impossible. It's beyond software. It's a hardware issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Oh ok, well in that case (sorry I'm a noob) whats a qfuse? I've searched it up and haven't really gotten anywhere with it

SkyAttacksX said:
Oh ok, well in that case (sorry I'm a noob) whats a qfuse? I've searched it up and haven't really gotten anywhere with it
Click to expand...
Click to collapse
From what I've read, it's a piece of hardware that only counts up. It is checked when attempting to flash old bootloaders.

DeadlySin9 said:
From what I've read, it's a piece of hardware that only counts up. It is checked when attempting to flash old bootloaders.
Click to expand...
Click to collapse
This seems like a good place to ask this question: does flashing 4.3 MK2 blow another qfuse? And if we're already on MF3, would you recommend waiting to update and not blowing that qfuse in case that might be the key to regaining access to custom recovery? Or are we doomed forever already and I should just go ahead and take the update?

karate104 said:
This seems like a good place to ask this question: does flashing 4.3 MK2 blow another qfuse? And if we're already on MF3, would you recommend waiting to update and not blowing that qfuse in case that might be the key to regaining access to custom recovery? Or are we doomed forever already and I should just go ahead and take the update?
Click to expand...
Click to collapse
MK2 does trip it, so no MF3 downgrade. Whether or not you upgrade is really up to you: progress is not coming too quickly and unless Samsung patched a security hole we haven't even found yet in the boot loader there's a chance any MF3 exploit may carry over. I would recommend MF3 personally since you can still use Safestrap for some freedom and it'll be less difficult since they won't have Knox to work around.

Hmmm... so it's a piece of hardware huh... would it be possible to remove this hardware? I took apart my S3 when the screen broke to see what was going on internally so if I'm correct, you can take apart the S4, right?
EDIT : Then again, that hardware could be pretty itty bitty...

SkyAttacksX said:
Hmmm... so it's a piece of hardware huh... would it be possible to remove this hardware? I took apart my S3 when the screen broke to see what was going on internally so if I'm correct, you can take apart the S4, right?
EDIT : Then again, that hardware could be pretty itty bitty...
Click to expand...
Click to collapse
I think it would be better for someone to hack the firmware and alter it to make it "think" it has checked this piece of hardware and return a favorable response.
However, i am no developer...

joeybear23 said:
I think it would be better for someone to hack the firmware and alter it to make it "think" it has checked this piece of hardware and return a favorable response.
However, i am no developer...
Click to expand...
Click to collapse
Hmmmm I've wanted to be a dev for quite some time and I am only 14... However I did do a little noob java scripting for irc chats back when I was like 10, so if you know anyone willing to teach me the basics and give me the structure to adb and coding for android and all that, that'd be great

SkyAttacksX said:
Hmmmm I've wanted to be a dev for quite some time and I am only 14... However I did do a little noob java scripting for irc chats back when I was like 10, so if you know anyone willing to teach me the basics and give me the structure to adb and coding for android and all that, that'd be great
Click to expand...
Click to collapse
This is a great community. PM some of the developers and they can probably point you in the right direction to get started.

LOL.. If it were that easy, it would have already been done.

joeybear23 said:
This is a great community. PM some of the developers and they can probably point you in the right direction to get started.
Click to expand...
Click to collapse
Alright, thanks a ton! +1

custommx3 said:
LOL.. If it were that easy, it would have already been done.
Click to expand...
Click to collapse
That doesn't help

I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.

TheAxman said:
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
Click to expand...
Click to collapse
CURRENTLY CHATTING WITH SAMSUNG (SORRY FOR CAPS JUST SO EXCITED ) This is what they said just now after I asked about an eFuse/qFuse. Tell me if this is invalid!!!
******: As of now, I would like to inform you that, eFuse is not available in S4 mobile.
This is what the rep has said so far for the i337, will be updating further soon
UPDATE BEFORE POST : I had to ask them this, as I am a newbie and I didn't want to put the burden on you guys.
Visitor: Thank you very much. If you don't mind, is there a difference between qFuse and eFuse?
******: You are welcome. I wish I could have helped you in this regard. However we in live chat have information regarding the US model devices trouble shooting only.
So I guess this could mean they aren't completely suited for these types of Q&A's? Either way, rumors did spread about eFuse stuff being involved but I was just told officially that this was incorrect. Please tell me if I am wrong? Or I might have to start a new thread on this, rather.

SkyAttacksX said:
CURRENTLY CHATTING WITH SAMSUNG (SORRY FOR CAPS JUST SO EXCITED ) This is what they said just now after I asked about an eFuse/qFuse. Tell me if this is invalid!!!
******: As of now, I would like to inform you that, eFuse is not available in S4 mobile.
This is what the rep has said so far for the i337, will be updating further soon
UPDATE BEFORE POST : I had to ask them this, as I am a newbie and I didn't want to put the burden on you guys.
Visitor: Thank you very much. If you don't mind, is there a difference between qFuse and eFuse?
******: You are welcome. I wish I could have helped you in this regard. However we in live chat have information regarding the US model devices trouble shooting only.
So I guess this could mean they aren't completely suited for these types of Q&A's? Either way, rumors did spread about eFuse stuff being involved but I was just told officially that this was incorrect. Please tell me if I am wrong? Or I might have to start a new thread on this, rather.
Click to expand...
Click to collapse
Samsung customer service reps have no clue about the device other than what's on their scripts. A noob on xda has 100 times the knowledge they do

jd1639 said:
Samsung customer service reps have no clue about the device other than what's on their scripts. A noob on xda has 100 times the knowledge they do
Click to expand...
Click to collapse
My hopes

TheAxman said:
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
Click to expand...
Click to collapse
Keep in mind the T-Mobile Note 3, N900T gets really bad LTE reception when using an AT&T sim. In places that had a -90dbm LTE signal on the S4 wouldn't even connect to LTE on the N900T for me. The device also got really warm when it was connected to LTE. I don't know if that's because the N900T isn't optimized for band 17, or just a way for them to discourage people from using AT&T.
Developers for the S4 have not called it quits. They are currently working on bringing safestrap to the latest MK2 update.

I'm really just wasting my time here because actually "searching" for any of the stuff in this thread would have provided answers, but I guess posting the information 1001 times is no different than the 1000 times it's already been posted.
A q-fuse involves hardware on some level, an e-fuse is software related. The AT&T S4 used q-fuses to increment firmware boot-loaders. It was incremented between MDL and MF3. It was incremented again between MF3 and MJ6. And it was increased again between MJ6 and MK2. When it is incremented, YOU CAN NOT GO BACK TO A PREVIOUS FIRMWARE...PERIOD! You can not simply change the information in aboot. Any changes invalidate Samsung's signature and without their encrypted key, a file CAN NOT be resigned.

scott14719 said:
I'm really just wasting my time here because actually "searching" for any of the stuff in this thread would have provided answers, but I guess posting the information 1001 times is no different than the 1000 times it's already been posted.
A q-fuse involves hardware on some level, an e-fuse is software related. The AT&T S4 used q-fuses to increment firmware boot-loaders. It was incremented between MDL and MF3. It was incremented again between MF3 and MJ6. And it was increased again between MJ6 and MK2. When it is incremented, YOU CAN NOT GO BACK TO A PREVIOUS FIRMWARE...PERIOD! You can not simply change the information in aboot. Any changes invalidate Samsung's signature and without their encrypted key, a file CAN NOT be resigned.
Click to expand...
Click to collapse
I'm very much sorry for that. However, do not misinterpret me when I say this but, your post was unnecessary as someone already said qFuse was on a hardware level. I dedicated a bunch of today to S4 and the I337 model specifically. Tomorrow or Wednesday is when I'll be sending some PMs to Devs
Basically, thread is over with. Thanks everyone

Root finally out? Nope nevermind.

http://forum.xda-developers.com/galaxy-s7/help/s7-s7-edge-root-t3321556/page16 Look there and you'll see it looks like root has finally been achieved. Sounds like they installed the newest TWRP and then using that flashed supersu. It does trip Knox though. I'm about to head off to work so I can't test this now but it looks promising.

Yeah source code is out for g930f & g935f but as that op says:
jcadduono said:
For those of you with G930FD, G930T, G930W8, G930P....be patient, I'm waiting for Samsung to release the kernel sources. The trees are already ready, just waiting on kernels...
Click to expand...
Click to collapse

Alarand said:
Yeah source code is out for g930f & g935f but as that op says:
Click to expand...
Click to collapse
Well, I guess I shouldn't have opened this thread then. That's what I get for trying to think that early in the morning.

sweet, i have my s7 on the charger waiting for the root so i can switch over from the s6

rmyc said:
sweet, i have my s7 on the charger waiting for the root so i can switch over from the s6
Click to expand...
Click to collapse
Looks like you may be charging that thing for a while, then. Seems that even the T-Mobile version is subject to the plague that is the locked bootloader for right now. Hopefully someone can figure something out or Samsung releases something along the lines of HTC's bootloader unlock for us. For once, the Snapdragon appears to be more crippled than the Exynos.

Yeah. I wouldn't count on anything any time soon. Not days, not weeks....
If you want a root able device. I would suggest taking the phone back.

Ummmmm, do you guys know what's going on with root on the US versions?
http://www.xda-developers.com/galaxy-s7-bootloader-lock-explained-you-might-not-get-aosp-after-all/

Yes that's old news.

Corwinder said:
Yes that's old news.
Click to expand...
Click to collapse
Then perhaps a change in thread title is worth considering until the situation changes :good:

start a facebook group to pressure samsung to release the lock,??

schreckles said:
Looks like you may be charging that thing for a while, then. Seems that even the T-Mobile version is subject to the plague that is the locked bootloader for right now. Hopefully someone can figure something out or Samsung releases something along the lines of HTC's bootloader unlock for us. For once, the Snapdragon appears to be more crippled than the Exynos.
Click to expand...
Click to collapse
What are you talking about? T-Mobile has an unlocked boot loader. It's been confirmed dozens of times. Where are you getting your information from?
Sent from my SM-G930T using Tapatalk

MacTheRipperr said:
What are you talking about? T-Mobile has an unlocked boot loader. It's been confirmed dozens of times. Where are you getting your information from?
Click to expand...
Click to collapse
Ummmmm, no.
Galaxy S7 Bootloader Lock Explained: You Might Not Get AOSP After All | XDA Developers
ROOT DISCUSSION - R.I.P. Sticky Root Guide - SM-G935T -> STATUS -> LOCKED BOOTLOADER
Unless John Legere at TMO can sway the powers-that-be at Samsung to unlock the bootloader for the G930T/G935T (and supposedly he's trying), nobody will be rooting any time soon.

MacTheRipperr said:
What are you talking about? T-Mobile has an unlocked boot loader. It's been confirmed dozens of times. Where are you getting your information from?
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
You must not get on here much. This is the biggest story lately and the reason why everyone is mad/frantic.

TMOBILE locked the bootloader John is playing us after 14 days when return period is up he will tell you guys Samsung said no its has nothing to do with Samsung it's the u.s carriers with the new leasing programs, warranty exchanges, and unauthorized tethering...They are losing money from phones which have been rooted
Sent from my SM-G935T using XDA Free mobile app

I understand everyone being upset about the latest development but some need to calm down a bit. Not saying it's anyone in this thread though some comments are a bit over the top. Maybe some people are new around here or others have the memory of a goldfish but this isn't' the first time this has happened to a device. There are a multitude of ways around this. Motorola who is known for locking bootloaders with almost a hatred for consumers, was defeated with the combined effort of many people on XDA. They managed to find the key to unlock the bootloader and it was smooth sailing from there.
Will we obtain the key? Quite possibly. we'll either do it the hard way and get lucky running a program on multiple computers and phones to decrypt it. The other option is that it'll be leaked by an internal source (probably the most likely). Samsung might even give us a dev program to unlock it similar to HTC. The fact is Samsung doesn't want a large customer base to be this unhappy. We are the most influential consumer base as well. Think of all the changes and additions to Android over the past few years. Changes that started here first and were adopted by manufacturers. They use us and in a way, need us to show them what people want. Let's not forget that XDA is the most influential Android site on the net. If Samsung gets snuffed here badly it'll spread very quickly.
TL;DR It'll happen one way or another guys. Chill out. May not be in the time frame we're use to these days (remember waiting weeks to months for root back in the day?) but it will happen. focus on pressuring those who can exact change into doing so. For the ones capable of it you should focus on ways around this.

I for one am not worried. I had a Motorola Defy that had a locked bootloader. By the time I had bought the phone though it had been out for a few months and people had found a way to put custom roms on it so I was happy.

At least I know I'll be able to keep my Samsung pay around for a bit ?

Shaffer678 said:
At least I know I'll be able to keep my Samsung pay around for a bit
Click to expand...
Click to collapse
lol I use my bank debit card and 2 credit cards. Not a one works with Samsung Pay. But all 3 work on Google Wallet.

Corwinder said:
lol I use my bank debit card and 2 credit cards. Not a one works with Samsung Pay. But all 3 work on Google Wallet.
Click to expand...
Click to collapse
How does Samsung pay or Google wallet work? How would I know which retailer supports it?
Sent from my SM-G930T using Tapatalk

This thread should be completely deleted.

Possible to unlock without account details?

Recently got this phone online from Ebay, did not realize that the phone was locked to sprint. Can it be unlocked without account details?

SuperTechno2004 said:
that the phone was locked to sprint
Click to expand...
Click to collapse
What do you mean under it? Is it locked to the carrier Sprint? (sorry, but I'm not familiar with the phone carriers outside my country)
Edit: if yes, then you may find this link useful
https://itoolab.com/unlock-sim/sim-unlock-software/#w2
It contains some info about softwares that can unlock the device. I haven't tested them yet, bc I didn't have any situations where I faced with an issue like this.
I hope this helps, if no, then we'll come up with other ideas.

gurtnyi said:
What do you mean under it? Is it locked to the carrier Sprint? (sorry, but I'm not familiar with the phone carriers outside my country)
Edit: if yes, then you may find this link useful
https://itoolab.com/unlock-sim/sim-unlock-software/#w2
It contains some info about softwares that can unlock the device. I haven't tested them yet, bc I didn't have any situations where I faced with an issue like this.
I hope this helps, if no, then we'll come up with other ideas.
Click to expand...
Click to collapse
Finished trying those, sadly, none of them work

I found this post on the forum, it's older, but may work.
https://forum.xda-developers.com/t/possible-to-unlock-without-account-details.4541665/post-88008885

Hi there,
Did it work?

gurtnyi said:
Hi there,
Did it work?
Click to expand...
Click to collapse
Unfortunately, no. I think you linked this post