Possible Bricked Nexus One

[Guest Peanut_One]

Hi all,

I've spent hours doing research before writing and I can't seem to find the answer anywhere, which brings me to finally asking all of the smarter people. I bought a new Nexus One recently as a development handset. It came with Froyo 2.2. I wanted to root the phone, which was successful using the superboot for FRF91. I was still unable to flash the CM Recovery or the RANexusOne due to the 0.35.0017 bootloader. I attempted to pass it an older version of the bootloader using the PASSIMG.zip method. I was able to successfully flash the bootloader, but now I get nothing. When the phone is plugged in, I get the charging light, but nothing else. When turned on, the phone vibrates once, waits about 45 seconds, and then vibrates once again. I have no screen (no logos or anything...just a blank screen), no communication, etc with the phone. I'm on a mac. The phone doesn't show up with adb devices or fastboot devices, etc. I'm sort of at a loss on what to do. Did I break it beyond repair? Does it seem like I need to send it back to google? Any suggestions would be greatly appreciated.

Thanks

~P

[Guest PTzero]

Can you get to Recovery or Fastboot? Hold down the Volume Down button while booting up. If you can do that you should be able to re-flash with a working ROM.

[Guest URPREY]

Hi all,

I've spent hours doing research before writing and I can't seem to find the answer anywhere, which brings me to finally asking all of the smarter people. I bought a new Nexus One recently as a development handset. It came with Froyo 2.2. I wanted to root the phone, which was successful using the superboot for FRF91. I was still unable to flash the CM Recovery or the RANexusOne due to the 0.35.0017 bootloader. I attempted to pass it an older version of the bootloader using the PASSIMG.zip method. I was able to successfully flash the bootloader, but now I get nothing. When the phone is plugged in, I get the charging light, but nothing else. When turned on, the phone vibrates once, waits about 45 seconds, and then vibrates once again. I have no screen (no logos or anything...just a blank screen), no communication, etc with the phone. I'm on a mac. The phone doesn't show up with adb devices or fastboot devices, etc. I'm sort of at a loss on what to do. Did I break it beyond repair? Does it seem like I need to send it back to google? Any suggestions would be greatly appreciated.

Thanks

~P

Sounds like you have an N1 with an SLCD. You need to flash a ROM with SLCD support maybe?

[Guest Peanut_One]

That sounds reasonable but my underlying issue is that I currently cannot boot to the bootloader or to recovery. I've tried both holding the volume down key and trackball while powering on and I get nothing...just a blank screen. Is there a way to force a flash? It doesn't show up in adb devices so I don't see a way to communicate with it. Do you think I've caused an unrecoverable error where I need to send it back or is there some way I can force it to flash a new bootloader?

Thanks

~P

[Guest stevenz]

That sounds reasonable but my underlying issue is that I currently cannot boot to the bootloader or to recovery. I've tried both holding the volume down key and trackball while powering on and I get nothing...just a blank screen. Is there a way to force a flash? It doesn't show up in adb devices so I don't see a way to communicate with it. Do you think I've caused an unrecoverable error where I need to send it back or is there some way I can force it to flash a new bootloader?

If booting into what should be the fastboot bootloader, and then running "fastboot devices" sees nothing, then you're almost certainly going to need to send the phone back to HTC/Google/whoever for repair. If it's still under warranty, then you might be lucky. Only they would have the equipment to do a hardware flash of the ROM, assuming it's even possible. You need fastboot access to flash a bootloader, and if fastboot won't even start then you're out of luck unfortunately.

[Guest crawler9]

Try pulling the battery to make sure the phone is powered off, then boot it up while holding the trackball. Then, connect to your computer and run the command "fastboot devices" to see if it shows up despite the screen being blank. If this is the case, it wouldn't be hard to upgrade back to the new bootloader.

Edited October 31, 2010 by crawler9