Random reboots - Galaxy Note 4 Q&A, Help & Troubleshooting

Hi guys,
I have a problem as I post a thread. I have recently owned a note 4. Before changing phone, I decided to configure all the note 4 settings and apps. After that, I transfer my sim from a xiaomi Redmi 1 to the note 4, and I continued doing other things :
15th july: I put the sim to the note 4.
16th july: I messed up my phone because i wanted to restore a nandroid backup done by the app "online nandroid backup" when I finished configuring my note 4 but it failed. So I re flashed stock rom, re rooted and restored backup from titanium backup.
17th july: I installed nova launcher.
18th july: I found that because I also restored the system data with titanium backup, the private mode didn't work, so I factory reset my phone with twrp and I restored only user app and data backup. I did a nandroid backup after that.
19th july: I messed up (again) with tasker and so I hadn't notification sound. I decided to re flash the stock rom but didn't work. After that, I left my home without my phone for 2h and when I came back, I sSAW THE FIRST RANDOM REBOOT.
20th july: To solve the sound problem, I decided to restore the nandroid backup. It works: the sound came back! But I saw again a random reboot.
The random reboots appear only two or three times per week: indeed, I remembered the other random reboots appeared on the 25th of July and on the 27th July.
The random reboots are special I think because they appear at any time: it appeared when I use the phone or when I don't use it. Moreover we can see the Samsung logo at the minimum brightness and it is infinite: I need to remove the battery to make it restart.
To solve the problem, I first thought that it was a problem from restoring any backup from titanium backup. So I factory reset the phone using twrp to keep root and internal storage. Then I reinstalled the apps with the official Google backup and restore tool. But as I can see, the random reboots are still here because on the 27th July, as I said, a random reboot appeared.
Please help me! I said all I know!

Sorry but I accidentally post this thread but the real one is http://forum.xda-developers.com/note-4/help/strange-random-reboots-note-4-t3167079
Please go to that thread instead and moderator, can you delete this one please?

Related

[Q] Trouble after Cyanogen 7 with the TB Restore

I just did my first ROM install on my Moto Defy, and it all went fine, til i had to restore my apps from the Titanium Backup, when i did it, i chose the "restore all your backup apps and System data" or some like that, and after i finished and rebooted the phone, a thread started chowing up, ".com.phone.android.phone." app just stopped working, and it asked me to force close it, and it just kept poping and poping, all the time, so i guess i restored some system config, from the TB that just wasnt working with the CM, so please i would like someone to tell me witch system configs i should not restore when using the TB, i just flashed the CM again, but it took me a loooong time to restore my apps from the TB so i wouldnt like to do it again, PLIIIIIZ HELP!!!!
PD
Moe1410 said:
I just did my first ROM install on my Moto Defy, and it all went fine, til i had to restore my apps from the Titanium Backup, when i did it, i chose the "restore all your backup apps and System data" or some like that, and after i finished and rebooted the phone, a thread started chowing up, ".com.phone.android.phone." app just stopped working, and it asked me to force close it, and it just kept poping and poping, all the time, so i guess i restored some system config, from the TB that just wasnt working with the CM, so please i would like someone to tell me witch system configs i should not restore when using the TB, i just flashed the CM again, but it took me a loooong time to restore my apps from the TB so i wouldnt like to do it again, PLIIIIIZ HELP!!!!
Click to expand...
Click to collapse
I forgot, i couldnt do anything on the phone anymore cuz the thread just kept showing again and again, and also my network signal went down
HEEEELP!!!

TWRP half restore

So I posted a threat earlier about TWRP not restoring my backups. I thought I'd start a new one since this seems to be a unique issue. I try to resotre any backup in TWRP and it says failed and then I reboot to system anyways and It literally like half restores my rom (PA 4). Ill have all my apps downloaded and all my hangout convos still there, yet none of my system settings are the same and my homescreens are wiped. All my apps are present...yet I have no googled account registered yet. WTF?

Strange things (random reboots and others) on note 4

Hi guys,
I have a problem as I post a thread. I have recently owned a note 4. Before changing phone, I decided to configure all the note 4 settings and apps, root, install twrp and SD fix. All worked fine. So i did a nandroid backup with the app "online nandroid backup". After that, I transfered my sim from my xiaomi Redmi 1 to the note 4, and I continued doing other things :
- 15th july: I put the sim to the note 4.
- 16th july: I messed up my phone because i accidentaly deleted the google framework odex file. So i wanted to restore the nandroid backup done by the app "online nandroid backup" when I finished configuring my note 4 but it failed. So I re flashed stock rom, re rooted and restored backup from titanium backup.
- 17th july: I installed an apk of nova launcher and configured it. Trust me, it is not the prime version I pay the developer me! I installed the apk from internet instead of the app itself from the play store because I never download from play store.
- 18th july: I found that because I also restored the system data with titanium backup, the private mode didn't work, so I factory reset my phone with twrp and I restored only user app and data backup. I did a nandroid backup after that.
- 19th july: I messed up (again) with tasker and so I hadn't notification sound. I decided to re flash the stock rom but didn't work. After that, I left my home without my phone for 2h and when I came back, I sSAW THE FIRST RANDOM REBOOT.
- 20th july: To solve the sound problem, I decided to restore the nandroid backup. It works: the sound came back! But I saw again a random reboot.
The random reboots appear only two or three times per week: indeed, I remembered the other random reboots appeared on the 25th of July and on the 27th July.
The random reboots are special I think because they appear at any time: it appeared when I use the phone or when I don't use it. Moreover we can see the Samsung logo at the minimum brightness and it is infinite: I need to remove the battery to make it restart.
To solve the problem, I first thought that it was a problem from restoring any backup from titanium backup. So I factory reseted the phone using twrp to keep root and internal storage. Then I reinstalled the apps with the official Google backup and restore tool. But as I can see, the random reboots are still here because on the 27th July, as I said, a random reboot appeared.
- 28th July (so today): I removed nova launcher, then shutdown my phone and pull out the battery. When I reinsert it, the phone takes a long time to switch on. Finally, it said system is not responding and reboot and the message re appeared, and reboot... I must remove the battery and reinsert it to restart the phone correctly: the message doesn't appeared. I tried removing the battery one more time to see if the message apprear when I pull out the battery but it didn't appear. However, there are no reboot since, but I think it is because it appeared tomorrow (27th july), and I have to wait to see if the reboots are still here, but I think yes because of this strange message. Or it may be a pure coincidence?
Please help me with all this strange events! I said all I know!
Finally I solved it by deleting nova launcher. And the pop up is only a simple coincidence!

Restoring from nearby device - couldn't finish restoring the backup error

I got a refurbished Nexus 6P from the Nexus Protect program. Now I'm trying to restore the new Nexus 6P from my old one. I go through the prompts on the screen and everything looks good until the final screen when it's actually restoring the device and I see the progress bar moving back and forth. After a short while, I just get an error message saying "couldn't finish restoring the backup". I tried it about 4 times now and I even tried restoring from the cloud to see if that would work.
Anybody know why it's not restoring?
Both my Nexus 6P's were updated to Nouget 7.1.1 but I was still getting the "couldn't finish restoring the backup" error message.
I finally got it FIXED, but I selected the option to restore back up from the cloud instead of restoring from nearby device. This is what I did:
On my old device, I went to settings>Back & reset>Backup my data and turned it off. You will get a warning message telling you that your backups will get deleted. Proceed.
Then I turned the Backup my data back on. I waited overnight to make sure that my new data was backed up again. (If you know of a way to verify that your data was backed up so that you can proceed with these steps then do it)
Then I factory reset my new device and proceeded with the restore procedure.
I took the steps to restore a backup from the cloud again and it worked!
It restored the location of all my app icons and my widgets on my home screens so I was very please.
I guess the backup was old or was backed up with an older version (before Nouget 7.1.1) so there were problems restoring it, but after deleting the old cloud backup and making your phone upload a new one it works! Hope this helps anyone running into the issues I was facing.

Nougat roms instantly auto-deleting texts in Messaging following TWRP restore

I currently have 2 backups in TWRP, the first from a couple weeks ago of a CM14.1 installation, and the 2nd I just made today prior to updating my current AICP nightly build.
A while ago I restored the CM backup and remembered I hadn't backed up my texts from that period, so I download SMS Backup & Restore and go into Messaging just to check that the correct messages were there. Sure enough they were, and at a glance I could tell the contents of the first few conversations were definitely from a couple weeks ago when I had them, but I could only see for a split second because immediately upon opening the messaging app, all conversations flew up the screen and disappeared over the span of about a second as if they were being deleted spontaneously before displaying the "Once you start a new conversation, you'll see it listed here" empty inbox background.
I didn't know why but I didn't care at the time so I left it for another day. Well that day is today, as right after I made my backup before updating the AICP nightly I saw the old one and thought hey I'll try grabbing those old texts again. Same thing happened so I restored back to today's backup and rebooted, went into messaging, and the same exact thing happened, albeit I was able to see that the conversations were indeed from recently, up to earlier today, before they all disappeared.
WTF? I installed a couple other 3rd party messaging apps just to see if the SMS content was still in the database and the stock app was just messing up, but they showed empty inboxes as well. Weird thing is if I restore from the nandroid backup again, I'll reboot and sure as sh*t, there the messages are once again, for a sweet split second before whoosh, they're gone! Does anyone know why it does that? Is this a nougat thing or has anyone experienced this on earlier android versions as well? I don't care about the backup, I just want to archive my old messages, but they nuke themselves as soon as I boot into a restore.
Oh if it helps, it seems upon restoring, the adopted SD card storage is wiped as well, so apps that were previously on the SD card show a dead white link on my home screen. The portable storage section of the card is just fine though (I did the fastboot trick where you split the adopted storage 50/50 between internal and portable storage)
I've noticed the same thing. It is not just you. SMS database doesn't survive TWRP restores on N roms.
I've got another phone that would give endless "Phone has stopped" FC messages upon a TWRP restore when it was first brought up to 7.1. It needed a fix in the roms to get TWRP backups to work right with it. Just a wild guess, but could be something similar at work here.

Categories

Resources