unlocking the bootloader?

[dstreng]

Didn't they try to do that with the D3 and it bricked?

Boot Manager

I think ur correct. The eFuse I believe is what bricked the D3. I may be wrong though

Sent from my DROID BIONIC using DroidForums

[denpth]

if what i read is correct efuse blows the device if its unapproved software, but what i am talking about is a motorola developed mbmloader thats in NS mode which then in turn unlocks the bootloader. (did a little more research, the mbmloader seems to be the "keys" persay that let the mbm know if its running in locked or unlocked mode.) so by us getting the mbmloader to go in NS mode (non secure) by loading in the mbmloader_ns.bin we should effectively unlock the phone and then from then on, the device will stay unlocked because the phone will report that is is a dev phone. So either we need to trick the update into thinking these are dev phones, or manually load them ourselves, which seems to be a kernel thing if i am reading correct. So that last option is out because we cannot load custom kernels. So basically we need to trick the update patch into thinking its a dev phone, or change the script to load the NS version instead of the HS version. Can CWM run this kind of code?

[dstreng]

Very unsure but this sounds promising

Sent from my DROID BIONIC using DroidForums

[denpth]

likewise now if we can just get a dev in on this. Because this is about as far as my skill takes me, i can understand but i cant do much more.

[1KDS]

Does p3 have anything else to say about this or just that it is there to determine dev or consumer phone?

[denpth]

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

[sos567656765]

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.

[sos567656765]

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.

[denpth]

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

[denpth]

Bump for hope.

Sent from my DROID BIONIC using DroidForums