Database Develop

[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] Another boot loop, but this one is different! SOLVED

C6603 Stuck in bootloop! [Last update: 24/1/14]​
UPDATE 24/01/14
This issue has been SOLVED.
I replaced the battery with one from eBay and the phone is working flawlessly, all the ROM flashing I went through was not the problem at all. Remember that if you are going to try to replace the battery you may as well buy a new rear glass piece as it is almost guaranteed that the glass will break in the removal process. You will also require new a adhesive piece. The entire procedure cost me $51AUD (battery, glass, adhesive).
All the content below is irrelevant, if your phone randomly shuts off (instantaneously) on boot or soon after, try to replace your battery!
Thanks for your help.
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
UPDATE 01/01/14
Currently I have a kernel installed that allows me to use cwm twrp (doomkernel v19, maybe), I have flashed a 'flashable' stock 4.3 rom using cwm and the phone didn't manage to get past the kernel logo. HOWEVER, using fastboot mode, I run the command "fastboot continue", and if I allow the phone to go past the kernel logo it vibrates, the LED turns green as opposed to showing a purple one, and it will begin charging (The LED isn't green as a result of the battery level). EDIT [1/1/14 3:01AM]: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
I must mention, I cannot get into recovery unless I boot the phone into fastboot mode, run the command in fastboot: "fastboot continue". If I don't do this, it simply crashes (shuts off) when showing the kernel logo.
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
UPDATE 08/01/14
I've come to the conclusion that my issue is battery related. After repeated from flashes and fastboot attempts, I managed to get the phone charging a few times, I witnessed the level was sporadic upon infrequent viewings. I have come across a few other very similar threads and feel that it is necessary to try replacing the battery, I try and post a youtube clip that details what happens currently.
Keringkien

keringkien said:
C6603 Stuck in bootloop!​
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
Keringkien
Click to expand...
Click to collapse
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader

elias234 said:
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
Click to expand...
Click to collapse
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.

keringkien said:
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
Click to expand...
Click to collapse
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)

Jambu95 said:
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Click to expand...
Click to collapse
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.

keringkien said:
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
Click to expand...
Click to collapse
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.

I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|

Jambu95 said:
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
Click to expand...
Click to collapse
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.

keringkien said:
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
Click to expand...
Click to collapse
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
billhainh said:
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Click to expand...
Click to collapse
look for the disaster recovery thread i posted above

Jambu95 said:
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
Click to expand...
Click to collapse
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.

keringkien said:
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
Click to expand...
Click to collapse
this problem occurs with every kernel you've used (including stock and custom kernels)?

Jambu95 said:
this problem occurs with every kernel you've used (including stock and custom kernels)?
Click to expand...
Click to collapse
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).

keringkien said:
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
Click to expand...
Click to collapse
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.

Jambu95 said:
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Click to expand...
Click to collapse
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.

keringkien said:
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
Click to expand...
Click to collapse
the device can't get pass the sony logo?

edNHour consum
Jambu95 said:
the device can't get pass the sony logo?
Click to expand...
Click to collapse
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.

keringkien said:
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
Click to expand...
Click to collapse
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.

Jambu95 said:
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Click to expand...
Click to collapse
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.

keringkien said:
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
Click to expand...
Click to collapse
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,

Jambu95 said:
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Click to expand...
Click to collapse
I imagine it is still under warranty, however I have read that unlocking the bootloader permanently voids warranty. And I have replaced the back of my white phone with a black glass, perhaps if I get a new white rear glass it will be ok, but then I might as well just replace the battery $40AUD isn't too expensive IMO.

[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.

[Q] Nexus 6 Infinite boot animation

I attempted to OTA update my stock Nexus 6 to 5.1 last night, setting it aside to do its thing and went to bed. When I turned the phone on this morning it went into the boot animation which just goes on indefinitely. I have attempted to clear the cache which did nothing. I was wondering if there is a work around without having to wipe the phone and thus lose all my data.

I have seen the first boot take up to 20 minutes you didn't turn off before then did you?
Sent from my Google N6 on VZ

No I left it in my pocket on my commute to work and tried to restart the phone over 2 hours later

Andrew_3 said:
No I left it in my pocket on my commute to work and tried to restart the phone over 2 hours later
Click to expand...
Click to collapse
Leave it booting for over 20 minutes. If it isnt booting after that, it isnt going to.
The next option is using fastboot to wipe the phone.
fastboot erase cache
fasboot erase userdata

Agreed 20 minutes is probably too long but I wanted to understand how long he was waiting. I know I get crazy impatient
Sent from my Google N6 on VZ

So left it over 20 mins and it did nothing. I have installed the 15 seconds ADB installer with all the drivers. Fastboot can recognise the device but the code >adb devices can't find anything! I even plugged in my Nexus 9 which works just fine with no result.

If during the upgrading process you used the command "fastboot erase cache" and received the message "did you mean format?" or something like that, then you need toflash the cache.img.
"fastboot flash cache chache.img"
I was stuck in a infinite boot animation at one point also. Did the above, and the phone booted in 15 seconds.

Andrew_3 said:
So left it over 20 mins and it did nothing. I have installed the 15 seconds ADB installer with all the drivers. Fastboot can recognise the device but the code >adb devices can't find anything! I even plugged in my Nexus 9 which works just fine with no result.
Click to expand...
Click to collapse
adb devices won't find fastboot devices. Adb works only in android or recovery. Fastboot only works in bootloader.

I didn't do the upgrade myself it was OTA!
Won't re flashing the image wipe the phone though?

Andrew_3 said:
I didn't do the upgrade myself it was OTA!
Won't re flashing the image wipe the phone though?
Click to expand...
Click to collapse
Yes, it will, but at this point, you either have a phone that won't boot, or the possibility of a phone that will afterwards, which one do you want?
I'd flash the image and see what you get. It's a small tradeoff at the moment.
Oh, and RootSU, like the new avatar!

My friend got the exact same problem - tried the OTA update, and after that the phone is stuck at the boot animation. I tried to clear cache/factory reset, and once it even booted up, but after showing the android logo it displayed something like "services stopped" (it was too fast to read carefully) and it powered down. And now no matter what I do, it stays on the boot animation. Is there anything I can do about it without my friend loosing his warranty?
PS. And when I tried the "fastboot erase cache" it displayed the "did you mean format?". Where can I find the "cache.img" to flash - and will it void the warranty?
Edit: Ok - I have flashed the Cache.img - now the phone boots quite fast, but immediately after the "android" logo I get "exchange services stopped", and "Print spooler stopped" with an "ok" that I can't click :/
Edit2: If I would have to flash the whole rom, which one should I choose? LMY47 - D, E, I ?
Edit 3: I have flashed the "I" version, and my friends phone works again

Fastboot.exe has stopped working - Phone Corrupt

Hello my lovely Nexus family,
I need your help! I've searched all over the web and these forums, and have yet to find a single thing that would help me.
After making a stupid mistake from tinkering, my phone was stuck on the "Google" screen. Not a big deal, just a simple wipe and fresh flash (and yeah, that's what I wanted anyways), right? So I went straight to Wugfresh's Nexus Root Toolkit to full wipe. It did the whole process of flashing MRA58R to the phone until I got to "sending sparse 'system'" on the terminal window. "Fastboot.exe has stopped working. Windows is finding a solution....." suddenly appeared while the terminal was processing everything. When the phone decided to reboot after thinking it had finished, it came back with the "Phone Corrupt" message.
I don't know what to do, as this is the 9,999th time I've flashed a phone, and I've never seen this before (obviously) so I'm not really sure what to do.
If I'm missing any details, which I feel I am, do not hesitate to ask.

May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?

scryan said:
May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?
Click to expand...
Click to collapse
Yes, I'm able to boot into fastboot with the phone powered off using the physical buttons. I'm also able to get working commands from the terminal.

Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)

scryan said:
Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)
Click to expand...
Click to collapse
I've done more than one flash today. My next will make 20 in the same hour with failed results. I'll try flashing the bits of the file manually and see how that works.
It could even be the computer I'm using. I'll report back soon.

Are you using the same fastboot.exe every time and getting the same error? Did you verify MD5

So, I got home, hopped on my laptop and got to work as usual. I used the factory provided cable and the problem was solved. I believe it has something to do with either the cord I was using to transfer the data, or the computer I was using.
Other than that - PROBLEM. SOLVED.

If the fastboot exe was fail ("stopped working") the cable was less likely the issue, most likely just the binary on that computer.

Perfect example of why not to use a tool kit until "after" you know how to do it manually.