Related
So I got my nexus 5 before not even a week ago and from the first day I got some random reboots that are really just random without a pattern, app or something to do them, they are just random. But I didn't care mostly because I wanted to wait a bit before I began customizing it. After I waited a little bit for the OTA update to come to my nexus 5 I thought to myself what could happen if I unlock the bootloader and root it so I could update my rom. So I did that and after a little more tweaking I found a nice merge of 2 kernels (franco & one that has DT2W) so I thought why not. I installed it, but the same night after 4-5 hours the phone began bootlooping to the point that I really couldn't even load TWRP. I fixed it by flashing default android and kernel and after that I updated it to 4.4.1 and rooted it without a problem. The random reboots kept occurring though Today I thought that I would backup my rom so I could try some other kernel, but I cannot literally be in twrp more than 10 seconds. After I begin installing a zip or backup or whatever else the device reboots for no apparent reason. I need help because it reboots every 2 minutes when I am talking, Thanks for your support ! Only fix that I have seen is that I flash default kit kat through the Nexus Root Toolkit.
The title pretty much says it all , phone crashes all of a sudden , but I've had 5.0.1 for however long Its been released and today my phone randomly started crashing . Wondering what could've caused it . I'm stock rooted and running twrp.
You have root access and a custom recovery so it could be one of many possibilities. Reflash system.img.
Did you undervolt it?
I work with a couple guys that have bone stock Nexus 5 with lolipop. Both are non-rooted and locked, however one has the random soft reboot problems. It mostly happens after phone calls. The other one doesn't have a single issue.
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
The_Wolf91 said:
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
Click to expand...
Click to collapse
Flashed Android 5.0.1 and no random reboots (as I also said when i wrote my first post).
I don't know if the "question" is clear, but can you help me reading the "last_kmsg" which I attached in first post? Thanks
Same exact thing happening to me also.
Sent from my Nexus 5 using XDA Free mobile app
The same is happening to me. And it looks like a hardware problem cuz when the phone reboots it keeping reboot until I keep pressing the power button while boots.
I have a bad experience about it. In my Nexus S when updates to Jelly Bean the same occurs until phone suddenly die. (I live in Brazil so, guess what? I have now a wonderful paper weight)
No luck with 5.1.1
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Try another (custom) kernel.
beekay201 said:
Try another (custom) kernel.
Click to expand...
Click to collapse
I just flashed ElementalX kernel but no luck, random reboot happened on 5.1.1 too. By the way it was quite obvious because it happened already on 5.1 Google's factory image (stock kernel so)..
I have exactly the same issue with nexus 5 since upgrading to 5.1.0.
I went back to 5.0.1, which solved it for a few days, but now this happens with 5.0.1 as well.
also, before random reboots happen, the power button becomes extra sensitive, so one keypress causes the screen to turn on and off again, or to display the shutdown menu.
this does not happen when the phone is stable.
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Sent from my Nexus 5 using XDA Free mobile app
noob424 said:
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Click to expand...
Click to collapse
Same here.
LG Nexus 5 - Lollipop 5.1.1 LMY48B
Unlocked bootloader;
Rooted;
ClockWorkmod 6.0.4.5 (not flashed - just boot on image when used);
Wipe factory reset (in cwm). Flashed 5.1.1 image files (boot, radio, bootloader, system and cache).
Random reboots, and sometimes with apps optimizing.
I have the same problem with N5 since upgrading to 5.1.1 - never had any problems before. Doing it several times an hour now. Trying a cache clean next, after I wait for the optimising apps to finish yet again!
Hi all,
I had the same problem. Everything stock, up to datę, no root. Phone was rebooting itself several times in a row.
Right now it seems that problem dissapeared. Reboots in my case was caused probably by application Autoguard Dash Cam Blackbox. After removal no reboots for 2 months and no memory leak.
cleared cache and it happened again within a minute...
Does seem to be linked to the power button
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
simbapenn said:
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
Click to expand...
Click to collapse
I have N5 kit kat 4.4.2 in Chrome watching videos randoms reboot its happens
This is happening to my fiance's N5. It happens when she's using it and also when it's not being used. When it reboots, it optimizes the apps and says the battery is at 0 when it was a full charge. Only way to turn it back on is to connect it to a charger. Frustrating.
FYI the update to 6.0 did not solve the restart problem. It's either hardware related, app related or a bug that's still in the OS.
I'm selling my Nexus because of this, has been happening for a few months now.
It's not software related, it has to do with the actual power button. Some people had success changing it out, soldering it etc., but I don't have that time or knowledge.
Google wouldn't help, as I'm out of warranty. So I guess it's goodbye Nexus. Really unfortunate given that the phone works fine, it's just a quality issue.. will have to re-evaluate buying another Nexus in the future.
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
---------- Post added at 04:41 PM ---------- Previous post was at 04:20 PM ----------
I have been using this awesome app on my nexus 5, just so I don't have to use the power button here is the play store link.
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree
maccboy2010 said:
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
Click to expand...
Click to collapse
Confirmed the update will NOT fix this issue.
Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
cart00nist said:
Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the LG/Google Nexus 4 at http://forum.xda-developers.com/nexus-4 which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/nexus-4/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.
I've only had this phone for a few weeks, bought new from Target. It is a US BLN-L24. It originally was running Marshmallow but I updated it to Nougat via the official updater (BLN-L24C567B360).
The first time I got this issue was when I rooted the stock ROM with Magisk. I later installed Apps2SD Pro (for linking apps to 2nd partition on SD card). It mounted this partition, I rebooted, the device then asks for a PIN# which I didnt have and never set. Afterwards I rebooted to @OldDroid's TWRP, it couldnt mount data partition, some error about not being able to find the crypto footer. I then used the dload method to rollback to MM, then updated to Nougat again, and rerooted, this time with systemless SuperSU instead..
Then eventually everything went fine for awhile, but it happened again. So I decided to try a custom Nougat ROM. I went with Resurrection Remix 7.1.2. And then.....it happened again. This time I had rooted with Magisk. I tried yet again, but with SuperSU. And yet again with Phh's Superuser.
I've also tried AOKP, AOSPA, LineageOS, OctN, all Nougat, the issue returns with all of them.
So, no matter what root solution I use, the encryption issue eventually returns. Magisk, SuperSU, and Phh are all supposed to disable data partition encryption. But it seems they aren't.
What I've tried so far:
1. 3 different root solutions, same results
2. Formatting data and wiping all partitions in TWRP immediately before installing a ROM zip, which is supposed to remove the encryption
3. A custom kernel (CycloX)
4. Formatting my MicroSD, as exFAT, every time I check it for errors in Windows 10 corruption is found and repaired, but it always returns. I had initially thought that the encryption might be related to the SD
It has happened numerous times, on different ROMs including stock, and MM/Nougat, and with different root solutions. I know when it happens, I get stuck on the boot logo forever. TWRP reports that data can't be mounted. At one point my phone randomly rebooted into eRecovery and I was shown a message stating that data partition was corrupted. Sometimes it happens as little as 15 mins after booting into a freshly installed ROM, sometimes it takes a few days, but it always comes back no matter what. So far several dozen times.
I'm at a loss as to what is the cause. It could be a hardware defect, a firmware defect/bug, or something I'm doing wrong/missing. So I really have to ask if others are experiencing this too, and what you did to resolve it, I'm sure I'm not the only one. Please provided detailed steps. This is driving me crazy. I bought the 6X to replace my Samsung Note 4 which recently died after 3 years of loyal service. I'm liking this phone alot, it's very powerful, but this is killing me.
If anyone can help then I would greatly appreciate it. If I can't get this resolved then I'll just sell the phone on Craigslist after returning it to stock.
Thanks!
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
AnonVendetta said:
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
Click to expand...
Click to collapse
Actually I think you are the only one with this issue. Flashing Magisk alone will remove auto-encryption. But then you already flashed custom roms.
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
AnonVendetta said:
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
Click to expand...
Click to collapse
Hello, can you help me? I have the same model BLN-L24C567B360. I got this phone today and updated today as well right out of the box. My problem is that I installed TWRP 3.1.1.0 Berlin version for this phone and it doesn't work at all. Now I have my phone working ROM but with no recovery option. Can you give me a link with the files I need? I was thinking on putting back the original recovery.img file back but unfortunately I never thought on doing a backup of it. I read on the top that you have all original stock files. Thanks
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
AnonVendetta said:
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
Click to expand...
Click to collapse
You can stop crying now, I won't be using your "topic" anymore. I just replied to you asking for files that you already have.
And BTW, I don't need them anymore but thanks anyways.
Yoooooo did Huawei do anything yet?
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
AnonVendetta said:
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
Click to expand...
Click to collapse
Sorry to hear you had such a bad experience with them. Pretty crappy that they used a lame excuse like water damage to deny responsibility in fixing the issue.
I agree with you, I will never buy Huawei again. The phone itself is great but the audio is so so bad Im trying to sell mine at a loss as well but no ones calling so Im tinkering with it again. I would be absolutely livid if I spent the money on one of the flagship Huawei phones. Oh well live and learn I guess, at least the 5T comes out sometime next month.