Related
i have to have the worst luck in the world..
got my nexus one today. condition is MINT. seller also included the receipt from HTC proving that it got replaced.
popped in my sim, everything worked fine. turned it off to swap batteries and thats when the hell started.
im not able to get past the nexus logo. NOTHING. it would turn on, than go to the screen, vibrate, than repeat multiple times. phone has never been rooted.
i did EVERYTHING. i did the volume down plus power and than i cleared wiped the memory, same result.
than i tried downloading 2.2.1, renaming it to update.zip, put it on my zip, but that doesnt work. the phone can't tell theres a update.
like **** man. i than went here
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
read that i needed FRG33 and rename it to PASSIMG.ZIP. when the phone turns on, it gives me the message if i want to update, i get excited. i click yes, everything says ok, than i reboot and bam, still endless reboot. tried to do the passimg again but this time i get a fail on radio V2 or something like that.
WTF is going on. i didnt do anything. ANYBODY HELP?
maybe the battery you swapped in is bad?
same result with both batteries :/
i hate my effing luck.
Make sure your batteries are fully charged, seriously.
great, now when i click recovery, it doesnt even go to the android guy with the exclamation mark, it just gets stuck at the logo. all im able to do is get to hboot. WTF.
i mean the battery has half a charge. just checked with my desire. i even tried with it plugged in in the wall. nothing.
my aim is screwupboy444. your welcome to help me there or even laugh at me for being a bone head and getting in this situation.
Do you have a different SD card you can use?
Sent from my Nexus One using XDA App
yeah, i was using both the desire 8gb and the nexus one 4gb. both were reading fine in the desire. i read that if it gets to the nexus one logo then my phone isn't bricked, but im starting to think otherwise. nothing works.
ive been searching for the past hour half. everyone seemed to have fixed there by doing the passimg method or wiping data. but unfortunately none of that is working. i tried placing the froyo "update.zip" and running it but when i clicked recovery, it went into the boot cycle again.
http://forum.xda-developers.com/showthread.php?t=614850
thinking about doing that but i have a feeling it doesnt apply to me. that and i don't understand any of the process. i dont think my phone will even be read by my comp.
did the passimg for the third time. went past the logo and actually to the set up screen. than it rebooted again. and now its stuck on the nexus one logo again.
could it actually be that? i left the battery charging in the desire for about 40 minutes, than took it out and put it in the nexus one and actually got to the set up screen for the first time.
but my question is, if thats the solution, does that mean my phone is gonna trip out everytime its less than 60 percent battery power?
this is what i get when i put the 2.2.1 update on my sd card and go into recovery mode
Uploaded with ImageShack.us
most of the threads where people got this fixed required them unlocking the bootloader and doing something. im the second owner of the phone but would like to avoid rooting but if its required in this situation, i will. i just need a dummies guide to do it..
No, there's threads for recalibrating the battery, if needed.
Keep it fully charged, and see if it will run for a reasonable period... That way, we can see if it really is the battery...
Sent from my Nexus One using XDA App
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
frick, i know thats what i should do. it just blows that i got this today and theres already a chance that its trashed...
danger-rat said:
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
thanks for all the help man. you dont think i need to unlock the bootloader right...? im just more curious on why the desire can work with either party no matter the charge. damn.
Wait until your battery is about 75% or more would be better, then try the passimg again...
Sent from my Nexus One using XDA App
not sure if its good news or not but (i apologize for my lack of patient before hand haha), i took out the battery the desire was charging again and put it in the nexus one. it got to the set up screen all three times before it resets again. i tried plugging it in the wall charger but it still resets at that area.
edit:
the battery level was at 74% when i tried it.
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
danger-rat said:
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
oh iam. im charging the nexus one battery in the desire because once i turn on the nexus one, it gets frozen there, and than i cant turn it off.
I recently installed Cyanogen on the girlfriends Wildfire, I am using the 'stock' kernel with the ROM, however from time to time she was getting random restarts and the screen was turning a yellowish green colour, only a reboot would solve the issue. I moved SetCPU back to stock clocks (It was only at ~610Mhz overclock) however the problem persists.
I've literally just changed to HCDR.Kernel v4.1 and on first reboot I've gotten the yellow screen. Does anyone know what could be causing this issue? The phone was absolutely fine before installing Cyanogen, and I don't really want to keep messing about with her phone flashing from ROM to ROM, it was hard enough to convince her that an AOSP ROM would be better than stock!
I've had a quick search and I can only see one instance of this happening and it's a two post thread , which is of no help to me, any light anyone could shed on the issue would be greatly appreciated.
Do not set your cpu min. Value too low. Keep it above 250mhz
Sent from my HTC Wildfire using XDA App
Profiler08 said:
Do not set your cpu min. Value too low. Keep it above 250mhz
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
As on all of my Android phones I keep it at 250Mhz for the lowest value.
I have a non-rooted stock NS on 2.3.3 and the phone was just sitting on my desk doing nothing when I felt it vibrate. I picked it up to check for a text or email, but the phone was instead rebooting.
Has this happened to anyone else on this build? I have had the phone reboot while in call before, but never just sitting there in standby.
This happens to me in 2.3.2. I will have the phone just sitting there and it will randomly just be rebooting. Its not frequently enough to bother me yet but it happens on and off.
Sent from my Nexus S using XDA Premium App
same here on 2.3.2.... thats why I wanted 2.3.3. Ill wait patiently for the nightlies to include it.
happened to me many many times on 2.3.2, but not 2.3.3. knock on wood
Happened to me...2 times already...never on 2.3.2...im rooted though
Sent from my Nexus S using XDA App
This happened to me like 2x a day with 2.3.2.
Hasnt happened once yet with 2.3.3.
I never got reboots in-call, though I did get them a couple times when I overloaded the phone's RAM.
Mine just rebooted in 2.3.3. I'm also getting "Can't connect to camera" anytime I use the Amazon barcode app which worked perfectly in 2.3.2.
Haven't tried the new update yet
Sent from my Nexus S using XDA App
I never had the in call rebooting, just overloading reboots on my nexus s. I have yet to have one since the update, but it has only been a little over 24 hours. Then again this has been happening to me since updating my nexus one be it stock, rooted, or CM6 FRF91 and FRG83D or any form of gingerbread I've used on it. The only thing I can say it it started in froyo for me.
Sent from my Nexus S using XDA App
on the new update havent had any issues.
I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App
MacGuy2006 said:
I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .
He's not rooted dude. Btw I get a reboot on every call. On cm nightly, no matter what I try/flash
Sent from my Nexus S using XDA Premium App
I just had reboot one time with 2.3.3 but I was running all processes 72 hours, without stopping and it suffered a lot !!!
deeren said:
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .
Click to expand...
Click to collapse
Nope.
It happens to 2 Nexus S, both stock, not even rooted. One barely has additional apps, too.
I think a lot of people don't notice the reboot, because it is silent, so if you are not looking at your phone exactly at the particular time it reboots, you wouldn't know it.
The inability to dial at times is much more annoying, IMO: you punch in a number, the phone tries to dial, then hangs up. At the same time, there are 3-4 signal bars. When it happens, it normally takes several tries to get it to work.
The crashing camera also doesn't happen every time, but it is definitely a new bug in 2.3.3.
Just had my first random reboot on 2.3.3 while phone was sat on my keyboard while at my PC.
Rooted detoxed Rom stock
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
This dim reboot screen thing used to happen quite a bit on my g2 in its early days, got it launch day. OTA fixed it.
Sent from my Nexus S using Tapatalk
fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
I am still hopeful, but I am losing some patience with Android.
The platform seems to be all about selling the newest hardware, but the user experience is definitely below that of the iPhone. I keep hoping that the next Android OS upgrade will close the gap, but....
The iPhone 5 will have 4" screen, with Apple's better screen aspect ratio. If it only did Flash....
Anyway, the Nexus S is really the best user experience Android has to offer, and it's overall fine. Except when it acts like WM6.
That random occurrence where my phone sits on the White Screen longer than I expect it too after a reboot, and just as I reach to pull the battery, after waiting longer than I think I should, the boot animation comes on...
HipKat said:
That random occurrence where my phone sits on the White Screen longer than I expect it too after a reboot, and just as I reach to pull the battery, after waiting longer than I think I should, the boot animation comes on...
Click to expand...
Click to collapse
This has happened to me many times lol
Sent from my PC36100 using XDA App
This happens to me e v e r y single time after flashing a new ROM. It freaks me out I gots to admit.
Sent from my PC36100
Almost like a proximity sensor or a live droid inside... just waiting
The first time I flashed a Rom I sat there patiently waiting for what seemed to be an eternity and every time since it hasn't got much easier. Lol
Sent from my PC36100 using XDA App
Sometimes, I toss my phone into a random drawer, shut it and walk away so I don't sit and stare.
Sent from my PC36100 using XDA App
I got freaked out yesterday. Here's what happened. I had icsp3 installed on my phone but I was in miui from my SD. (Boot manager). So I tried to boot back into ics and it instantly went to hboot, and not the hboot I'm used to seeing. This didn't have the option for recovery. I would hit reboot and it would go black for about half a sec and then right back into hboot. I was like oh s*it! So I pulled the battery and booted into hboot then recovery and all was good. Still don't know what happened but I thought I was eff'd for sure.
That's why when I flash a ROM I cunnect it to the USB, type "adb logcat" and sit and watch what it's doing.
No longer do I wonder if it's locked up... I see it going through all its processes before it gets around to updating the screen... real stress reliever.
pfft...
Come talk to me when you've made your own connection prong for the WiFi antenna and soldered that to the Evo board... then the ever so wonderful post-"in pieces" boot up.
btw - WiFi works well now!
erulai said:
pfft...
Come talk to me when you've made your own connection prong for the WiFi antenna and soldered that to the Evo board... then the ever so wonderful post-"in pieces" boot up.
btw - WiFi works well now!
Click to expand...
Click to collapse
I know what ya mean, it freaks me out every time I have to do that.
mildlydisturbed said:
That's why when I flash a ROM I cunnect it to the USB, type "adb logcat" and sit and watch what it's doing.
No longer do I wonder if it's locked up... I see it going through all its processes before it gets around to updating the screen... real stress reliever.
Click to expand...
Click to collapse
Ahh, good plan. I always have mine plugged in, too, when I flash a ROM, just to keep the battery charging while booting
Ahaha! I get scared deleting things from Titanium Backup! Lol scarred myself for life when I was on r3chargeD I accidentally deleted some app/s (still don't know what I deleted) and I rebooted and it never came back lol I had to reinstall the ROM fresh lol
TrevE Supporter!
I got the phone just 3 days ago from an insurance claim, had no problems with it other than the power button is a pain sometimes.
I rooted the phone yesterday with visionary at first, then gfree after i got the s-off, and I have the CWM 5.8 touch recovery. I then flashed Virtuous Unity 2.39 and the Darkside v12 kernel, as well as all sorts of different radio's. I then fell asleep after installing those, and before setting up the ROM, and i left it charging on my computer overnight.
I woke up about 5 hours later, and the phone was at 4% battery life. I dont know what happened. i can get it to about 2% charge and then it stops and dies out. i did notice that the clock on the status bar froze at one point and said 11:40 when it was really 12:27. the clock widget on the main screen was correct the whole time.
I am able to get into recovery, I am able to get into fastboot, I am able to get into the ROM...
I have switched out the radio to different one than the one last night, and i have switched the kernel to "CollectiveACE-BFS-v0.1.5" and that doesnt solve the issue. I have also cleared the battery stats, even though i didn't want to since it was at such a low level of power...none of these things helped.
I have also noticed that after the phone shuts off, when i power it back on, it goes into recovery. I am unsure why, but when I tell it to reboot from recovery, it goes right back to recovery, and i have to pull my battery to get it to go to the OS.
Any idea's? and I am sorry if this is confusing...
Try flashing a new ROM. But before you do, flash Mike1986's superwipe script from here: http://dl.dropbox.com/u/61962340/Android_Revolution_HD_Super_Wipe.zip , just to make sure everything is fully clean . Then flash your ROM of choice. Also, never flash radios for the heck of it. They can easily brick your device. Be careful, and report back
RUMyBruncle said:
I got the phone just 3 days ago from an insurance claim, had no problems with it other than the power button is a pain sometimes.
I rooted the phone yesterday with visionary at first, then gfree after i got the s-off, and I have the CWM 5.8 touch recovery. I then flashed Virtuous Unity 2.39 and the Darkside v12 kernel, as well as all sorts of different radio's. I then fell asleep after installing those, and before setting up the ROM, and i left it charging on my computer overnight.
I woke up about 5 hours later, and the phone was at 4% battery life. I dont know what happened. i can get it to about 2% charge and then it stops and dies out. i did notice that the clock on the status bar froze at one point and said 11:40 when it was really 12:27. the clock widget on the main screen was correct the whole time.
I am able to get into recovery, I am able to get into fastboot, I am able to get into the ROM...
I have switched out the radio to different one than the one last night, and i have switched the kernel to "CollectiveACE-BFS-v0.1.5" and that doesnt solve the issue. I have also cleared the battery stats, even though i didn't want to since it was at such a low level of power...none of these things helped.
I have also noticed that after the phone shuts off, when i power it back on, it goes into recovery. I am unsure why, but when I tell it to reboot from recovery, it goes right back to recovery, and i have to pull my battery to get it to go to the OS.
Any idea's? and I am sorry if this is confusing...
Click to expand...
Click to collapse
Stop flashing aosp kernels on your SENSE rom... Try darkside sense v7 or one of the unity kernels and all should be fine.
Sent from my HTC Glacier using xda premium
I have installed Icecreaminsanity 7.1 AOKP fixed or whatever the name of it is. I did not know the kernels were different depending on AOSP and Sense. If i have ICS on it now, which kernel should I use since there are no ICS kernels for the glacier?
I dont know if the charging issue is fixed yet, because i just did the superwipe and put on the ICS ROM. I will post if it is fixed or not, but my hopes are low
edit: Sorry, it is IceColdInsomnia 7.1.AOKP-test.
WOW i love this ROM...but i digress...its still too early to tell if it's going to fix the charging issue. I did notice that when the screen was on and i was going through the launcher, it didnt interrupt me telling me my battery was only at 3%...maybe that's a good sign.
No, it didnt fix the issue. While leaving the screen off and plugged into the wall, the charge dropped to 2%, and now it's blinking between the green and orange LED's...what do I do now??? Any recommended kernels for this rom? would an AOSP kernel be better than a Sense kernel for this new ROM?
Edit: I am already using the kernel mentioned by the OP in the thread for that ROM...the Collectives ACE kernel.
Get an external battery charger or find a friend with a glacier or t-bolt and charge the battery. Flash PD15IMG.zip and start over. If it still doesn't charge tell them they sent you a busted device, raise some hell, and see what you can get.
Sent from my HTC Glacier using XDA
i think that may be my only option. I appreciate your guys' help. it was really nice to see people giving actual advice with links instead of just telling me im in idiot and telling me to search for it.
Haha, well some of us are trying. Also, you didn't post in the dev section, so that's an automatic plus.
Don't forget to get S-On if you have to send it back.
estallings15 said:
Haha, well some of us are trying. Also, you didn't post in the dev section, so that's an automatic plus.
Don't forget to get S-On if you have to send it back.
Click to expand...
Click to collapse
Haha yeah, props to OP!
i'm no noob to this forum or to rooting...but i am to the MT4G...lol it's a completely different beast than the MT3G i came from. Thanks again, and i guess a mod can close this thread out...