Database Users

Nexus One "continuously reboots to "X" screen."

Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!

fastboot
just check for fastboot. the rest is easy cheeze.
how much is a good deal ?

unlocked $300 (cad)
What should I check? Instruct me plz, I never had a nexus one or even a Droid phone before ... (coming from 2 years old HTC cruise, with WM 6.5 with an XDA rom ....)
If I meet the guy, how to I check that hes not selling me a bricked nexus lol ?

Installing a new rom will fix it
Sent from my IPhone 4 using XDA App

Amritttt said:
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Click to expand...
Click to collapse
are you 100% ?
I dont mind working on it, I just want to make sure that it is reparable via software/roms.
ppl plz tell yours, im just about calling this guy, really dont wanna waste $300
what is its restarts so much, that I cant flash the rom or something? there's no way that that could be the case, right?

sold ... goddamit lol But I'll get one one way or another

I was having this happen to me a lot. I moved in to a new place with no cable or internet yet, so my N1 was under extremely heavy use. And when it was warm, it would get both the touch screen problem and the random reboots.
I was using pershoots 2.35 Kernal. I went back to the stock kernal and the phone has since been running a lot cooler. Zero reboots, touch screen responds correctly. I take the stock kernal stability over an OC kernal any day.

It's a kernel issue that can most likely be fixed by flashing a new
ROM/Kernel, however there is always a small chance that it is triggered by faulty hardware.

My Nexus had this Problem Was unfixable by software. Hardware defect. I wouldn't buy.
Still waiting for my swap unit

i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?

xxlikquidxx said:
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
Click to expand...
Click to collapse
all is not lost if you can still get into hboot:
Have you tried to restore these original files via adb?
boot boot.img
recovery.img
system.img

I have this problem now...
It keeps on rebooting and rebooting ... and just comes not forther than the flashing X..
I tried system wipe but this didnt help ( I installed a battery widget which wasn't for my rom)
how can i restore my nexus now?
Pleas help!
Edit: Found a way...
Unlock you phone, fastboot, clockworkmod(?) recovery and the select the nandroid backup...
about passimg (see lower) i have no clue

passimg FRG33...
Sent from my Nexus One using XDA App

Even though solved, something to keep in mind: Its probably a ROM (or kernel issue as they said), but I had a revolving X due to a bad battery too.

it can be solved
ViSK said:
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
Click to expand...
Click to collapse
4 color problem can be solved ..

my Nexus S just died on its own!

it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...

Good luck, man. I feel your pain.
Hope you don't have to resort to odin, but if you do, that safety net will have proved its utility.
Again good luck!
Sent from my Nexus S using XDA Premium App

I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.

AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
hey what is your "flashing" history? (i.e. roms, kernels, etc.)

serialtoon said:
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
Click to expand...
Click to collapse
Well, that's if Odin is used right, otherwise it can ruin the phone. I've used it to bring back my Vibrant a bunch. It's good knowing that these Galaxy S phones are nearly brick proof.

All is not lost, honest...
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
Hi AllGamer.
I had a similar disaster with the black google screen, and I had the unlocked bootloader as well, first I relocked bootloader, then used odin to reflash (http://forum.xda-developers.com/showthread.php?t=947950 ) then used the e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4 update (http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip) renamed it to update.zip, put it on root of memory, and ran it via the built in recovery mode after..phew.
Odin saved my life to!!
Good luck...

i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip

Yipee
AllGamer said:
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Click to expand...
Click to collapse
Glad your sorted....

N4 upgrade failed

Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA

Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?

If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.

BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...

As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?

Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?

Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...

Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium

Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4

TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...

Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.

tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.

NAE modem, multiple ROMS all same issue.

I've recently flashed NAE modem via Odin 3.09, also flashed Philz latest recovery. I was doing this so i could flash Rawintellects Stock(ish) ROM.... which seemed so badass. Really wish i could have got it working. Anyway, on to the problem.
Firmware flash went fine, Philz reovery went fine, ROM flash went fine. Now... I BELIEVE (can't remember) that i was coming from a MDL firmware, not sure though. After ROM flash, things were glitchy. No wifi (fixed after following suggestions in his thread. No 3g... fixed after a clean wipe 3X's and fresh ROM flash. And NO SOUND... never fixed. I spent half a day trying to get it right, never could.
So I decided to try another ROM, next was Negalites WondROM. Seemed cool, but had all the same issues. Exact same. Locking up, swipe screen locking up. System crashes, random reboots. NO SOUND. Figured, WTF.... tried another ROM same issues. At this point I thought maybe all these ROMS had the same kernal and that was the issue, so i flashed dif kernals compitable and recommended for dif ROMS. ALL SAME ISSUES. From here I figured it was the NAE modem the phone didn't like for whatever reason.
So now I'm stuck. I want to start over, want to flash MDL modem again, want to put the ROM i had back on here (I believe it was BluKuban or something). I am fairly certain there is now ay to take this phone back to the store and have them repair it, they will surely find something that will void the warranty even though im also fairly certain there is no warranty left on the phone. This phone is a business phone on our business account (one of 6 phones) and we've had buisiness with this sprint location for over a decade so i amy be able to persuade a repair.
Need help guys =(

Fixed
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:

ograyray said:
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
Click to expand...
Click to collapse
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.

tensux said:
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
Click to expand...
Click to collapse
Thanks, at that point I was happy to get anything to work, nothing lost really, just maybe 4 or 5 roms, a few GAPS packages, dealing with realizing I flashed a 4.4.3 image though.... And reading through everything looks like there is no root method available for 4.4.3 yet.... BUT HEY, got the phone functional and usable.

You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA

tensux said:
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
Click to expand...
Click to collapse
I like two things. 1. Phone works 2. 4.4.3 is fast and battery life is awesome so far. I do hate the bloatware and bright ass yellow splash screen on boot. But i believe i can stick with this until root for 4.4.3 is out.
Gonna miss my ROMs till then. Unless you can find root method for 4.4. It's out for S5 but not S4. I'd be shocked if i was wrong.

You should read up a bit... No reason you can't be rooted on 4.4.3
Sent from my SPH-L720 using XDA

My phone keeps rebooting over and over again.

When I first got my phone ((Without a simcard)) My phone rebooted like maybe twice in the 3 days. But ever since I put my simcard in ,after about 4 hours ish. I notice it rebooted and just after about 10 seconds or less it reboots again. It did it yesterday about 5 times in a row before I turned off my phone booted into recovery and cleared my cahce and dalvik, removed the sim, booted my phone and put the sim back in. No problems after that.
Then today morning It did it again rebooting back to back, removed the simcard out.
Does anyone know what is going on? Is it my simcard? I also have a case on, could that be? I can't rma cause I don't live in the states.

Adding on. It was my old phones simcard and hard to get cut. On android 6.1 running elementalx

Bump. I am thinking of going back to factory. What is the best way to do it? Using the one in settings or should I reflash googles stock image and unroot using nexus toolkit.

try a properly cut simcard. like one actually meant for the phone

Soulfly3 said:
try a properly cut simcard. like one actually meant for the phone
Click to expand...
Click to collapse
It doesn't look like it has anythin to do with the sim. I left my phone without the sim and it rebooted 2-3 times. Booted into safe mode and rebooted once.

do you have any crappy apps on the phone, or did u edit things while being rooted, that maybe you shouldnt have

Soulfly3 said:
do you have any crappy apps on the phone, or did u edit things while being rooted, that maybe you shouldnt have
Click to expand...
Click to collapse
I did change my governor options to something called ghostpepper settings from another thread, maybe its that? But like I said it all started happening yesterday. I have managed to get my bugreports. I could attach them.
Which method is best? Factory rest from the android settings or flashing stock image using nexus tool kit.

xringo said:
I did change my governor options to something called ghostpepper settings from another thread, maybe its that? But like I said it all started happening yesterday. I have managed to get my bugreports. I could attach them.
Which method is best? Factory rest from the android settings or flashing stock image using nexus tool kit.
Click to expand...
Click to collapse
I don't believe in toolkits, but feel free to use it.
I'd reflash the stock image, personally.

bump

You won't much support here for tool kits. They can cause trouble to begin with. Try flashing stock image and use Heisenberg's guide in doing so. If you successfully return to stock (not using a toolkit) and you still have issues I would say you have a hardware issue.