What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

unlocking the bootloader?

He says that it determines which device it is. He also basically said it cant be done, but I just think that this route has to be possible. It is possible to flash a bootloader. Yes there was a bricked 3 but that was with unofficial firmware. This is technically official. I tried flashing it but the file knew that this wasnt a dev phone. So basically if we can find out where the status of dev vs consumer is and hack this we can flash it. I still cling to the notion that there is hope here. I feel this is closer than we have gotten, so its worth exploring further if only to just find out that this is just another way it wont happen u know? the question is how did the guy that bricked his 3 flash the mbmloader with a custom. The chip will fry if its unofficial firmware hence his.being fried but.the process must be similar for our phones and this is official firmware so if we cqn write it the.same way it should work.

Sent from my DROID BIONIC using DroidForums
 
What i am curious about is if we were to simply rename the hs and ns copy of the bootloaders what would happen?

Will the update see that it is a consumer phone and flash the hs bootloader that is now actually the ns loader... food for thought.
I have actually been working on this for a while as well as a few other things that i am making very little headway on.
 
I have been analyzing the two bootloaders and the differences are minimal. if we can get the right people working together this might be a really viable option.
 
Unfortunately we cannot modify the update packages in any way. If u do it messes with the signature verification of the stock recovery. Basically we either need to write it in the same way they tried on the 3 or somehow finding out where the value (motorola.omapdevtype()) is located and changing the value. Any thoughts on how to start.
Sent from my DROID BIONIC using DroidForums
 
Bump-Back for the "AMEN."

____________________
"King of the 'Self-Edit'"

"Patriotism is supporting your Country at all times. And your government only when it deserves it" --Mark Twain
 
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
 
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

has anyone tried changing permissions to the file? My PC is down currently but in three middle of a restore.I will try as soon as I can. God speed.

Sent from my DROID BIONIC using DroidForums
 
Last edited:
Yeah I set the permissions in root explorer. though it may be needed to be done from adb? Sorry not very Linux savvy this being majority of my experience. Chmod?

Sent from my DROID BIONIC using DroidForums
 
Back
Top