Hey guys,
just flashed CM13 on my Nexus 5X. For some reason, everytime I reboot the phone, the following notification pops up "There’s an internal problem with your device. Contact your manufacturer for details.".
The phone is working fine tho, but this notification is kinda making me a bit worried. Is something actually wrong with my device? Has anyone had the same issue and got rid of it somehow?
Please let me know if you do so, or if you have some clues for me to fix that.
Thank you very much.
- Yougosha
There are quite some similar topics on the internet on different Nexus devices. Some reflashing did help, some talk about vendor.img being wrong. Would recommend flashing something from scratch to validate in deed it is caused by the ROM itself
Apb said:
There are quite some similar topics on the internet on different Nexus devices. Some reflashing did help, some talk about vendor.img being wrong. Would recommend flashing something from scratch to validate in deed it is caused by the ROM itself
Click to expand...
Click to collapse
Thanks for your reply. I saw some fixes for the Nexus 9, but wasn't quite sure if it works for the Nexus 5X as well. Maybe someone else has a different idea to how to fix this problem? I just flashed CM and put all my apps/data back on my phone, so I'd like to try reflashing something as a last resort ^^ Putting all my stuff back on it is quite a hassle
Yougosha said:
Hey guys,
just flashed CM13 on my Nexus 5X. For some reason, everytime I reboot the phone, the following notification pops up "There’s an internal problem with your device. Contact your manufacturer for details.".
The phone is working fine tho, but this notification is kinda making me a bit worried. Is something actually wrong with my device? Has anyone had the same issue and got rid of it somehow?
Please let me know if you do so, or if you have some clues for me to fix that.
Thank you very much.
- Yougosha
Click to expand...
Click to collapse
This message occurs when you have a mismatched Vendor partition on the Nexus 5x and 6P. This is a separate partition that was once included in the system on previous Nexus devices. Flash the vendor.img that matches your rom base. You can download the factory image from Google and inside that 1+ GB file, you will find the vendor.img.
Edit: Alternatively, you can download the Vendor.img from the OP of the Pure Nexus thread and flash this in TWRP:
http://forum.xda-developers.com/showthread.php?t=3244601
Make sure to thank that developer if you do.
Sent from my Nexus 5X using Tapatalk
Thanks man, gonna try that out.
Related
I hit a boot loop snag on my Galaxy Nexus GSM after installing the recent 4.3 OTA security update. I had no issues with the initial Android 4.3 release, but the security update did something that made my device hit a boot loop. I could restore from a Nandroid backup, but about once a day I would hit the boot loop snag again. After dealing with daily restores for a couple days I dug into it a bit and found that when the phone gets mired in a boot loop I can fix it by deleting two files.
The trick is you have to be using TWRP on the recovery partition because that will let you use a file manager to delete the two files. There may well be other solutions but that's been the easiest for me. The two files which need to be deleted are:
/data/system/locksettings.db
/data/system/locksettings.db-shm
If you use Google Wallet you'll see a similarly named file there "locksettings.db-wal" -- DO NOT DELETE THIS ONE, just the two above.
If this helps anyone please post so if it doesn't people won't waste their time -- THANKS!
Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4
Vekhez said:
Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.
sansnil said:
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.
Click to expand...
Click to collapse
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4
Vekhez said:
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!
sansnil said:
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!
Click to expand...
Click to collapse
Nope it didn't.. Same problem.
Sent from my Galaxy Nexus using Tapatalk 4
Vekhez said:
Nope it didn't.. Same problem.
Click to expand...
Click to collapse
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...
sansnil said:
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...
Click to expand...
Click to collapse
Ok, so it turns out this is actually being caused by the app "Delayed Lock" if you use a pattern lock. If you use a PIN/password lock it won't happen, but if you use a pattern lock with the current version of Delayed Lock on a Galaxy Nexus this boot loop issue will occur.
I've opened a bug with the Delayed Lock Dev so hopefully he'll find a way to fix it. In the meantime, choices are to either disabled/uninstall Delayed Lock (hate!) or switch to a PIN or password lock setting.
Hey guys,
I had the same problem and found out that it could be solved, without losing any data, by directly flashing the update.
Here's what I did: http://forum.xda-developers.com/showthread.php?t=2427613
Best of luck.
Hello guys,
A friend of mine just bought nexus 5 from some guy at a cheap price the only problem with the phone was its wifi & Bluetooth was not working so my friend changed some IC's and still the problem persists now he has handed his phone over to me(I love fixing things) for few weeks to fix the problem. I don't know whether the problem is related to hardware or with the OS I'm thinking to root the phone and install CM 13 and see whether it fixes the problem.
What else would you guy's suggest ? Where could possibly the problem lie?
Your suggestions are most welcomed.:fingers-crossed::fingers-crossed:
Thanks for reading.. waiting for replies.
rootb3r said:
Hello guys,
A friend of mine just bought nexus 5 from some guy at a cheap price the only problem with the phone was its wifi & Bluetooth was not working so my friend changed some IC's and still the problem persists now he has handed his phone over to me(I love fixing things) for few weeks to fix the problem. I don't know whether the problem is related to hardware or with the OS I'm thinking to root the phone and install CM 13 and see whether it fixes the problem.
What else would you guy's suggest ? Where could possibly the problem lie?
Your suggestions are most welcomed.:fingers-crossed::fingers-crossed:
Thanks for reading.. waiting for replies.
Click to expand...
Click to collapse
Is this a Nexus 5X with a fingerprint sensor or Nexus 5? I'd say start from a clean slate with the factory image then decide if it's hardware or software related.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Is this a Nexus 5X with a fingerprint sensor or Nexus 5? I'd say start from a clean slate with the factory image then decide if it's hardware or software related.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Sorry, I posted in wrong section its Google nexus 5 not 5x.
Where can I find factory image?
Also, how should I figure out what the problem might be?
Can I go for CM instead of stock ROM?
Thanks for reply.
rootb3r said:
Sorry, I posted in wrong section its Google nexus 5 not 5x.
Where can I find factory image?
Also, how should I figure out what the problem might be?
Can I go for CM instead of stock ROM?
Thanks for reply.
Click to expand...
Click to collapse
Factory images: https://developers.google.com/android/nexus/images?hl=en
I've never owned the Nexus 5 but for any phone I'd go back to stock and test out the phone. I suggest resetting the router, upgrading the software, or changing frequencies with WiFi. For BT, try pairing with another device and see if it works.
If WiFi and BT are not connecting even after a factory reset and install of the factory image, that's likely a hardware problem.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Factory images: https://developers.google.com/android/nexus/images?hl=en
I've never owned the Nexus 5 but for any phone I'd go back to stock and test out the phone. I suggest resetting the router, upgrading the software, or changing frequencies with WiFi. For BT, try pairing with another device and see if it works.
If WiFi and BT are not connecting even after a factory reset and install of the factory image, that's likely a hardware problem.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I guess to even install stock image I'll need to unlock bootloader and root it and install the stock image or should I root and install other ROM's like PURE LEXUS...etc.
rootb3r said:
I guess to even install stock image I'll need to unlock bootloader and root it and install the stock image or should I root and install other ROM's like PURE LEXUS...etc.
Click to expand...
Click to collapse
That's up to you. Maybe it is software related and easily fixable via custom rom? I'm sure people in the Nexus 5 forums would be better informed.
Sent from my Nexus 5X using Tapatalk
Have you simply tried to open the back cover and see if the antenna's are properly connected? There are 2 (left and right of the battery). If that checks out then i would unlock the bootloader and install the latest factory image. Installing another ROM like Pure or whatever doesn't guarantee it's a software or hardware issue. Best troubleshooting step is to use the latest stock rom and go from there.
Hi,
A few hours ago I randomly got into a some kind of bootloop. It's not the "normal" bootloop where simply the boot animation is played forever. Instead my boot continues afterwards like normal until there's this short black screen before entering your SIM's pin card. This never appears and it begins again with the "Your bootloader is unlocked. Please lock it...."-message.
I already flashed the Factory Image twice via the ADB console on my PC and Wugfresh's Toolkit.
Additionally I can't seem to acess the stock recovery, the "red android guy" never appears and it only reboot itself after choosing the recovery in Fastboot Mode.
Any help is appreciated!
Vulkaistos
Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk
dc239 said:
Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I already tried that, same problem as Stock Recovery.
Vulkaistos said:
I already tried that, same problem as Stock Recovery.
Click to expand...
Click to collapse
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?
dc239 said:
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?
Click to expand...
Click to collapse
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!
Vulkaistos said:
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!
Click to expand...
Click to collapse
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here
Vulkaistos said:
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here
Click to expand...
Click to collapse
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk
dc239 said:
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help
Vulkaistos said:
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help
Click to expand...
Click to collapse
You'll get the RMA, that is a hardware failure.
Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.
Vulkaistos said:
Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.
Click to expand...
Click to collapse
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk
dc239 said:
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I bought my Nexus in December 2015 so around 2 1/2 years ago. It's a nice phone never had any serious problems with it except now.
Hello. Yesterday, I uploaded my Nexus 5X to Android 8 - official updated as appeared on my mobile´s screen. After completing the update and rebooting, I saw this message "can't load android system data corrupted". I have tried the adb sideload following the instructions at google´s developers site. It seemed that the configuration was correct, but when rebooting, same problem.
I´d appreciate if anyone can help me out. I would like to mostly recover my photos on the phone.
Thanks.
This happened to me today as well, though I have been running 8.0 since the end of August. By looking around, I came to the conclusion that its the bootloop of death problem. I think Google changed something in Oreo how the system uses the processor and thats why it happened now. I tried using the boot image which disables the 2 BIG cores, but that didnt work either. Right now I think that my phone is gone, and I am mad, because I cant even backup the data that was on there. You could try following these instructions: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Maybe it will help you.
koostamas said:
This happened to me today as well, though I have been running 8.0 since the end of August. By looking around, I came to the conclusion that its the bootloop of death problem. I think Google changed something in Oreo how the system uses the processor and thats why it happened now. I tried using the boot image which disables the 2 BIG cores, but that didnt work either. Right now I think that my phone is gone, and I am mad, because I cant even backup the data that was on there. You could try following these instructions: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Maybe it will help you.
Click to expand...
Click to collapse
Thanks, I am not so sure if I would know how to do that. Seems a little bit risky. Thanks for your reply.
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
tnsmani said:
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
Click to expand...
Click to collapse
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
the_mentor said:
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
Click to expand...
Click to collapse
You will need to replace the main board if the issue persist.
Same problem here
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
New geek said:
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
Click to expand...
Click to collapse
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
try using msm v3.0 tool fixes most problems not hardware though
the_mentor said:
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
Click to expand...
Click to collapse
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
New geek said:
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
Click to expand...
Click to collapse
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
what you will need to do is download the oneplus 3 recovery tool and put the phone into qualcolm mode and restore the phone that way. here is a link https://www.androidexplained.com/oneplus-3-unbrick-return-stock/
New geek said:
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
Click to expand...
Click to collapse
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
the_mentor said:
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
Click to expand...
Click to collapse
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
tnsmani said:
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
Click to expand...
Click to collapse
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
Please share the guide as I am also suffering with same problem.
Still not working
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
I was about to update here with good news but wife's phone went back to restart loop the next day. I am not sure but probably triggered by her installing whatsapp and facebook. I put the phone away because I have already spend quite a lot of time behind this. Is your's still going? Please list the step by step procedure. Thanks
download from here https://mega.nz/#!zsdnkCDA!UyJRwbJK6kHTDpmesBYao0knaOTwbgu4dSiokV1XLYU then turn off phone run tool,connect phone with volume up pressed,should have a com in the list if so just click start thats it and wait for it to turn green or device restart