Recently, I rooted my phone with unrevoked. At random times when turning on my Aria, at the Htc logo screen, my battery will vibrate multiple times before Cyanogen 7 android logo appears. I changed out my battery, unrooted then rooted again only to have this problem. I'm using the lasted Google gapps posted on XDA and don't think it's that. I tried stable and nightly r roms with no change. I believe it's possible that a bug in Unrevoked, Clockwork mod could be at fault. Again, this is at random times when turning on my phone. If anyone knows something are at times experienced this, please post it here.
I don't know what causes it exactly, maybe DT's apps2sd. But I have this too.
gods_archangel said:
Recently, I rooted my phone with unrevoked. At random times when turning on my Aria, at the Htc logo screen, my battery will vibrate multiple times before Cyanogen 7 android logo appears. I changed out my battery, unrooted then rooted again only to have this problem. I'm using the lasted Google gapps posted on XDA and don't think it's that. I tried stable and nightly r roms with no change. I believe it's possible that a bug in Unrevoked, Clockwork mod could be at fault. Again, this is at random times when turning on my phone. If anyone knows something are at times experienced this, please post it here.
Click to expand...
Click to collapse
This is not a problem with Unrevoked or Clockwork. It means the ROM you have installed has something weird going on that causes it to restart a few times before booting normally. This has happened to me also when using CM7, but only after I had installed a different kernel. It never happened to me with the original default kernel, and it's also never happened with any other ROM (CM6 or any of the Sense ROMs).
Just curious, but can you tell us exactly which ROM you're using, and whether you installed a custom kernel on top of it?
drumist said:
This is not a problem with Unrevoked or Clockwork. It means the ROM you have installed has something weird going on that causes it to restart a few times before booting normally. This has happened to me also when using CM7, but only after I had installed a different kernel. It never happened to me with the original default kernel, and it's also never happened with any other ROM (CM6 or any of the Sense ROMs).
Just curious, but can you tell us exactly which ROM you're using, and whether you installed a custom kernel on top of it?
Click to expand...
Click to collapse
I was using RC4, 7.0.3 and trying some of the latest nightly roms. This isn't my first Aria phone that I rooted. My first one didn't have this problem but I forgot which Google gapps version that was used at the time. If it were the gapps, the phone would go in a endless loop at the Cyanogen android boot screen but I'm having this multiple vibrate problem like it keeps rebooting at random on the HTC boot screen when turning on the phone. I changed out my battery for a new one which didn't fix it. At this moment, I unrooted and flashed the original stock rom and no problems are popping up. I believe it's a unknown bug in Clockwork.
gods_archangel said:
I was using RC4, 7.0.3 and trying some of the latest nightly roms. This isn't my first Aria phone that I rooted. My first one didn't have this problem but I forgot which Google gapps version that was used at the time. If it were the gapps, the phone would go in a endless loop at the Cyanogen android boot screen but I'm having this multiple vibrate problem like it keeps rebooting at random on the HTC boot screen when turning on the phone. I changed out my battery for a new one which didn't fix it. At this moment, I unrooted and flashed the original stock rom and no problems are popping up. I believe it's a unknown bug in Clockwork.
Click to expand...
Click to collapse
Well, I suppose it could be. You might want to try formatting boot and system partitions before installing the ROM to see if that clears it up. We already know Clockwork doesn't clear the system partition properly when installing ROMs that use Edify scripts.
Hi guys. I got my X10 yesterday, but i got a few problems with it.
I used Miui but the battery drain was a bit to hard. So i switched to Wolfbreak-009. I want to install the undervolted DoomKernel-03-X too but if i do that the system stucks in the white Sony-Logo and reboots the whole time.
I have flashed like this:
Stock 2.1
Baseband-67
Wolfbreak-009
CustomKernelEnabler
bootloader_bypass_files_v04
Doom-03X
Doom-03XWifi
I think i have chouse the wrong order or anythink else?
after wolfbreak rom install free kernel 3.60 and forget all other you mentioned...
reboot phone....
phone off... enter xrecovery and flash with doom kernel
I will test it.
Thanks
So i tryed it. Flashing fresh Wolfrom-009->FreeKernel3.60->Reboot->Poweroff->DoomKernel0.3X->WLOD...
So this dosen't work ...
The undervolted 0.3X works perfekt on my last MIUI.
Hi guys,
I'm using a new AT&T Galaxy S2. It seems as though whenever I install a custom kernel other than stock, eventually my phone gets slower and slower and crashes. This includes the daily kernel from Entropy, as well as the basic CWM one from codeworkx.
It doesn't matter what ROM I'm using (I've tried a few), but whenever I'm using a custom kernel, it will work for a while, but then stop. It usually works for a few hours or so. However, after this, the phone will freeze. I'll do a fresh restart, and then it will fail to load a lot of my widgets, and start to freeze again.
I've tried this maybe 9 or 10 times, with consistent results. As soon as I flash stock kernel, it works perfectly fine (I ran it for about 4 or 5 days on stock with no slowdown).
Can anyone help me out with this? Thanks!
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
ferincr said:
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
Click to expand...
Click to collapse
have you ever considered its the tweaks your doing to your phone.. have you tried just flashing the rom and running it without doing the tweaks... not every phones hardware is identical so not all tweaks might work... ive flashed a rom recently that experienced some boot loops after doing some tweaks to the rom, and now im running that rom flawlessly without any tweaks...
---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------
you might also want to try the rom with the default kernel that comes with the phone not faux which i'm assuming your using
To be honest, no I haven't thought of that.
I just re flashed everthing, if the problem starts again I'll remove all the tweaks.
But the thing is the phone was working well and one day without changing anything it started with this. But I'll try removing the tweaks if this persist
Thanks,
Nope, it wasn't the tweaks.
Fresh flash, no tweaks and I still have to press the on button many times to get the screen to turn on
which rom are you using again?
I'm on NRG blue but I tried the Bulletproof for a while and it did it too that's why I'm thinking that is not rom related. It has to be something deeper than the rom.
Phone was working great until last month that I travelled abroad.
As soon as I got to the country I was visiting I put a local sim card and it took me a while to be able to boot, to the point that I had to restore from a backup.
Then during the time I was there I had several random reboots (like once or twice a day).
When I came back I swapped the sim again and no more reboots but after a week or so I started with this black screen problem, it was really bad to the point when sometimes I needed to pull the battery off to see if that helped and the rom got really screwed (I think sense got screwed because the screens were doing weird things). So I reflashed, it fixed all the weird things but not the black screen.
Now it's not as bad (I only need to press 3 or 4 times the button) and it's not alway, only if the screen been off for a while but my previous experiencest tells me that it will get worse in few days time...
okay i have a few suggestions.. do you do a full wipe when you flash a rom? wipe data/factory then format system then wipe cache partition's then wipe delvik cache.. and you should try going back to stock completely then trying a different rom and see.. its about testing all possibilities before coming to the conclusion your phone is damaged somehow
yes I always do a full wipe and/or the 4ext wipe and clear dalvik and cache. Not sure about the factory reset since I wasn't sure where that would take me.
you should try going back to stock completely
Click to expand...
Click to collapse
Do you mean relock, S-ON and goall the way to GB? or to ICS T-mous stock??? I did go to ICS (this one) http://d-h.st/3VD but I can do it again (I can alway use some practice with these procedures...)
I
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Ninjistix said:
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Click to expand...
Click to collapse
I did that yesterday and yes the ruu Iused is the same as the one listed there as most recent.
I just found an interesting discusion on the faux kernel thread about a problem, with the earlier version (which is the one I was running when the whole thing started) and that happened to me before this black screen.
This is the thread http://forum.xda-developers.com/showthread.php?t=1359951&page=232 and it's mentioned in the quote on post #2316 and ahead.
I PM'd AJ to see if he thinks this could be related since in one of his posts he said something like reverting to stock won't help (for some reason)
but overall from what i just read... the issue seems to be related to the faux kernel.. i only flashed it once but ii didnt do any tweaks,, i mostly use the stock kernel that comes with most of the rom's i flashed... here's what to try... in 4ext wipe all partitions except sd card, then wipe both sd card partitions internal and external.. toggle usb storage and flash this super wipe script in recovery.. then flash a different rom and don't flash faux.. test the rom out to see if your problem occurs again.. or flash the super wipe then place the ruu on the SD card then attempt to flash back to stock
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Double0EK said:
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Click to expand...
Click to collapse
I'll try it.
Thanks,
Tried that and didn't help, but thanks for the suggestion.
What I noticed today is that since Icouldn't get the screen on no matter how many times I pressed the darn button I pulle dhte batt out and then rebooted the phone to see if that helped and even though I got the little vibration confirmation when the phone boots up there was no white HTC splash screen or bootanimation whasoever, anyway since I could still not get the screen on I tried the same thing a few time and then once I finally managed to the the screen on I said int the bottom left corner SAFE MODE (never seen that one before). I'm running Bulletproof reloaded now.
Oh and the batt was kind of low (may be 20%).
Wow!!!! I do own a very messed up phone!!!
Today this piece of crap threw a total temper tantrum.
Would nos turn the screen on no matter what. I removed the batt and not even rebooting to the point that when I finally got it to boot it had an internal SD error. It didn't allow me to format, wipe or partition it from bootloader or recovery.
Now I'm at home so I flashed stock RUU (again) and it seems like its running one more time but I was really close to throw it over the cliff where I was Flying my RC gliders.
We'll see if I can make it last a bit longer...
so its working once again, cuz you said you flashed back the stock ruu right?
Yes,it's alive (will for how long this time). I flashed stock a couple of times , I unlocked once again, flashed 4ext, flashed JP hboot, superSU, NRG rom, supersu again (since IO wasn't sure in which order I should have done this) flash rom 2nd time, flashed Faux's v 24 (twice) and Downloaded most of the apps clean from Gplay.
I'm getting a lot of practice with this, who knows, may be one day I become good at it
its good your practicing now, but don't forget to do backups before you flash anything to your phone, this this way you'll have a stable install to restore back to incase anything goes wrong again
I been doing more tests and yesterday I run it on stock most of the day with no apparent issues, then I restored the NRG rom from a backup and still no issues so I started to think it was something I messed up flashing the JB Hboot, I moved to a bulletproof rom and decided to do another test.
I sat on the phone as to block signal and the issue came back.
Now I'll try the same with NRG, yep it seems like it's when the phone loses signal the screenwon't come back afterwards.
I'll try the same in stock rom next...
Yes, it did it in stock too but not so bad, it seems like after few attempts the screen worked againgvs. on bulletproof didn't
Ok, I found this in some other thread...
[QUOTE8. Black Screen - Phone will not wake-up
I'm accidentally find out and solved the problem of Black Screen during in-coming call (BulletProof 2.2.0). By replacing the service.jar from the previous version (BulletProof 2.1.0) with the intention to get rid of the CRT file in my system, by doing this I am also discovered that the black screen problem is gone. However, this problem can be easier solved by simply dis-able the screen-on/off animation setting instead of replacing the service.jar with the one from previous build which doesn't have CRT.
It's worth to be note that during my old days with the HTC HD2 running Nandroid I've encountering similar problem of black screen when waking up the phone and it was caused by the CRT as well. This, at least happened to me with more than 3 Rom, including the famous AmeriCanAndroid, HyperDroid and Tytung's ...
So if you are experiences Black Screen problem, please check to see if you did flashed the CRT and/or enable it? ][/QUOTE]
Can somebody tell me to how do I check this?
Thanks,
had been trying roms for months now, and 2 weeks ago just starting bootlooping. was running carbon rom when the bootloop started. changed to padawan v2, bootloop went away for a few days and then came back. thought it was power button but when im in cwm it doesnt bootloop.
even all my backups they bootloop. today i went back to stock and using odin and reboots after the att logo.
is my phone done for? thanks
Try an emergency recovery with kies.
fixed it!
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
ufuknut said:
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
Click to expand...
Click to collapse
Hi, I wanted to know what radio version you flashed, because I'm getting the exact same error but none of the radios works for me, I'm also using padawan because of what you said.