Related
When I install it, my phone tends to restart after I make a call or when I turn on my wifi. It reoccurs everytime it loads does anyone know what might have caused it
Sent from my PG06100 using Tapatalk
After you've installed Miui, did you reboot after it finish the first loading?
I had that issue after installing it.
So I wiped it and started over again.
After installed and loaded, rebooted it, everything has been fine.
you can also try doing a cache and dalvik wipe and then reflashing the rom. Of coarse nandroid it first just in case.
Not following instructions
That's a known issue, gotta reboot after a fresh flash. That's why the OP instruction on the MIUI thread tell you to reboot.
^ Shift Faced
Thanks I will retry it again later on in the day
Sent from my PG06100 using Tapatalk
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.
I was running Thor Rom, but I installed the update, but from This thread and others, even the ones I had to decrypt first. The update always went smooth and ICS looks and works great; except....
Any time the screen goes to sleep, or I press the power button to turn off the screen, the screen won't wake up. OK, correction, it WILL wake up if I turn it on within ~10 seconds, but wait longer than ~20 seconds and it won't come back on. I have to press and hold the power button to apparently shut it down (hard to tell because you can't see anything and there are no indicator lights). Then I have to press and hold it again and it boots back up.
Hence, I have to press and hold the power button for several seconds twice each time I want to use it.
I'm not sure if it's shutting down or just hard freezing. I can't seem to shake this. It didn't do this with the old stock rom or Thor.
Ideas?
Currently Running the following on my A500 1.0
Image: Acer_AV041_A500_RV05RC01_PA_CUS1
Build: Acer_AV041_A500_1.033.00_PA_CUS1
same problem
I have the same problem, I updated my tablet via the acer update and now it does that :/
First I thought it was some problem with a program I had installed, but then did a factory reset and left a couple programs and still doing that.
Im going to try to hold the reset button to see what happens.
This issue is known to occur with several custom ROMs and is referred to as the Sleep of Death or SoD. It occurs when the tablet goes into deep sleep and refuses to wake up. Thor has suggested those affected and using his ROM to increase the voltages of their CPU or flash his performance kernel. If you are using Stock ICS from Acer then I think there's a thread documenting issues with it. You can check that, it should be in the general section. Hope this helps. It happened to me only once and I can't recall which ROM, but it never happened again.
Sent from my Iconia A500 using Tapatalk 2 Beta-6
That's just the thing, I want the stock ICS and I thought I had it (still think I do!). I'd like to go back to stock to make things work correctly. However, there is no 'check update' button for me in my settings. I have no way of looking for an OTA update that I can find. I'm dumb at times, but not that dumb.
I have the same problem and I'm running CM9 now. I started with the same ICS update that you listed in your first post. I have two GEN1 ICS updates I think I'm going to try. Since the problem has transcended roms (Stock ICS to CM9) I'm thinking this is a firmware issue with the CUS update. I read a thread that said (man I'm rhyming tonight...) the CUS didn't come with some firmware images that the GEN ones did.
EDIT: Since I'm on the V3 Bootloader I don't think I can install these updates. I decrypted them, but it's still failing to install. Probably have to be on the stock bootloader for these to work.
Frostcall said:
That's just the thing, I want the stock ICS and I thought I had it (still think I do!). I'd like to go back to stock to make things work correctly. However, there is no 'check update' button for me in my settings. I have no way of looking for an OTA update that I can find. I'm dumb at times, but not that dumb.
Click to expand...
Click to collapse
I downgraded my tablet back to 3.2 using info in one of the Dev threads. Then I let it update with OTA updates to 3.2.1. I then had to install the Acer Update Helper app on the play store in order to get it to update to ICS. The point of all this is that until I went back to a stock 3.2 I could not do an OTA update as the roms were not stock.
Then once I was on stock 4.0.3 ICS I was STILL getting SoDs. I put in a trouble ticket to Acer and the response I got was to do a full hardware reset (power off, hold power and volume up until it vibrates, then toggle the screen lock switch a couple times.) I finally got back to installing a custom rom (flexreaper r13) and I now no longer have SoDs. A lot of work but I think I'm finally stable.
Sent from my A500 using XDA Premium HD app
BakaNeko59 said:
I downgraded my tablet back to 3.2 using info in one of the Dev threads. Then I let it update with OTA updates to 3.2.1. I then had to install the Acer Update Helper app on the play store in order to get it to update to ICS. The point of all this is that until I went back to a stock 3.2 I could not do an OTA update as the roms were not stock.
Then once I was on stock 4.0.3 ICS I was STILL getting SoDs. I put in a trouble ticket to Acer and the response I got was to do a full hardware reset (power off, hold power and volume up until it vibrates, then toggle the screen lock switch a couple times.) I finally got back to installing a custom rom (flexreaper r13) and I now no longer have SoDs. A lot of work but I think I'm finally stable.
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse
I wonder if this will work with the V3 bootloader?
naviathan said:
I wonder if this will work with the V3 bootloader?
Click to expand...
Click to collapse
That's what I had installed when I started the process. Of course it eventually got overwritten with the unpatched stock bootloader, but that was easily fixed.
Sent from my A500 using XDA Premium HD app
How did you manage that? I need to figure something out because right now I can't set my tablet down for two minutes without doing a hard reset. Over clocking helps, but it's got limits. Not to mention the wifi...Man it's horrible now!
So I flashed mako-jb-kernel-028u-JWR on my nexus 4 and when I rebooted the notification light was flashing red. I booted back into TWRP and flashed mako-jb-kernel-027m-JWR to try and fix it. After I rebooted it was stuck on the boot animation with the flashing light. Whenever I started up TWRP the light would start flashing and the phone would turn off before I could reflash carbon rom. The light wouldn't flash when I was in fastboot . Now it won't even turn on, even if I plug it into power. I looked around and couldn't find anyone else with this problem. I'm assuming the battery ran out of power and I need to let it charge before I can do anything. Though last time I booted into TWRP the battery was above 90%. If someone could suggest something to do it would be great.
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
simms22 said:
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
Click to expand...
Click to collapse
I'm hoping I won't need to do that since I don't have a T5 screwdriver and I don't trust myself with manually charging a battery with a power supply.
I should also mention that I used this https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en about an hour before flashing the new kernel.
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
RASTAVIPER said:
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
The problem is that it won't even turn on. I think it ran out of battery and its refusing to charge.
Alright so I did some searching and found this post http://forum.xda-developers.com/showpost.php?p=43291951&postcount=27 I did that and my phone can actually boot up now. Also I should mention that you need to hold the buttons for EXACTLY 60 seconds or it won't work. I'll let it charge and attempt to reflash Carbon Rom after.
TWRP kept closing on me before I could reflash Carbon, so I restored to the stock rom and kernel using WugFresh's toolkit. I couldn't boot into the rom until I went into fastboot, went into stock recovery, and restarted my phone. Now I can boot up perfectly fine! Also I flashed the latest faux kernel again just to make sure it was the problem, and after flashing mako-jb-kernel-028u-JWR I got the red led again, So I'm advising everyone to stay away from that build.
Hello. So, I was using the default ROM for my Galaxy Y, everything in factory settings, and then it started rebooting a few weeks ago. So I tried and installed a custom ROM (BeautySense), but it didn't solve the problem.
The strangest thing is: when I put on the battery, the cell phone turns on all by itself, I don't need to press the power button for it to turn on, and when the cell phone is on, when I press the power button to lock the screen, nothing happens.
Anyone has any idea what might the problem be?
Thanks.
don't worry
vitorassuena said:
Hello. So, I was using the default ROM for my Galaxy Y, everything in factory settings, and then it started rebooting a few weeks ago. So I tried and installed a custom ROM (BeautySense), but it didn't solve the problem.
The strangest thing is: when I put on the battery, the cell phone turns on all by itself, I don't need to press the power button for it to turn on, and when the cell phone is on, when I press the power button to lock the screen, nothing happens.
Anyone has any idea what might the problem be?
Thanks.
Click to expand...
Click to collapse
it has nothing to do with the software its a hardware problem it can be one of thees two:
1.the power button is stack and that will explain why you can't lock the screen and the reboot because you are making him power off and then power on
2.the battery keeps moving form inside the case causing it to shutdown and then start by it self which happens with a lot of phone like my note 2 and y duos
report to me after you chick step 1 and step 2
press thx if i helped :fingers-crossed:
Hello. It did help, but I don't think the problem is the battery moving. As for the power button being stuck, I'd already thought of it, but I don't know how to fix it. Apparently it is not stuck, but maybe it is stuck on the inside. In that case, how can I be sure?
Thanks.
It's a 90% hardware problem scenario.... But why don't you try changing to another kernel? (any stable kernels like hells fusion, jarvis, savie etc)
If it still reboots then u will be damn sure it's the power button problem.
vitorassuena said:
Hello. It did help, but I don't think the problem is the battery moving. As for the power button being stuck, I'd already thought of it, but I don't know how to fix it. Apparently it is not stuck, but maybe it is stuck on the inside. In that case, how can I be sure?
Thanks.
Click to expand...
Click to collapse
you can try flashing a kernel because when my phone fell in the bathroom i opened it my self and i lost my volume Button so i prefer that you keep the opening of phone as the last Solution :fingers-crossed:
Try to flashing with new kernel if it didn't work i think it's hardware problem
Solution
Many replies stated just to flash kernel.
Actually, you have to flash a kernel and then flash ROM.
If you do the reverse, you will stuck in bootloop.
The instability of the kernel is the cause.
Also do not install too many tweaks, which also causes some stability issues.
Over Clocking in some kernels also cause this restarting problem.
Solution: Flash Kernel and then flash the ROM
If it doesn't work, it is surely the hardware problem.
Press thanks button if I have helped you!
the_pirate_predator said:
Many replies stated just to flash kernel.
Actually, you have to flash a kernel and then flash ROM.
If you do the reverse, you will stuck in bootloop.
The instability of the kernel is the cause.
Also do not install too many tweaks, which also causes some stability issues.
Over Clocking in some kernels also cause this restarting problem.
Solution: Flash Kernel and then flash the ROM
If it doesn't work, it is surely the hardware problem.
Press thanks button if I have helped you!
Click to expand...
Click to collapse
this is not true
for stock based roms flash rom then flash kernel - this is because kernel has things like wifi driver that needs to be flashed after the rom however it doesnt matter if you do it the other way round - you can always flash the wifi driver seperately
for cm based roms you need to flash kernel first in order to format your system to ext4 in order to install the rom if not already on ex4 system partition
Thanks
marcussmith2626 said:
this is not true
for stock based roms flash rom then flash kernel - this is because kernel has things like wifi driver that needs to be flashed after the rom however it doesnt matter if you do it the other way round - you can always flash the wifi driver seperately
for cm based roms you need to flash kernel first in order to format your system to ext4 in order to install the rom if not already on ex4 system partition
Click to expand...
Click to collapse
Thanks for correcting my mistakes and guiding me!!
Anyone solved this problem? I am experiencing it right now, what to do .?
Sent from my GT-S5360 using Tapatalk 2