Hi guys,
i'm running AOKP Build 3 , fresh install, Apps downloaded through the Play Store and restored data for some apps ( no system apps) via Titanium Backup.
But from time to time i notice hot reboots. I turn the screen off, but it will not get on again. After about 1-2 minutes the phone reboots ( i see the Boot animation).
Except all is running smooth. Also i tried the latest Franco Kernel, but same Problem.
Could someone look into the last_kmsg i pulled right after a hot reboot? Maybe a dev or someone with more knowledge than me can find the Problem.
Thx,
Ebi
https://www.dropbox.com/s/xvetw35abc8yti3/last_kmsg
Pastebin:
http://pastebin.com/wZ1JJVyW
What kernel are you using? And are you using supersu, or superuser? I had the same issue b4 random reboots, it seemed that the issue was root not sticking in and also the Franco kernel, think my phone didn't like it, I had to re-root and re-install cwm recovery, using the toolkit and that seemed to help, I had the issue with every ROM I flashed, hope It helps
Sent from my Galaxy Nexus using Tapatalk 2
I faced the constant reboot issue on stock JB... apparently, switching to CM10 or AOKP helped (I've stuck to AOKP since it contains the stock apps... sans the bugs present in all AOSP roms).
Are you sure it's a root problem? I'll go try it out now and check.
aeoveu said:
I faced the constant reboot issue on stock JB... apparently, switching to CM10 or AOKP helped (I've stuck to AOKP since it contains the stock apps... sans the bugs present in all AOSP roms).
Are you sure it's a root problem? I'll go try it out now and check.
Click to expand...
Click to collapse
I used the Stock AOKP Kernel, and later the Franco. And both had the same issue.
Will try suprakarmas way
It all points at the root not sticking with the Franco kernel app as well for some reason once I started messing with that sucker I started having the reboots, if the problem persist I advice to use the toolkit to reinstall stock ROM, re-root and reinstall custom recovery, I had teamwins but I went back to cwm, it all has been good am on android revolution HD am staying away from aokp and cm10 till there's a stable release
Sent from my Galaxy Nexus using Tapatalk 2
I was seeing a lot or partition remounts (not sure which one as it was listed as the physical block device) as well as an emergency read only remount in your log.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
I was seeing a lot or partition remounts (not sure which one as it was listed as the physical block device) as well as an emergency read only remount in your log.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Any idea what could cause this?
EbiEre said:
Hi guys,
i'm running AOKP Build 3 , fresh install, Apps downloaded through the Play Store and restored data for some apps ( no system apps) via Titanium Backup.
But from time to time i notice hot reboots. I turn the screen off, but it will not get on again. After about 1-2 minutes the phone reboots ( i see the Boot animation).
Except all is running smooth. Also i tried the latest Franco Kernel, but same Problem.
Could someone look into the last_kmsg i pulled right after a hot reboot? Maybe a dev or someone with more knowledge than me can find the Problem.
Thx,
Ebi
https://www.dropbox.com/s/xvetw35abc8yti3/last_kmsg
Pastebin:
http://pastebin.com/wZ1JJVyW
Click to expand...
Click to collapse
that log is from cm kernel??
Code:
[ 26.531280] Restarting Linux version 3.0.36-cyanogenmod-geb0f696 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Thu Jul 12 13:52:24 PDT 2012
what's going on? i thought we were dealing with aokp and/or aokp+franco.
No, this was after flashing Francos kernel. Don't know why it is not shown but maybe this was the problem, a bad flash?
What I did was rerooting the phone with the toolkit and re flash Francos kernel. No reboot till then, but what I noticed after switching the phone on this morning the cpu settings are gone. They are back at the defaults...
Is this a known issue?
Will report back after work.
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
ahem i wouldnt know. dont run aokp or cm right now.
i would advise you first to learn how to start fresh google way. forget toolkits. read efrant's stickies, they're in his sig. good, know you all about fastboot and adb basics.
reflash latest cwm non-touch. reflash aokp in cwm, you dont need to root to flash a rom. use it like that for a couple of days. no issues risen? reflash franco in cwm. this is how you troubleshoot.
sent from my i9250
So, it seems that for some reason, flashing the Franco kernel thru his app causes the reboots, and, either thru Google or toolkit, going back to stock, re-rooting or no need to do so, reinstalling cwm recovery solves the issue, at least on my end, just my 2 cents \„„/
Sent from my Galaxy Nexus using Tapatalk 2
Ok work is over and no reboots since about 20hours
I think the rerooting or the re flashing of the recovery, which is one step in rerooting, solved the problem.
Thx everybody
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
EbiEre said:
Ok work is over and no reboots since about 20hours
I think the rerooting or the re flashing of the recovery, which is one step in rerooting, solved the problem.
Thx everybody
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Click to expand...
Click to collapse
please edit the title thread with the [SOLVED] tag.
Hey guys,
me again.
The problems are back
I don't know why, but i don't get a rom to run more than 1 1/2 days without having a reboot.
Today i also tried the Odin Flash. So know i am running a stock Rom, just rooted. The whole day it was fine, i used my phone the normal way. But now i am back at home, and what? I pressed the power button to turn the screen off and instantly a second time to get it back, but it didn't come back. Black screen.. and some seconds later i see the Boot Animation.
After it was back i tried to find the last_kmsg, but it is not there in the stock Rom.
Is ther another place to find something like a log?
Hope to get some help
Cheers
Could someone tell me the most efficient method to go back to full stock, and reroot again?
Maybe i did something wrong during this process !? Everything i tried to do seems not to work :/
EbiEre said:
Hey guys,
me again.
The problems are back
I don't know why, but i don't get a rom to run more than 1 1/2 days without having a reboot.
Today i also tried the Odin Flash. So know i am running a stock Rom, just rooted. The whole day it was fine, i used my phone the normal way. But now i am back at home, and what? I pressed the power button to turn the screen off and instantly a second time to get it back, but it didn't come back. Black screen.. and some seconds later i see the Boot Animation.
After it was back i tried to find the last_kmsg, but it is not there in the stock Rom.
Is ther another place to find something like a log?
Hope to get some help
Cheers
Could someone tell me the most efficient method to go back to full stock, and reroot again?
Maybe i did something wrong during this process !? Everything i tried to do seems not to work :/
Click to expand...
Click to collapse
You should have edited thread title again, removing [SOLVED] tag; I just happened to come back because I wasn't sure if I had checked this one already or not.
/proc/last_kmsg should be there. How did you try getting it, adb or from a file explorer on the device? I'm at work so no adb here, but I've just checked and /proc/last_kmsg is there for me. Not sure if factory image from Google doesn't have it, but it should, I'm running my own build from JZO54K (android_4.1.2_r1), and I believe this is the closest to the factory image as it gets.
As for your last question, I already told you: read this thread.
bk201doesntexist said:
You should have edited thread title again, removing [SOLVED] tag; I just happened to come back because I wasn't sure if I had checked this one already or not.
/proc/last_kmsg should be there. How did you try getting it, adb or from a file explorer on the device? I'm at work so no adb here, but I've just checked and /proc/last_kmsg is there for me. Not sure if factory image from Google doesn't have it, but it should, I'm running my own build from JZO54K (android_4.1.2_r1), and I believe this is the closest to the factory image as it gets.
As for your last question, I already told you: read this thread.
Click to expand...
Click to collapse
Ok i found the last_kmsg but it is really big and i only See a line with omap and while no Data requested... Again and again.
Will have a closer look at it later and Maybe Post it from my PC.
But before that i will follow your guide and hope to solve the issue.
Btw good morning
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
I'm back, i followed the guide, did everything and just rooted my Phone. Except that everything is original.
More than 1 day i had no issues, but today... reboot. I didn't do anything, at first it happened in the morning at work, but i think it was not a "full" reboot, because in the about phone menu i saw a on time around 8 hours.
But later the phone was just lying at my table and suddenly i saw the boot animation. I have no idea what to do.
What i got is the last_kmsg, but it's really big again so i was just able to copy a little thing of it. I don't know how to find the exact time of the reboot so i hope it is inside this pastebin:
http://pastebin.com/raw.php?i=xZatKns5
Any ideas? Is the reboot shown there?
What i will try is to get a new sim, mine is very old, maybe this could be a solution!? Except i have no idea .. could it be a hardware issue?
Cheers
Edit: Just an idea, could it have something to do with the baseband? I read a lot of errors or something like that related to omap things.. !?
Can I suggest you they flashing another kernel - one with SmartReflex off? Faux's kernel (v22) works... so long as you have the version WITHOUT SmartReflex.
Well... it works for me. SmartReflex and my phone hate each other (it happened one, random day... no rhyme kr reason to its occurance). And I don't undervolt.
sent from my mini tractor
What exactly is smart Reflex?
Iam still running the Stock Rom just rooted and the Problem changed a bit . I did not have real reboots, 1-2 Times a Day the screen keeps beeing Black if i Switch it on. But After some seconds it is back and runs as if nothing happened. So not real a Reboot But a relatively long break...
Will wait for my New sim now...
Dont know if i should try a custom Rom till then.
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Smart Reflex is some automatic voltage/undervolting the kernel performs in order to save some battery. It comes enabled with the stock kernel... and for me, that's the cause of my reboots (and kmsg wasn't very helpful except for the fact that some MPU clock was being reset... and there's an option [to disable it] with the Smart Reflex parameters).
Soooo.... I turned it off altogether.
Rarely do I see blackouts for a second while my phone screen is on and I'm doing something on it. Before, it would reboot without warning.
If you're in the stipulated warranty timeframe, try getting it replaced and see if your new unit fixes it... else, try a new kernel.
PS: trickster mod is a very useful app... hint hint.
sent from my mini tractor
Related
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
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
Last month, my gnex suddenly rebooted itself when texting, then it just stuck in bootloop forever.
I got it work again only after several times of factory reset and even pushing factory image.
I was using xenon + franco at that time.
However, 3 days ago it rebooted itself again when playing a music app, then the bootloop problem happened again. Somehow it could boot, but within a minute, it reboots and bootloops again.
i was using xylon + ak kernel this time.
I started to think if this is due to hardware problem.. and i took it to store yesterday after pushing the factory image to it. they said this is due to some incompatibility of some apps... (i dun understand why factory image could have this issue...) and did a recovery for me. My phone is reset back to 4.0.4 and it seemed working fine..
Then i pushed back the 4.2.1 factory image to it and still nothing happened. i started flashing back xylon and ak kernel to see if it works. It did run perfect for the whole night until this morning. When i was installing some ordinary apps, eg. air, skout, it rebooted itself again...
Flashing factory image of 4.2.1, 4.1.2, and even 4.0.4 all do not work.
it got past the google screen, and then to the bootanimation for a few seconds and it freezes and color seems weird, and then reboot again.
i have tried flashing through the toolkit and also through fastboot command..
does anyone know what is the problem causing this...
thanks in advance.
Anyone help please..
thyau said:
Anyone help please..
Click to expand...
Click to collapse
ok lets see if my craziness can help lol
ok this will seem crazy but it is a last resort which i did the other day .
if you have nothing to lose do this its a 50-50 shot
but first
what recovery and what toolkit do you have before i tell you this
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
thyau said:
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
Click to expand...
Click to collapse
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Alpha_wolf said:
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Click to expand...
Click to collapse
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
thyau said:
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
Click to expand...
Click to collapse
nothing to lose right? might as well try anything lol
sounds like your device might have a problem with its internal storage
Alpha_wolf said:
nothing to lose right? might as well try anything lol
Click to expand...
Click to collapse
All user data has been lost due to the crash already, really nth to lose.. lol
simms22 said:
sounds like your device might have a problem with its internal storage
Click to expand...
Click to collapse
You mean physically right??
thyau said:
All user data has been lost due to the crash already, really nth to lose.. lol
You mean physically right??
Click to expand...
Click to collapse
yea, physically. when/if it finally goes, you wont be able to recover from the bootloop.
simms22 said:
yea, physically. when it finally goes, you wont be able to recover from the bootloop.
Click to expand...
Click to collapse
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
thyau said:
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
Click to expand...
Click to collapse
well, it is a common issue with the nexus devices without a sd slot(nexus s and the galaxy nexus).
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
thyau said:
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
Click to expand...
Click to collapse
Op the same thing is happening to me, i also was on xylon and it was running fine and it just started bootlooping. i tried everything toolkit, flashing factory image lie you did and nothing, the only one that works now is ics stock 4.0.4 .if i try any other rom stock or custom the bootloops starts again and it wont boot, it only boots on 4.0.4 .so pretty much the same thing happened to me .
Sorry for the bad english...
My Samsung Galaxy Nexus reboots about every 20 seconds if I'm trying to start the System. When I'm in the Recovery (TWRP), everything works fine. Here is a short Video, to show the booting issue:
/watch?v=sGfQDrah55s
(I have not enough posts to post an outside link right now, sorry. But I think you know how to use the part of the youtube URL)
As you can see, sometimes the SGN reboots after a few seconds while showing the bootlogo and sometime (as you can see at the end of the video) it boots until I can make a few things on the system like unlook it. But at least... it always reboots after a short time until the battery is empty.
At the moment, I have a CyanogenMod ROM installed, but it doesn't matter which ROM I'm going to try. Exactly the same bootloop happens with AOKP or SlimROM or even the FactoryImage. I realy don't know how to fix it. I tried so many things until now. The Video is taken with my new Galaxy S4, but the Galaxy Nexus is to good to throw it into the rubbish without any hardware fault...
You need more information? Please ask me!
Thank you for your help.
Jakob Kühne
Did you wipe data before flashing the rom?
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
Did you wipe data before flashing the Rom?
Click to expand...
Click to collapse
Sometimes I wiped it before and sometimes not, I tried it so many times and it doesn't make any change to the boot issue :/.
wipe data and cache then flash whatever rom you want.
if it doesnt work, try to flash stock rom.
That is bad zip.
Sent from my Galaxy Nexus using xda app-developers app
If any method mentioned in earlier post don't work, then follow this guide thorougly.
http://forum.xda-developers.com/showthread.php?t=1626895
Lately I have been getting random reboots and random black screens. The phone will either reboot itself show the galaxy s3 screen then go to complete darkness or vibrate and go straight to complete darkness. This seems to be random and usually starts happening a week or so after flashing a rom or kernel. Right now I am using my own TW rom (in dev section) with kt kernel and team kernalizer scripts. But the kernel doesn't seem to matter as this happens regardless. Does anyone know whats going on? Also this started happening after I ran aokp 4.2.2 for awhile, then odin back to stock and issues started. I've also been having less battery life since then.
Someone please help
anyone?
aamir123 said:
anyone?
Click to expand...
Click to collapse
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Aerowinder said:
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Click to expand...
Click to collapse
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
aamir123 said:
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
Click to expand...
Click to collapse
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Aerowinder said:
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Click to expand...
Click to collapse
ok I guess I'll go back but I don't see why the md5 firmware would be a problem now after I was using it with no problem for a while.
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I flashed the LJC fw and so far it's been pretty stable, only having trouble with excess heat but will probably get better with time. Also I'm having trouble getting a logcat app running (catlog etc). The app opens I give it root permissions, then I get a black screen with loading ring. No log whatsoever, is that normal? tried on both fw btw.
just got another random reboot on ljc fw. any other ideas?
aamir123 said:
just got another random reboot on ljc fw. any other ideas?
Click to expand...
Click to collapse
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
cboss718 said:
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
Click to expand...
Click to collapse
Idk what the issue is I'm gonna go stock for a while without recovering and see if that will fix anything, if not maybe tmobile is the way to go. Btw I tried taking a log cat but get error saying that dev/log/main doesn't exist.
Ok I was doing good for a few hours after flashing stock and not restoring Google account until I got a random reboot just now. I was able to get a log cat tho so I'd anyone can look at it and help.
Sent from my SGH-T999 using xda app-developers app
anybody? Does anyonehave any ideas?
aamir123 said:
anybody? Does anyonehave any ideas?
Click to expand...
Click to collapse
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Aerowinder said:
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Click to expand...
Click to collapse
ok I will try to get that the next time it reboots. Hopefully it's a simple fix, but just not sure what the problem could be.
So I went all these days without a random reboot and finally got one today, but was unable to pull a dmesg as it said does not exist. What can I try to get a dmesg now?
Also the phone feels like it never shuts down, even when I choose to shutdown in the menu it ends up restarting itself then bootlooping or just restarting. I've also noticed that holding home and power to turn phone on works most of the time to get it back to the os only to have it crash shortly after. I press home and power until I see the white splashscreen then let power button go. but staying in os for more than a few mins right now is impossible.