Originally Posted by Huey85

That is how this thread began...

Sent from my XT910 using xda premium

Lol

10char.

We've examinated with Skrilax_CZ (Thanks man!) the whole situation and unfortunately we've discovered that the bootloader we've got is only a different one.

We still don't know with precision in what does it differ, it shows "Factory Use Only" on Fastboot Mode and it is SIGNED, so it can be flashed on retail RAZRs without any problem, but still, the unlock procedure is disabled and it can't be enabled.

We've tried multiple ways 'til now and I'm sorry to say that: nothing to do. It wasn't of any help.


I can't explain more on the things we've tried, but the bad thing is that the guy where we've taken the bootloader from has got a really strange device, it is a RETAIL EU device but its OMAP4430 is soldered in GP Mode (like the Engineering phones), so its security is disabled by eFuse.

I can explain just one thing for you, as I feel somehow in debt with you all because I've raised everyone's hopes in that thing:

When the bootloader is loaded, it first checks for a value of an eFuse. If the eFuse that determines the device security (RETAIL or ENGINEERING) is blown it is recognized as RETAIL. If it isn't blown it is recognized as ENGINEERING.
Our eFuse is set to RETAIL, so that the bootloader checks other eFuses to determine if the device has been manually unlocked or not.
That guy's eFuse is set to ENGINEERING, so that the bootloader won't check other eFuses and goes on directly with the UNLOCKED status.


That guy's device isn't an engineering one because other parameters of its device doesn't correspond to an engineering device. It's a really strange device, but something is different on the hardware side: we don't know if its OMAP is soldered to GP or HS Mode, but we're sure its eFuse is set to ENGINEERING and, unfortunately, the fuses cannot be blown TWO times because they're One Time Programmable "memories", so we cannot reprogram our fuse.


I would like to really say thanks to adlx.xda for his device's dumps and to those who trusted us and gave us the possibility to test it on their devices with a good chance of hardbricks. (Sorry if I don't say your nicknames guys, we've talked on GTalk and I can't clearly remember your xda nicknames!)
Thanks guys, without you, we would have never known the truth on this.

Oh, another word to the testers. Please, don't make this bootloader to be public prior I will: I don't know if WE CAN upload it to the public or not.



As for now, I'm sad to announce that this TEST has been failed.
This thread will be closed in an hour or so.



The EternityProject Team Manager,
--kholk

Originally Posted by Ronin3178

Then a suggestion that the OP edit the title to reflect that so us xt912 users don't get overly excited.

Thanks

Sent from my DROID RAZR using xda premium

I'm sure the bootloaders are very similar, if not identical in nature. All they have is a phone with a mysteriously unlocked/engineering mode BL. People automatically assumed it meant they had figured it out. It's just another possible tool to help in the task to unlock the bootloader.

Originally Posted by seanmcd72

People automatically assumed it meant they had figured it out. It's just another possible tool to help in the task to unlock the bootloader.

original post clearly states I didn't make it happen, that I just have it like that (lucky or unluckily... )

Originally Posted by kholk

As for now, I'm sad to announce that this TEST has been failed.
This thread will be closed in an hour or so.
The EternityProject Team Manager,
--kholk

Thank you anyway for trying so hard. It's sad that it didn't work but that is not your fault. You guys spent a lot of time and am sure your sleep and life suffered some trying to get this to work. I appreciate the hard work that went into trying to get this to work. Thanks to all those involved!

So, let's politely ask Motorola to unlock the bootloader.

Sent from my XT910 using XDA App

Thank You

---

Originally Posted by kholk

We've examinated the whole situation and unfortunately we've discovered that the bootloader we've got is only a different one.

We still don't know with precision in what does it differ, it shows "Factory Use Only" on Fastboot Mode and it is SIGNED, so it can be flashed on retail RAZRs without any problem, but still, the unlock procedure is disabled and it can't be enabled.

We've tried multiple ways 'til now and I'm sorry to say that: nothing to do. It wasn't of any help.


I can't explain more on the things we've tried, but the bad thing is that the guy where we've taken the bootloader from has got a really strange device, it is a RETAIL EU device but its OMAP4430 is soldered in GP Mode (like the Engineering phones), so its security is disabled by eFuse.

I can explain just one thing for you, as I feel somehow in debt with you all because I've raised everyone's hopes in that thing:

When the bootloader is loaded, it first checks for a value of an eFuse. If the eFuse that determines the device security (RETAIL or ENGINEERING) is blown it is recognized as RETAIL. If it isn't blown it is recognized as ENGINEERING.
Our eFuse is set to RETAIL, so that the bootloader checks other eFuses to determine if the device has been manually unlocked or not.
That guy's eFuse is set to ENGINEERING, so that the bootloader won't check other eFuses and goes on directly with the UNLOCKED status.


That guy's device isn't an engineering one because other parameters of its device doesn't correspond to an engineering device. It's a really strange device, but something is different on the hardware side: we don't know if its OMAP is soldered to GP or HS Mode, but we're sure its eFuse is set to ENGINEERING and, unfortunately, the fuses cannot be blown TWO times because they're One Time Programmable "memories", so we cannot reprogram our fuse.


I would like to really say thanks to adlx.xda for his device's dumps and to those who trusted us and gave us the possibility to test it on their devices with a good chance of hardbricks. (Sorry if I don't say your nicknames guys, we've talked on GTalk and I can't clearly remember your xda nicknames!)
Thanks guys, without you, we would have never known the truth on this.

Oh, another word to the testers. Please, don't make this bootloader to be public prior I will: I don't know if WE CAN upload it to the public or not.



As for now, I'm sad to announce that this TEST has been failed.
This thread will be closed in an hour or so.



The EternityProject Team Manager,
--kholk

Hi! Kholk and the Team

Thank you for the wonderful work... now we know for clear that eFuse is there,.... but if the efuse is "One Time progamable" then how can we work or how can we or Moto unlock it by re-programming it once more. oh
maybe it would remove the efuse.
Anyways. Am glad that we are hitting the right point.!
done worry guys!!! Lets keep working without tiring!!!

Originally Posted by bahathir

So, let's politely ask Motorola to unlock the bootloader.

Sent from my XT910 using XDA App

Yes we must go on asking Moto for all their devices.

Sent from my XT910 using Tapatalk

Originally Posted by kholk

We've examinated the whole situation and unfortunately we've discovered that the bootloader we've got is only a different one.

We still don't know with precision in what does it differ, it shows "Factory Use Only" on Fastboot Mode and it is SIGNED, so it can be flashed on retail RAZRs without any problem, but still, the unlock procedure is disabled and it can't be enabled.

We've tried multiple ways 'til now and I'm sorry to say that: nothing to do. It wasn't of any help.


I can't explain more on the things we've tried, but the bad thing is that the guy where we've taken the bootloader from has got a really strange device, it is a RETAIL EU device but its OMAP4430 is soldered in GP Mode (like the Engineering phones), so its security is disabled by eFuse.

I can explain just one thing for you, as I feel somehow in debt with you all because I've raised everyone's hopes in that thing:

When the bootloader is loaded, it first checks for a value of an eFuse. If the eFuse that determines the device security (RETAIL or ENGINEERING) is blown it is recognized as RETAIL. If it isn't blown it is recognized as ENGINEERING.
Our eFuse is set to RETAIL, so that the bootloader checks other eFuses to determine if the device has been manually unlocked or not.
That guy's eFuse is set to ENGINEERING, so that the bootloader won't check other eFuses and goes on directly with the UNLOCKED status.


That guy's device isn't an engineering one because other parameters of its device doesn't correspond to an engineering device. It's a really strange device, but something is different on the hardware side: we don't know if its OMAP is soldered to GP or HS Mode, but we're sure its eFuse is set to ENGINEERING and, unfortunately, the fuses cannot be blown TWO times because they're One Time Programmable "memories", so we cannot reprogram our fuse.


I would like to really say thanks to adlx.xda for his device's dumps and to those who trusted us and gave us the possibility to test it on their devices with a good chance of hardbricks. (Sorry if I don't say your nicknames guys, we've talked on GTalk and I can't clearly remember your xda nicknames!)
Thanks guys, without you, we would have never known the truth on this.

Oh, another word to the testers. Please, don't make this bootloader to be public prior I will: I don't know if WE CAN upload it to the public or not.



As for now, I'm sad to announce that this TEST has been failed.
This thread will be closed in an hour or so.



The EternityProject Team Manager,
--kholk

Thanks so much for trying, kholk! We appreciate you and everyone involved's hard work in figuring this out. :]

Originally Posted by kholk

We've examinated the whole situation and unfortunately we've discovered that the bootloader we've got is only a different one.

We still don't know with precision in what does it differ, it shows "Factory Use Only" on Fastboot Mode and it is SIGNED, so it can be flashed on retail RAZRs without any problem, but still, the unlock procedure is disabled and it can't be enabled.

We've tried multiple ways 'til now and I'm sorry to say that: nothing to do. It wasn't of any help.


I can't explain more on the things we've tried, but the bad thing is that the guy where we've taken the bootloader from has got a really strange device, it is a RETAIL EU device but its OMAP4430 is soldered in GP Mode (like the Engineering phones), so its security is disabled by eFuse.

I can explain just one thing for you, as I feel somehow in debt with you all because I've raised everyone's hopes in that thing:

When the bootloader is loaded, it first checks for a value of an eFuse. If the eFuse that determines the device security (RETAIL or ENGINEERING) is blown it is recognized as RETAIL. If it isn't blown it is recognized as ENGINEERING.
Our eFuse is set to RETAIL, so that the bootloader checks other eFuses to determine if the device has been manually unlocked or not.
That guy's eFuse is set to ENGINEERING, so that the bootloader won't check other eFuses and goes on directly with the UNLOCKED status.


That guy's device isn't an engineering one because other parameters of its device doesn't correspond to an engineering device. It's a really strange device, but something is different on the hardware side: we don't know if its OMAP is soldered to GP or HS Mode, but we're sure its eFuse is set to ENGINEERING and, unfortunately, the fuses cannot be blown TWO times because they're One Time Programmable "memories", so we cannot reprogram our fuse.


I would like to really say thanks to adlx.xda for his device's dumps and to those who trusted us and gave us the possibility to test it on their devices with a good chance of hardbricks. (Sorry if I don't say your nicknames guys, we've talked on GTalk and I can't clearly remember your xda nicknames!)
Thanks guys, without you, we would have never known the truth on this.

Oh, another word to the testers. Please, don't make this bootloader to be public prior I will: I don't know if WE CAN upload it to the public or not.



As for now, I'm sad to announce that this TEST has been failed.
This thread will be closed in an hour or so.



The EternityProject Team Manager,
--kholk

Some technical mistakes in here but the outcome is correct