Related
Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
lilhaiti said:
Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
Click to expand...
Click to collapse
You flash anything or change anything with a2sd etc, before this started happening?
It's not doing it on an older NANDROID (from 4/22).
I flashed Drowning 7-6 ad then noticed it. But since my last restart before that, I've installed a lot of stuff. I will try it for a while on this NANDROID and see if it does it again after updating my apps, too many changes to rebuild from here...
Basically what happened was I flashed the Kernel (7-6) and restarted, things were fine...but then (per Drownings advice) I restarted again, and then all hell broke loose. I recovered my last NANDROID but experienced the same thing with just a restart, so now I am on an earlier NANDROID and tried a restart and all went well..Like I said I will try to update my apps when I get home (damn ATT data caps) and see what happens then...
OK...several restarts after installing updates, and everything seems normal it's definitely got something to do with either drowning 7-5 or 7-6, or n75 and/or n76.
Right now with the NANDROID I am running n42 with drowning 7 with aufs enabled (as was with the newer ROMS)
I also run DT A2SD with apps and dalvic on SD.
I will try to upgrade to n76 and drowning 7-7 in a few and see how that works out...
n76 and Drowning 7-7 has been good so far...I think the problem is solved...there was definitely something wrong with my setup that was common to the later NANDROID...thank god I saved some NANDROIDS
Wasn't there some kind of known issue with 7.6? I don't remember the details, but I seem to recall that there was some reason why I didn't flash it at the time (aside from general laziness).
Did a fresh install of n76 with S2E and Drowning 7-7, all is running smooth again and I have restarted a dozen times with no issue. After flashing over top of ROM's for the last few months there was probably some trash getting in the way, so I decided to clean house.
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Drachen808 said:
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
Click to expand...
Click to collapse
Drachen808 said:
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Click to expand...
Click to collapse
A bad flash can occur but generally they aren't prevelant. The best place to look for feedback on ROMs is in that specific ROM thread. If that specific ROM isn't setup well, or has bugs, these will cause random reboots.
If you're really interested in helping out the devs, the best first step in technically troubleshooting a random reboot is to grab the /proc/last_kmsg file. This is a log of the kernel as of last boot and will indicate whether or not the kernel was involved in the random reboot. If the issue is in the kernel, will narrow down the focus. If the issue is not in the kernel, will eliminate that possibility.
Another common cause of random reboots can be poorly coded 3rd party apps. Unfortunately, depending on the number of 3rd apps installed, this process can take a while to troubleshoot as the best method is to remove all and start installing in batches waiting to see if any random reboots occur.
Hope these few suggestions and some technical information help!
Thank you Joeykrim. I will look into that, but I am fearing more and more that it may be my phone. I have tried probably every sense 3.0 rom (need wimax and camera so no 3.5) and several different kernels, and it keeps happening.
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
VR32 said:
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
Click to expand...
Click to collapse
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
shoman94 said:
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
Click to expand...
Click to collapse
thanks shoman. much appreciated for the tips.
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
beaverslayer said:
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
Click to expand...
Click to collapse
no I've never used one.
but it appears this was all caused by the app Screen Off And Lock by Katecca. I had the donate version. its always worked for me on every ROM up through ICS, but it seems to wonk out JB. I changed to Lock Screen App by Kenneth Cheng and have had zero problems in days now, which is a first.
Sent from my SGH-I777 using xda premium
Hey guys; I've been using dastin1015's ROMs for almost a year now on my Sprint Evo 3D. I definitely don't know everything (probably not even close) about using custom ROMs, but I'm not a complete noob.
That said, I screwed up. I successfully replaced my 4ext touch recovery with TWRP as dastin1015 says must be done for this ROM. I then wiped everything except my SD card and 'System' and flashed the latest ROM located here (Villuminati 12/08/13), and the "full complete" GApps package located here (4.4).
I rebooted the phone, and admired the new CM splash screen. Once the ROM loaded, I immediately got a couple of stock (system) apps (com.android.phone and ThemeManager along with some others) forceclosing repeatedly, preventing the phone from fully booting and making it very difficult for me to reboot the phone into recovery-- the messages popped up over and over again on top of the menu for reboot. I eventually did manage to get back into TWRP though.
At that point, I wiped *everything* except my SD card, and flashed the ROM and GApps again. Now I'm having the same problem, but with even more system apps force-closing, and I cannot reboot the phone or do anything else with it via the phone itself.
What do I do now? Can I fix this with ADB?
I read that using this 4.4.1 GApps might solve or prevent this problem, but it's iffy. In any case, unless someone has a better solution, that's the next thing I wanna try after managing to reboot into recovery. Do any of you think that will work?
Thank you.
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Glad to hear it dschlemmer.
The proper answer to the first part of my question (can I fix this in adb) is "of course, you idiot, just connect the phone to your pc and type "adb reboot recovery" and then wipe and re-install your old ROM or something."
However, I can't get the PC to recognize the phone, despite it having the proper drivers and having recognized it before. I think it's stuck at a phase in its boot-up that comes before the usb debugging is activated. My PC recognizes something is plugged in, based on the ding noise it makes (it's a Win 7 Pro x64 machine, and I think most of us are familiar with that ding noise), but the normal behavior of searching for and finding the drivers and then telling me the device is ready to use never occurs. Neither is there that "safely remove hardware" button in the taskbar.
So, of course, if the computer itself doesn't recognize it, adb can't either (confirmed by typing "adb devices" and it showing nothing). Is there anything I can do, or have I actually managed to completely (irreparably) brick my phone?
EDIT: The usb port is functioning, at least, as is whatever part of the circuitry or firmware controls the LED while plugged in and/or charging, because that works just like it should. It's just that I can't do anything but repeatedly cycle through the same "Unfortunately, the process com.android.phone has stopped", "Unfortunately, Themes provider has stopped", and a couple other messages that get covered up by those two, including one I briefly saw that mentioned "Settings". Haven't been able to see any of the others for long enough to identify any part of them.
EDIT2: I forgot about using the bootloader. Completely forgot. Stupid. Successfully in recovery, about to flash the same ROM with the new GApps. If it gets screwy again, I'll just remove the battery, replace it, and get into the bootloader to get into recovery.
dschlemmer318 said:
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
electrickoolaid said:
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
Click to expand...
Click to collapse
i flashed rom then 12-6_gapps_standard_4.4.1_signed then reboot this is the link for the gapps : http://forum.xda-developers.com/showthread.php?t=2012857
So my girlfriend's EVO 4G LTE is a bit of.. well, I'm gonna say bastard. I'm not new when it comes to rooting devices but I've never had to deal with one that fought me so much.
I've been through this adventure many times with it, and it gets more complicated each time. Here is what's happened with it so far.
It was stock, and it was terrible. It lagged so much, despite factory resets, that apps like google maps were completely unusable. It got no battery life AT ALL, and was generally freeze-happy and miserable.
So then I s-off'd it and after learning all its quirks, installed recovery and CM 11.2 (I think? It's been a year)
This worked great! For.. a few days. The phone worked, we went on vacation to a roaming area where Sprint had no coverage. We come back, and only the data works, texts and calls do not, and the phone acts like it's not activated. Yay. All attempts to get it activated are met with failure, much to the confusion of the poor sprint person on the line. The phone just will not take, at all. (damn lack of real sim cards..) We tried recovering back to a backup from twrp of the stock firmware but that won't work either? It wouldn't register with sprint even on the backed up version of stock sense. The phone seemed dead at this point. Bricked radio?
So we give up. We bring it to the sprint store, and they do some magic to it, and its back to stock, slow and terrible, but functional. We don't touch it until about three weeks ago.
But, my girlfriend is tired, again, of the terribleness, and asks me to try again. Okay, sure.
I install TWRP again, so far so good. The phone is still S-OFF from last time, which is nice. I go to install CM11.2 from the files used from last time (the MD5 does check out correct) But, the phone complains about not having a new enough bootloader. ???? (So I assume sprint downgraded the bootloader in the process of fixing it. somehow)
I forget the exact numbers, but we can't install CM11.2, only 10. or 10.whatever. the newest 10. Okay, fine. I gather a new set of cyanogen files, gapps, whatever, and flash all of that, so far so good.
This time it works, and stays working! Yay! So I thought.
As it turns out, its on a very old version of android (so old that it goes into a special usb file host mode when usb is plugged in) and more importantly, the camera is TERRIBLE. I've read that the evo 4g lte uses a special ImageSense chip to boost camera performance, and that cyanogen 10 does not support it. I can tell, because the camera is absolutely terrible. The battery life also is terrible, presumably because it lacks optimizations. It had way better battery life on CM11.2 when it worked. Other then that, its working just fine, but the camera is just unacceptable.
So, I want to know what to do from here. I see a few paths.
plan A:
update HBOOT to a newer version to allow the install of CM11.2
(how do I do that? I heard you have to use an RUU, but which RUU? I read that there is some touchscreen driver that is an issue depending on what version you run)
(Once I install the ruu is it business as usual, install twrp and then flash cyanogen like normal? Will it do the crazy not activation thing again? was that a fluke??)
plan B:
update HBOOT, but to a much newer one that allows the install of CM12 or whatever the newer ones are. Presumably updating past the touch screen driver issue and not allowing us to go back to an old version.
(once again, what do I need to do that? Is this advisable? I quite prefer the idea of running a newer version. So if this is the better idea, I will do it.)
I thank you greatly for your help. I'm not used to it being this complicated. I've read a lot of things about this phone and it seems very conflicting at times. I just want to get straightened out.
yeah, it's probably running like crap because the firmware is so out of date.
use this RUU http://forum.xda-developers.com/showthread.php?t=2653730
then re-flash twrp and another ROM if you want (i've been running cm12.1 for MONTHS) but she might be able to survive just like that. only fear would be staying vulnerable to security threats, but you've been living in that house this whole time anyway.
for a good while i was running this stock 4.3 with root and some xposed modules installed to get the cm functionality that i missed. but seriously, run the RUU, let it activate, then go under settings and update profile and PRL, fire up maps/navigation with GPS on so that it gets a good lock and its cache populated, then you should be good from there.
Thank you!
Can I use the same utility that I used to flash twrp (that one-click thing that seems to support a half million phones) or do I need something special? This sounds very easy to do. Almost too easy, given that the story of this phone's life is that the easiest thing I've ever done to it was take it completely apart to replace its battery.
never used the one-click stuff. flashing recovery via fastboot is simple enough.
get the adb tools, here's some easy instructions for that http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
get the latest twrp from here https://dl.twrp.me/jewel/
then follow these directions to flash twrp https://wiki.cyanogenmod.org/w/Install_CM_for_jewel#Installing_a_custom_recovery_using_fastboot
if not installing cm or any other rooted rom (you want to root stock) get supersu from here http://forum.xda-developers.com/showthread.php?t=1538053 and use the twrp installable zip
If you've gone through the trouble to S-Off, then fastboot flash the latest TWRP (3.0.2.0, I believe), which supports the new partition layout (extra 4gig of internal SD space).
From there, flash the official 651.4 developers version, go through the device setup which updates your PRL, then shut it down and reboot to TWRP and flash the latest CM12.1 and a proper gapps package (I use "stock", which is a bit much for some, but I like having everything available to me).
The one thing I do that most don't is to disable zRam and enable swap with my own script I wrote specifically for the external SD I formatted as vFat/ext4/swap.
After doing all this, I do not have the issues you seem to have, and the PRL seems to stay from the last install of stock Sense 5. Even with all the apps I have installed, it's still fairly snappy. Facebook/Messenger, and other memory hogging apps run smooth with no discernable lag, unless there's network issues.
YMMV, but look into using an app like "Ampre" to measure battery life and gauge if the battery is going bad or not.
Outside of that, there's not much left to do with these older devices that hasn't been done already.