Database Develop

Freeze at G1 Splash SCreen, I Need Help!!

Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped

tehseano said:
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
Click to expand...
Click to collapse
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.

andonnguyen said:
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
Click to expand...
Click to collapse
Sorry, I should have provided more information, and explained that the 2nd half of this post was my original post, which was just me asking how to correctly use ADB. I do already have JF 1.41, I upgraded yesterday. It wasn't my first theme I installed either. I was using Vintage War (for the Dream), but it hadn't been updated for 1.41, so I was trying the standalone apk adb push method found in this forum, which is where this post first oriented.
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
But like I said this wasn't my first time trying to mod the phone, I've had it rooted for a month or so now, and have been keeping up-to-date.
Any more information I can provide, please let me know. My phone is my livelyhood, I need it. So if anyone can help, the sooner would be better. Either way I am entirely greatful for any help anyone can provide. Thanks in advance!

tehseano said:
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
Click to expand...
Click to collapse
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)

andonnguyen said:
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
Click to expand...
Click to collapse
....How do I get out of the loop. My phone doesn't get passed it. There has to be something I can do in console or recovery or something. I'm really sorry if I'm coming off as rude or demanding but I really need a phone, and I need it right now. I don't know what more I can tell you before someone can finally give me a solution (sorry)

1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.

Datruesurfer said:
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Click to expand...
Click to collapse
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it. Regardless thank you so very much, you are my Savior right now!

tehseano said:
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it.
Click to expand...
Click to collapse
That's easy. Just grab a copy of the fastboot utility and the images off your sdcard in the 'nandroid' directory and boot your phone into the SPL. Plug your phone in via usb and press the back button once and you should see "Serial0" change to "FASTBOOT" Then open up a windows command prompt in the location of the exe you downloaded and run:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot reboot
Your phone will come back up with all of your applications, settings etc from when you did the backup. Keep in mind you need the HardSPL to do this though(look for three androids on skateboards in SPL). The G1 factory bootloader does not support fastboot, only NBH images that come from the factory.

Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.

Isn't the 4 color screen the standard bootloader that ships with retail G1's (not a dev phone bootloader)?

lugiamx said:
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Click to expand...
Click to collapse
I had the same problem, almost verbatim. ADP1.1, JFv1.41, ran the Holiday update 1 of 2, no problems, did the 2 of 2 update, got stuck at the flashing Android boot screen. Pulled the battery, rebooted, same thing, waited 2-3 minutes at the flashing screen and was just about to pull the battery again and then all of a sudden the damn thing came to life, the OS loaded up and now everything's working fine. Gave me quite a scare.

ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.

chinoman said:
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
Click to expand...
Click to collapse
Why have you just hijacked a 5 month old thread? You haven't given use any details either. Fastboot is available for all OS's, it will work on your computer, you just probably don't know how to use it. Please make a new thread in the Q&A section where we can help you out there.

This should be closed or moved to Q&A.

hey man just unroot ur phone and root it again u soft bricked ur phone its ok

hey just try to unroot k

hey if u want me to fix it for u just email me at [email protected] and ill help u

Bricked G1?

New to G1 and have a problem. Bought a G1 and it came with elcaires rom I think it was.
So I downloaded UK RC7, renamed it to Update, and placed it on the root of my card.
Held the home and power button, and tried to install but I'm getting installation aborted each time. I've also tried to wipe, but that gets aborted too.
I rebooted and now its stuck on G1 screen
I hope somebody can help, had the phone an hour and I've mucked it up already.
Thanks in advance

Im also "bricked" at the loading screen, i turn it on and it gets frozen at the tmobile screen. Home+power, camera+power, Alt+L etc dont work.
Is this fixable?

sirlewis said:
Im also "bricked" at the loading screen, i turn it on and it gets frozen at the tmobile screen. Home+power, camera+power, Alt+L etc dont work.
Is this fixable?
Click to expand...
Click to collapse
No. It's Not.

if its not than what should he and i do?

Are you trying to boot into recovery while its in the G1 screen?

yo my name is sammy as well and i swear i just did the same thing with my g1 on eclair. hit me up dude on [email protected]. we can try and help each other out. plus i love the uk man. i never been, but plan too very soon. i love the music and the accents of the women, oh god. hit me up bro!

If you cannot access recovery or bootloader, you have a rather expensive paperweight. If you can, then you have hope.

AroundTheWorld said:
If you cannot access recovery or bootloader, you have a rather expensive paperweight. If you can, then you have hope.
Click to expand...
Click to collapse
It is not so expensive since it be can brought for less than 100>$$
You can fix it by replacing the board with one from a working phone which is not the easiest thing to do.

hey ill take one of those paper weights... I need a new screen...

in the same boat cant get into anything hung up on splash screen

maybe our only option is jtag, ive never bricked before i always put cm 4 then go and install cm5 above that and it worked but this time it told me to go kick rocks and and and it was a customers phone so i gave him mine which is running eclair.

you guys arn't bricked. If you can turn on the phone than your perfectly fine.
You just gotta learn how to use it

G1 hanged at white screen!
Hi all,
I really need a help here. I have a G1 rooted with CM rom ver5. it was working fine since 3 months but suddenly now the phone doesnt boots up, it goes to white screen with 3 droid skaters and highlight on Hboot. It is freezed then and nothing can be done. I removed battery and tried booting by home + power ; camera+power etc etc . nothing happens it goes to that screen only. i have amons recovery and also nand backups in sd card. but the system doesnt let me go any where!! Please help......
attached is the snapshot

Either your back-button hangs, or something messed up your phone completely.
But as long as you have the fastboot mode, it's not bricked. I would suggest you to clean everything, i.e.
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
and then flash recovery again, i.e.
Code:
fastboot flash recovery <recover.img>
After that you can boot into recovery and restore your latest backup.
Please note: fastboot is a command you execute on your PC and you have to connect your phone with USB to your PC.
If after that procedure your phone boots again into hboot, most likely your back-button is defect.

I myself I think got a bricked G1...
I first installed many custom roms and thought that they were slowing my g1 so I wanted to get my g1 back to normal... For that I googled and was gone to the htc official website and ported the radio and rom from there but unfortunately I read it somewhere and it said that the rom is for only developers phone.
Everything first went very good... no error on clockwork recovery but when I reboot my phone, it got stuck on T-mobile G1 logo screen? I now can not even go to recovery mode or in fastboot mode? I need help...
Someone told me to use odin multi loader? but how do I use it or do it?? I need some instructions?
What should I do now? All I want to do right now is to get rid of my g1 by fixing it and selling it at once!!!

before flashing radio, spl, rom...anything...u need to check out the warnings and compatibility-MUST!!!!
there are 32B and 32A devices...both have different stuffs for themselves....which can be bricked if u dont follow the guidelines and try to act in sort of a haste to accomplish something new!!!
for those who can get to the camera+power (hboot) screen, but cant do anything else...u need to format ur sdcard...FAT32...then download dreaimg.nbh file...keep it in the root of ur sdcard...
then boot into the hboot menu, and ur phone should read the dreaimg.nbh file and prompt u to take an action(flash it)....do that and it'll get ur phone to the stock rom thingy....
then later u gotta root ur device again(telnet, great)....then install amon ra's recovery...change radio and what not and play again....
u gotta be patient...that's the only thing!!!
check this too
http://code.google.com/p/android-roms/wiki/Get_Root

Is it possible to...

...Brick an *UNROOTED* G1...?!
I attempted a soft factory reset (which I have done on many occasions previously successfully) but on this occasion I've run into the bootloop. Hitting Camera+Power button results in bootloop also.
One thing to mention is I removed my SD card before running the factory reset?
I've tried leaving the battery out over night and trying again in the morning.
I've tried placing the SD card back in and booting up the phone.
I've tried holding Home+Power to get into recovery but results in bootloop
I've tried holding Camera+Power to get into Bootloader but results in bootloop.
Any suggestions please?
Thanks!

No, this should not happen. With Bootloop do you mean there is just the G1 logo and nothing else, or does it get past the logo and reboots then?
Another thought, has this phone ever been rooted and unrooted again?
If you are still under warranty and the phone is completely stock, I'd return it.

Nope. Phone has never been rooted then unrooted.
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Warranty is only for a single year, right? So then that's not an option.
Thanks for suggestions.

Jignesh Sutar said:
Warranty is only for a single year, right? So then that's not an option.
Click to expand...
Click to collapse
Depends on where you are: http://www.htc.com/www/support/warranty.html
It looks like you phone either fails to boot, thus tries to boot recovery (box picture is the background of the recovery) and then reboots (best case, i guess) or the boot to recovery flag is set, recovery fails, reboot (you might seriously be screwed).
You are sure that you can't enter the bootloader? Also try Back+PowerOn. That would make things alot more easy.
How long does it stay with the box picture? Long enough to get adb connected? If yes you could try "adb shell reboot bootloader".

Tried all combinations of buttons to try get into bootloader or recovery, nothing!
Definitely no chance of being able to ADB, the phone switches off very quickly...
Also, have ensured the battery is fully charged, in case that has an impact?

I really looks like you are the first all stock bricked guy I ever heard of.
The boot recovery flag seems to be set for some reason (is this set during a normal hardreset?) as all boottime commands are ignored.
The recovery fails improperly (sounds strange, but if it failed properly, you would end up in bootloader or your system).
-> That really looks like a brick...
Options:
- Warrenty
- JTAG
- perhaps someone else has another idea / sees something I missed...
Good luck with it.

Jignesh Sutar said:
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Click to expand...
Click to collapse
What where you flashing? It probably had a radio and something got copied incorrectly into the staging area of ram.. if the radio passes recovery's validation but not the current radios validation you can get stuck.. this shouldn't be possible but I've seen it before.. my bet is a bit error at the wrong point in time.

[Q] Urgent: Nexus failing to boot

Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.

Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.

Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!

Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.

Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!

Confirmed - Dude is giving you good info... xD

Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.

Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?

Use the FRG33 image

Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?

Try the passimg, but it's possible that you are looking at hardware failure...

ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.

Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.

According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?

None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.

Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.

If it's running, you can try to pull a log, and see what error reports you get?

andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.

So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?

Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks

[Q] Hard reset screen / reboot loop

Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."

picante544 said:
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
Click to expand...
Click to collapse
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.

A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
sphinxcs898 said:
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
Click to expand...
Click to collapse

picante544 said:
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
Click to expand...
Click to collapse
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
http://theunlockr.com/2012/10/16/how-to-root-the-htc-nexus-one/
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.

Resolved--hardware problem--trackball
Coincidentally, another user had a very similar experience with his N1 at the same time. He determined it was his trackball. I tore my phone apart, disconnected the trackball and the phone now works again.
Thanks again to those two people who responded.
sphinxcs898 said:
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Click to expand...
Click to collapse