Develop Bugs

Help! Phone not bricked, but won't boot.

Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?

Try flashing the stock tar in odin if nothing else works.

DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok

I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you

Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol

fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store

DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha

[Q] Boot hang after flashing using Odin back to stock rooted

Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...

rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.

Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!

rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.

avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD

rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.

Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.

rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.

avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.

rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.

When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium

That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).

crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks

NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.

I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.

[Q] huge problem, need help

this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
It is a rooted samsung galaxy s4 M919 from t-mobile

is it stock rooted or what ROM are you running ?what kernel? what settings ? what mods? we need some detail sir but for starters if you can get it to boot try *#2263# and if its not set to automatic try clicking your options auto is the default setting

bobolinko said:
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
Remove your sd card sim card and battery let set 10 minutes put back in see if the message is still present if so you might need a new sim card.
Click to expand...
Click to collapse

I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!

Might just be a lemon. I would just flash back to stock then take the phone and get a replacement.

bobolinko said:
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Click to expand...
Click to collapse
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app

tylerholbrook said:
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!

bobolinko said:
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
Click to expand...
Click to collapse
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app

tylerholbrook said:
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...

Glad I could help. The modem isn't in your back up that's why back ups won't fix this problem. As for apps, it's from syncing your Google account. Aloha
Sent from my SGH-M919 using xda app-developers app

bobolinko said:
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Click to expand...
Click to collapse
If you chose to have Google back up and restore your apps, it will do just that.

Lost root somehow, any ideas how?

I turned my s3 off for about a month while I used my note2. When I turned it off it was rooted with twr recovery and running a custom Rom. When I turned it back on the Rom was still running however I did loose all the widgets I was using. Over night titanium tried to run the scheduled backup redo. Then in the morning I noticed titanium said it could not gain root access. I tried other apps that require root and none will gain access. The super user app is still there but says there is no root. It's simple enough to re-root but I'm really curious as to what happened. Any ideas?
Sent from my SGH-T999 using XDA Premium 4 mobile app

Please Specify Rom and Android Version.
In short, if your TWRP recovery is intact try a factory reset from there.

Thanks Persius, I haven't tried to go into recovery since I have to do it manually cause I'm not sure what will happen if it's not there. My computer is broke right now so I'm limited. It's been since the s3 first came out that I installed the Rom so I'm not really sure which one I'm on but it says JZO 54, and it's 4.1.2 Thanks again for your help

bls2633 said:
Thanks Persius, I haven't tried to go into recovery since I have to do it manually cause I'm not sure what will happen if it's not there. My computer is broke right now so I'm limited. It's been since the s3 first came out that I installed the Rom so I'm not really sure which one I'm on but it says JZO 54, and it's 4.1.2 Thanks again for your help
Click to expand...
Click to collapse
Say... Are you sure we talking about an SIII or an S-II ?? That sounds like the 4.1.2 Stock of an S II. What does it say under Settings > About Phone > Model Number ?
Turn off completely then Hit Volumn Up + Home +Power all at the same time. Wait for 3 minutes or so with all 3 pressed. You will see Recovery come on. Let go of all 3 buttons and then do a Factory Reset in the recovery.

Thanks again, under build that's what it says, jzo 54, I think it might be Liquid Smooth. And it is an s3. I will try to go into recovery if you don't think anything will happen if that's not there either. Something else weird I just thought of is I also had some strange kiddie like themes and apps I never put there. It's like someone else used my phone but that's not possible as I saw it every day and live alone. Strange. Any way, thanks again

bls2633 said:
Thanks again, under build that's what it says, jzo 54, I think it might be Liquid Smooth. And it is an s3. I will try to go into recovery if you don't think anything will happen if that's not there either. Something else weird I just thought of is I also had some strange kiddie like themes and apps I never put there. It's like someone else used my phone but that's not possible as I saw it every day and live alone. Strange. Any way, thanks again
Click to expand...
Click to collapse
Yes its safe to Go into Recovery. Go ahead and do a Factory Reset. Let me know how that goes.

Ok, did the factory reset and went ahead and did the ota update to 4.0 I'm going to root again. Do you have any suggestions on a good Rom? Also what is the best way to root these days and best recovery? Thanks Perseus I appreciate your help and advice
Sent from my SGH-T999 using XDA Premium 4 mobile app

I am confused. Wasn't (or shouldn't it be ) your S3 already on the JB 4.1 ? What did you mean by OTA update to 4.0 ? Are you referring to the OTA Update to 4.3 ?
I can not comment on Rooting unless I know which os version you have.

Sorry, was a misprint. Yes, went to 4.3
Sent from my SGH-T999 using XDA Premium 4 mobile app

So if you still have TWRP then flash Superuser from Recovery. Lookup its thread here on XDA.
However, with the Knox being present and SELinux in Enforcing state, your chances of Rooting are slim.
Please don't brick your device.

Unfortunately settings has been stopped?

What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.

I'm sure I'm not the first one and only one who got this message. Could anybody please help?
Thank you very much!

testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.

Irwenzhao said:
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Click to expand...
Click to collapse
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...

testrider said:
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...
Click to expand...
Click to collapse
U could try reflashing stock rom if u don't want a custom one.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.

testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.

0.o said:
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.
Click to expand...
Click to collapse
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM

testrider said:
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM
Click to expand...
Click to collapse
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app

kintwofan said:
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?

testrider said:
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?
Click to expand...
Click to collapse
Yep right after it happens. If there is something that triggers it. Reboot, to clear the log, then trigger the fc and pull log
Sent from my SGH-T889 using xda app-developers app