i been getting a random restart issue after rooting and eris lightning 3.02. I searched to no avail. How can i fix this issue? i would just go take my phone off standby and it will just restart. It might have started after i rooted my phone has nothing to do with lightning because it happened once before i installed lightning.
feverw0w said:
i been getting a random restart issue after rooting and eris lightning 3.02. I searched to no avail. How can i fix this issue? i would just go take my phone off standby and it will just restart. It might have started after i rooted my phone has nothing to do with lightning because it happened once before i installed lightning.
Click to expand...
Click to collapse
do you have it overclocked? if so what are you setting? this is normally have to do with either overclocking or jit
Did you wipe and reset your cache?
vash8806 said:
Did you wipe and reset your cache?
Click to expand...
Click to collapse
Yes i did both and i didn't overclock and i don't know what jit is. I changed to another custom rom and am having the same problem
not sure if it matters, but what rom did you switch to, that it is still doing it?
also, was this a problem before root?
just another thought.. you said you didn't mess with overclocking, but with most custom roms they are over clocked already, maybe the default setting for the kernel the too high or low for your phone.. try installing setcpu, if you dont have it, then do auto detect, and then try adjustint the low end to 245mhz and the high end to either 528, which is stock, or 710 which should be very stable.
then set to on demand. here is a link for setcpu http://forum.xda-developers.com/showthread.php?t=505419
Related
Weird issue...
Doesn't matter which rom, when I'm not on stock, my phone will freeze...
I have used odin and flashed one click root, clockwork mod then installed different kernels, roms and with same result. It will freeze eventually until I pull the battery... am I doing something wrong here?
I mean, I completely wiped using Odin so I don't see the residual thing here.
And in case there are, I wiped data, cache, dalvic prior to flash or followed chefs instructions to the T.
Am I the only one that's experiencing this? (probably am T_T)
Any inputs would be appreciated.
Same here. I've found that its the custon kernels that cause it. I just flash the rom I want and then flash the stock kernel back.
Sent from my Epic 4G using the power of the Holy Spirit
Hey, thanks for writing to confirm. good to hear that I'm not the only one but sucks to be one of the few...
I have done multiple wipes, cache clearing (both cache and dalvik)
Gone fresh from di18 fresh install, rooted and unrooted (I heard that old 1 click conflicts with genius dog's kernel) I have come to conclusion that it's the under voltaging that's the culprit here... I may be wrong but what kinda grinds my gears is that why is that only you and me are having these issues?
I'm using Andromeda kernel and it seems to be stable for me.
Any ways around this ??
I just recently started having this problem. I never had it until the day I flashed bakedsnack 1.3. The ROM is wonderful besides the occasional freezing. I usually freeze up about 2 times a day and have to pull the battery. This ROM does use a custom kernel though and I was OC'd to 1.3ghz but reflashed and went to 1ghz and still freezing.
Have you tried OC kernel before? i.e. genius dog's kernel. (not dogging Genius dog or anything. I'm naming his because his kernel is most widely used and I'm dying to use it.)
Just want to try to eliminate the culprit here lol.
Also try flashing andromeda kernel and see if your problems persists because I'm having no problems however my mflops will never go over 8.5 T_T
Im having an unusual problem when i flash any of the Stupidfast kernels, right now I am on the test version of v1.0.36, i tried to flash the stable version as well as the UV kernel and the v1.1.4. When i tried to flash the stable version i was able to boot up fine but i have an issue where it freezes when my media scanner runs and the only remedy is to do a battery pull. the same thing happened when I tried the UV kernel, I think my phone doesnt like UV kernels anyways so im not too concerned with that one, I am running setcpu with min at 100 and max 1000 on conservative. Im just curious if any one else had has this issue with the freezing. Any help would be appreciated!
civicr6 said:
Im having an unusual problem when i flash any of the Stupidfast kernels, right now I am on the test version of v1.0.36, i tried to flash the stable version as well as the UV kernel and the v1.1.4. When i tried to flash the stable version i was able to boot up fine but i have an issue where it freezes when my media scanner runs and the only remedy is to do a battery pull. the same thing happened when I tried the UV kernel, I think my phone doesnt like UV kernels anyways so im not too concerned with that one, I am running setcpu with min at 100 and max 1000 on conservative. Im just curious if any one else had has this issue with the freezing. Any help would be appreciated!
Click to expand...
Click to collapse
I'm having the same problem. But only when I plug in USB while media scanner is running. I'm using the most recent stupidfast kernel 1.2.3. I have to wait until the media scanner is done then plug in the USB, but have to be patient. If I try to do too much too fast..... freeze.
I wish thats all i had to deal with, i dont even touch my phone and it freezes all on its won, and for some reason my media scanner runs twice, and its always on the 2nd time when it freezes.
My phone always ran media scanner twice, before root and now, have u tried wiping ur phone reinstalling kernel and rom and then use titanium to restore apps?
Sent from my SCH-I500 using Tapatalk
I have done a full wipe on my phone and it is still doing it, maybe my phone doesnt like being played with ha ha. im not running any rom, just root and a kernel
just some noob questions..
its my first time to flash a custom yesterday and i flashed cm7 #57..
main reason: i want my battery last and wana use openvpn..
last night, it freezes and reboot itself many times.
i think its because i set the cpu at 768
i wiped my WF again and flashed # 50 last night..
i just notice that my battery gets easily drain even i use setcpu, 245min 614max and some profiles...
what should i do then? do i need to wipe batt stat? if so,how to do that guys?
....
the next thing is i want the openvpn to got work and i cant find any tutorial how to do that..?
can someone help me? thanks in advance
sorry for my bad english
ijestan said:
just some noob questions..
its my first time to flash a custom yesterday and i flashed cm7 #57..
main reason: i want my battery last and wana use openvpn..
last night, it freezes and reboot itself many times.
i think its because i set the cpu at 768
i wiped my WF again and flashed # 50 last night..
i just notice that my battery gets easily drain even i use setcpu, 245min 614max and some profiles...
what should i do then? do i need to wipe batt stat? if so,how to do that guys?
....
the next thing is i want the openvpn to got work and i cant find any tutorial how to do that..?
can someone help me? thanks in advance
sorry for my bad english
Click to expand...
Click to collapse
well that happens to me also when i set my WF on 768...best set up for me (stable) is max 710 min 245...fast enough!
to conserve battery set your profile (set cpu) when screen is off to a lower frequency however, i suggest you use overclock widget as sometimes set cpu causes WF to freeze or hang up...then set your on screen and off screen speed...this will do the trick.
If your experiencing boot loop after flashing new nightlies probably its because of 4.2 kernel...try kernel 4.1 surely this will sort this problem out.
about vpn try to check main xda thread...i already pm you a link which might give you an idea where to start...
s0ulbl5d3 said:
well that happens to me also when i set my WF on 768...best set up for me (stable) is max 710 min 245...fast enough!
to conserve battery set your profile (set cpu) when screen is off to a lower frequency however, i suggest you use overclock widget as sometimes set cpu causes WF to freeze or hang up...then set your on screen and off screen speed...this will do the trick.
If your experiencing boot loop after flashing new nightlies probably its because of 4.2 kernel...try kernel 4.1 surely this will sort this problem out.
about vpn try to check main xda thread...i already pm you a link which might give you an idea where to start...
Click to expand...
Click to collapse
i installed kernel 4.1, full wipe.. phone opened (without bootflop)..
after 5 minutes, it loops again Boot Screen animation..
i backed up my #52
i flashed now CM 7 RC
there is nothing problem for now.. But statusbar icons are still bad..
than I flashed cm7_nightly49_inexussmatte_blackstatusbar ..
and looping in bootscreen
Now i am flashing RC again..
anyone knows an answer for Good Staturbar?
infectedtr said:
i flashed now CM 7 RC
there is nothing problem for now.. But statusbar icons are still bad..
than I flashed cm7_nightly49_inexussmatte_blackstatusbar ..
and looping in bootscreen
Now i am flashing RC again..
anyone knows an answer for Good Staturbar?
Click to expand...
Click to collapse
I updated it for RC1 btw.
I've been using Mikfroyo 4.5 for a few weeks now and finally decided to flash a kernel. I chose this one here
http://forum.xda-developers.com/showthread.php?t=719763&highlight=rebooting
I think I am using clockworkmod recovery and I've been using rom manager to flash my roms and Mikfroyo had a built in reboot to recovery feature that I used to reboot my phone into recovery to flash the new kernel. I did not delete dalvik cache or anything I think. I'm not entirely sure. So when i tried to set the cpu to the max that it would allow it froze twice. and i rebooted each time and chose a different setting. I also saw a setting that said "set at boot" and i chose yes for that option. After a random reboot it seems to freeze just after the lockscreen shows up and it starts setting up the sd card. I have held down the power and raise volume button and nothing happens. And I have also tried the hold down power and lower volume button and nothing happens. Am I supposed to do both volume buttons at the same time? How can I fix my phone? It is completely unusable right now. Please help!!
sent17inel said:
I've been using Mikfroyo 4.5 for a few weeks now and finally decided to flash a kernel. I chose this one here
http://forum.xda-developers.com/showthread.php?t=719763&highlight=rebooting
I think I am using clockworkmod recovery and I've been using rom manager to flash my roms and Mikfroyo had a built in reboot to recovery feature that I used to reboot my phone into recovery to flash the new kernel. I did not delete dalvik cache or anything I think. I'm not entirely sure. So when i tried to set the cpu to the max that it would allow it froze twice. and i rebooted each time and chose a different setting. I also saw a setting that said "set at boot" and i chose yes for that option. After a random reboot it seems to freeze just after the lockscreen shows up and it starts setting up the sd card. I have held down the power and raise volume button and nothing happens. And I have also tried the hold down power and lower volume button and nothing happens. Am I supposed to do both volume buttons at the same time? How can I fix my phone? It is completely unusable right now. Please help!!
Click to expand...
Click to collapse
You can try reflashing Mikfroyo 4.5 without wiping and see if you can recover, or just flash another kernel over what is currently installed to reset setcpu. It's not wise to enable "set at boot" until you are sure that your settings are stable.
How can I flash a new rom or kernel if I can't get it to fully boot? It gets to the lock screen and then reboots. I have tried the holding down power button and volume and nothing happens. It still continues to boot up.
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
chandlerw88 said:
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
Click to expand...
Click to collapse
No way it would let me get that far. I've tried.
Soo nandroid backup or full data wipe. Either sound fine with me. How do I do that though?
Pull out battery, wait a couple seconds to put it back in, and press power and volume down until white screen shows up. You should know the rest.
It sounds like your messing around with a lot of things you don't know about. Before you do anything like majorly over clocking CPU Research it first
Sent from my Superphone. (Evo)
chandlerw88 said:
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
Click to expand...
Click to collapse
Ha, had to do that a few times myself. Gotta be very quick lol.
Sounds like you aren't holding down the volume button if its starting up normally. Set CPU wouldn't have messed up your recovery. Hold down the volume button before pressing the power button and don't let go untilled the white screen pops up. Then you can reflash mikfroyo.
That was all I needed. I looked up a couple ways on how to get into recovery and they were all very vague. I didn't know that you needed to initially hold down power button and volume. I was initially tapping the power button and then holding power and volume. But I should be able to take it from here. Thank you everyone for you speedy responses!!!
When you flash a kernel you are supposed to clear cache and dalvik or else you will get the issues you described.also running set cpu at max can cause instability and random reboots.
Most 1gHz devices will only support overclocking around 1.9 before coming unstable. do as the thread says FULL WIPE, reflash rom, flash kernel, boot, then when adjusting set cpu dont "set on boot" until you have tried it out first.
pureEVO91 said:
Most 1gHz devices will only support overclocking around 1.9 before coming unstable. do as the thread says FULL WIPE, reflash rom, flash kernel, boot, then when adjusting set cpu dont "set on boot" until you have tried it out first.
Click to expand...
Click to collapse
A 1Ghz device at nearly 2Ghz! That's an awesome overclock!!! How stable?
Its completle stable in a powered off state!!!
Sent from my PC36100 using XDA App
^^^ yeah... lol
1.19 is best I can do on my evo.. before lockup/reboot.
i wish we can do 1.9
OP.. sounds like you got it handled...
and was able to get into recovery. I hate ROM manager... because of this kind of issues.. you did not really know how to do it manually.
to a nandroid restore or flash the ROM again (only wipe cache and dalvik) should fix it.
I did the same thing when i first tryed to overclock my last phone and checked "set on bootup". Learned.. never do that till I am 100% sure it is stable.
I was a noob back then.. and what I did was put my phone in the freezer.. then raced the clock before the cpu overheated and locked up. LOL silly.. but it worked.
hah. Our evos don't have enough of a heat sink to reach 1.9ghz
Wow. Sry guys didn't mean to miss post. 1.19gHz
Oh ok 1.19 sounds alot better. I was lookin like 1.9 WOOOOOOOOW!!!! I wish mine would go that fast.
I had the same problem as you b4. Netarchy's kernel doesnt like overclocking. Looks like your good tho....
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
JRW 28 said:
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
Click to expand...
Click to collapse
I would have just taken it in but my phone is unlocked, rooted, and using Romracers CWM so I doubt Best But will accept it. I've tried all of this. I'm going to try CM7 Beta2, if the problem still persists I don't know what to do cause Best Buy won't accept it when they see the Unlocked at the top of the bootloader. It works fine when it's charging but so far no matter what I've tried I always got reboots. Does your phone get hot? Can you check what temps you get in SetCPU? Thanks for the suggestions btw.
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Sorry I meant 39* on phone temp
I went into my settings>widow and turned it off then rebooted, seemed to work, I also would get random reboots after a fresh install. Like at least 20x. But try that. Worked for me.
Sent from my MB860 using XDA App
JRW 28 said:
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Click to expand...
Click to collapse
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Ecstacy42 said:
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Click to expand...
Click to collapse
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Ecstacy42 said:
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
Click to expand...
Click to collapse
Go the fruitcakes thread in the developement section. Stock cwm flashable builds.
Sent from my MB860 using xda premium
JRW 28 said:
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Click to expand...
Click to collapse
It will only reset to the current rom defaults. If you have cm7 or alien flashed, It will revert back cm7 or alien. Doesn't effect root or bootloader. If the rom is pre rooted it stays rooted even after a full wipe.
Sent from my MB860 using xda premium
Dirtburgler said:
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Ecstacy42 said:
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Click to expand...
Click to collapse
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
when I was on Ninja SF I performed a factory reset and forgot to perform a backup and it took me back to completly stock gingerbread....sorry if I was misleading him
Dirtburgler said:
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
My phone came shipped with 2.3.4 Gingerbread, I never used the OTA update. I re-ran the script and got another random reboot.
Edit: I'm flashing the official 2.3.4 SBF from here: http://forum.xda-developers.com/showthread.php?t=1125944
I'll let you all know how things went.
From what I understand ...once u are on 2.3.4 if u try to flashback to. 83 it will hard brick you...definitely flash back to stock gingerbread 2.3.4 and hopefully that will solve your problems ....good luck
I installed Aura 1.1.3 Debloat #7 two days ago and my phone rebooted by itself today. I had it in my pocket, then I took it out and it was loading. I thought I might have pushed something when moving, but maybe it is related to the rom.
Okay, I flashed 2.3.4 with pudding boot loader unlocked and Romracer CWM Recovery. I'm going to install Alien and faux's kernal, hope flashing 2.3.4 fixed this and it's not a hardware issue.
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
JRW 28 said:
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
Click to expand...
Click to collapse
I flashed straight to Alien when I got the phone so I'm not sure it stock Gingerbread had problems. I just flashed 2.3.4 with pudding unlocked bootloader, Romracer's CWM, and finished installing Atrix Build 4 and faux's kernal 0.1.7. I'm going to take the phone off the charger (I only get reboots and shutdowns while on battery), and start installing my apps, restoring contacts, messages, and see if I have any problems. I'm not going to install SetCPU and mess with profiles and undervolting till I know I'm good.
I'll report how it's going tomorrow morning (usually by that time I get at least 5 to 10 random reboots/shutdowns). If this doesn't fix it then I'm going to flash the stock 2.3.4 SBF so they don't know I messed around with the device and take it back to Best Buy to get a replacement.