If somebody has correctly answered your question, please remember to accept an answer and vote them up if you can! Read more at the FAQ
Featured question: what's your favorite game?
vote up 1 vote down
star

Whoops - I flashed recovery-RA-dream-v1.5.2R.img instead of recovery-RA-dream-v1.5.2.img on my Android Dev Phone 1 from here. It's stuck on the Android screen (not the animated one - the one before Android starts booting.) Power and (home / back / camera) doesn't do anything. The only way to reboot is to pull the battery. Please tell me it's not bricked!

flag
Can you get to it via ADB? – Chuck Feb 3 at 21:59
@Chuck - no. All signs point to brick. – Isaac Waller Feb 4 at 0:29
Guh, that stinks. – Chuck Feb 4 at 14:15

1 Answer

vote up 1 vote down

Hmm... This is the first time I'm hearing of a wrong recovery image causing a brick. In theory this shouldn't have happened, since the recovery is simply a separate boot and system Linux image. I've heard people writing boot images to recovery and still being able to re-flash the proper image from fastboot (Camera + Power).

The only sure-fire way to brick a G1/ADP1 was to create a mismatch of SPL and Radio images, i.e. older Radio with the "Danger" SPL. Neither of these are being touched when you flash a recovery image. Are you absolutely sure you can't get into fastboot mode by holding the Camera and Power buttons with the phone being off?

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.