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
Related
Okay, so pretty much, my phone won't boot past the booting animation thing.
Everything was working pretty much fine on AOKP, I did all the steps (root, unlock bootloader, cwm, fastboot stock, gps, then flashing gapps and a custom rom)
But today, I was in my car and turned on my bluetooth, and then basically it got stuck in a boot loop where it would freeze, reboot, and then do the same as soon as I did anything on my phone.
I came home, wiped everything, cleared caches, went back to stock, and then I reflashed aokp and gapps. Now it won't get past the animation logo. I tried to restore a backup from recovery but it tells me that it can't mount /sdcard for some odd reason, and while the bootloader and recovery still works, no matter what rom I try, I can't boot.
Any help?
crackanduse said:
Okay, so pretty much, my phone won't boot past the booting animation thing.
Everything was working pretty much fine on AOKP, I did all the steps (root, unlock bootloader, cwm, fastboot stock, gps, then flashing gapps and a custom rom)
But today, I was in my car and turned on my bluetooth, and then basically it got stuck in a boot loop where it would freeze, reboot, and then do the same as soon as I did anything on my phone.
I came home, wiped everything, cleared caches, went back to stock, and then I reflashed aokp and gapps. Now it won't get past the animation logo. I tried to restore a backup from recovery but it tells me that it can't mount /sdcard for some odd reason, and while the bootloader and recovery still works, no matter what rom I try, I can't boot.
Any help?
Click to expand...
Click to collapse
how did you go back to stock was it fastboot or rsdlite. I screwed up my SD partition once by doing some experimental stuff and fastboot to stock still did not work. the only way I could get it back to normal is rsdlite.
frog1982 said:
how did you go back to stock was it fastboot or rsdlite. I screwed up my SD partition once by doing some experimental stuff and fastboot to stock still did not work. the only way I could get it back to normal is rsdlite.
Click to expand...
Click to collapse
I've been there, you can fix it with fastboot. Just gotta format /data completely. You'll lose everything on the internal SD, but its worth it to boot the phone. I'm assuming the issue is the 4.2.2 sdcard setup clashing with 4.x.x sdcard setup.
@crackanduse
use the snapdragon fastboot and try
"fastboot -w"
or
"fastboot erase userdate"
"fastboot erase cache"
or
"fastboot format userdata"
"fastboot format cache"
Note that doing the above commands will wipe your internal sd....Oh, and to @frog1982, RSD uses the command "fastboot erase blah" as the last steps.
frog1982 said:
how did you go back to stock was it fastboot or rsdlite. I screwed up my SD partition once by doing some experimental stuff and fastboot to stock still did not work. the only way I could get it back to normal is rsdlite.
Click to expand...
Click to collapse
I fastbooted to stock
skeevydude said:
I've been there, you can fix it with fastboot. Just gotta format /data completely. You'll lose everything on the internal SD, but its worth it to boot the phone. I'm assuming the issue is the 4.2.2 sdcard setup clashing with 4.x.x sdcard setup.
@crackanduse
use the snapdragon fastboot and try
"fastboot -w"
or
"fastboot erase userdate"
"fastboot erase cache"
or
"fastboot format userdata"
"fastboot format cache"
Note that doing the above commands will wipe your internal sd....Oh, and to @frog1982, RSD uses the command "fastboot erase blah" as the last steps.
Click to expand...
Click to collapse
Alright so I was just about to do that but...my phone now is just a black screen. When I plug it into my computer the LED is green. I can hold down the power and volume buttons and the green light will go off for a split second, my computer will tell me the phone gets disconnected from my computer, and then it will recognize it as a usb device again.
EDIT: After playing around with it more, as I hold down the buttons, the device is not connected to USB, but as soon as I let go, the LED comes back on and my computer recognizes it again.
crackanduse said:
I fastbooted to stock
Alright so I was just about to do that but...my phone now is just a black screen. When I plug it into my computer the LED is green. I can hold down the power and volume buttons and the green light will go off for a split second, my computer will tell me the phone gets disconnected from my computer, and then it will recognize it as a usb device again.
EDIT: After playing around with it more, as I hold down the buttons, the device is not connected to USB, but as soon as I let go, the LED comes back on and my computer recognizes it again.
Click to expand...
Click to collapse
Might be low on power. Plug it into a wall or car charger for a few hours then try again. The phone reacts differently depending on what kind of USB source you are using.
Having same issue
I'm having the same issue no matter what rom I flash the phone gets stuck at the boot logo. Been working on this phone for days now just can't get it to boot properly.
P.S. Got it working properly now for some reason when I flashed gapps at the same time I flashed the rom it wouldn't boot. So I flashed the rom then booted and then rebooted and flashed gapps,.
skeevydude said:
Might be low on power. Plug it into a wall or car charger for a few hours then try again. The phone reacts differently depending on what kind of USB source you are using.
Click to expand...
Click to collapse
Yea I figured out it was that. It would charge, show the warning, then immediately turn off and go back to charging. I'm using my wall outlet now and it's charging up. I'll let you guys know how it goes.
Skeevy: your instructions worked perfectly. Phone is now working again. But my stupid GPS still doesn't. I'm on AOKP again and when I went back to stock I did verify my gps did work. I then flashed to aokp and now my gps isn't picking up any satellites. I know it should work so I'm probably doing something wrong.
So I started having trouble after flashing a rom. The old infinite htc boot logo. The troubling part was when I tried to reboot to recovery and TWRP blackscreened and device turned off.
I tried re-flashing recovery.img with identical results.
Now my phone locked while attempting a fastboot flash boot.img with a known working boot.img just in case the rom I flashed had a corrupt boot image.
I left the cmd window open and its been "sending boot.img" for about forty-five minutes now. I am terrified to ctrl+c the command or restart my device.
So boned or no boned?
On a scale of one to boned how boned where do I fall on the bonage spectrum?
Any ideas on what to do next, or if rebooting to fastboot is safe?
You have to wait the final of the sending.
Probably your USB cable is *****d up, and i'm advising you because i had the same issue.
A flash of a boot.img was of 15 mins.
Tried fastboot erase cache to get back into twrp?
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 9.1.0
Bulletproof 4.3
Afraid to stop the current fastboot operation to try to clear cache. Tried running from another window and it just sits there, cursor blinking, like its waiting for the other operation to complete.
Waiting for it to complete seems fruitless as its been almost two hours now for a 5836kb flash.
-update-
Okay so I took a couple valium and quickly switched out the usb cable. The cmd window running the flash operation crashed, but fastboot on the device became responsive again. I feel like this is a fact that might be useful to others in the future.
Fastboot stalls out--don't panic, just disconnect the usb cable...
I'm still scared to reboot it, even to reboot to fastboot. Is fastboot part of boot.img? If this botched op boned up my boot.img is it possible that fastboot might not work after a reset?
Gonna give cache erase a shot and report results.
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
hypocritelecteur said:
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
Click to expand...
Click to collapse
After the cache's erase you can boot in recovery.
Guich said:
After the cache's erase you can boot in recovery.
Click to expand...
Click to collapse
Phone still reboots right after TWRP logo is displayed!
hypocritelecteur said:
Phone still reboots right after TWRP logo is displayed!
Click to expand...
Click to collapse
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Yeah, I tried that before posting but for sake of thoroughness I did it again.
erased cache
reflashed m7 twrp
erased cache
Going to try CWM now.
Really appreciate the guidance and support in a problem you have no personal stake in. Being on the receiving end of the goodwill of strangers makes me all warm and tingly.
Also switched USB cables and did a fastboot reboot to make sure commands were being passed on... nothing wrong on that front.
Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Aaaand CWM worked for whatever reason.
Odd, since I've never had a problem with TWRP before but plenty with CWM... Every duck has its day I guess.
---
Well... CWM loads properly but executing any command that touches phone data causes a reboot.
Factory reset -> reboot
Install zip from sdcard -> reboot
Trying sideload next... it goes into sideload mode fine. I'm guessing that as soon as it tries to write something it will reboot, but I'll have to wait till I've re-downloaded and double checked md5s like a paranoid bastard first.
adb sideload ohdeargod.zip
---
Hmm, wiping cache partition alone works.
--
Noticed that on booting into CWM it displays the message:
Warning: No file contexts.
--
formating /system alone works
formatting dalvik causes reboot
formatting data causes reboot
--
sideload seems to have worked although its taking a long time to boot. I'll give it another 15 minutes.
Which firmware are you running?
Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Guich said:
Which firmware are you running?
Click to expand...
Click to collapse
Aaaand bingo gringo. It's booted.
Its a tmo m7. I haven't touched firmware afaik.
Resolved just in time for me to take it sailing today and drop it into lake Huron.
hypocritelecteur said:
[snip]....drop it into lake Huron.
Click to expand...
Click to collapse
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Okay so I have a brand new HTC TMO One I got last week and its waterlogged. I drilled a hole in the back of the case to drain it and then left it on the radiator to make sure all that moisture is gone. I can't get it to post to TWRP.
Please help.
Deciding after recent events that XDA can be a dangerous place for sarcasm. So--thanks all, problem solved, no, no phone was damaged during the making of this thread. It was just my business partner, Lloyd, who fell in and became waterlogged. No amount of drilling or radiator baking could revive him.
Please help.
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
darylbu said:
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
Click to expand...
Click to collapse
How did you fix it?
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Recovery
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
MikeNaples said:
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
Click to expand...
Click to collapse
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
serophia said:
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
Click to expand...
Click to collapse
This process seems to work quite well.
I'd recommend to use MFastboot. With your phone off, you can boot into fastboot by holding power and volume down for a few seconds, release and it will boot into fastboot. Connect the usb cable, and first try "fastboot erase cache". If that doesn't work by itself, repeat the process but also use "fastboot erase userdata" (THIS WILL ERASE ALL YOUR DATA!) but at least there is a chance you might get it to boot normally. It´s like a factory reset, you will have to start from scratch.
I know my answer is out of date but it might be useful for someone coming for this same solution.
Moto x Stuck in TWRP loop
pls help me guys it just goes on restarting it dose not even goes in recovery mode
Guys.. I got struck at unlocked boot loader. Flashed TWRP on 5.1 ( GB retail rom). And its not booting now and not able to flash any rom.. kindly Help...!!!
Dear xdadevelopers members,
I have anHTC One m7 (GSM Version Unlocked without Providerlock)
It is rootet and Bootloader unlocked and at the moment is TWRP v.2.8.1.0 Recovery installed (before it wasCWM Touch).
It is the Stock ROM it got with which I bought it, not completely ... before rooting I did one OTA update . So it is now 4.2.2 with normal sense edition.
I am trying to resolve the problem, but with no success. So the phone starts normally until I have to enter the PIN, if I'm quick enough I can enter it successfully. Then everything looks quite normal, then only after about 5-10 seconds it goes black and reboots again, this happens all the time.
Booting into Save Mode has the exact same issue!
Recovery is working normally.
Does anyone have any idea why this might be and how I could fix it?
My guess is that it has occurred because I installed a root uninstaller tool to uninstall/disabled some of HTC's own apps, so maybe I have deleted too many of them. But that's a long time ago, it worked for weeks even after the erase with the tool (I did never a restart after), only when I then made a reboot weeks later the problem occured.
Saturos said:
Dear xdadevelopers members,
I have anHTC One m7 (GSM Version Unlocked without Providerlock)
It is rootet and Bootloader unlocked and at the moment is TWRP v.2.8.1.0 Recovery installed (before it wasCWM Touch).
It is the Stock ROM it got with which I bought it, not completely ... before rooting I did one OTA update . So it is now 4.2.2 with normal sense edition.
I am trying to resolve the problem, but with no success. So the phone starts normally until I have to enter the PIN, if I'm quick enough I can enter it successfully. Then everything looks quite normal, then only after about 5-10 seconds it goes black and reboots again, this happens all the time.
Booting into Save Mode has the exact same issue!
Recovery is working normally.
Does anyone have any idea why this might be and how I could fix it?
My guess is that it has occurred because I installed a root uninstaller tool to uninstall/disabled some of HTC's own apps, so maybe I have deleted too many of them. But that's a long time ago, it worked for weeks even after the erase with the tool (I did never a restart after), only when I then made a reboot weeks later the problem occured.
Click to expand...
Click to collapse
First thing you should do is a factory reset and see if its still rebooting
then return to return to 100% stock
what is your fastboot getvar all?
alray said:
First thing you should do is a factory reset and see if its still rebooting
then return to return to 100% stock
what is your fastboot getvar all?
Click to expand...
Click to collapse
THanks for your help. I tried a few things now in the 10 sec I had , moved the phone to air plane mode rebooted again and since then its working normally again. I even diabled airplane mode and everything is up to normal again its running like a charm since 30 minutes. I Also got a HTC message that the phone was recovered from a problem and it would like me to send an error report (I did). But I am a bit afraid now to reboot it again, so I think I can not make the fastboot getvar all command or can I place this command without restarting and booting into the bootloader?
Saturos said:
THanks for your help. I tried a few things now in the 10 sec I had , moved the phone to air plane mode rebooted again and since then its working normally again. I even diabled airplane mode and everything is up to normal again its running like a charm since 30 minutes. I Also got a HTC message that the phone was recovered from a problem and it would like me to send an error report (I did). But I am a bit afraid now to reboot it again, so I think I can not make the fastboot getvar all command or can I place this command without restarting and booting into the bootloader?
Click to expand...
Click to collapse
this command must be entered when in bootloader/fastboot mode
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign 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, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. 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 it wouldn't boot past google screen after that. It doesnt even get 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 spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign 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, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. 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 it wouldn't boot past google screen after that. It doesnt even get 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 spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. 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 know, it's been a long time, but coud you tell me what happened to the phone?