Related
Upon every reboot I get the following error message:
Your device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source... ... ...
It goes on to say press the UP VOL button to hard reset or any other button to continue.
I press any other button and it proceeds to boot correctly.
Any way to disable the message?
VZW TP2 - Stock 6.5 ROM
EDIT / UPDATE: If don't touch anything when it is on this screen it will eventually continue to boot normally... so again I would just like to disable this message if at all possible.
Anybody???
Or maybe an idea of where to look for log files so I can tell what specifically is causing it?
I've had the same message at least twice now. Almost had a heart attack the first time. Mine also rebooted fine after a minute or so. Not sure what caused this.
For me this happens everytime I reboot.
I did a hard reset and after installing and configuring everything, it is happening again.
It isn't affecting anything, just annoying.
Anybody?
Having this screen come up after every reboot is really annoying.
Surely somebody has had this happen before..
after you hard reset did you reinstall all your applications again... is that what you mean by configured it? If so it's likely one of your programs that's causing it. If you didn't install anything and it still pooched out like that then, well I'm stumped!
It started happening after I installed everything, but everything works on it.
There has to be some type of log file somewhere that will tell me what is causing it
You may just want to go and take the time to install a program and then see if it happens... when you get to the one that you know causes it.. uninstall it and see if the issue is still there. If not then carry on with installing all your other aps you have left doing the same thing to see if any of them cause the issue. It may take some time to do but it cant take along longer then waiting around for someone to chime in on some advice for you. Gotta do what you gotta do right?
Aaron McCarthy said:
You may just want to go and take the time to install a program and then see if it happens... when you get to the one that you know causes it.. uninstall it and see if the issue is still there. If not then carry on with installing all your other aps you have left doing the same thing to see if any of them cause the issue. It may take some time to do but it cant take along longer then waiting around for someone to chime in on some advice for you. Gotta do what you gotta do right?
Click to expand...
Click to collapse
I'd rather wait than do a hard reset
brent372 said:
I'd rather wait than do a hard reset
Click to expand...
Click to collapse
I would do a task29 then reinstall
lufc said:
I would do a task29 then reinstall
Click to expand...
Click to collapse
What is task29?
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.
It seems that my menu and back button is possibly broken cause it is not working in "some time". Working then few min, not working.
So is it a hardware problem? or firmware problem? possible conflict in firmwares? I noticed it when i flashed DXLC1 from DXLB1. I've try hybrid v3.0 and repencis v3.0, same problem occurred.
Anybody have the same problem?
makeoutactics said:
It seems that my menu and back button is possibly broken cause it is not working in "some time". Working then few min, not working.
So is it a hardware problem? or firmware problem? possible conflict in firmwares? I noticed it when i flashed DXLC1 from DXLB1. I've try hybrid v3.0 and repencis v3.0, same problem occurred.
Anybody have the same problem?
Click to expand...
Click to collapse
I dont think flashing would damage your buttons. Its not the problem with only you. It happens with me too but a restart resolves it. Have you ever dropped your phone or something?? That could be the only possible reason for that problem
if only they put the question if FAQ section...this forum will looks nice and they'll get the answer.
hell_lock said:
I dont think flashing would damage your buttons. Its not the problem with only you. It happens with me too but a restart resolves it. Have you ever dropped your phone or something?? That could be the only possible reason for that problem
Click to expand...
Click to collapse
Never been dropped. Yeah restarting resolves it temporarily,for me, then it will come back again.
search a post about cleaning the screen in accessories secction. read the method suggested below. try it.
kurotsugi said:
if only they put the question if FAQ section...this forum will looks nice and they'll get the answer.
Click to expand...
Click to collapse
Oh. wrong post? Can mods merge it? or perhaps delete this thread.
kurotsugi said:
search a post about cleaning the screen in accessories secction. read the method suggested below. try it.
Click to expand...
Click to collapse
Thanks, i will try it. I'm out of thanks. Will press it tomorrow.
no need to do that...give your thanks for the real dev instead of me
Can someone help me with this? I found that if you remove sprintandroidextension.apk it goes away but it didnt. I also found that by removing SprintOMADMConnMOPlugin.apk it goes away, but i cant find it on my Galaxy note 2. Any ideas? Thanks in advance.
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
digitallogik said:
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Click to expand...
Click to collapse
I tried doing that many times but it never worked, it just gave me an error.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
Thank you! it worked
interesting. found this thread buried, and there still seem to be many people with this issue... seemingly related to the chameleon FCs some are getting, somehow possibly related to the LK8 update and/or a return to an earlier stock version...
digitallogik said:
If you let it go all the way through HFA once it won't return.
Click to expand...
Click to collapse
I've let it complete (personally) aprox 20+ times, so no go.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
could the "fix" really be this simple? (at work, can't test this right now.)
kingdazy said:
could the "fix" really be this simple? (at work, can't test this right now.)
Click to expand...
Click to collapse
yes, and you can delete the activation.apk as well to stop it
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
thanks, stopped the HFA, still have the chameleon errors to deal with...
t3project said:
yes, and you can delete the activation.apk as well to stop it
Click to expand...
Click to collapse
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
kingdazy said:
thanks, stopped the HFA, still have the chameleon errors to deal with...
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
Click to expand...
Click to collapse
your solution is to thoroughly wipe and reflash whatever rom you are running.
t3project said:
your solution is to thoroughly wipe and reflash whatever rom you are running.
Click to expand...
Click to collapse
I would have thought so too. As I've been advised by other as well. But...
I have, at least five times, run a return to stock, both through ODIN and OneClicks.
I still have the issue. Baffles the mind. Makes little sense. But there it is. And I'm not the only one.
(Just so it's noted, and before you accuse me otherwise, I am not new at this, and I follow directions fastidiously. I've never once had a problem that I didn't cause myself, and I've always been able to fix them by further reading/researching.)
Just for SnG's I'll quote myself and others from a few other posts in other threads:
kingdazy said:
well, this is annoying. I seem to be stuck with the "hands free activation" and chameleon fc.
i'm assuming a nice total stock one click should fix it?
Click to expand...
Click to collapse
garwynn said:
Sure should! Please try the stock restore or rooted restore.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
kingdazy said:
interestingly, it didn't fix it... "preparing network", "hands free" and chameleon FC on every reboot. this is after the rooted full restore OC. what am I missing? weird.
(history: I was rooted stock w/ twrp from the mskip toolkit method of rooting, got rid of twrp using the mrRobinson stock w/ root, and flashed the sxtp update to lk8, got a wifi failbug and tried to get back to stock rooted using mrRobinson and started getting this issue. lol. ok. so... one-clicked your rooted full restore, still there. is that even possible?)
well, my phone seems to work, as long as I don't reboot.
but I find it worrisome.
have to sleep for work now, but if you had any advice for things to try when I wake up, let me know? thanks dood.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
kingdazy said:
Just my 2 cents, my experience with this error.
I'm getting the Chameleon FC, and the persistent HandsFree Activation on every reboot. All started when I lost wifi on the LK8 update zip (I was rooted, thanks to Voodoo OTA rootkeep), and tried to get back to LJC...
And this morning, I tried the following:
Installed TWRP with GooManage, restored a nandroid from my orig rooting using the toolkit, no luck, same two errors.
So then I OneClicked the Full Restore (SPH-L900_LJC_Stock_Restore.exe), and wtf, still there.
As I mentioned in my quote, it (the Note2) works, not broken, but I find the persistent error worrisome.
I am open to criticism, suggestions, whatever. What am I missing?
Click to expand...
Click to collapse
Itchiee said:
I'm having similar issues, I was on the release before LK8, then updated to LK8 but wanted to start over again.
Once i downgraded to LJ1? the hands free bug kept popping up every reboot, until I moved onto to LJC then LK8 update file which is fine.
I'm trying to figure out myself how to go back to the original firmware (pre any updates) without the issues... /subscribed.
Wonder if this is tied into it somehow...
I dunno, my head is exploding reading all these posts, replies.... 5 different versions of restore.
Click to expand...
Click to collapse
evilgenyus said:
I have tried the one click restores back to ljc and the original tar, and I still have the hands free activation issue and the chameleon error. And when I update to lk8 I get no wifi. I have tried returning to stock about 4 times and then updated to lk8 with the same results. I always go back to ljc bc I need wifi.
Click to expand...
Click to collapse
kingdazy said:
interestingly, even using a stock oneclick full restore (and even using a TAR in Odin), still have the handsfree repetition and chameleon FCs. (lol, I'm not complaining really, it's early in the dev life for this device I suppose. )
Also, I've been reading that re-flashing the LK8 update.zip (via sxtp?) while it seems to fix the HFA and ChameleonFC, it kills the wifi? (it killed my wifi after aprox 2 days use, when I orig updated...)
Click to expand...
Click to collapse
garwynn said:
I'm starting to wonder if the move to 4.1.2 changed something that isn't handled properly by older versions. Without a gn2 will be hard to confirm... but I may be resolving that soon as well!
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It would apear that something in the LK8 changes ... something. Permanently?
So, any new advice would be welcome...?
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
smooth703 said:
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
fine question, but without knowing what the chameleon apk does, i'm reluctant to f**k with it.
anyone know? (a goog search gave me nothing...except this XDA rom w/ a fix...? I'm going to try n PM him...)
and again, my concern is the issue seems to be more significant, seeing as a Full Wipe to Stock doesn't fix it.
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
sxtp site said:
If you need to clear NVRAM/Sprint data login info, perform a ##72786# reset from the Dialer and enter MSL.
Type getprop ril.MSL in adb shell or terminal to retrieve your MSL.
Click to expand...
Click to collapse
kingdazy said:
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
Click to expand...
Click to collapse
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
shiftr182 said:
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
Click to expand...
Click to collapse
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
kingdazy said:
it would seem that the factors that all of us with this issue have in common are: a) rooting w/ ToolKit ver2 b) flashing LK8 update zip c) trying to return to stock LJC/LJ1 because of a wifi problem... please chime in if you have the issue, but not one of those factors?
After everything, I just returned to stock LJC w/ Flash Counter @ 0 (no) w/ the errors still present, took it into Sprint store said, 'hey guys, this is weird, i've got a persistent error, won't go away after resetting my phone." (IE, acted dumb enough to not have rooted/flashed unofficial shtuff/etc, but smart enough to know that it's a real issue), they looked at it, asked a few obvious questions, replaced it, because obviously something was wrong in a permanent way. I want to a corp store, not a "repair center". I think it was a good thing that these guys were not super techie.
I told them as little as possible, that I had a "wifi issue after an update, tried full reset (through the android settings menu, of course), and the problem didn't go away, no matter what". Once they heard that I had done a full factory reset, and saw the problem/error happen, it was a no-brainer to swap out.
I'll be avoiding the LK8 leak for now, and frankly gun-shy about the toolkit.
Click to expand...
Click to collapse
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
kingdazy said:
ok, to get back to stock, first use this OneClick to get to Stock+Root, it will wipe ALL internal memory except SD card:
http://rwilco12.androidfilehost.com...sung Galaxy Note II (SPH-L900)/LJC/ROM/Rooted
Instructions are here:
http://www.sxtpdevelopers.com/showt...-TAR-SPH-L900-LJC-(LJC-Modem-Kernel-ROM-Stock)
then use TriangleAway, this will set your counter at 0 (reads as "no" in download mode). it should also say "Official" And "Samsung Official"
Then, if you want to get Total Stock unrooted, for returns to Sprint, or any other reason, use Odin (not mobile) to flash this:
http://www.androidfilehost.com/?fid=9390214368362234120
Instructions for flashing that are here:
http://www.sxtpdevelopers.com/showthread.php?76-TAR-STOCK-Full-L900VPALJC-quot-Back-to-Stock-quot
After I did those things, I was stock unrooted, no flash count.
Click to expand...
Click to collapse
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Yeah, I have to give it up to garwynn, he hooked me up with the pit file for our phone. Good people.
ProjectROM 2.1
Did a clean install and I get this as well =/
RussellAlan said:
Did a clean install and I get this as well =/
Click to expand...
Click to collapse
a clean install, coming from what? And what did you use to get back to stock? (Just asking so people will have a clear history of what is causing this. In case a dev wants to look closer at the problem, have clear ideas where to start)
Sent from my SPH-L900 using xda premium
ceabbott2 said:
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
+1
Sent from my galaxy note 2....
kingdazy said:
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Click to expand...
Click to collapse
I try that method but mine still show 1 on the counter. Is there a way to get rid of that?
i have a cayogenmod rom stable 10.1.3 and after i play a little on the phone its restart....someone can help me plz?
please help me.....
i dont know what to do please help me fix it:crying:
try another ROM.
You have given so little information, how can you expect people to give good direction based on your minimal explanation?
Seriously, try another ROM or another kernel or reflash current ROM after wiping. Good luck.
tweeny80 said:
try another ROM.
You have given so little information, how can you expect people to give good direction based on your minimal explanation?
Seriously, try another ROM or another kernel or reflash current ROM after wiping. Good luck.
Click to expand...
Click to collapse
what information i need to write? sorry that im asking alot but I'm really upset about it....and i tried now to flash the CM11 on my phone and same problem...maybe it is because my modem? or somthing else i don't know what to do...
ohhh and one more thing when i charge my phone it is'nt restart it is stuck on the image when the device is off.
please tell me what info' i need to write so someone can help me?
sorry for my bad english^^
Ynot12 said:
what information i need to write? sorry that im asking alot but I'm really upset about it....and i tried now to flash the CM11 on my phone and same problem...maybe it is because my modem? or somthing else i don't know what to do...
ohhh and one more thing when i charge my phone it is'nt restart it is stuck on the image when the device is off.
please tell me what info' i need to write so someone can help me?
sorry for my bad english^^
Click to expand...
Click to collapse
*)you have to write your steps of flashing.... and :
*)Which ROM you came from before CM 10?
*)Did you do full wipe?
*)After which things you do and your device started to restart all the time?
More details, and more ppl can help you.
antique_sonic said:
*)you have to write your steps of flashing.... and :
*)Which ROM you came from before CM 10?
*)Did you do full wipe?
*)After which things you do and your device started to restart all the time?
More details, and more ppl can help you.
Click to expand...
Click to collapse
ok first:i flashed cm10.1.3 from stock rom 4.1.2 and this morning i flashed cm11 from 10.1.3.
yes i did full wipe (data/factory reset,dalvik,cashe,and format/preload) i have the last version of CWM (6.0.4.3)
i had problem with IMEI (0049) and i fixed it with flashing this tow modems-Modem DDEMG2 and modem_XXDME4.
i had binary count of 6 and i bought traingle away and now its 0.
and when my device go to restart It's not often at the same time, but when i plug my charger it go offline and doesnt restart its stuck untill i take the battery off and then click the power botuum till next time it go to restart.
Edit: I think I found out what the problem is but I do not know how to fix it. The device does restart every time it is not taking advantage of the battery - I mean that when I put the device near me or charge it. it goes restart again but when it is charging is not turned on. Someone who knows how to handle it?
Second Edit: I've done in the System of the developer when the handset is charging the screen does not turn off. When the device does not enter sleep mode so it does not restarts.
Why is this happening? How do I fix this?
someone please help me....
please someone help me im sooo upset.....:crying::crying::crying:
someone must know what should i do
Ynot12 said:
please someone help me im sooo upset.....:crying::crying::crying:
someone must know what should i do
Click to expand...
Click to collapse
After your device restarts itself, go to ADB terminal then do this
Code:
$ su
# cat /proc/last_kmsg > /sdcard/last_kmsg.txt
post your last_kmsg.txt in your internal storage here (as an attached file)
[email protected] said:
After your device restarts itself, go to ADB terminal then do this
Code:
$ su
# cat /proc/last_kmsg > /sdcard/last_kmsg.txt
post your last_kmsg.txt in your internal storage here (as an attached file)
Click to expand...
Click to collapse
what it is should do? and how i go to ADB terminal? oh and one more question-if i will change my karnel it will help me?
Ynot12 said:
what it is should do? and how i go to ADB terminal? oh and one more question-if i will change my karnel it will help me?
Click to expand...
Click to collapse
It will likely tell us why your device is restarting.
If you don't know how to get in to the adb, forget it.
[email protected] said:
It will likely tell us why your device is restarting.
If you don't know how to get in to the adb, forget it.
Click to expand...
Click to collapse
I think i did it...i have a file in my device with the name "logcat.txt" and its something like 380kb and when i open this i see a long text..
This is it? Please help me
Ynot12 said:
I think i did it...i have a file in my device with the name "logcat.txt" and its something like 380kb and when i open this i see a long text..
This is it? Please help me
Click to expand...
Click to collapse
No it's not.
kmsg = Kernel Messages, useful for kernel panics, restarts etc (your case)
Last_kmsg = the previous kmsg that contains the error caused kernel to panic.
search for how to install adb in this forum. I can't tell you the whole story from the beginning.
[email protected] said:
No it's not.
kmsg = Kernel Messages, useful for kernel panics, restarts etc (your case)
Last_kmsg = the previous kmsg that contains the error caused kernel to panic.
search for how to install adb in this forum. I can't tell you the whole story from the beginning.
Click to expand...
Click to collapse
Ok i will check it.
Do u have email or something that we can chat?
Sent from my GT-N7100 using xda app-developers app
Ynot12 said:
Ok i will check it.
Do u have email or something that we can chat?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I'd like to keep this conversation here because I might not be your savior
I just had the same symptoms few days ago. My Note2 was rebooting by itself with no reason.
I checked last_kmsg, it turned out EXT4-fs error http://pastebin.com/r3UNm9AS
I was using 4.3 rom with knox-free bootloader and wifi patch.
This combination, somehow was causing this error, kernel was entering panic mode due to the mount options used in fstab.
I went back to 4.1.2 with stock bootloader, everything is fine since then.
[email protected] said:
I'd like to keep this conversation here because I might not be your savior
I just had the same symptoms few days ago. My Note2 was rebooting by itself with no reason.
I checked last_kmsg, it turned out EXT4-fs error http://pastebin.com/r3UNm9AS
I was using 4.3 rom with knox-free bootloader and wifi patch.
This combination, somehow was causing this error, kernel was entering panic mode due to the mount options used in fstab.
I went back to 4.1.2 with stock bootloader, everything is fine since then.
Click to expand...
Click to collapse
So maybe should i change my kernel?
Sent from my GT-N7100 using xda app-developers app
[email protected] said:
I'd like to keep this conversation here because I might not be your savior
I just had the same symptoms few days ago. My Note2 was rebooting by itself with no reason.
I checked last_kmsg, it turned out EXT4-fs error http://pastebin.com/r3UNm9AS
I was using 4.3 rom with knox-free bootloader and wifi patch.
This combination, somehow was causing this error, kernel was entering panic mode due to the mount options used in fstab.
I went back to 4.1.2 with stock bootloader, everything is fine since then.
Click to expand...
Click to collapse
View attachment last_kmsg.txt
i hope this is it....
Ynot12 said:
View attachment 2527101
i hope this is it....
Click to expand...
Click to collapse
Yes it is. But we need this to be taken at the first boot after your device restarts by itself.
BTW looks like you have "failed to power up wifi chip" errors
I suggest you to use stock kernel and see if there such errors still exist.
[email protected] said:
Yes it is. But we need this to be taken at the first boot after your device restarts by itself.
BTW looks like you have "failed to power up wifi chip" errors
I suggest you to use stock kernel and see if there such errors still exist.
Click to expand...
Click to collapse
I use now a stock rom with stock kernel and to get my network connection fix I used this video https://www.youtube.com/watch?v=i7K6RDVRBhs&feature=youtube_gdata_player
Please someone help me because after I used this video installations I get the imei fixed but my phones reboot all the time
Sent from my GT-N7100 using xda app-developers app
Please someone help me im begging for helppp
Sent from my GT-N7100 using xda app-developers app
Ynot12 said:
Please someone help me im begging for helppp
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
All the files given on that video link belong to S3, I don't know if they are same to Note2(despite the video title).
I would never flash those files because I'm convinced.
Firstly I would search in this forum for the people who has the same error.
I would read their attempts and results.
I would find proper files that are for my phone model. Etc, mine is n7100, so I should never flash the files for n7105!!! I would use %100 stock files to avoid errors.
I would check everything twice, then flash.
But you look like you do the opposite. You do flash first, then think
Find a stock firmware that is exactly for your model and for your country from here http://forum.xda-developers.com/showpost.php?p=31987995&postcount=9
Then enter to recovery and do a factory reset, cache wipe.