I dl and odin'd EB01 this afternoon. I had the "opportunity" to pull the battery and when it booted their was a little box in the left bottom screen that said Safe Mode. Anyone ever seen this before on the epic?
Sent from Bonsai 5.0.3
I got a random reboot earlier this afternoon on DK28 and saw this.. think it's a automatic safety put into Froyo (whether by Google or Sprint is unclear) that lets you remove a problematic app if it's causing the phone to bootloop.. notice how it doesn't let you run anything but the stock apps in that mode.
I'm sure there is a special way into it as well so Sprint doesn't have to refurb every phone that installs a bad app... a technician can just boot into safe mode, delete the bad app. Back to normal..
That's only my theory...
The other day I installed the new CM RC2 rom on my HTC Wildfire. Everything went fine for the couple of days until it went into sleep mode and I could not come out of it. I had to pop the battery and when still problems, I re-installed rom - again with flashed kernal 4.1 and up to date gapps.
Managed to get it working. But then same thing again. Overall I had to re-install 5 times yesterday alone!
Out of frustration I tried to re-install my CM RC1 from before with the kernal 4.1. And this was fine again for about an hour, then again, mobile went into sleep mode, and again was left with black screen. Again not able to come out of it.
Am at a loss as to how to get my mobile back up and running. If anybody can help, this would be most appreciated.
Thanks
Does this happen with all ROM's, or simply CM7? Also, what are your overclock values and SetCPU Profiles, if any?
Have only tried cm7 so far. and cpu was not touched. was left at default settings. Am not able now to even boot into recovery. Totally DEAD!
Probably a hardware issue. I doubt CM7 can have such far reaching implications as to make the phone dead. Anyhow, this issue looks uncannily similar to this
Thats worrying.
If I do manage some how to get it switched on, is there anything that you can suggest to stop this happening again?
Also keeping the battery out of the mobile for a 5 mins, SHOULD that help instead of just taking out and imediatley replacing?
Doesnt sound too good. If you manage to switch it on you could try setting your minimum cpu speed to 245mhz+ Although it sounds like you have more serious issues. If its still under warranty I would consider returning it
Thats what I feared.
Thing is, cause it is rooted, it is out of warranty. I dont think I have a leg to stand on.
Its worth a try, they may not even check/notice that its rooted
Well.......
I managed to get it switched on. And decided to try and install Wildpuzzle as I had that on the phone before with no problems. And so all was well......
....untill just now.
Mobile went into sleep mode, and when I pressed the power button to get into it, black screen. Wouldnt come out of sleep mode. So had to pop battery again and after 10 mins, re booted it.
This seems to be the norm now. If it gets a chance to drop off into sleep mode, then I am stuck.
I am starting to pull my hair out.
Have just read on another thread that should try turning off auto rotation and auto brightness.
Fingers crossed this will work.
If the problem occurs throughout various ROMs it could well be hardware related. Flash an RUU (this will get rid of all traces of root) and return it
Will do.
Thanks
cant access cm7 rc2
any ideas why i cannot access or see any file in the website download.cyanogenmod.com regarding cm7 rc2 for buzz/wildfire?
My T-Mobile USA G2 has been rooted running CM7 stable with no issues for a few months now. I reboot the phone a few times per week. Everything has been great for months, then all of a sudden my battery was low and the phone started to slow down. I figured it was just setCPU lowering the CPU down to the 245mhz I had it set to. Then all of a sudden it froze, I had to pull the battery, I thought that was kind of weird, but figured what the hell, why not. A good reboot can't hurt, right?
WRONG.
I put the battery back in and at the boot animation (blue arrow circling Android on a skateboard above "Cyanogen Mod 7" banner) shows up, but the arrow starts to stutter, then the screen dims -> then goes black. So I figure the time out activated, no big deal. Then I realize I can't wake hte phone up! No matter what I did, if I plugged it into my PC, the screen would come on (lock screen) but it wouldn't register any touching of the screen, therefore I couldn't unlock the phone, and it would just time out again.
I ended up having to reboot into CWM and do a Wipe Data and re-install of CM7 from my SD card for it to work!! I tried wiping dalvik cache, battery stats, etc... everything except for wiping Data, but nothing worked. I HAD to wipe my data and re-install the OS...
Anyone know why this happened? Or what could have caused it? At this point I downloaded the newer version (7.0.3) and after wiping installed that, now I have to re-download all of my apps and re-setup all of my settings (extreme pain in the @$$ and very time consuming)...
Thanks in adv.
Do a search, I thought there was some issue with low cpu speeds and waking the phone up from sleep. Basically, the cpu is undervolted and doesn't have enough juice to turn the screen back on.
Search around.. it's on here somewhere. In the meantime, increase your min cpu speed.
maybe in here?
http://forum.xda-developers.com/showthread.php?t=1043118
Thanks, I had read about that prior to setting my phone up, and that had never caused an issue for months... I don't get why it would all of a sudden cause an issue?
Also, I couldn't even get to my desktop to change the min CPU speed... no matter how long I waited, the phone wouldn't wake/wouldn't let me unlock it...
I ended up having to wipe the phone clean and re-install a fresh install... in the new install I have the min cpu higher than it was before.
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
CapsLockKey said:
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
Click to expand...
Click to collapse
Was the CRT script based on the EI22 framework?
I got it from the EI22 CRT off thread in the theme section.
Last night I also had an odd reboot. Not like the old random reboots that would happen when the phone was asleep, this one seemed like it was caused by a GPS crash. I had been using an app that triggered the GPS, (weatherbug I think) and when I closed it, the GPS icon stayed on. Even after I turned off GPS it still stayed on. The phone also started getting pretty warm. GPS itself no longer worked. After a few minutes of trying to shut down GPS the phone locked up. A minute later it did a "partial" reboot, playing the startup sound and eventually giving me the launcher screen. It was still not running right, with the GPS icon stuck on and the phone very sluggish. I did a shutdown and restart. The phone took a long time to start up, sitting on the "big S" for a while just like on it's first startup. Makes me think something got corrupted in the cache and it had to rebuild it.
I don't know if this was just a random event or the sign of problems to come.
This was on Stock EI22, installed as an OTA upgrade over a fresh EC05 install. The only mod was the CRT off / Circular battery mod that I created at the UOT kitchen.
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
CapsLockKey said:
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
poit said:
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
Click to expand...
Click to collapse
Tried clearing data, reinstalling, etc. Doesn't matter, still FC's immediately after reboot. Problem must be with Launcher Pro not liking something, because I just flashed CleanGB Rom (which includes the CRT-off and several other tweaks) to try it out and it does the same thing on that.
Update: Seem to have solved it, but not sure why. Had Voodoo Plus set to load module on boot, when I turned that off LP did just fine after rebooting. Decided to flip the load on boot back on to see if it would start FCing again and magically enough it hasn't.
I just had a random reboot and im in stock EI22..... Why?
Sent from my SPH-D700 using XDA App
Been on it since it was released, no reboots here... Working great for me.
ive had this off and on for a few days now. i find it to be caused by having multiple launcher in my case spb shell .had it running stock the first day so i flashed a rom and its still there. also other apps that use alot of resources will cause it. it partail reboots about 3 or 4 times and then runs normal.
CapsLockKey said:
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
I have the same issue with Zeam Launcher, clearing defaults doesn't seem to help. I wonder if there's some kind of half-assed check to make sure that TWLauncher is running? I dunno, but it's obnoxious considering how many times a day I'm forced to reboot EI22, added to the fact that they got rid of the deathgrip reboot.
My phone has "Randomly" rebooted on me several times, usually in an area with little signal coverage. Each time, it seems like there's some program (like Spotify or DI.FM) running that's making network calls when the signal craps out.
EI22 has been nothing but problems for me.
Just had my first random reboot. I'm stock EI22 not rooted yet. Imanually installed on the first day and this was my first. Phone was off just sittin on the table and the screen come on showing low battery but was still sittin at 30% and it shut off and the samsung screen come up and went thru the boot up process.
Sent from my SPH-D700 using xda premium
Please see this thread if you get random reboots with WIFI on.
http://forum.xda-developers.com/showthread.php?t=1359315
My Stable setting with no random reboots !!!!
After trying out virtually every rom/kernel out there (started with stock) I finally got a configuration in which I hadn't got any random reboot (or any other silly issues). My current setting are :
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
Hope this helps !!!!
Epic Timezzzzzzzzz !!!!!!
I still get random reboots in EI22, but not as many as I did on the GB leaks. I can cause a reboot by scrolling to fast in Settings, Applications, Manage Applications, All. I have had the phone run for 90 hours without a random reboot so I'm happy.
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
rando991 said:
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
Click to expand...
Click to collapse
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
i dont get any with
ROM = ASC AICS 5.5
Kernel : Samurai 2.0.6
Theme = Shake & Bake Mix Up v.5.9
kennyglass123 said:
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well I did notice it only happened on that particular charger (from Walmart)...also, my wife's epic didn't reboot, but had the charging light stuck on all day. I had to power it off and remove the battery to end it. Would that be maybe the same problem?
Been on CleanGB for quite a while. Went out of town this weekend to Chicago and ended up being rebootpalooza on my phone. Probably had almost half a dozen, once it just shut down in the middle of a phone call at the train station after the low battery notice came up, even though after I powered it back on it still had 28%. Another reboot was I unplugged the car charger shortly after the "full" indicator light came on. Others were just amazingly random. I've loved my Epic up until this trip when it turned into the most unreliable thing I've had.
I was going to give my girlfriend my D2 that I no longer use because I'm running a Stratosphere now. When I stopped using it I had CM7 GB on it, but figured I should SBF it back to stock (blur) so she can get an out of the box experience and then decide if she wanted me to rom it. I used a 2.3.3 SBF and RSD Lite. I've always used the Froyo SBF prior to this and then took the OTA to GB, but this phone isn't hooked up to Verizon, so there wouldn't be an OTA to get. I SBF'd to 2.3.3 and it seemed fine. I rooted using the one click root took via Pete, and everything was fine. I put Milestone Overclock on it and turned the setting up to 1300. I then used Super Manager to rename the Blurupdater.apk to a .bak and deleted the odex file, then rebooted into factory recovery and wiped the cache and things were fine. I put the phone on my dresser and left it. Next day I picked it up to check it and it wouldn't turn on, figured the battery was dead so I just left it and thought I would deal with it later. My girlfriend took it to work with her to get it switched over and couldn't get it to turn on either. She took the battery out and swapped it with the battery in her OG Droid and the battery was fine. Plugged it into the wall and the charging light comes on next to the USB port but it won't boot for anything. Holding the up on the physical keyboard, holding the x, none of this works. It just won't turn on. I'm aware it's bricked, but suggestions on why this happened when it was perfectly fine when I set it down?