Atrix HD black screen of dead, common? - Motorola Atrix HD

Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)

vite0150 said:
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
Click to expand...
Click to collapse
This is not common at least not for CM11.
I've been running CM11 nightlies since they started to roll out, currently running 20/12 without issues.
I would recommend going to recovery, back up, and erase system, data, cache and dalvik, then flashing CM11 nightly to start clean.

I've been running CM11 and Validus13 ROMs since they became available and never had this issue.

I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required

I don't recall wiping Cache, Dalvik, or Data after installing 4.4 ROMs.

vite0150 said:
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
Click to expand...
Click to collapse
You should totally clean cache and dalvik when flashing new roms (CM usually does this by itself anyways). Make sure you're cleaning these, won't hurt at all anyways.

Ok, make a factory reset after flashing... Also i see in some roms that i gotta mount system and other things, i never did that (i didn't saw that in the instructions of the two roms that I've tried...)
Also I used for this couple of days the stock rom just to check that it wasn't a hardware problem... worked flawless...
Right now i'll try valadus... I'll let you know how it goes
Update: valadus gave me a lot of errors... Something like it couldn't write on storage/cwm... And when it was aborted it says that cache can't be mounted... So i ended up installing cm11 (the same that i flashed before)

You're running the latest CWM or Philz recovery?

Philz

It's strange because I'm running the latest CWM and I can install the latest Validus13, Cyanfox, CM11, and Probam without a problem.

Flashed probam last night, and it survived the night! Only thing I changed from before was wiping again after flashing...
Thanks for ur help
Update:
In the morning i connected the phone to the charger, and now i went to see if it was fully charged and surprise!!! It happened again!
Maybe is the charger cause I'm using a generic, but why it doesn't happen on stock rom?
At this moment i will just leave it stock and put it for sale, don't want to keep dealing with this...

Hi guys,
A couple days ago i noticed that on stock (att) rom i wasn't getting bsod but i do was getting reboots when charging the phone (i don't know how i didn't noticed it before)...
So maybe someone can tell what are the specs of the original power brick (amps, input, output) to find a similar one and see if that can solve the problem
Edit:
Nvm i found a samsung charger... Now everything is working flawless on OSE rom

Related

Nexus one Boot-Loop

anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.

[Q] Stuck on LG screen [Solved]

Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Beorn1 said:
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Click to expand...
Click to collapse
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
This fixed the same issue for me.
Wiped everything and flashed CM9. Works great (but battery drain is incredible!!!)
Solved!
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
Thanks, I did this, and now I was able to boot again with Gueste 3.1 (I'd rather wait for a bit more stable and mature version of CM9).
Actually, I did this thing twice, and it still didn't help, and in the third time I tried to make a logcat (I'm rather new to this logcat thing), and while trying to boot and make a logcat at the same time it suddenly started workind
I just hope that it will stay good now, and that I won't have this problem again in future flashes...
Thanks!

CM10 won't shut down or display battery properly

My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Which version are you using? It was a known bug in an older ROM, which should have been fixed in the newer ones.
Using the 20120816 version that I got from the link in this thread: http://forum.xda-developers.com/showthread.php?t=1803593
I've also had this problem for awhile, with several different ROM's.
Does fastboot work for you? Cause it doesn't for me, but not sure if related.
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
http://droidbasement.com/galaxy/roms/cm10/p3/recovery.tar.md5
GaryWS said:
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
Click to expand...
Click to collapse
I got the recovery from the same thread I linked above, so pretty sure it was the right one. Just to be sure I downloaded and flashed the one you linked with Odin, but it's made no difference. However, I have (finally) had success in getting the battery to charge to 100%. I kept wiping the battery stats every time I booted up, and powered it down while plugged in and left it on charge when I wasn't using it. After a couple of days (with it on and off charge) it finally said it was fully charged when I powered it on. I have used the battery calibration app with it at 100%, so hopefully it shall begin indicating properly, although it still says it's charging all the time, and the charging animation when it is powered down does not indicate its actual charge level.
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Xanthippus said:
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Click to expand...
Click to collapse
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
pruano said:
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
Click to expand...
Click to collapse
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Xanthippus said:
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Click to expand...
Click to collapse
I would recommend you re-download and re-flash it, since others (myself included) have no such problem with that version.
Didn't work. Redownloaded, reflashed, same problem. I even tried to unroot it so that I could flash it all again fresh, but somewhere along the way something has gone wrong. Odin is not working anymore. I can transfer files to and from my tablet, the computer still recognises it when plugged in, and Odin recognises the USB connection too, but if I try to flash something with it, it always says it is unable to open the COM port.
Tried this many different ways, with different roms, nothing seemed to work. Finally, tried AOKP milestone 6 (based on CM9) and it works perfectly. Go figure...

[Q][GT-I9001] Ivendor CM10 plus CastagnaIT Kernel (from Softreboot to Hardbrick)

Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter

Problem restarting Galaxy Note

Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
I just did a test with the App eMMC BrickBug Test and it said that Yes. Insane chip.
DanielG27 said:
Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
Click to expand...
Click to collapse
1. Boot your phone in recovery and flash the latest kernel from here
http://forum.xda-developers.com/showthread.php?t=1789397
2. Restart and allow some time to settle.
3. reboot and do wipe data /factory reset, wipe cache, wipe dalvik
4. Use pc Odin to flash stock ROM from sammobile.com
5. Check if it works and update...

Categories

Resources