Nexus 5 became a paperweight overnight (help!) - Nexus 5 Q&A, Help & Troubleshooting

Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.

Ashleyware said:
Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.
Click to expand...
Click to collapse
Since you've already wiped data, have you tried unlocking the bootloader and flashing the Google factory image

I haven't because I can't. I'm on a Macbook and the Nexus 5 drivers aren't compatible with Macs apparently =/

Wait okay, so I misread what I looked at this morning.
So it says I have to flash a new rom to my phone O.K. but every website says I have to turn on USB debugging--how am I supposed to turn on USB debugging to unlock the bootloader if my phone is bricked to begin with? This doesn't make any f***ing sense!
HELP.
Also, my Mac doesn't recognize my device in fastboot mode; what am I supposed to do?!

Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk

ldubs said:
Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Don't you understand? I can't enable USB debugging because I can't ACCESS my phone! It's stuck in bootloop! I can't unlock the bootloader to begin with! Unless you know how to unlock the bootloader from the fastboot menu, you saying that you unlocked your bootloader doesn't help me. I tried everything in that thread and nothing works, I tried the terminal bull**** and the only thing that happens as I can get into the folder where the factory rom is, but I can't get it to flash, I can't get anything to happen--I don't know what the hell I'm doing.
Is there a way to start over without all of this stupid bootloader crap?

As far as I know ADB is not active in fastboot, it is not recognized. In fact I just flashed TWRP again with ADB off. You do need the fastboot drivers on your Mac installed correctly but that's no big deal. If you have access to your phone in fastboot it is simply fastboot oem unlock to unlock your bootloader.

PROGRESS REPORT
So last night I stayed up trying to fix my issue, and I've had no success. I've managed to flash back to Kitkat 4.4.4 but as soon as the phone boots into set up, immediately I get the error messages "unfortunately Camera has stopped working", "unfortunately Gallery has stopped working", and "unfortunately Google Playstore has stopped working". After setting up, my phone has NO service! It doesn't even recognize if there's a SIM card even inserted, or if I remove it.
I cannot open Playstore, it immediately crashes and my phone believes that it has no storage now, even though I see 12GB of space free. I tried flashing multiple roms and nothing beyond Kitkat will work, otherwise I get caught in a bootloop.
I tried installing Cyanogen mod and although it worked, I had the same issue--no service, no Playstore no storage.
I tried clearing the cache, the Dalvik and factory resetting several times and nothing works. I just flashed 4.4 and I'm updating it to 4.4.3 as we speak.
Also I think it's worth mentioning that every time I got caught in bootloop after flashing a new rom (and I tried all of them, including Lolipop, which always hangs) that when I boot in Recovery mode it says something along the lines of:
Invalid arguement couldn't mount blahblahblahgeniusspeak
Invalid arguement blahblahblahgeniuspeak
and so on. Does this have something to do with my lack of service, camera not working, Playstore not working and storage not working? I'm desperate people.

Have you got an imei number?,settings/about phone
Usually you just flash factory ROM, extract the file and then the second archive and flash each individual file and it should boot, factory reset and wipe cache to fix storage
I do this on my mac
If you can't do this then you may have a hardware issue
How did you try to turn off proximity sensor. There would be another way to keep screen on while skyping (keep screen on wake lock)

Also it sounds like you flashed custom roms without flashing gapps...
Sent from my Nexus 5 using Tapatalk

Definitely sounds like no gapps.

What's gapps? And I have no IMEI number (unknown), it says my (with my SIM inserted) Network is: Unknown
Mobile Network Type: Unknown
Mobile State is disconnected
Out of Service
Phone number is unknown
IMEI SV is unknown
IMEI is unknown
Not roaming either
What's the second archive? Every guide I used said use the flash-all.script and that's all you have to do, what're all these extra steps? How do I flash gapps, I don't even know what that is; I don't see the file anywhere in the factory image folder.
=/

I flashed again (back to stock; 4.4) and did everything manually instead of using the script, I even flashed the cache.img, recovery.img etc . . . and it's still the same issue. No service. No external storage available. No Google Playstore.
=/
I didn't flash a custom rom, I only flashed the official factory image from Google. Why doesn't anything ****ing work.
Is gapps going to return my storage and service?

Gapps is only for custom ROM. Since your imei etc is unknown seems like you have bad efs partition. I am not 100% sure. May be others can help.
Sent from my Nexus 5 using XDA Free mobile app

Related

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium
Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!
I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?
I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.
Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.
He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O
@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves
Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!

[Q] ExMIUIv4 2.4.13-r1 on my ST17i causing random reboots?

Hi,
Ever since I installed the [MINI|MINIPRO|ACTIVE|LwW] ExMIUIv4 2.4.13-r1 on my Xperia active, after a week or so I've been getting these random reboots. I am assuming those are reboots because when I look at the phone it wants me to punch in the SIM-PIN again, on the top of that it also asks me for the "SIM network unlock PIN" (on which I have to press the "Dismiss" button to get past). Neither of both issues have occurred with past ROMS.
Does anyone have any ideas/suggestions on the subject?
I've been looking for answers on the ROMS thread, but still haven't found someone with the same issue...(I might have missed it, though I'm still following the thread)
This might be the wrong place to post such a question, but rules are clear and won't let post under the that ROM's developer's thread...maybe one of you could post-forward my question to the guy's thread (the link above).
Nothing still? Geez...
Hi there!
I am not using MIUI, I'm using Spartan but I have recently started to experience the same thing.
It has happened from time to time in the past when using GPS software + loads of other apps but just recently it has started to happen extremely regularly and completely at random on my active too.
One trigger seems to be trying to get the phone to unlock after using GPS software, I slide the unlock toggle and boom, reboot.
I cannot say that I have fixed it at this stage but after reading a few threads this morning I have not had a reboot yet and I have been trying very hard.
What have I done so far: 1) Take out my sim card and rub it vigorously + ensure it is totally clean, reinserted my sim taking extreme care to ensure that it is properly seated. Do the same for the SD card to be on the safe side.
2) Put some paper between your battery and your phone.
This seems absolutely insane, I just bought this damn thing a couple of months ago and it is already screwed. I have tried factory reset + reflashing, numerous different roms and 2 kernels - it just will not stop rebooting now. Driving me insane.
Happened for the first time today whilst I was in a call. Not happy and I have blown my warranty by unlocking bootloader with testpoints
Please let me know if you get anywhere.
Hi,
What type of cellular phone do you have?
I fear that the problem does not lie within the phone, but in the ROM itself. I have a xperia active, and have not ever had any problems with it until I changed roms.
My handset is an Xperia Active also.
There are a number of people experiencing this problem with the Active - many of them are using the latest stock firmware from sony and myself I am using Spartan rom - I do not believe it is specific to any one rom.
Somebody in another forum suggested it might be a problem with the .62 kernel base power management!
What are you usually doing with your phone when it reboots? A lot of us are having the problem when going into or coming out of power saving mode.
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
http://talk.sonymobile.com/message/143782
Well, last time it rebooted I just did things that I usually do: I surfed the web for a bit, then shut down the wifi, kill the tasks afterwards and went to bed. When I picked up the phone the next day I noticed it had been rebooted (it asked me for my SIMPIN). That's pretty much it...
Now the phone hasn't rebooted in a while, even though I still use it the same way that I did before.
Hi again,
I didn't notice your link until now. I haven't had a reboot (that i know of) in a while now. But I'm gonna try out the battery insulation technique and see if that improves anything for me. I'll post the results as soon as I've tried it out!
Thanks again!
Placing the paper between the phone and the battery seem to have helped! Thanks you! I am mentioning it to others and giving you the kudos for it.
It has been so freezing cold here lately that I'm almost positive it is nothing to do with heat transfer of the battery.
I am using ExMIUI now too. Did you download the update that became available on the 12th?
Since flashing that update I have not had a single reboot. Not counting my chickens yet but fingers crossed.
Well the paper-trick did the trick for me, and yes I am running on the latest version of ExMIUI. So far no reboot for me either!

Boot Loop To Factory Reset to Nothing now Please Help!

Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt
Theoutbackdream said:
Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt
Click to expand...
Click to collapse
ok, pulling the sdcard to avoid deleting personal data is useless. When u do a factory reset all information is wiped except the sdcard..anyway, you have to flash this in fastboot usb.
To boot in fastboot you have to do this: pull the battery, then press volume down + power until you get a white screen with 3 androids at the bottom. Then press power to choose fastboot. Plug the phone to the PC and you should see fastboot usb in red in the cell. Run this exe file (is the official AT&T ruu):
http://dl4.htc.com/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
If you are not having a hardware issue, then the phone it should reboot normally when done.
Thanks Glevitan!
Ill give this a shot, if something pops-up ill be sure to ask.
Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.
Theoutbackdream said:
Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.
Click to expand...
Click to collapse
Att Firmware Is a buggy as all the others. It Is weird that You end up in boot loop being stock.....maybe there's something in the hardware that Is messed. Just try to use it and assess the bebaviour of the device for a while, then if nothing Is failing You can try root it and run a custom ROM.....
Glad to have it back....:laugh:

Stock HTC One S got bricked sudenly?

so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.
Very strange!!!
Root the phone and make a nandroid backup. Stock Rom's sucks!!!
Sent from my HTC One S using xda app-developers app
Warmo said:
so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.
Click to expand...
Click to collapse
Did you let the phone die? the phone don't like to do that. Get Dropbox or Google+ that will sync your pictures online.
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?
Warmo said:
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?
Click to expand...
Click to collapse
yes, I take care that I don't have more than 5-10 in my list. since that it didn't brick again. but a few days ago I had ~10 in my list and it suddenly restarted again while I was in the wifi list screen and I was like pleeeaassse no bootloop! but fortunately it was no bootloop but my whole wifi list was reset. it must be an error in htc's software.. so we can only wait for updates..
I've had this happen with other Android devices, it's generally some rogue app that screws up the device and only a factory reset will clear it. I've never had more than 3 or 4 wifi points saved so can't comment on that as a possible cause.
It's not 'bricked' by the way, just slightly fubar'd
-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
You are not the only one. I also encountered the same thing because of too much wlan connections and the only thing i could do is run into bootloader and restore factory settings, since i don't have a nandroid backup because i'm not rooted.. fortunately i synced my pictures thru dropbox, and a backup of sms in gmail.. but i don't know why it is happening to us, so this issue isn't an individual case..
Sent from my HTC One S4 using xda-developers app

[Q] Phone booting on it's own Fastboot Overnight

This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
EDIT (8/28/15): After trying a sense based rom the issue went away. Just followed the advice given below
Gevork Gevorkyan said:
This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
Click to expand...
Click to collapse
Does this happen every night?
If it occurs often.. I would honestly just try flashing a Sense ROM for a few days and see what happens. At least you will know in a few days instead of pulling your hair out.
If it still reboots in Sense, probably a hardware problem
If it doesn't reboot anymore, probably a software glitch in CM
So after wondering "maybe the USB cable plugged into my wall charger causes it to somehow go to fastboot mode"... I just had a reboot at work. Had a youtube video open, I hit pause and turned off the screen, and slid the phone into my pocket. No sound, no vib no indications, 5 minutes later I check and find out that its in fastboot mode. So its not from the USB.
I'll try to install a Sense 7 ROM and see how that goes. Very frustrating.
The only other issue I have is GPS not updating quickly enough, it only catches my location approximately and only if WiFi is enabled even if its not connected...
I've only had issues with a bad boot.img, but i couldn't boot the ROM at all. I would try a different ROM & see if that is the issue
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
What ROM are you on? Just plan CM
Same issue here, running Candy ROM. Never see this before, it's almost made me miss my alarms.
Gevork Gevorkyan said:
So after wondering "maybe the USB cable plugged into my wall charger causes it to somehow go to fastboot mode"... I just had a reboot at work. Had a youtube video open, I hit pause and turned off the screen, and slid the phone into my pocket. No sound, no vib no indications, 5 minutes later I check and find out that its in fastboot mode. So its not from the USB.
I'll try to install a Sense 7 ROM and see how that goes. Very frustrating.
The only other issue I have is GPS not updating quickly enough, it only catches my location approximately and only if WiFi is enabled even if its not connected...
Click to expand...
Click to collapse
Any luck with Sense ROMs?
It happened to Me while on BlissPop,and Sonic Open Kang when I had root,it would take two reboots to get my phone back running
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I have the same problem. I seems to be completely random. It only happens when plugged in overnight. Also, I have to select reboot twice to get the phone to reboot. The first try doesn't work.
HTC M8 running The latest Candy ROM.
gmoe65 said:
It happened to Me while on BlissPop,and Sonic Open Kang when I had root,it would take two reboots to get my phone back running
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say when you had root. Did it stop when you turned root off?
I had to get a replacement phone,and it came back with lollipop 5.0.1
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Gevork Gevorkyan said:
This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
Click to expand...
Click to collapse
Did you install the right GAPPS package for that CM?
Did you fac reset before new OS install?
Fastboot was an option with KK, it is not an option with lollipop.
I use CleanRom 4.0 which is 5.0.1 based, no issues. Sense 6 based. Does not need GAPPS. If your gonna tryout other ROMs, I would try CR 4 for the M8. If it does not reboot auto like then maybe its the CM ver you used or maybe it did not load right. I like CR because it has been cleaned of all carrier software. Has only what you need to function as a phone and mini surf machine, lets you do the customization.
Hope you solve it.
luck
spyknee said:
Did you install the right GAPPS package for that CM?
Did you fac reset before new OS install?
Fastboot was an option with KK, it is not an option with lollipop.
I use CleanRom 4.0 which is 5.0.1 based, no issues. Sense 6 based. Does not need GAPPS. If your gonna tryout other ROMs, I would try CR 4 for the M8. If it does not reboot auto like then maybe its the CM ver you used or maybe it did not load right. I like CR because it has been cleaned of all carrier software. Has only what you need to function as a phone and mini surf machine, lets you do the customization.
Hope you solve it.
luck
Click to expand...
Click to collapse
I'm on Candy ROM which I believe is based off 5.1.1 CM12.1. I flashed GAPPS only after the installation and did a full wipe beforehand. After sticking with a N6 so long I don't really like the Sense layout anymore.
The method I used as per CleanRom guide.
Get 2.8.5 TWRP installed, a must for lollipop.
Make a nandroid backup.
Get firmware for Android 5 installed, carrier dependent!
Factory reset from bootloader
Install Sense or AOSP rom android 5.x.x.
if Sense based your done, if AOSP based install GAPPS ver for your OS/rom
Installing lollipop without right FW could cause issues.
Installing FW can brick your device! so be sure its right one, and make sure you get a nandroid backup stored on your added sd card. More importantly do not just take my word, double and triple check all steps before you leap.
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Gevork Gevorkyan said:
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Click to expand...
Click to collapse
I've been rebooting the phone every night. So far I haven't run into the issue, and I've never had my phone reboot in my pocket.
Gevork Gevorkyan said:
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Click to expand...
Click to collapse
Flash another ROM, or reflash CM. Make sure you wipe first. It was probably a bad flash and something is bonked. It'll take you less than 30 mins. I bet that'll take care of your issue. Good luck.
After many months now of using a sense based rom I've yet to run into the fastboot reset problem. I'm going to switch back to CM this weekend and see where it takes me.

Categories

Resources