Database Develop

Nexus One boot loop issues

Hi everyone,
I have a problematic Nexus One. I've googled the issue and read all the corresponding threads and none of them seem to have boot loop issues as bad as mine. At least I dont think so, anyway.
Where should I start? I recently bought the phone off ebay. The seller did clearly state the phone's issues and that he couldn't be bothered fixing it, let alone paying over $200 to send it back to Google to be repaired or replaced (from Australia). Call me a sucker for punishment, but I do like dabbling in electronics so I thought I'd give this a go and hopefully will be successful. It wouldn't bother me if it rebooted once every few days then rebooted again normally but this isn't the case. I'll try to describe it's behaviour as precisely as I an and I sincerely hope the collective expertise on this forum will be able to help me successfully resolve this issue. BTW, I've been using a gorgeous Desire since July.
The Nexus one is running Modaco r21, 4.06.00.12_7 radio, 2.6.32.9 kernel, CMR 2.5.1.0.
1. When the phone has been powered down for at least 5 mins, it will power up as normal. If left alone on the bench or very lightly used ie a few minutes, then pwr button sleep, no problem. If I continue 'sleeping' the phone every few minutes while using it it continues to function normally for a few hours. If I don't 'sleep' the phone and use it continuously, then after about 20 mins it goes into a reboot cycle with the static 'X' going on and off every few seconds then ending up with the continuously on "X" with the unlocked padlock underneath, which is unrecoverable until the battery is pulled.
2. Battery reinserted immediately after removal and the reboot cycle continues. I can boot into the white Recovery or Fastboot sreens but when I select an action like Recovery, the boot loops starts again. Battery pulled and reinserted again, boot loop occurs again. Pull battery and leave it out or powered down with battery inserted for 5 mins, reboots normally. Then point '1' above continues.
3. I have Rom Manager, Titanium and Superuser Permissions installed. I received the phone with Eclair installed and after many attempts managed to install the new radio and Modaco R21. Last night I tried doing a back up via Rom Manager since I cant get into the black Recovery screen and now Titanium and SU are force closing.
This is all I can think of right now and will update with more info as they come to light. I've been trying to install setcpu to see if underclocking will help however I have been unsuccessful due to SU force closing. I am an Android and Linux noob but am always willing to learn. I really would like to get more stability in this phone so I can either use it as my primary or back up.
Thanks in advance for all your help.
Edit. I magaed to do a factory reset when it dont momentarily allow me into Recovery mode. Wiped all data and davlic as well.

My first instinct is that the phone has suffered or is suffering from a heat problem of some type.
Do you have the android SDK set up on your computer? You should be able to flash an aftermarket recovery using the "fastboot flash" commands. You could also use the "adb reboot recovery" command to reboot the phone directly into recovery mode.

I'll give your suggestions a try. What fastboot commands should I be entering? I am an absolute virgin with all this.
Sent from my HTC Desire using XDA App

I think this thread should have some good information for you

Thanks for the link, mate. I'll have a read and I'm sure there'll be more Q's soon.
Sent from my HTC Desire using XDA App

Hi again,
I've installed Android SDK and usb drivers. Where do I go from there? I am a complete newbie at this so please be kind.

julian.kueh i was posting to ask how things have been progressing along this matter?

I got the same problem. No matter what I do, I can get into Recovery. It stay in loop with X
I change twice recover and nothing.

[Q] Odd graphical glitches/wont boot after flashing CM10.2

Hey guys, I've been working on this all day, finally got cm10.2 and gapps installed. I was in stuck booting into TWRP, but then sideloaded cm10.2 and gapps, I thought I was finally done... then when it loads up it has the orange kindle Fire logo, then has a brief "noise" sort of affect on part of the screen, then after that it just has a vertical sort of flashing line of blue down the center. Anyone have any idea whats going on? I've been doing some research and I cant find anything about that... if there is already an established issue and thread, please point me there, but otherwise...anyone know whats going on? I'd really rather not have to get the factory cable, mainly just because of the shipping time, but can if thats needed.
EDIT 1: It wont actually do anything when its stuck after the kindle fire logo, its just black w/ the line. Lately it hasnt even been displaying the blue line (more like whatever color it feels like though). I cant use either ADB or fastboot commands using KF First Aid either.
EDIT 2: Just realized I forgot to say some important info, sorry. I have a KFHD7". I followed some XDA tutorials and only really had trouble right after I sideloaded my CM10.2 rom, and thats the problem I'm having right now.
EDIT 3: I did some more testing. I think I sort of got into fastboot mode, but no "Fastboot" logo like I'm used to. I have the kindle off and unplugged,then tried fastboot -i 0x1949 getvar product, and got "Bowser-04". From what I can see, there is really nothing on Google about this so I'm assuming thats not supposed to be there. I tried to take this one step further and flash the right TWRP recovery 2.6, but it just hangs on <waiting for device>. So it seems like it is ALMOST there...but not.
FINAL EDIT: Fixed. For anyone else having this problem, I used the little bit of actual fastboot mode I had to give the fastboot command to load into fastboot (reboot-bootloader) and then it would load me into actual fastboot w/ the "Fastboot" logo on the screen, but that would only last a couple of seconds. I was then able to use the http://forum.xda-developers.com/showthread.php?t=1951254 and restored img/boot/etc, then installed stock recovery and cleared data/cache. Now it actually loaded up and I have a normal kindle again! I'm going to reinstall the RIGHT stuff and not have this happen again now.

[notice] please read!!!

They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.

I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?

U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk

Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.

rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
I've heard it called a "sponge" I like that lol

shard111 said:
I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?
Click to expand...
Click to collapse
coldconfession13 said:
U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
i flashed each file separately yes no errors when flashing everything went through okay but still wont pass google screen

If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk

coldconfession13 said:
If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no.
but after flashing the factory img, you might have to wipe data for it to boot.

jeromechrome1 said:
They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
Click to expand...
Click to collapse
NONE of this suggests that your phone is a brick. In fact, it all proves that it is NOT a brick.
*which is not to say that it isn't BROKEN.
"i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C"
Let me ask you this; did it reboot when you booted into a custom recovery? If custom recovery worked, then it seems like the unit can still be saved.
BTW: LRX22C is also 5.0. Specifically, 5.0.1. 5.1 is not available yet.
So a little bit of clarifications first;
HAVE you tried to perform a factory wipe (via recovery) or otherwise FORMAT (not "fastboot erase") the data and cache partitions? No part of your message mentions formatting the data or cache partitions. If the init is unable to manipulate/mount a possibly corrupt data or cache partition (or possibly some other partitions as well), then it WILL REBOOT.
In addition, some logs of the reboot could be useful if you are able to obtain any. A somewhat modified boot image can enable adb and kernel logging at a point from before the reboot occurs.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I don't think you need a new mainboard.
If what he explained to you is correct, then my previous about fixing corrupt data partitions should solve the issue for you.

Agree with the guy above me. Same thing happened to me on my Nexus 9. Manual flashes all successful but could not boot. Booted into recovery and did a factory wipe and all was well. I know this is the nexus 6, but it sounds like corrupted data.

Bricked my Amazon fire 5th gen

Hey guys, after successfully changing my OS to cyanogenmod I wanted to do the same on a second amazon fire 5th gen I had laying around. So I rooted it, installed the google apps, downloaded Flashfire from the google play store, but when I used flashfire to flash the most recent CM12.1 from the XDA thread it kept saying that the data was incompatible or something. So I tried doing a factory reset and tried again, but the same thing kept occurring. After that I thought I would try installing the SlimLP mod instead, and it worked. Once I got SlimLP up and running I downloaded Flashfire again, and went to go install CM12.1 once again, but this time it got stuck at the very beginning. It didn't even look like it was writing any data or anything. The whole process only took about a minute on my other amazon fire, so I knew something was wrong. I waited 15-30 mins and no change. Eventually I turned it off, and rebooted, hoping for the best. Unfortunately, it loads the CM boot logo, and just gets stuck their permanently. I tried going into boot recovery by holding down volume down, and the power button, but when I do that it gets stuck at the amazon boot logo. I can still get it to boot into fastboot by holding down the volume up and power button, but when I try to flash a recovery image using fastboot it says that Flashing images is locked, or something.
Can someone tell me if there is still anyway to save it?

This will work
Hi
So i have the same tablet as you do and i faced the same problem as well and i found a way to fix it and this is what i did-
1) I went to recovery mode ( Power button and volume up button at same time) and factory reset and cleared data.
2) Wipe cache patition
3) Then I used this tutorial so i can go back to original state
4) Once there, I rooted my tablet again and download google play store and blahh balhh
5) Then I downloaded flashfire apk
6) This time i didn't download latest CM 12.1 for the tablet but this one ( cm-12.1-20151230-R01-UNOFFICIAL-ford.zip )
7) And gapps
8) I flashed and it worked beautifully.
9) Once done then I flashed the latest version CM 12.1 for the tablet and it worked amazingly . Sorry for not providing the links because i am new and i still have to wait a bit longer Thanks for reading this and i can guarantee 99.9% this work. Don't forget to tell me what happened.

Yeah, but like I said, the device freezes before it can get into recovery mode. I can only get into fastboot, but I don't think there is anything I can do with that.

speaker1264 said:
Yeah, but like I said, the device freezes before it can get into recovery mode. I can only get into fastboot, but I don't think there is anything I can do with that.
Click to expand...
Click to collapse
Return it to Amazon. I rang them and basically claimed ignorance that the device had stopped working, they sent me another one (and I returned the 'bricked' one). Luckily the replacement one came with 5.0.1 so I carefully made sure I did not upgrade before replacing the ROM instance with CM12.1.

jeromeof said:
Return it to Amazon. I rang them and basically claimed ignorance that the device had stopped working, they sent me another one (and I returned the 'bricked' one). Luckily the replacement one came with 5.0.1 so I carefully made sure I did not upgrade before replacing the ROM instance with CM12.1.
Click to expand...
Click to collapse
exactly the same thing happened to me as in the op. there is absolutely no way to fix it with the bootloader being locked down. i filed a replacement, telling them that after i installed a program it no longer goes past the boot screen. (i call that a grey area as far as lies go). go through their little trouble shooting performance where they ask if the device is charged.... then they will replace the device as long as it is in the warranty period. drop the old one off at ups, and 2 days later you will get the new one in the mail.

Kindle Fire, rapid boot loop, can anyone help?

(Keep in mind all of this is happening without a OS on it after the sentence where i decied to format) New to the forums and still noobish at flashing roms and the like. But here is my delima, I had a kindle fire HD that i got years ago and flashed properly with the 2nd boot loader, TWRP ( I think at the time the version was like 2.7.0.0), and Pac-Rom, well wanting to try the Cyanogenmod and other roms, being a complete idiot I decided that I would format the device completely and flash a new rom and gapps because I have just had more success flashing that way. Anyway, I finish and was looking at roms on XDA and noticed that TWRP finially got updated to 3.0 so I assumed that I would finially get mass storage support over usb, like a flash drive. well that didn't end up working still, oh well no biggie i have used ADB a few times to push some roms over. So I find out ADB had a message to the extent of when I did the ADB devices command , the device was unauthorized. So I thought crap something must have gone wrong when I was updating to the new version, so ended up fastbooting into a version of TWRP 2.8.something, and that worked but my device was still unauthorized, so restarted, and now its in some odd boot loop, like the kindle fire logo will only stay up for a few seconds then shut down immediately, and just keep repeating like that, the blue logo won't show up and I cant boot into fastboot or into TWRP.
Does anyone know what went wrong or how to fix it. Huge thanks if you can!