Related
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.
Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk
I am so glad I didn't update to 1.0.7!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...
The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..
I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.
coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App
I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App
My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.
I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself
Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2
This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App
My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.
Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.
CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue
First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App
I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured
Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App
That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...
joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.
Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.
I've been searching for the last few days and have yet to really find anything to help me fix my problem.
the story:
Phone was rooted, back in Jan and I was running GummyJar 2.5, no problems, went to Apex V 1.3, no problems, but it ran a little slow. Today I decided to switch to something else to attempt and fix the speed problems, first I tried Incredibly Re Engineered v1.0, the phone ran well, but every 2-3 minutes it was rebooting me and sending me to the clockwork screen. So then I figured it had something to do with the ROM, so I went to Fission 2.5.7. Same problem, the phone runs great when it's on, but the constant restarted is unreal. I've done a factory reset, unrooted then rerooted the phone, then reinstalled the ROM, same problem.
Anyone ever have this issue and have a solution?
Thank you,
Eric
edit: Phone acts fine while plugged in to the computer or wall charger. Also made and attempt with SBF, to no avail.
Try an sbf....then go back to fission.
Just my thoughts. No overclock at first.
Running the SBF restore again...we will see what happens.
Hopefully someone else will stop by with thoughts.
Fission for me is real stable, ran it for long time now.
Worried it may be hardware problem....?
Might want to only install important apps at first also.
Try wiping data from Clockwork several times.
If that doesn't work you should definitely try SBFing and wiping data several times afterward.
Sent from my DROIDX using XDA App
I agree, I also loaded several ROM's and had a growing list of issues, SBF took care of everything for me.
Mine reboots when I pause video playback when connected with hdmi. But only since gingerbread, and I'm on my fourth version of gb. They have all done it so far, hoping official .596 will fix.
DX 2.3.3
Did the SBF'd it. Phone works flawlessly. I am now running Fission and Launcher 7, all without a hitch. Guess the phone just had to much going on and needed a fresh start.
Thank you all for the input. After I get a few more posts, I will post links and a DIY on how to do what I did. It was difficult for me to find anything with all of the steps and links in one spot, I want to make it easier for the next person experiencing this problem.
Yay! ....
Hey I been having the same problem with my droid x mines runnin stock 2.2.1 tho but it just keeps restarting and I don't know how to fix it lol. Im kinda new to this phone so does anybodyy have any suggestions?
Sent from my DROIDX using XDA App
CHip0,
SBF it...it's fairly easy and you can even find a youtube on how to do it....
http://www.youtube.com/watch?v=c58XaWnr6XE
Thank u very much! Lol
Sent from my DROIDX using XDA App
Ok, if anyone can help me out on this, I'd be really grateful.
So, it started something like a couple months ago.
I was on Cyber.GR and Matr1x kernel, all was fine, when suddenly the phone stopped being usable: everything FC'd at boot and rebooting was of no use. I was pissed off but luckily I had a NANDROID from a couple days before.
I restored it and all was fine again.
One week passes and BAM everything FCs again.
I tried to switch kernels, but nothing.
I decided to wipe everything and flash AOKP (faster updates and Cyber.GR dev was going in service) and AIR Kernel.
I restored my apps using Titanium and everything was fine again.
One month passes and all of a sudden, a friday night, FCs again.
I was in panic, tried reflashing kernel, fixing permissions, wiping cache and dalvik, no use.
So I googled a little bit and found out that reflashing the ROM usually fixed the problem.
I reflashed ROM and gapps and, as google said, everything was back to normal.
Except that once again, nothing's fixed.
The phone stays stable for a couple of weeks circa, then it starts again to force close everything.
Reflashing ROM and gapps seems to fix this, but as you can see it isn't a permanent solution.
I post a logcat I took when the FCs started, so it's like 2 months old.
If anyone knows the reason of all of this, I will gladly pay you a couple beers: this ****'s driving me nuts.
Here's the logcat: http://pastebin.com/C6hr0sDT
tl;dr: phone randomly start force closing everything at boot on different combos of kernels and ROMs. no ****ing idea. paying money for solution.
Have you tried using another ROM? Seems like the easiest route to take.
Sent by pocket technology
After you flash the rom when you install your apps again do you just install the app or do you install with data? Its better to install apps fresh cuz if the data's corrupted then your going to get FC! Try installing the CM9 Skank Rom & don't flash another kernel leave it as is then install all your apps fresh no data & run it for weeks or months see if your still having fc the CM9 skank kang Rom are really great & stable try it out here you go! :thumbup:
http://forum.xda-developers.com/showthread.php?t=1386869
°N€×U$ $⁴G°
Make sure not to include system apps when restoring backups using tb. That might be the issue
Sent from my Nexus S®
That as well. I saw you did use AOKP also. Hmmmm. In my personal experience, my phone likes stockish kernels. Matrix always froze up on me after 100+ hours of up time with the stock nexus voltages applied. Air Kernel always gave me FCs. My phone is picky. No idea why. Maybe try using another kernel, stockish this time and see what happens? I haven't had any lock ups using thalamus', Pete's or, Simple Kernel.
Sent by pocket technology
Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think
Thanks for the replies, guys!
Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.<br />
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).<br />
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think <br />
Thanks for the replies, guys!
Click to expand...
Click to collapse
Yeah starting from scratch will not hurt too much ;-)
Sent from my Nexus S®
My Nexus 10 is exhibiting sleep of death issues when I leave it overnight. Are there troubleshooting steps to help me determine what the cause of the issue is?
apastuszak said:
My Nexus 10 is exhibiting sleep of death issues when I leave it overnight. Are there troubleshooting steps to help me determine what the cause of the issue is?
Click to expand...
Click to collapse
When you leave it on over night, do you have it charging or not charging? If not charging, what is the battery level before and in the morning?
ROM? Rooted? Mods?
SmokinCharger said:
When you leave it on over night, do you have it charging or not charging? If not charging, what is the battery level before and in the morning?
ROM? Rooted? Mods?
Click to expand...
Click to collapse
Stock 4.3. Rooted with SuperSU 1.65. ClockworkMod Touch installed.
I had Sleep of Death overnight, and I was not plugged in.
Yesterday morning it was dead. I plugged it in via pogo cable and factory charger to charge and by 8:00 PM it was only at 37%. Switched to USB cable and got it to 90% in a couple of hours. Went to bed at Midnight. Charge was 80%. After I rebooted the device this morning after the SOD, it was at 60%.
A little history.
I was on rooted 4.3, but had connectivity issues to my Verizon Wireless JetPack.
So I decided to roll back to 4.2.2. I installed CyanogenMod 10.1.3 RC2 and lo and behold, I could one again use my JetPack for Internet access.
But then I started to have Sleep of Death issues. I used CM for over a week and and had 4 SOD problems.
I then found out about Wifi Fixer in the Play Store. Went back to stock 4.3 and installed Wifi fixer and all my JetPack problems went away.
But now I am getting SOD issues. I have been on 4.3 since Saturday night, and have had 4 SOD incidents.
I did a data, cache, and dalvik wipe in between each ROM install.
I'm contemplating doing a full factory reset and re-rooting, but I really don't want to backup all my data and reinstall it, unless I really have to.
Are you running an app like Crossbreeder? It has been known to cause random reboot issues and sleep of death.
If you started getting SoD on a CM based ROM running 4.2.2, and it continued after switching to stock 4.3, perhaps it is an app you installed at some point recently. or an app that was updated and the new version is causing problems.
EniGmA1987 said:
Are you running an app like Crossbreeder? It has been known to cause random reboot issues and sleep of death.
If you started getting SoD on a CM based ROM running 4.2.2, and it continued after switching to stock 4.3, perhaps it is an app you installed at some point recently. or an app that was updated and the new version is causing problems.
Click to expand...
Click to collapse
I had installed the Cyanogen cLock widget, because I really liked it. So, I thought that might be it. I deleted the widget, but I still had the issue with the SOD.
And now I am not sure why the pogo cable charging is so crappy. It used to be much faster than microUSB.
I am not running Crossbreeder.
apastuszak said:
I had installed the Cyanogen cLock widget, because I really liked it. So, I thought that might be it. I deleted the widget, but I still had the issue with the SOD.
And now I am not sure why the pogo cable charging is so crappy. It used to be much faster than microUSB.
I am not running Crossbreeder.
Click to expand...
Click to collapse
With all the changes back and forth, I recommend, as you suggested, doing a full reset, data wipe, etc. I was flipping between 4.2 and 4.3 AOKP ROMs and was seeing strange issues as well. I believe my problem was related to corrupted files, partition, etc for the /SDCARD or TIBU because I was flashing a lot of mods and playing around with programs. I finally did a full wipe of everything (backing up TIBU to dropbox first especially the apps that were not in Play Store) and did a clean, fresh install including the apps from Play Store - not TIBU. It was a pain of course having to reset it all back up, but it is working much better now.
If you can, backup via OTG so you have it.
OK, did a factory wipe and used Fastboot to push the stock ROM and stock bootloader onto the device. No Sleep of Death issues, battery life has doubled. Haven't tested the pogo cable yet. But overall it's good to be in a stable place.
Now trying to decide if I want to root again. I really didn't do all that much with root. I think I will leave it this way for a while to get a baseline and then tinker.
Whether you root or not it would probably be a good idea to make a Nandroid backup of everything so that if you have an issue again you have a completely stable and known good configuration to come back to.