Database Develop

Simlock. you have tried 8 times , Please wait until timeout

I have a Treo 750, which has incorrect code entered 8 times. how long is the timeout wait ?.
any other methods of resetting the phone or unlocking it ?
( I have the correct code from Cingular. someone else entered the incorrect code )

sod that, use the unlocker...

DONT use unlocker...u will have hard time updating to wm6!!

chakli said:
DONT use unlocker...u will have hard time updating to wm6!!
Click to expand...
Click to collapse
shut up you ****ing idiot, are you some sort of self-professed ****ing expert now?

summiter even says you can't upgrade to WM6 the right way with using an HTC rasio in ur treo

how does one enter the code into the treo 750
tical said:
I have a Treo 750, which has incorrect code entered 8 times. how long is the timeout wait ?.
any other methods of resetting the phone or unlocking it ?
( I have the correct code from Cingular. someone else entered the incorrect code )
Click to expand...
Click to collapse

What are my options
I am still not clear what are my options.
How long do I have to wait for the timeout ?
what other methods are there ?

I think searching will be productive on this subject.
Mod Edited

god everything i read from this guy, your either his buddy or your waste of skin.. Always a lot of filth from this guy.. I wouldn't take any advice from someone calls one a retard because they have a question..lol

and this statement... i know you are the expert on your software but honestly are you anymore of an expert on the devices than anyone else.. The actual experts work at palm and have way better attitudes
Olipro said:
* * ** * **** MOD EDITED
Click to expand...
Click to collapse

He said whaaa? Huh?
I think what he said is that if you install the patched bootloader (using the unlocker) you will have the ability to flash a Hermes radio, and if you do so, you will be stuck with that radio for the time being. I'm pretty sure that's all he's said..I'll ask him. Yep, that's all he said. To elaborate on that, this wouldn't affect your ability to flash WM6 in any way except that your Hermes radio (should you decide to flash one) will stay put. Olipro warned folks of this fact early on. Most people will find no compelling reason to flash a Hermes radio to their Treo.
Summiter isn't the expert on the mysteries of bootloader assembly..that's Olipro's realm of dark wizardry. And he knows far more than any of the cubicle monkeys answering the support line at Cingular or Palm. He's also saved a lot of people many dollars/loonies/euros/pounds/pence/rupees by creating free unlockers for a multitude of HTC devices. So, uh, like, respect the man and stuff and whatnot. And so forth. And so on.
jhowle said:
summiter even says you can't upgrade to WM6 the right way with using an HTC rasio in ur treo
Click to expand...
Click to collapse

I have a suggestion for you. Click on Olipro's name, and then choose to search for his posts. Now read them. You will find that he knows these devices far more intimately than most folks at Palm or Cingular, and perhaps even a good portion of HTC. There's a total of perhaps 10 folks who frequent xda-dev who can skillfully dig into and modify the bootloaders and radios - and he's in the top 3. So yeah, he's much more of an expert. Now go read the forums I suggested to you in an earlier post for f*cks sake, or go away.
jhowle said:
and this statement... i know you are the expert on your software but honestly are you anymore of an expert on the devices than anyone else.. The actual experts work at palm and have way better attitudes
Click to expand...
Click to collapse

i have no desire to learn about the dude since he a very fluent user of cuss words in poor taste... im not doughting his skill,, justnot the most people friendly person i have came across. Doesn't compell me to want to see what he is about.

Olipro said:
I think searching will be productive on this subject.
Mod Edited
Click to expand...
Click to collapse
Hello Olipro,
I think you can help me on my problem, you are the boss for HTC,
I have same problem with the above topics, same with my HERME200 X01HT, I already have network unlocking code, but I can not enter the code, because it says.
"You have tried 35 times, please wait until time out" however, I've been waiting for 6days ago but still can not comes out. I still can not enter the code.
What would be the solution for this????
thanks for your sharings
Jhemzz

Is there no solution for this?
Same thing but 13 times been waiting over a week on an Elf HTC to enter sim lock code?

I'm getting this same error- sorry to bump a dead thread.
Using the Magic_Unlocker and Olipro's HardSPL/Unlocker doesn't work, and my phone is telling me that I've tried 100 times, please wait until timeout.
Is there any way to edit the rate it times out in so that I can enter the code?

Same problem, Treo 750V, tried 67 times, please wait until timeout...
Guys, how did you solved your own?
How much do I have to wait, or what can I do to speed things up?
I have the code now, official one, just can't enter it...

HTCDEV tell us what you want LINK

There is a small link at the HTCDEV site on the Lower right corner that reads:
Tell us what you want.
Lets go Guys all you have to put there is : unlock the AT&T HTC Vivid !!!!!
Just everytime you remember. go and write that in there and hit send. maybe they will get tired of hearing this and unlock it.
You can throw in a little " You Liars!!!!" in there if you like.

carlosjcar said:
There is a small link at the HTCDEV site on the Lower right corner that reads:
Tell us what you want.
Lets go Guys all you have to put there is : unlock the AT&T HTC Vivid !!!!!
Just everytime you remember. go and write that in there and hit send. maybe they will get tired of hearing this and unlock it.
You can throw in a little " You Liars!!!!" in there if you like.
Click to expand...
Click to collapse
I'm convinced AT&T will not let them unlock it no matter what. Some think it has to do with tethering. No root = no tethering = better for AT&T.

According to my contact at HTC, the whole issue is that HTCDEV.com is a 'sign up for' deal. Basically AT&T hasnt been specifically lying when they say ' we didnt ask them to lock it ', its more, 'we didnt say OK to them unlocking it'....
We need to beat up the bastards at AT&T. I want a copy of that damn agreement they have, since it would show that AT&T has been specifically manipulating the public with fake statements.

http://htcdev.com/contact

gtkansan said:
According to my contact at HTC, the whole issue is that HTCDEV.com is a 'sign up for' deal. Basically AT&T hasnt been specifically lying when they say ' we didnt ask them to lock it ', its more, 'we didnt say OK to them unlocking it'....
We need to beat up the bastards at AT&T. I want a copy of that damn agreement they have, since it would show that AT&T has been specifically manipulating the public with fake statements.
Click to expand...
Click to collapse
I want it too.
Also, I heard that when you use HTCDev, if it works or not, they void your warranty. Is this true? I honestly doubt it's LEGAL to void your warranty if your bootloader is locked.. if this is true, **** HTC forever, and hi Samsung.

I went to it and summited it and then hit the back button summited it again like 100 times already lol I will keep on too don't know if it does anything but if it does all they will see for hundreds of comments is
Vivid unlock boot loader thank you
Vivid unlock boot loader thank you ......

Still posting lol

You bet every day and will till they do something

I'm adding my posts.

Keep bothering the HTC people someone will eventually listen and at the very least lie again to us like Peter did when enough people protested.
Sent from my HTC PH39100 using Tapatalk

Well they didn't listen to this:
http://www.facebook.com/HTC/posts/10150571266758084
or this:
http://www.groubal.com/htc-vivid-ha...rary-to-statements-by-the-company/#signatures
I think they have more on their mind like why they lost 30% market value last quarter.
I say like the phone for what it is, go figure out how to root it yourself, or just buy a samsung.

This is it vivid is gone! !!
Sent from my new skyroket with root and loving it using xda premium

I must say, the longer I have this phone the more I like it, much more than the samsung, this is a nice piece of hardware

slapshot30 said:
I'm convinced AT&T will not let them unlock it no matter what. Some think it has to do with tethering. No root = no tethering = better for AT&T.
Click to expand...
Click to collapse
......What? I downloaded PDANet right from the android market on my unrooted Vivid and used it to tether... So I'm gonna say that's not it

i'm new to htcdev and this is probably a stupid question but they have instructions for unlocking the boot loader on phones, does it just not work on the Vivid?

No... when you try to go through the unlock process at the very end you receive the following message: error 170: CID is not allowed

[TOOL][CyboLabs] Open Bump! Sign your boot images by yourself!

CyboLabs is Proud to present
Open Bump!​
What is Open Bump?
Open Bump is a recreation of the closed source Bump project run by Codefire.
It will allow you to "sign" your boot images in the same way that Codefire does it, only you don't need an internet connection.
Click to expand...
Click to collapse
What Open Bump is NOT
lets get the obvious out the way. It won't axe murder you.
It is not a direct reverse engineer of Codefire's implementation. I found the key and iv on my own
The magic bytes were taken from Codefire's method however. If anyone has insight has to how they were found, please shout up.
It does NOT take your private data so you can use it. Tin hatters feel free to double check
Click to expand...
Click to collapse
How did I find this out
I had a general idea of what to look for, having heard that the exploit is related uicc, and is signed with a cipher.
Dropping the aboot image in to Ghex led me to finding a reference to "uiccsecurity". Using the bytes around this, I found a repeat of 32 bytes, which was followed by 16 bytes which formed something that resembled "SecureWallpaper".
As you can probably guess, this was mainly trail and error backed by common sense and logical thinking.
you can programmatically find these values with the python script:
Python:
aboot_name = './aboot.img'
aboot = open(aboot_name, 'rb').read()
key_end = aboot.index('uicc')
key_start = key_end - 32
key = aboot[key_start:key_end]
sec_key_start = aboot.index(key, key_end)
iv_start = sec_key_start + 32
iv_end = iv_start + 16
iv = aboot[iv_start:iv_end]
deciphering some already generated "signatures" proved that these were the key and iv used for "signing" the images.
Click to expand...
Click to collapse
What is coming next?
Inspecting the signatures that were originally uploaded and the ones that people can generate now, I found only one pattern.
The only similarities were the first 16 bytes of each "signature". I believe that only the magic number is needed, and none of the garbage that follows. This has been confirmed by the LG G3 dev from CyanogenMod, Invisiblek Done
Click to expand...
Click to collapse
How to use it?
I don't know how well this will run on anything other than linux, so for now.. I won't talk about it.
First, ensure you are using python2
then run the script
Code:
python2 open_bump.py "/path/to/boot.img"
flash the output, and enjoy
Click to expand...
Click to collapse
Thanks to:
Obviously, this wouldn't have been possible without Codefire since I wouldn't have known where to look, or that it was exploitable. And it was them that found the magic key.
Big thank you to @pulser_g2, who offered invaluable input on cryptography
Big thank you to @invisiblek, who I mercilessly kanged the main part of the image padding script from
note:
The original part of finding this information out was done on my own with guidance from pulser. The final results of this are posted above.
XDA:DevDB Information
Open_Bump, Tool/Utility for the LG G2
Contributors
cybojenix
Source Code: https://github.com/CyboLabs/Open_Bump
Version Information
Status: Beta
Created 2014-11-23
Last Updated 2014-11-23

Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.

g4rb4g3 said:
Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.
Click to expand...
Click to collapse
simple answer, this can be added to the build step really easily. See this commit
edit:
of course it may be useful to make a c program to do this.... I shall think on it.

Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!

After getting the bootloader may be open G3؟؟

Why not use the original Bump?
Quote:
Codefire has been extremely vague about their method, obviously to prevent someone else replicating their results.
They are also storing people's data unnecessarily, and even adding some information relating to the user in to the "signature", possibly for tracking purposes.
As a result of it being an external service, many reputable teams (which won't be named unless they want to be) have said they will not use it, and would rather wait till LG releases the official unlock method.
Finally, Codefire have said the sha1sum of the boot image is required. Whether they knew or not, it is NOT required, and I will be changing this tool to compensate for that.
Click to expand...
Click to collapse
Happy you found a new exploit for us builders and devs, just feel like you kinda disrespected codefire team by accusing them of things before actually talking to them, seems a bit counter productive, this may piss them off and next device you can kiss new exploits by them good-bye,
just my 2 cents on the matter,
i'd remove the line...
in any case thank you very much, i will add it to my build script
---------- Post added at 08:34 PM ---------- Previous post was at 08:29 PM ----------
nikosblade said:
Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!
Click to expand...
Click to collapse
"Bump stuff" has nothing to do with users, the devs and builders do the "bumping", and development of the G series has nothing to do with bumping, it just takes time to bring everything up

Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.

thecubed said:
Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.
Click to expand...
Click to collapse
First off, I didn't black mail. I gave your team notice about open sourcing it after reverse engineering the LG bootloader, not your "signatures".
It's your choice if you want to leave Android. Pinning the blame on me is somewhat childish though.
LG not patching Bump? That's a ludicrous statement, and even if it's true, it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
The hardest part of your teams work was getting the keys. If you know where to look, then it's easy enough to get engineering builds which I suspect contain the master magic bytes which you released.
I'm honestly shocked at your reaction though. I gave your team all the credit and stated which parts I did myself. The part about the service, and the deception was justified.
You tried to obscure something which by logic can't be obscured. That's how so many people realised they can just append the bytes to the image.
So which one would you rather have, LG not patching the exploit (as you so claim), and having an unknown number of people in china running around flashing custom boot images, or have everyone know how to do it to force LG to recheck their security measures.
What I did may not have been fantastic for the community, but what you did was insanely dangerous for the 90% of LG users.

All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.

cybojenix said:
it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
Click to expand...
Click to collapse
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.

savoca said:
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.
Click to expand...
Click to collapse
Yes, because I've been such a massive supporter of cm. (sarcasm in case you didn't realise).
I started reverse engineering the bootloader for research purposes. If it was more complex than what I have said above, then I probably wouldn't have done this thread.
If it weren't for the fact that the magic stays the same across all signatures, then I also wouldn't have done this thread.
The response I got from them when I contacted them before releasing this was pretty much one of lack of care. So I went ahead and posted it.
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
And once again, I refuse to take the blame for their team leaving Android.

whoppe862005 said:
All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.
Click to expand...
Click to collapse
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong

cybojenix said:
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
Click to expand...
Click to collapse
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo

savoca said:
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo
Click to expand...
Click to collapse
Tbh I thought it would have been clear by now what I care about. Then again I may have been wrong about considering you one of the smart android people.
I care about learning and sharing knowledge. Which is precisely what this thread did.

cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect

sooti said:
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect
Click to expand...
Click to collapse
Wrong, I stated that I was going to open source it, meaning the work of put in to getting the key and how it's used to get the original magic.
It was after that that I realised the final magic is the only thing needed. I actually worked out how to get the magic key a few hours ago, but since I don't have the right images, it won't be globally usable.
Fair enough, I apologise for pointing out the flaws in codefires service, and that they took it badly.

cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.

I don't know who Enderblue is, and I'm not affiliated with him..
whoppe862005 said:
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.
Click to expand...
Click to collapse

cybojenix said:
I don't know who Enderblue is, and I'm not affiliated with him..
Click to expand...
Click to collapse
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.

whoppe862005 said:
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.
Click to expand...
Click to collapse
but the chat wasn't with me, so your point is null
autoprime had ample opportunity to say "don't do it yet", or "go talk to IO". but no, no objections were made.
Codefire treated the service like any other company would treat their unlocking service, so I treated them like a company and showed how it was done.

Are you willing to pay for OEM unlock option to be available? I am

Hello,
I have paid nearly a thousand dollars for the note 8. I have also bought 4 cases with two screen protectors. The total reaches up to 1100$. Despite paying all this money for a phone, I cant do whatever I want to with it because I don’t have the OEM unlock option. I have nearly read all of the 225 page about OEM unlock for Exynos through this month. I have already signed with google, Samsung. I already waited more than 9 days with no boots but with no luck.
My suggestion to solve the OEM unlock option :
Donating money for any developer who is willing to try solving this mystery. I already paid about 1100$ for this phone and I am willing to pay a little extra to root it and to install custom roms whenever I want.
I am starting with myself. I am donating a 25$ as a start for anyone who is willing to take the challenge. What do you guys think? Are you willing to donate for anyone who are willing to try to solve the issue?
To keep things clear, I suggest that a moderator to open a thread for this subject where anyone willing to donate sees his name and the amount of his donation, so that we can know the approximate amount of donation money or a moderator can do whatever he wants as long as everything clear to us.
This thread is intended to check if people may want to donate money for anyone who may want to solve the issue of OEM, so If you got lucky with the OEM unlock option, please do NOT post your experience here, post it in this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
Thanks

This is a good idea, i'm willing to donate 30 EURO.

I don't know what to say. I paid just as much for this phone knowing full well that root or an unlocked bootloader might not ever happen. I made that choice knowing that there are or would be phones nearly as capable as the Note 8 that would have root or an unlocked bootloader.

anameeeen said:
Hello,
I have paid nearly a thousand dollars for the note 8. I have also bought 4 cases with two screen protectors. The total reaches up to 1100$. Despite paying all this money for a phone, I cant do whatever I want to with it because I don’t have the OEM unlock option. I have nearly read all of the 225 page about OEM unlock for Exynos through this month. I have already signed with google, Samsung. I already waited more than 9 days with no boots but with no luck.
My suggestion to solve the OEM unlock option :
Donating money for any developer who is willing to try solving this mystery. I already paid about 1100$ for this phone and I am willing to pay a little extra to root it and to install custom roms whenever I want.
I am starting with myself. I am donating a 25$ as a start for anyone who is willing to take the challenge. What do you guys think? Are you willing to donate for anyone who are willing to try to solve the issue?
To keep things clear, I suggest that a moderator to open a thread for this subject where anyone willing to donate sees his name and the amount of his donation, so that we can know the approximate amount of donation money or a moderator can do whatever he wants as long as everything clear to us.
This thread is intended to check if people may want to donate money for anyone who may want to solve the issue of OEM, so If you got lucky with the OEM unlock option, please do NOT post your experience here, post it in this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
Thanks
Click to expand...
Click to collapse
I'm in. Too bad chainfire retired, maybe this bounty will entice him. If it's possible to get SU first then disable knox. Then get to system and find what's causing this ghost toggle by expert means. Unlock it and then Odin twrp . But this is just my novice idea.

douger1957 said:
I don't know what to say. I paid just as much for this phone knowing full well that root or an unlocked bootloader might not ever happen. I made that choice knowing that there are or would be phones nearly as capable as the Note 8 that would have root or an unlocked bootloader.
Click to expand...
Click to collapse
me too, but I want the note 8.
kilayo said:
I'm in. Too bad chainfire retired, maybe this bounty will entice him. If it's possible to get SU first then disable knox. Then get to system and find what's causing this ghost toggle by expert means. Unlock it and then Odin twrp . But this is just my novice idea.
Click to expand...
Click to collapse
Thanks for the reply. To be honest, I don't know how the developers will do that. As long as they can do it whether with your way or their way, that would be great.

I am ready to pay.

I am willing to pay up to $50 or even more if that would solve our issue

solve what issue?
OEM unlock wont give you root or anything else..

Can you complete it? Is it Exynos or Snapdragon? Imo all Exynos chips have OEM unlock but we have the " 7 days " jail time. And we also have those impatient fooks who keeps on flashing sht on their phones then complain " Its been 500 years, I still dont the have OEM toggle "
I myself waited for 7 full days. 1st flash of TWRP was unsuccessful because of the " only official binaries are allowed " thing. So I went back to sleep and updated my phone ( samsung released a security update ). Woke up and decided to try it again ( The FRP and OEM were off even tho the OEM toggle in dev option is gone ) then BOOM!! I didnt expect it to succeed, my phone restarted and Odin indicated that the flash was successful so I immediately pressed buttons for TWRP and everything went good after that. Now I have TWRP+Renovate Ice+Magisk+Xposed.
I think the update from sasmung fixed the " Official binaries " thing

wase4711 said:
solve what issue?
OEM unlock wont give you root or anything else..
Click to expand...
Click to collapse
Solve the issue of it not appearing (or dissappearing). It's needed to install a rom, etc. (At least on Exynos...Snapdragon has that locked bootloader of course)

mehrec said:
I am ready to pay.
Click to expand...
Click to collapse
that is good. Thanks for passing by.
Sultan1234 said:
I am willing to pay up to $50 or even more if that would solve our issue
Click to expand...
Click to collapse
We are not sure if that would solve the issue, but at least let us try. If everybody contributes a little for a developer, that developer may have the time to solve the issue for us.
wase4711 said:
solve what issue?
OEM unlock wont give you root or anything else..
Click to expand...
Click to collapse
The issue that there is a topic now with more than 230 pages of members' observations about OEM unlock, and still we don't have an answer. if you have OEM unlock option appearing for you, that is good for you. here is the topic we are talking about :
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
xDreDz said:
Can you complete it? Is it Exynos or Snapdragon? Imo all Exynos chips have OEM unlock but we have the " 7 days " jail time. And we also have those impatient fooks who keeps on flashing sht on their phones then complain " Its been 500 years, I still dont the have OEM toggle "
I myself waited for 7 full days. 1st flash of TWRP was unsuccessful because of the " only official binaries are allowed " thing. So I went back to sleep and updated my phone ( samsung released a security update ). Woke up and decided to try it again ( The FRP and OEM were off even tho the OEM toggle in dev option is gone ) then BOOM!! I didnt expect it to succeed, my phone restarted and Odin indicated that the flash was successful so I immediately pressed buttons for TWRP and everything went good after that. Now I have TWRP+Renovate Ice+Magisk+Xposed.
I think the update from sasmung fixed the " Official binaries " thing
Click to expand...
Click to collapse
I am talking about Exynos. Members have different experiences here. No one have the absolute answer for this mystery, otherwise ; that topic won't reach 230 pages if replies, and I wouldn't open this thread.

This is just me but if my OEM unlock was refusing to show up after one week I would get a thread going and compare notes with affected devices alone There are one or more things you are all doing, software you are running, somthing, which is affecting your ability to get OEM unlock. Figure that out and you're home free.

anameeeen said:
that is good. Thanks for passing by.
We are not sure if that would solve the issue, but at least let us try. If everybody contributes a little for a developer, that developer may have the time to solve the issue for us.
The issue that there is a topic now with more than 230 pages of members' observations about OEM unlock, and still we don't have an answer. if you have OEM unlock option appearing for you, that is good for you. here is the topic we are talking about :
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
I am talking about Exynos. Members have different experiences here. No one have the absolute answer for this mystery, otherwise ; that topic won't reach 230 pages if replies, and I wouldn't open this thread.
Click to expand...
Click to collapse
Imho it got to 230 pages because most people complain first before they read and or have flashed something before even waiting for 7 full days. And mostly of the first pages is the discovery of the 7 days jail time. It would have been lesser that 230 if they have read first and have been patient
Have you fully updated your phone btw?
Use only 1 sim?
Got the phone from another country?
Never flashed anything on it?
Im currently using SM-N950F/DS btw

xDreDz said:
Imho it got to 230 pages because most people complain first before they read and or have flashed something before even waiting for 7 full days. And mostly of the first pages is the discovery of the 7 days jail time. It would have been lesser that 230 if they have read first and have been patient
Have you fully updated your phone btw?
Use only 1 sim?
Got the phone from another country?
Never flashed anything on it?
Im currently using SM-N950F/DS btw
Click to expand...
Click to collapse
- The phone was fully updated.
- I used two sims the first 10 days, then when OEM didn't appear, I removed one.
- I got it from the same country.
- During the first 10 days, I did nothing except for showing developers option. I waited 10 days but OEM didn't appear. After this, I flashed different stock rom, and now I am waiting. My up time is 66 hours now and I am using one sim. If no solution was descoverd, I can report at 168 hours (7 days).
By the way, I nearly read all the 235 pages. I have a friend who has his OEM appeared out of the box, he bought his phone from another country.

how is the petition going? Can we nudge chainfire for this bounty? I bet he can crack it

kilayo said:
how is the petition going? Can we nudge chainfire for this bounty? I bet he can crack it
Click to expand...
Click to collapse
it seems that people don't want to spend money for it. we have 15 voters : 8 with paying money, and 7 with not paying money. if there are more people, we can try to nudge him to take a look.

I´ll pay US$50, for an OEM unlock option to be avaiable upon flashing any ROM so that we don´t have to wait for the 7 day period to everytime we want to root or wipe or flash CSC.

radi8 said:
I´ll pay US$50, for an OEM unlock option to be avaiable upon flashing any ROM so that we don´t have to wait for the 7 day period to everytime we want to root or wipe or flash CSC.
Click to expand...
Click to collapse
Yes US $50 is about right to avoid this oem switch. The fact that we our boot loader is not completely locked..

i am willing to add $50 to get out this NO-OEM jail on N950FD.... i can't believe i got tricked into this samcircus .... i am debating myself if i have to sell this device & get s8 duos instead..

I made an account just now for the sole purpose of replying to this thread;
I will donate money towards this, probably the same as others ($50) I didn't buy my Note 8 to be restricted

Sad news for Galaxy s9 G960U users wanting root.

I have looked around the internet and finally found over on a sprint forum some sad news about rooting. So in the case most of you are unaware, the US models for the Galaxy s9 have had their OEM Unlock(Bootloader unlock) option disabled. I finally found the reason why on an old post back from the Galaxy s8. Please don't harp on me that its a different phone because its the concept discussed that actually gives the real reason why vendors like sprint have disabled the option!
"Link to below quote: community.sprint.com/t5/Samsung-Board/OEM-Unlock-option-is-gone/td-p/965240"]https://community.sprint.com/t5/Samsung-Board/OEM-Unlock-option-is-gone/td-p/965240:
"Quoted from Community manager, seawolf's post!"
Re: OEM Unlock option is gone
First of all, wow @zahale! its my job to be somewhat aware of our current population and to keep an eye out for knowledgeable posters (we like to try to make those people Advocates, like @DJ_Damjano and @Fireguy_6364). I have run across several of your comments in this space lately and you're definitely above the curve when it comes to technical device knowledge and experience. I'm kind of following you around now just to learn Smiley Wink
I was pretty sure I knew why Sprint locks down developer options but I put the question to some of my device folks in conversation yesterday. The explanation probably won't be something you like, but hopefully, it'll be something you can understand. Unfortunately, as with many things, knowing why also won't change anything but you asked a fair question and I wanted to try to give you a fair answer.
Sprint locks things like boot loaders down to control the average customer experience and to prevent a novice user from accidentally damaging the device or negatively affecting performance. While technically such a change isn't Sprint's fault, I can tell you from experience from when I was in customer service that most customers think it is and correcting the problem, if its possible, can be a challenge at best.
Unfortunately, this is an all or nothing kind of situation. We either leave it open for everyone or we lock it down for everyone. Since we can't customize the experience based on user knowledge, we try to optimize it for the novice, which means some of the more advanced setting areas on the phone are locked down.
This is clearly important to you and I can understand why. With this particular phone there isn't anything we can do on our end to unlock the developer options for one individual. When you are ready to upgrade again, you might want to look for factory unlocked versions of the phones you like or OEMs that leave theirs unlocked (although that's harder to verify). In this case, the developer options are not locked down in the factory unlocked versions of the S8 and S8+.
SeaWolf
Sprint Community Manager & Customer Advocate
Captain of the Vicious Cream-puff
I encourage you to post your questions on the community, give Kudos when earned and always mark the correct answer as "Accepted Solution".
Like SeaWolf states, it is just easier after your contract is done to just buy a OEM unlockable version. They do this for customer based reasons to make a novice experience for all users so that new users can't brick their phone on accident messing with settings. Sorry all but OEM unlocking will never be an option for g960U users.

All US (snapdragon) model S9s have a locked bootloader, it has been the case for a long time since at least the S7....

*Detection* said:
All US (snapdragon) model S9s have a locked bootloader, it has been the case for a long time since at least the S7....
Click to expand...
Click to collapse
Yes we already know this, but this post is an update on the reason why its that way. I have looked everywhere and even asked around but no one gave me a reason why they made it this way. I finally found this post and was just sharing it for news so that people can finally understand and get an update.

WatchersGrim said:
Yes we already know this, but this post is an update on the reason why its that way. I have looked everywhere and even asked around but no one gave me a reason why they made it this way. I finally found this post and was just sharing it for news so that people can finally understand and get an update.
Click to expand...
Click to collapse
but the info is nothing new plus its just a thread of people living in the stone age mixing up sim unlock with oem unlock and then complaining about it.
US snapdagon device's bootlaoder arent unlockable its a very very well know fact. any other device destined NOT for American soil can have its BL unlocked and probably be rooted.( so thats any device made for the rest of the world). surely this info has been plastered all over xda...

https://forum.xda-developers.com/ga...s-recoveries--other-development/root-t4041815
root is out

I have been rooting and modding various and sundry devices since 2011. I find, for my purposes, the s9 doesn't need it. Of course YMMV