[Q] Random Reboots - Galaxy Note II Q&A, Help & Troubleshooting

Hello!
My note ii is almost a month old and the last two daysit reboots automatically...today the phone rebooted 2 times...Is there any solution to this problem?
P.S: I am on stock 4.1.1

Maybe first signs of SDS? update it to 4.1.2
Sent from my GT-N7100 using xda premium

Hey try wiping cache and dalvik cache. Then optionally apply the latest v6 supercharger(just google it) script using script manager

There ia nothing bad in updating either.
Secondly try factory reset.
Maybe some app...
Sent from my GT-N7100 using xda app-developers app

Related

Problem after the OTA Tmo update

After applying the latest update (not the JB leak), I get this problem everyday. The system sound mutes itself randomly. There is a slash across indicating it is muted (pic). I can still raise it up and down but I can't remove the slash...and its still muted. Problem solved after I restart,but it will come again. Before the update, I never have this issue.. Anyone has the same issue?
Sent from my SGH-T999 using xda premium
I haven't seen that one yet. Try reflashing the update or just flash the rom from wildchld. Wipe cache, dalvik and factoey reset and see if it continues.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
I haven't seen that one yet. Try reflashing the update or just flash the rom from wildchld. Wipe cache, dalvik and factoey reset and see if it continues.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Haven't got this either. I flashed the ROM from Wildchld.
I did factory reset 2 times... No help. It keeps coming back. I haven't rooted yet. Running on stock. I'm waiting for the official JB to see if this still exists..
Sent from my SGH-T999 using xda premium

com.android.phone force closure every time I boot up my Samsung Galaxy Note 2 LTE

Hi!
Okay so I recently flashed Cyanogen Mod and whenever I booted up my phone "com.android.phone" (I think it's the phone app?) would force close once and I'd never see it again unless I rebooted. This only began happening when I switched to Cyanogen Mod from my stock rom, I thought it was because of Cyanogen Mod so I flashed JB-MR1 Build 3 of AOKP (released a few hours ago) however the force closure is still occurring.
Does anyone have any idea of what might be causing this? I have tried clearing my cache, re flashing Cyanogen Mod, yet it still persists.
Any help would be appreciated!
Clear data is mandatory when moving from stock to aosp.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Clear data is mandatory when moving from stock to aosp.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I'm pretty sure I did that every time I flashed
Was cm released for lte version ?
Sent from my GT-N7100 using xda app-developers app
Is it possible that I'm flashing the wrong GAPPS.zip? I'm currently flashing gapps-jb-20121212-signed.zip for all my roms.
Gapps has nothing to do with com . android . phone
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Was cm released for lte version ?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
CM 10.1 was released as nightlies for Note 2 LTE (t0lte) and AOKP was released around 4 hours ago for the LTE version.
K just wanted to confirm you didn't flash N7100 version.
Try data and cache and dalvik and system wipe then flash stock rom.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
K just wanted to confirm you didn't flash N7100 version.
Try data and cache and dalvik and system wipe then flash stock rom.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
One thing I didn't do when reflashing roms, was clear dalvik cache, could this be the issue?
I fixed it by reverting back to a backup, however I don't get 4G connectivity now. How can I fix this?
Make a backup of your efs asap.
I am suspecting its related to it.
Sent from my GT-N7100 using xda app-developers app

Android is upgrading on every reboot

I upgraded to omega v12 doing full wipe and now every time i reboot i get the "Android is upgrading" message.
Which is kinda annoying.
So any way to fix this.
Can Motomotoos theme be the reason?
I flashed it after flashing v12.
Sent from my GT-N7100 using xda premium
try wiping delvic cache
No result
Still says Android is upgrading..
On each reboot. :-\
Sent from my GT-N7100 using xda premium

Note 2 wont booting stuck on "samsung gt-n7100"

Good evening,
My galaxy note 2, jb 4.1.2.
I decided to root, then using crash rom.
1. Im flashing to 4.1 (im kinda sloppy think zip file is 4.5)
2. Flashing to 4.5 (stuck in samsung gt-n7100 logo)
3. Flash to 4.4 it works.
4. I still trying to flash 4.5 and failed again.
5. Flash back to 4.4 it failed too !
6. And download 4.3 then flashing it, now it works !
The question is, is there something wrong? Any help please
Many thanks
Sent from my GT-N7100 using xda app-developers app
Download the latest version.
Do a mega wipe then install.
This will delete everything.
Always carry a efs backup though it won't delete efs.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Download the latest version.
Do a mega wipe then install.
This will delete everything.
Always carry a efs backup though it won't delete efs.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Where i can find the mega wipe installer? When im flashing crash rom, im always factory reset wipe cache and wipe dalvik cache. And still not working, so weird when i can succed install 4.4 then i cant installed back.
Sorry for my english.
Many thanks mate
Sent from my GT-N7100 using xda app-developers app
Here it goes dude.. http://forum.xda-developers.com/showthread.php?t=1983489
Sent from my GT-N7100 using xda premium
it has happened to me a few times... dont panic, you can either press the power button for several seconds or remove the battery. then try again. if it stays like that, remove battery and open recovery, install the rom again... it should work then
joseka22 said:
it has happened to me a few times... dont panic, you can either press the power button for several seconds or remove the battery. then try again. if it stays like that, remove battery and open recovery, install the rom again... it should work then
Click to expand...
Click to collapse
In the installer crash rom instruction, i should wipe cache, factory reset, wipe dalvic. Is it do that again? Or just flashed again?
Many thanks
Sent from my GT-N7100 using xda app-developers app

Wicked v10 Stuck at Samsung Screen

So I tried many times installing Wicked in my S4 and Everything going good with the installation now going in to the First boot which is that longest one like I was told But I Waited More The 20 Minutes On the Phone and It just seemed to gotten stuck on the Samsung s4 screen cause it was like throughout the whole time any suggestions ??? I'm Using the latest TWRP recovery and I Was On The NB4 Modem if that help
I'd boot into recovery and do a wipe.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I did and it was the same results
Sent from my SGH-M919 using Tapatalk
I read that you have to wipe the internal sd card ?
Sent from my SGH-M919 using Tapatalk
Wipe cache and Wipedata/factory reset
I Give It Another try then
Sent from my SGH-M919 using Tapatalk
Slayer809 said:
Wipe cache and Wipedata/factory reset
Click to expand...
Click to collapse
I guess I'm Giving up Now Cause I Have Tried everything , I've Done Factory Rest/Wipe and Even Advance wipe And It Still Boot In The Samsung S4 Screen And I Even Downloaded it Again Thinking it Was A Bad down But I got the same results :/ And After That I switched recovery think that would work Cause I Read Around Forums people Mentioning that The Latest TWRP Has Problems Flashing Roms Sooo I the Flashed CWM 6.0.4.4 Which Was the Latest one And Still that didn't Work :/ im I Missing A Step Or Something ?
Sent from my SGH-M919 using Tapatalk
Could try flashing an earlier version like wicked 9. And then try flashing vI0.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
Could try flashing an earlier version like wicked 9. And then try flashing vI0.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay Thanks For the help I'll give it a try
Sent from my SGH-M919 using Tapatalk
Still Did Not work :/ waited 15 minutes on the Splash screen but still nothing and i made sure i selected something during the installation like they mentioned .. There Might Something wrong with my phone Can It possibly be the stock kernel ?

Categories

Resources