Ok, since SirCmpwn cannot visit any TI site until Summer 2011, I am relaying his request for him:

He would like to ask if someone has a routine to lock/unlock flash memory? He also wants to know which pages would this affect?

This has been questioned and answered in some UTI topics. mapar007 should have one routine for that and calcmaniac84 probably will (for his TI-Boy SE).

I know he can not visit the TI forums but we can save the pages and send to him. Or see WikiTI ports documentation, I have saw there code to unlock flash.
And Brandon Wilson has the most up to date method to unlock flash (if there is some bcall we can use or details in the instructions to unlock flash) and even knows details in the emulated TI-84+ SE in a Nspire unlock flash.

OOOH RIGHT! The last part is the one that can be the most dangerous. I think this is what Brandon talked about. When unlocking flash, be VERY careful to not overwrite the certificate, otherwise, big "OOPS".

Thanks for the help, but I was hoping for the routine in hex.

Thanks for the help, but I was hoping for the routine in hex.

A SirCmpwn drew near? o.o

He is working on some project that isn't a game but I think it's secret so I can't tell much.

He just need to be VERY careful with that Flash unlocking routine. He should really test on a computer first if he can.

I would say why he might need that, but I don't know if I am allowed to do it. I would need his permission first.

I personally do not like when people say things like "why do you need that?" or "why do you want to do that?" when someone asks for a routine or programming help, because it sounds like it implies any use of it would be pointless or that his idea makes no sense or something, while in fact, the programmer may have something special in mind. Why prevent someone from doing something he wants? Plus he might want to keep his ideas secret until he's certain it will work out, anyway.

If everyone cancelled their help requests everytime they got told that in the past, half of the POTY poll choices on ticalc would never have happened. Illusiat 13 would have never been possible, same for Metroid II (the first person to ever want to write a XCOPY/Resource style routine and asked help for it was hit by that question in the past).

All he needs to make sure is to be careful to what he does with the help people provides him.

Let's not get into a "MaxCoderz 2003-04" mentality here

I can't think of any reason why you'd need to directly write to flash from a user program...
Only an OS should need to do that, in which case you don't need to bother with a hack, since it's your OS.
The only reason for which it could be needed is if you need to create an app directly on-calc. But to do that, you'd have to mess w/the certificate too, and that is just a very bad idea.
Anybody have a better guess?

Flash unlocking is unusual unless you are writing an OS or patching something.
But he might want only to experiment something, nothing more.

I personally do not like when people say things like "why do you need that?" or "why do you want to do that?" when someone asks for a routine or programming help, because it sounds like it implies any use of it would be pointless or that his idea makes no sense or something, while in fact, the programmer may have something special in mind. Why prevent someone from doing something he wants?

You are right. But sometimes asking why can help can be to give better help or support, not this case, though.
calcdude84se is intrigued and maybe curious. I am curious, too, but I will simply wait for SirCmpwn.

Regardless of what this will be used for, although I think I have an idea, I still say that this is very dangerous.  No one is being close minded here, the routine was already posted that he requested.  We are just discouraging it becasue no one wants to accidentally brick their calculator, you really really have to know what you're doing.  The fact that the routine was asked for in hex makes me think that this is not going to be written in pure assembly.  If that's the case, I would definitely stay away from the flash, there's a lot more to it than just unlocking it.  You still need to swap pages, read things into registers, swap them back into buffers, and other things that really have to be done in assembly.