Originally Posted by ArcanaXVIII

No wonder the guy is angry and hating after XDA.

A bunch of retard harassed him for a dump giving him some wrong instructions that broke his phone.

Wrong instructions that broke his phone?

I highly doubt "adb pull" is capable of breaking anything...

Take a break... go to d/l CyanogenMod 5.0.7-Test3.

It's not that hard to flash back to stock recovery...k so we need a standard way to dump so we don't "mess up" anyones phone

Originally Posted by mikef1182

Ive read a few places saying we need stock recovery to flash the zip from sd. I hope those reports are wrong.

same question, do i need a stock recovery image?

is it possibe that the nlocked bootloader is causing the updates not being able to get to us??

Originally Posted by mohsin125

is it possibe that the nlocked bootloader is causing the updates not being able to get to us??

thats very very unlikely

Originally Posted by Domskibus

But i isnt bricked, is it?
Engadget got the update again, after they've flashed to 2.1....

No, there is no way to brick it like that. He can just reflash the stock rom if he wants. It's on Modaco.

http://android.modaco.com/content/go...nsecure-himem/

He wants it in image format if it's signed with the official keys. Then just renaming it to PASSIMG.zip, putting it in the root of his sdcard and booting to the bootloader will allow him to flash it to stock.

Originally Posted by mixxy

same question, do i need a stock recovery image?

Yes, of course you do. The official updates are signed with the release-keys, not the test-keys the custom recovery-images use.

i have a question... the problem with the multitouch has been solved with froyo???

....Is his phone now bricked???
Or is it just some one of the simple errors?

Edit. @blunden. Thanks

Originally Posted by FeRoX80

i have a question... the problem with the multitouch has been solved with froyo???

Supposedly Google's made some improvements. Only one way to know for sure