Root Cook 2.2 OTA ZIP For Baseband and Bootloader

[amoeller]

I was looking at the OTA ZIP file from VZW and noticed some BIN and IMG files. I'm guessing that it bootloader and baseband images. Is there a way that I can swap out those files with a nicer bootloader? Basicly what I want is stock OTA 2.2 with 29.01 or 30.01 bootloader but I want the new baseband with the update. Can I do this or does it just fail because of signatures, checksums, or some other crap I can't think of?

Thanks

 

[OMJ]

I wouldnt suggest it. If it was a safe and easy thing to do a dev would have done it already.

A nicer bootloader though? Who knows what they changed with the bootloader. They may have locked it down even more.

If you really want those things right now you are best off flashing the OTA

 

[Piiman]

I was looking at the OTA ZIP file from VZW and noticed some BIN and IMG files. I'm guessing that it bootloader and baseband images. Is there a way that I can swap out those files with a nicer bootloader? Basicly what I want is stock OTA 2.2 with 29.01 or 30.01 bootloader but I want the new baseband with the update. Can I do this or does it just fail because of signatures, checksums, or some other crap I can't think of?

Thanks

What's nicer about the new bootloader? I think they just locked it down more and used the change to render the 2.1 SBF useless (if you go to the 2.2 OTA)

OMJ have you heard if the new boot loader change change the engineering mode thing? Birdman has been pretty quite lately.

 

[mazz0310]

What's nicer about the new bootloader? I think they just locked it down more and used the change to render the 2.1 SBF useless (if you go to the 2.2 OTA)

OMJ have you heard if the new boot loader change change the engineering mode thing? Birdman has been pretty quite lately.

He meant he wants to take out the new bootloader and inject the old one... reread the post.

 

[Piiman]

He meant he wants to take out the new bootloader and inject the old one... reread the post.

opps me bad (Note to self; don't read forum before coffee.)

 

[OMJ]

What's nicer about the new bootloader? I think they just locked it down more and used the change to render the 2.1 SBF useless (if you go to the 2.2 OTA)

OMJ have you heard if the new boot loader change change the engineering mode thing? Birdman has been pretty quite lately.

I havent heard anything but more skepticism.

He meant he wants to take out the new bootloader and inject the old one... reread the post.

I totally read this wrong as well. The problem with this is that the new keys actually come in later in the boot process and not when the bootloader is flashed. I dont know anyone is sure yet when exactly the keys are changed but its not during the changing of the bootloader.

 

[D13]

A reason why I always wait out OTAs, a dev will make something better...
especially since moto knows what we are doing

 

[mazz0310]

I havent heard anything but more skepticism.



I totally read this wrong as well. The problem with this is that the new keys actually come in later in the boot process and not when the bootloader is flashed. I dont know anyone is sure yet when exactly the keys are changed but its not during the changing of the bootloader.

Just my 2 cents, I think the dev's are too afraid to mess around with the bootloader as much at this point because of the lack of a full SBF. Atleast I know I would be.

 

[D13]

Just my 2 cents, I think the dev's are too afraid to mess around with the bootloader as much at this point because of the lack of a full SBF. Atleast I know I would be.

I also think most of the devs are smart enough to not get the OTA and continue working on the one they already know about

 

[vanilla_android_fan]

I have written in several different threads at Motorola's Official Droid X forum about getting a 2.2 SBF, but as you can imagine, my words fell on deaf ears. Motorola is dead set on not making things easy (or next to impossible) for the hacker community (Sorry I'm being captain obvious, please don't rip for it ).

I know this is probably a crazy/stupid/impossible idea, but don't most (if not all) console gaming systems have some sort of protection against loading "backup" copies of games? I had a PSX that I soldered a mod-chip to that allowed me to bypass the protections created by Sony. I realize that this is not exactly the same thing as what we're facing with the locked boot loader and efuse, but it seems that someone with a strong background in electronics or an EE might be able to solder a chip of some sort to the board on the Droid X that would trick the boot loader into thinking that a custom loaded rom was actually an official Motorola piece of software? Again I apologize in advance if I'm breaking any rules here or if I'm just totally crazy/unrealistic about a hardware modification approach to our uber locked down phone.

 

[tom108]

I have written in several different threads at Motorola's Official Droid X forum about getting a 2.2 SBF, but as you can imagine, my words fell on deaf ears. Motorola is dead set on not making things easy (or next to impossible) for the hacker community (Sorry I'm being captain obvious, please don't rip for it ).

I know this is probably a crazy/stupid/impossible idea, but don't most (if not all) console gaming systems have some sort of protection against loading "backup" copies of games? I had a PSX that I soldered a mod-chip to that allowed me to bypass the protections created by Sony. I realize that this is not exactly the same thing as what we're facing with the locked boot loader and efuse, but it seems that someone with a strong background in electronics or an EE might be able to solder a chip of some sort to the board on the Droid X that would trick the boot loader into thinking that a custom loaded rom was actually an official Motorola piece of software? Again I apologize in advance if I'm breaking any rules here or if I'm just totally crazy/unrealistic about a hardware modification approach to our uber locked down phone.

i doubt you would ever be able to get Moto to release the sbf willingly. that file is for manufactures and the cell networks only. as of right now i dont even think verizon has the sbf. that is not a file that gets handed over to the end user it has to be leaked.

 

[D13]

I have written in several different threads at Motorola's Official Droid X forum about getting a 2.2 SBF, but as you can imagine, my words fell on deaf ears. Motorola is dead set on not making things easy (or next to impossible) for the hacker community (Sorry I'm being captain obvious, please don't rip for it ).

I know this is probably a crazy/stupid/impossible idea, but don't most (if not all) console gaming systems have some sort of protection against loading "backup" copies of games? I had a PSX that I soldered a mod-chip to that allowed me to bypass the protections created by Sony. I realize that this is not exactly the same thing as what we're facing with the locked boot loader and efuse, but it seems that someone with a strong background in electronics or an EE might be able to solder a chip of some sort to the board on the Droid X that would trick the boot loader into thinking that a custom loaded rom was actually an official Motorola piece of software? Again I apologize in advance if I'm breaking any rules here or if I'm just totally crazy/unrealistic about a hardware modification approach to our uber locked down phone.

yes this method has been discussed before but who wants to do that

 

[vanilla_android_fan]

yes this method has been discussed before but who wants to do that

So I take it that the hardware mod approach was not a popular/viable option? Was it discussed on this forum? I will try and do my research before I propose an idea next time

 

[D13]

So I take it that the hardware mod approach was not a popular/viable option? Was it discussed on this forum? I will try and do my research before I propose an idea next time

not extensively, but I think the devs just decided to not take that approach