[Q] Nexus One Randomly Rebooting - Nexus One Q&A, Help & Troubleshooting

For the past few weeks, my phone has been randomly rebooting. I would say about 20 times a day. I cant nail down a pattern. Sometimes its while im using it, sometimes its while its idol. Here is what Ive tried so far:
Reinstalled Rom (different versions)
Reinstalled DT A2SD
Whiped Everything (dalvik, SD, and everything else).
Formatted SD card with Amon_RA's recovery.
New Battery
I've tried running a logcat, but this doesn't tell me anything. It just stops when it reboots.
The only thing I havent tried is purchasing a new SD card. I want to see if I have any other options before I do that. I feel like there is something i'm missing. Ive read something about formatting the SD card in windows, instead of in the phone. Are there any other things I can do to troubleshoot? Log's I can check?
Phone Details:
Nexus One
Amon_RA Recovery
CM7 Nightlies
16GB Class 10 SD
DT A2SD
EXT3 SD partition for apps & Dalvik
Thanks for any help that can be provided

It's a known hardware issue.
You have to send your device back to HTC for repair.

I've seen a few claims that similar problems are actually caused by a bad SIM. I've no idea how accurate this is, but it's easy enough to test...?

Related

SD card damaged with 4.0.3.1 but not 4.0.2

I'm getting a SD card damaged error after going from 4.0.2 to 4.0.3.1. The laptop reads the card fine so I know the card is ok. What's going on here?
Nandroiding back to 4.0.2 makes the problem go away.
Thanks for the info I had the same exact thing happen to me.
Did not think it was the rom but I knew there was no way all my microsd cards where messed up.
Weird thing the first one got somehow wiped to ext3 without me requesting it.
Going back to 3.8.1 let u know if got mine fixed or not.
Still tough might switch to jf again or other roms from haykuro.
Be right back as soon as I get home in 3hrs
I was getting this on one of Cyans roms before especially when unplugged from PC then restart and it would be fine. Haven't had any problems since so I'm sorry to say I don't know what it is, but at least it's not permanent haha.
Just tried 4.04 and same thing happens.
Changing the SD card seems to work but why is just THAT card affected? I'm going to back up the data on the card and try a few things. I'll let you know what happens.
sucks I had to start from scratch had to use a regenerator to fix the sdcard.
Basically phone nor pc would pick up past partitions. Used a corporate software from Paragon and Norton to undelete or try to recover deleted partitions. And now I was able to recover some of the files there are some that have a I/O read error so no luck with those kinda like a data redundency check failure.
Then used a regenerator to wipe the whole drive and recreate it. Wierd thing is that the droid did not read it until I reverted back to old cyanogen 3.8.1
now I'm back debating if to update to the newest 4.0.4 but scared now.
well I already lost most of the data what else can I lose right? lol
Im telling you it is a great investment to have Paragon Hard Disk Manager for business. At least that is what saved me this time.
Well for me. the ext3 partition works fine. All my app2sd works good. But my fat32 parition doesn't work (but works on other builds)
Well, it works now.
See whenever I mounted the SD card to Windows Vista, it said there was problems with the SD card and Windows wanted to scan it and fix errors. Well knowing the card worked fine, I always said no to the scan.
Well since I was having problems with 4.0.3.1 and 4.0.4 I decided to let Window scan and fix it, and it seemed to actually fix it. So there.
yeah i had the same issue also i thought it was cause i was trying to add an old theme to 4.03.1 but it wasnt...i did a wipe repaired the extfiles then added 4.02 again went straight to 4.03.1 through cm updater and it was fine..so if anyone has the same issues try to wipe first and see if that helps
Wipe did not fix problem.
I have the same problem. I tried a wipe through the recovery and with the
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
command. It still says the SD card is damaged. Restore with Nandroid, and everything is fine. I think I will try a fresh partition (I currently only have two partitions). I will try to get back after I reformat to get the three partitions.

Wierd Problems

Ok so I rooted my phone as well as partinoned my SD card (I have an 8 GB now) a while back and now I am having problems with my SD card. The other day my phone gave me a message saying that my Sd card was not supported and that I needed to format it. Stupid me I did that on my computer and wiped everything of of it. My friend who also has a rooted G1 got my phone to restore the CM but now everything is saving to my phone again. I tried to part it again and it says that nothing is found. Any ideas on what I did and what I can do to get everything back to the way it was when it was working correctly?
Also my phone started doing this other weird thing where I'm viewing anything and im scrolling through whatever the screen timesout eventhough I'm touching it. Anything to help with this aswell?
Thank you guys so much for the help!
I lost ya when you said you tried to part it again but nothing is found. Did you partition the card and no apps are found or you couldn't partition the card.
I tried to partition the card again but there was no data found and I couldn't partition it.
If you can't even partition it then you have a bad card brother. The strange behavior could be a symptom of the ext partition failing. I'm assuming you have a swap partition but don't actually use it with a user.conf file otherwise a failing card would cause your phone to completely freeze.

Can an SD Card be bad but not bad?

I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
robkoehler said:
I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
Click to expand...
Click to collapse
How did you partition your card?
using parted in console. I've re-done it several times as well.
So no matter what rom you flash your getting a bootloop. Do you have a nandroid?
I do. Using Amon_Ra's 1.2.3
On 2nd thought, do you mean a nandroid of a bootloop instance?
robkoehler said:
On 2nd thought, do you mean a nandroid of a bootloop instance?
Click to expand...
Click to collapse
Naw a nandroid of a rom that was working before you started flashing.
unfortunately no. i got partition crazy and removed the fat32 it was on right before i thought "did i back that up?"
With my old class 2, i've been able to get up and running on 4.1.999 and this king hero rom with no troubles.
Can a taco be bad but not bad? like, it tastes good, but it was made with bad ingredeints or a horrible chef.....
It sounds to me like your wiping after flashing.
You wipe data, Wipe ext, fix ext, flash rom.
If you wipe after flashing, or flash without wiping you will always get a boot loop.
The image doesnt run from your sd card, so the only thing that would cause the loop is the data on your phone.
Find a tested and working rom (i suggest either Mligns newest or Kings newest)
Go into recovery and turn on USB.
Move rom to sd card.
Wipe data
Wip EXT and fix
REBOOT INTO RECOVERY
then go to flash any ZIP (if you dont reboot, the rom file will not be seen correctly)
flash the rom
Fix ext again just in case
Reboot and leave the phone alone for a few mnutes.
EVERY phone is different. Some take 2 min some take 10-20 min
But if you have flashed properly, the best way to know is the shimmer on the HTC will continue to flow and not stop.
Sometimes it will fade, sometimes the noti bar will appear for 5 min then boot...
Just have patience and try.
EDIT- You typed while I was typing, It sounds like then maybe that card is bad then. If all works with older card, then the flash may be bad on the newer card. may want to return it unless you have other uses for it.
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
robkoehler said:
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
Click to expand...
Click to collapse
Possibly the upgrade from ext2 to ext3. Thats why I like to do mine in Ubuntu. Format the card using linux for a linux phone.
Decided to go a step further and go back to parted and resize fat32 and add a 500mb ext2. Rebooted and it fired up and shows the ext2 in the settings screen.
All that and it's not even Halloween yet. I'm going to try to flash 4.1.11.1 just to see if i can break it again
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
robkoehler said:
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
Click to expand...
Click to collapse
lol.....you give up quite easily.. those problems arent related to the sd card (they are on your /system partition)
try to reflash your rom and repair ext partitions then fix_permissions in recovery
hmmmm.....got card #2 and it appears to be the same case....boot loops. i can't believe that 2 sd cards would be bad only when it comes to apps2sd.
got adb running on my work pc and uploaded a log of the fail
again, everything boots just fine (just booted king's new 1.0) with my lexar class 2
updated logcat - 1st one was when i couldn't get off of the g1 screen.
this logcat is of the bootloop. any help would be great

Stuck in bootloops, not sure what to do

I recently tried to flash Fresh Toast 2.1 and after 15+minutes my phone was stuck in a bootloop. I rebooted to recovery and deleted all the data and cache. Now no matter what ROM i try to flash it just keeps booting over and over. Anyone have any ideas? I was using apps2sd and completely formatted the sdcard, would this have affected anything? Also tried nandroid back up, but says "No files found" when I try to do so. Also when i try to format the sd:ext i get an error mounting sd:ext
In recovery try and format your sdcard with only a fat32 partition. Then try and enable ?MS-USB? and copy a ROM to your sdcard.Wipe data and dalvik and then flash ROM.
If that doesn't work try replacing your sdcard with another one.
Or you can push your ROM.zip to the sdcad through adb without mounting the sdcard
A2SD will only work if your sdcard is partition with EXT and swap. So if you don't have it partitioned then apps will install on your phone.
I gave it a shot but no luck, i am using the clockworkmod recovery 1.8.1.4.
I had the same issue happen the other day after a wipe and reinstalled rom... I have the same clock work mod you have also... what I noticed was that my phone only did that when I had the sd card in but once I removed it (after several hours of flipping out over it!) it booted fully.. but every time in reinserted the card, it rebooted.. so what I did was used paragon partition manager to create 3 partitions on the sdcard (i have an 8gb card) and made 2 Linux ext2 partition of 258mb or something close to it and the remaining was formatted at Fat32.. after I did this, I re-flashed my rom and everything has been working fine ever since... it may have been some corrupted files in the 2 Linux partition or something because I was running all my apps from the sd card and I had noticed the other day that every time I connected my hero to my laptop via usb, and launched pdanet, my phone rebooted...EVERYTIME.. and this is what led me down this road... If I made any mistakes here, I'm sure someone will correct me, as this is my first post...
27midwest1 said:
I had the same issue happen the other day after a wipe and reinstalled rom... I have the same clock work mod you have also... what I noticed was that my phone only did that when I had the sd card in but once I removed it (after several hours of flipping out over it!) it booted fully.. but every time in reinserted the card, it rebooted.. so what I did was used paragon partition manager to create 3 partitions on the sdcard (i have an 8gb card) and made 2 Linux ext2 partition of 258mb or something close to it and the remaining was formatted at Fat32.. after I did this, I re-flashed my rom and everything has been working fine ever since... it may have been some corrupted files in the 2 Linux partition or something because I was running all my apps from the sd card and I had noticed the other day that every time I connected my hero to my laptop via usb, and launched pdanet, my phone rebooted...EVERYTIME.. and this is what led me down this road... If I made any mistakes here, I'm sure someone will correct me, as this is my first post...
Click to expand...
Click to collapse
Would you mind posting the steps to do that? Im pretty computer savvy but I need some steps to go from. Would I be better off picking up a new SD?
pulled the SD and it booted, thank god lol. Thanks for your help guys!
no problem... glad I could help.. as for the new sd card, you could very well just get another, but I managed to keep the one that I had but just reformatting it and re-flashing my rom (Damage Control v2.08.1) and it's been working fine since then..

[Q] Does my N1 have a RAM defect?

Up until a few weeks ago, my N1 worked fine. Rooted, CM7.
Then I got lots of FCs and decided to re-flash CM7.
It worked fine for a week or so until last night. It was fine before I fell asleep but dead next morning.
I can VOL.DN + POWER on and switch between FASTBOOT and BOOTLOADER/HBOOT
I can boot into ClockworkMod recovery.
Booting CM7 presents coloured X; then a blank screen (it may be off) and sometimes I get softkeys lit or flash once. Usually N1 vibrates slightly every 5 seconds or so. Only way out of this is to remove battery.
I have a very recent backup. but it or any of it's img files have MD5 errors.
So, either this image is bad, or perhaps I have a RAM error that also prevents phone booting?
Is there a log file I could look at (I can connect using adb)?
Is there a way to test RAM? Is there a PASSDIAG.ZIP or PASSDIAG.NBH image I could try?
I also tried re-flashing CM7 - no change.
Any other ideas?
Did you try to use another SD card to use in your device? It could be a SD card failure and is easier to fix than a RAM failure. I also remember reading in other threads that a SIM failure could make reboots and freezes in these devices
I had a similar problem in my Nexus One with the original ROM, but in my case I think that the failure was in some corrupted file in the system partition.
Doubt SD card nor SIM is issue
Same defect when SD card and/or SIM removed (except I can not attempt a restore with SD card removed).
So I don't think either is at fault.
SD card mounts fine when USB connected to a linux laptop under FASTBOOT (I think I did this) or RECOVERY.
Mine have a like problem, i only do a full wipe and start without SD and it worked

Categories

Resources