Froyo 2.2 and Root - Use this thread to post questions / concerns...

[DebianDog]

Cool thanks for the link

[Droid-X-Forums]

[jrac86]

Worked for me too! You may need to toggle the bluetooth when you run "./rageagainstthecage-arm5.bin"

EDIT: Are you able to see the paid apps in the market after rooting? I replaced the build.prop (Build.prop edits = great battery life + fast phone + full market), but still cannot see them

[iDr0id]

I can't get the damn drivers to work. I did as the instructions said point for point, but I only would come up with android sooner composite, and not android composite. And alwaysw when i go to where it sais hit "have disk" I do and go to the folder where teh drivers are and they say there are no combatible drivers for your device or whatever...

Windows 7 64bit

[SlickYamaha]

Does anyone know if easy root works? It seems to work but then when I restart it days I'm not rooted. I know I'm lazy but one click root and unroot is so efficient lol

Sent from my DROIDX using Tapatalk

[DebianDog]

Does anyone know if easy root works? It seems to work but then when I restart it days I'm not rooted. I know I'm lazy but one click root and unroot is so efficient lol

Sent from my DROIDX using Tapatalk

I spoke with the developer a few weeks back. He said when 2.2 came out he would update. I assume that would be today...

Some folks have said Androot works. Give it a shot. Let us know http://forum.xda-developers.com/showthread.php?t=747598

[smalltowngirl13]

Will be merging related threads into here...

[Martin030908]

This was posted by DroidForums "Chief Droid Scientist" (sbf/recovery guru) Motocache1

ALERT: Droid X FroYo OTA - new bootloader uses new signing keys
I got brought in on this by someone who hit my Gtalk on my phone at 4:30a to let me know that the world was coming to an end -- more or less.

In the last couple hours we've sorted out a lot and the deal is, in the new Droid X OTA it appears that they have replaced the entire HAB chain from the mbmloader (the loader for the boot loader) on forward. The keys that were used to sign the prior HAB components are no longer trusted by the new HAB components. What that means is that if you take the current OTA, and then subsequently use an SBF (or any other method) to replace a signed code group (which is just about every code group on a DX) that signature will not be valid and the boot process will halt when that CG is encountered. Since pretty much every SBF contains the "boot" and "recovery" code group, as well as the very-critical "CDT" code group, this means if you apply an SBF to your OTA'd phone (that is now running the 30.03 bootloader) your phone is toast. But not permanently.

In the above scenario you will still be running the new mbmloader (GC63) and mbm (CG30), so as long as you put code groups back on that are signed with the new signatures, you'll be back in business. None of the prior SBF's are going to help you -- they are invalid as of this OTA.

I'm sure Verizon is expecting this and has the 2.3.13 SBF standing by in the retail stores so they can flash you back to stock and get you working again (and give you the evil eye when you lie about how your phone got this way -- because I'm sure they have been warned about this happening in advance).

That's all for now. Hopefully this helps avoid too much unnecessary confusion, so you can just concentrate on dealing with the necessary confusion.

[ajp]

This was posted by DroidForums "Chief Droid Scientist" (sbf/recovery guru) Motocache1

ALERT: Droid X FroYo OTA - new bootloader uses new signing keys
I got brought in on this by someone who hit my Gtalk on my phone at 4:30a to let me know that the world was coming to an end -- more or less.

In the last couple hours we've sorted out a lot and the deal is, in the new Droid X OTA it appears that they have replaced the entire HAB chain from the mbmloader (the loader for the boot loader) on forward. The keys that were used to sign the prior HAB components are no longer trusted by the new HAB components. What that means is that if you take the current OTA, and then subsequently use an SBF (or any other method) to replace a signed code group (which is just about every code group on a DX) that signature will not be valid and the boot process will halt when that CG is encountered. Since pretty much every SBF contains the "boot" and "recovery" code group, as well as the very-critical "CDT" code group, this means if you apply an SBF to your OTA'd phone (that is now running the 30.03 bootloader) your phone is toast. But not permanently.

In the above scenario you will still be running the new mbmloader (GC63) and mbm (CG30), so as long as you put code groups back on that are signed with the new signatures, you'll be back in business. None of the prior SBF's are going to help you -- they are invalid as of this OTA.

I'm sure Verizon is expecting this and has the 2.3.13 SBF standing by in the retail stores so they can flash you back to stock and get you working again (and give you the evil eye when you lie about how your phone got this way -- because I'm sure they have been warned about this happening in advance).

That's all for now. Hopefully this helps avoid too much unnecessary confusion, so you can just concentrate on dealing with the necessary confusion.

Thanks for posting that. I had just read that on its original post, but I think it deserves all the attention it can get.

[Ant]

Ok so two of my buddies have got their update this morning and I haven't...is it because im running the leaked 2.2(2.2.9)??? And if so do I have to sbf to get ota?

[movadoevo8]

Hey guys I read a couple of threads stating that the new OFFICIAL OTA bricks your D X if you are currently running the leaked froyo 2.2 and try to downgrade via sbs to stock 2.1 and then applying the OTA.

Is this 100% true? Is there a way around it yet?

Im on leaked 2.2 rooted and am afraid to downgrade to 2.1 and apply the OTA.

_____________________

-DXed via Tapatalk-
_____________________