unlocking the bootloader?

[dags5000]

All im saying is that this is not something that one will just "figure out" by looking at code or taking shot in the dark guesses. Take p3droids advice that it simply is not gonna happen unless the keys are leaked or some unlocked version is leaked or moto provides a way

Sent from my DROID BIONIC using DroidForums

 

[sjflowerhorn]

Since we cant change /proc/dev-type Beings that the bootloaders files are the same size(42kb i believe) inside of the updates would crossing the names of the two files just be a retarded waste of time? Or a brick in the making.

Dont anyone go trying this

Sent from my DROID BIONIC using DroidForums

 

[denpth]

i actually already tried this. I got a backup phone if worse comes to worse, obviously would rather not have a brick. It checks for the md5 of the files as well. so it knows the names are switched. But you have given me an IDEA maybe we change the md5 checksum verification file too.......... major shot in the dark there tho. guess back to source.


edit: no

 

[sjflowerhorn]

I figured with dile size the same md5 might be tricked but guess not.

Sent from my DROID BIONIC using DroidForums

 

[dstreng]

Overclocking can be now done on the Bionic, it just wont survive a reboot. Its time to put the focus back on the bootloader. Especially with updates coming soon and the need to return to stock kernels.

 

[firefighterguy]

We need a spy- an inside man at Motorola!

Sent from my DROID BIONIC using DroidForums

Or if one of us knows someone who was a code breaker in the Military. Or if one of aaUs was.... That would be gravy.

 

[sjflowerhorn]

Overclocking can be now done on the Bionic, it just wont survive a reboot. Its time to put the focus back on the bootloader. Especially with updates coming soon and the need to return to stock kernels.

Never lost the thought. . . Not for one second. Lol

Sent from my DROID BIONIC using DroidForums

 

[prime]

Ok so I found in /proc/ a file called omap_dev_type with the HS value in it but whenever I go to edit it to NS the changes dont keep meaning either I dont have the permissions for it or the OS is reverting it after saving it. I think its possible.if.we can change this value then update via normal update it might just do it. Thoughts?

Sent from my DROID BIONIC using DroidForums

If the update mechanism indeed uses the /proc/omap_dev_type to determine if the device is dev/non-development it may be possible to change the value in memory. Much like how the milestone overclock kernel module functions.

 

[denpth]

If the update mechanism indeed uses the /proc/omap_dev_type to determine if the device is dev/non-development it may be possible to change the value in memory. Much like how the milestone overclock kernel module functions.

That is actually the direction i am heading with it, however just like the overclock modules it will not survive a reboot. The trick is being able to run a module in stock recovery. But i am thinking once you get the NS bootloader installed I dont think we will have to do this again. PRIME if you wouldnt mind i can be a guinea pig and also i will give you as much insight as i have gathered. I think changing the value is not going to be the issue. The issue is changing the value while in stock recovery so one can run an update with the value changed. If you have any insight on how to do that last part it would be amazing. As i mentioned before there is HS which the bionic installs normally and NS (non secure) that is installed if omap_dev_type is set to NS. But if we are able to run cwm should we be able to run a modified stock recovery with this flag changed?

 

[prime]

I have my hands in twelve bowls of skittles right now so I may not be able to help. I am currently working with the bionic kernel source to enable loading outside modules into the running kernel, once I have this done I may be able to help.

Do you have a kallsyms in /proc? Does it contain the string omap_dev_type?

 

[denpth]

I have my hands in twelve bowls of skittles right now so I may not be able to help. I am currently working with the bionic kernel source to enable loading outside modules into the running kernel, once I have this done I may be able to help. Do you have a kallsyms in /proc? Does it contain the string omap_dev_type?

Yes it does infact. Now that i got my debian system up and running I can download the source and can also dump that variable and see what i can do with it. This is the area that i will have issues tho. I can understand the C from the source, but the assembly language? i understand how it works, but the syntax is hard to follow to me. I have got maybe 3 other times i have ever needed to look at it.

 

[prime]

You mean the 0x000a00 or push, eax..etc?

 

[denpth]

push, eax etc. I dont know what all of those mean.

 

[prime]

push, eax etc. I dont know what all of those mean.

I haven't directly dealt with assembly in over ten years so I don't much remember either.

Using memory registers or memory mapping has always been a pet peeve of mine anyway. I never understood why anyone would write in assembly unless absolutely necessary (in driver development it's a necessary evil).

 

[firefighterguy]

denpth and everyone else working on this, you guys rock! I have no friggin idea how to go about what you guys are doing.

I think I have seen more done here than enywhere else. There are threads all over the place that are for the most part dead. And those who are tight-lipped about it are greedy because they want the bootloader bounty all for themselves.

Well, they will be working on it a looooong time, because I like what is being done in this thread. A bunch of brains are getting together to pool what knowledge and theories they have for the better of the community here. And I believe you will have this cracked before any of the other tight-lipped people.

Keep up the good work on the quest to truly make our phones OURS!

____________________
"King of the 'Self-Edit'"

"Patriotism is supporting your Country at all times. And your government only when it deserves it" --Mark Twain