Nexus One stuck in boot screen

[BobaFett]

So I Got my nexus one(serial no. HT069P900411) yesterday..a friend of mine got it for me..as suggested I charged it until the notification light turned green..
1) Upon powering up..it got stuck in the boot screen for more than 5 mins..(Google coloured X logo)..
2) Tried to boot it in the recovery mode(Vol down + Power button) and did 'Clear Storage'[Hard Reset]...it said it'll reboot in 5 secs..but it didn't power up..
3) took the battery out..powered it up normally..the same problem persisted..
4) This time I boot it in the fastboot menu(Trackball down + Power button)..went into bootloader..that's when I see these error messages momentarily..

SD checking..
Loading PASSDIAG.zip..
No Image!
Loading PASSDIAG.nbh..
No Image or Wrong Image!
Loading PASSIMG.zip..
No Image!
Loading PASSIMG.nbh
No Image or Wrong Image!

I'm not sure what to do next..shouldn't the image be in ROM anyway..why does it look for the image on the SD card..

Anyways what i plan to do next is to flash the stock Froyo build(FRF91) onto the phone..now the problem with this is that I do not know the current Froyo build number on my phone(since i haven't been able to boot it up even once)..Is there a way to find out the build number from the serial number?(I knw it indicates the date as 2010, 9th June).From this date I'm very sure that it has Froyo on it..just not sure about the build number..any ideas on how i could proceed from here?

Thanks so much.

[danger-rat]

You always get those messages in hboot. If you ever want to re-image the phone, you can place a PASSIMG.zip file on the SD, and it will auto install... though this function seems to have been disabled with the 0.35 hboot.

As for your problem, if it's a new phone - send it back. It's not how I'd want to start life with a new phone...

Sent from my Nexus One using Tapatalk

[aseems]

I've got the same issue
where do we get this PASSIMG.zip file
and how do we place it on the SD Card?

[danger-rat]

Here's a link. Follow unroot/restore using PASSIMG method:
http://forum.xda-developers.com/wiki...ore_your_Nexus

This won't work on hboot 0.35

Sent from my Nexus One using Tapatalk

[aseems]

Originally Posted by danger-rat

Here's a link. Follow unroot/restore using PASSIMG method:
Nexus One/Guides & Tutorials - XDA-Developers

This won't work on hboot 0.35

Sent from my Nexus One using Tapatalk

Thanks Danger!

I don't even know what hboot 0.35 is ?!!??!!??

But i'm Downloading Nexus One FRG83 system image from HTC - Developer Center and renaming it as PASSIMG.Zip

Then i'll try to laod it on my sdcard root and start her up....

Hoping (Praying) it'll work

[danger-rat]

Your hboot number will show up on your bootloader screen.
Also, you may want to try FRG33, because FRG83 seems to struggle with the PASSIMG method...
http://www.mediafire.com/?dxwh5l4b5ygh6nf

Sent from my Nexus One using Tapatalk

[fele]

(sorry my english)

Hi, I am with the same situation now. I bought a new Nexus One but never start. It's stucked in the boot screen with an coloured

I have no warranti to send it to and I would like to fix it myself. Did any of you have fixed the problem?

What happened after flashing?

Thanks id advance.

Fele.-

[danger-rat]

Can you get into the bootloader (when powering on, hold volume down key, and while still holding power on)?

Sent from my Nexus One using Tapatalk

[fele]

Thanks for yout reply!

Yes, I can get into the bootloader.

I have tried to flash the FRG33 ROM from the SD card whith passimg.zip but I get the following errors:

Parsing...[SD ZIP]
[1] Boot - OK
[2] Bootloader - OK
[3] Radio_V2 - Fail-PU
[4] Recovery - OK
[5] SP_CUSTOM - OK
[6] SPLASHH1 - OK
[7] SYSTEM - OK
[8] USERDATA - OK
Partition updtate fail!
Do you want to reboot device?

I would apreciate any help !!!

In this video you can see the boot problem. This video is not mine but this guy has the same problem:

YouTube

YouTube

When I turn on the phone the X appear, vibrates 7 times and then freeze.

[danger-rat]

I would say that your best option is to try a factory reset

If that doesn't work, then I suggest setting up the sdk, and seeing if you can communicate via adb or fastboot...