SBF "ACTUALLY" Fails... Need help with ADB fastboot

[BHuber09]

Wow. Not gonna lie I thought my next post was going to be your phone is toast haha

But dude congrats. And thank you for teaching me a few things.

Sent from my Galaxy Nexus using Tapatalk 2

[Ads]

[tbodary]

Teaching??!?! I havent a clue what im doing!!! lol i just fiddle with things till they work Ha!

[clothednblack]

Great job BHurber09

Pimped out Dx WiZaRdS MiUi

[GoCliffGo05]

Teaching??!?! I havent a clue what im doing!!! lol i just fiddle with things till they work Ha!

Hahah...

B you are the man!

Sent from my X2 using DXF

[Goose306]

Glad to see it working, B a few thoughts that might clear things up for you as I've hacked around the bootloader a bit on the OG X. The X2 is a bit different because it has fastboot enabled but the lock on the bootloader is similar.

You are able to fastboot to any partition with the locked bootloader (most likely, I haven't experimented fully obviously as I don't and never had an X2) however it will only accept Motorola signed images. So, if you pull the boot.img from an updater zip (the img.p is just how they come, but as was stated prior you can just delete the extra ending) you can flash it manually in fastboot. You can do that on the OG X but it doesn't have fastboot. Fastboot allows the X2 to have an extra layer to save yourself (possibly) with an SBF, for most people's cases though it is easier to just SBF.

With the OG X you can do similar commands with the write_raw_data command in Edify scripting in CWM. That is how you can actually feasibly use CWM and go from Froyo to GB and back again, however its slightly imperfect (to be honest I never figured out why exactly as it should work as normal, but something about the way CWM is bootstrapped around stock recovery makes things a bit bumpy going back and forth in CWM). You just have to make sure you use Motorola signed files, and make sure that the files you are using are compatible with your mbm (Motorola Boot Manager) and MEM_MAP (signature checks) for the correct version and it will flash. That's how we were flashing the .621 kernels and other firmware files prior to the Magic MD5 root method. In fact, it doesn't even need to match in signature checks, the phone will take it and flash, but you will never get out of the bootloader (that's the eFuse)

I assume Fastboot has similar permissions to how you can get Edify scripting working in CWM, so you can flash the individual Moto files as long as they signature and bootloader match.

[BHuber09]

Glad to see it working, B a few thoughts that might clear things up for you as I've hacked around the bootloader a bit on the OG X. The X2 is a bit different because it has fastboot enabled but the lock on the bootloader is similar.

You are able to fastboot to any partition with the locked bootloader (most likely, I haven't experimented fully obviously as I don't and never had an X2) however it will only accept Motorola signed images. So, if you pull the boot.img from an updater zip (the img.p is just how they come, but as was stated prior you can just delete the extra ending) you can flash it manually in fastboot. You can do that on the OG X but it doesn't have fastboot. Fastboot allows the X2 to have an extra layer to save yourself (possibly) with an SBF, for most people's cases though it is easier to just SBF.

With the OG X you can do similar commands with the write_raw_data command in Edify scripting in CWM. That is how you can actually feasibly use CWM and go from Froyo to GB and back again, however its slightly imperfect (to be honest I never figured out why exactly as it should work as normal, but something about the way CWM is bootstrapped around stock recovery makes things a bit bumpy going back and forth in CWM). You just have to make sure you use Motorola signed files, and make sure that the files you are using are compatible with your mbm (Motorola Boot Manager) and MEM_MAP (signature checks) for the correct version and it will flash. That's how we were flashing the .621 kernels and other firmware files prior to the Magic MD5 root method. In fact, it doesn't even need to match in signature checks, the phone will take it and flash, but you will never get out of the bootloader (that's the eFuse)

I assume Fastboot has similar permissions to how you can get Edify scripting working in CWM, so you can flash the individual Moto files as long as they signature and bootloader match.

Okay. Some of that was over my head but I'm pretty sure I understand it. But if Fastboot works on the x2 and you can boot into their boot.IMG.p then maybe. Just maybe you could create an insecure boot image? (Or would it run through the checks and not flash?)

Sent from my Galaxy Nexus using Tapatalk 2

[AdamTomaino]

Just read through this posting and my emotions were as follows:

[Goose306]

Okay. Some of that was over my head but I'm pretty sure I understand it. But if Fastboot works on the x2 and you can boot into their boot.IMG.p then maybe. Just maybe you could create an insecure boot image? (Or would it run through the checks and not flash?)

Sent from my Galaxy Nexus using Tapatalk 2

Not sure exactly on the end result as I've never messed with fastboot on the X2 but I'm pretty sure it would either fail a flash or trip the eFuse and put you in boot loader until you flashed a Motorola signed image. As Motorola never released an insecured kernel for the X2 that would lead me to believe its not possible.

Tapped from my jelly-beaned d2vzw