Is there any way at all to disable the Fascinate from ever loading into safe mode again? It's really annoying when it happens because I have to reset all my widgets.
I've flashed my phone several times and it happens with every rom that I've had on it so is it part of the baseband kernel?
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
johnnyplaid said:
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
Click to expand...
Click to collapse
X2
List off the steps you used when flashing these last few roms (and what rom specifically) that you say are making you boot into safe mode...I've only seen it once on my phone and 1 reboot fixed it and I never seen it again, but that was months ago and I just chalked it up to me missing a step?! I have flashed many roms since and never see safe mode again.
Sent from my SCH-I500 using XDA App
Im starting to think that it's more a problem with my Fascinate than anything else. It usually happens when I have to pull the battery due to it locking up. Sometimes pulling the battery out a second time still doesn't get me out of safe mode and I have to continuously do it until it does.
For the past few months I've been using CM7 and updating with nightlies. On Monday I updated to the stable GLITCH kernel and so far it seems to be running much better. It's always had a problem with randomly bringing up my keyboard and backing out of apps and I have not had that problem yet since putting the GLITCH kernel on it.
Figured I'd also note in here that the GLITCH kernel is not currently working with the newest Cyanogen nightlies. It bootloops and I found that out the hard way.
For now im running GLITCH v11.1ML and CM7 Nightly 35 and it's been great so far.
so glad I havent run into safe mode
Related
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
yep
+1
Not very often but very annoying if you use your phone as alarm clock.
I honestly haven't experienced either with my SGS. I can sympathise though as my Milestone used to do both way too often (hence swapping for the SGS).
It hasn't happened to me.. It might be running a software or hardware watchdog to reboot automatically when the system panics. Ensure you are using a stock rom, otherwise, it may even be faulty hardware
Would happen several times a day on my Motorola Milestone so I sent it back and got the SGS. Totally rock solid. Only time it reboots is when I want it to. Maybe you have a rogue app?
you guys have any changes to the CPU speed whatsoever, task killers and all? i once used SetCPU and it sort of sent me into a random spree of reboots and such.
i remember rebooting, scanning 10gb of media, auto-reboot... repeat 4 times. lol.
Well it hasnt happened since yesterday. I will flash to froyo today just in case it was software related
Sent from my GT-I9000 using XDA App
dakine said:
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
Click to expand...
Click to collapse
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
AllGamer said:
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
Click to expand...
Click to collapse
Link would be helpful, because I can't find that topic.
WOW, old thread that got dug up, for me it was just a software issue. I flashed many roms since and haven't had it happen again. I never reset my battery stats but I think clockwork mod recovery has an option to do that so most of the custom roms make that easy.
I also had random reboots and power-offs, on average once every 2 weeks, running on stock-firmware JF3. Problems did not go away when I manually upgraded to JM2. Problems stopped when I upgraded to Froyo...
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.
Hey,
I was hoping to find someone who had similar problems to mine but have had no luck, so I decided to break down and just make a thread.
My Evo (003) has been giving me really scary problems ever since I tried installing CM7 rc3. To preface, I have been installing the nightlies since 15 and could be considered a flashaholic. I run amonra 2.3 and have all of the latest radios and such. To avoid a long paragraph, I'll post them as bullet points. I've tried other ROMs and plenty of kernels and I get similar errors in every attempt. I'm currently running CM7 final and the latest savaged kernel
- Whenever I reboot the phone, it bootloops once, then boots fine
- When I take the phone off the charger in the morning, the phone runs badly and the charging light stays on until I reboot
- I get a lot of "phantom" keypresses every now and then that render my phone useless until it stops in roughly a minute
- The screen off animation no longer works in CM7
- The phone randomly reboots every other day or so
- General slowness
I can't help but be scared that I will restart the phone at one point and it won't boot up, like some other people are experiencing. Can I be saved?
Thanks for any help!
When placing phone call my device crashes with purple led flash.
cell signal normal, text messages work, cell data works
I'm not sure if problem lies in hardware or software(bad flash, radio, ect)
I replaced the digitizer
Currently running Kang ICS RC0-9.0 | faux123-v025
Had same problem with Neutrino 2.1
Any ideas or test suggestions?
PROBLEM SOLVED, WHERE DID MY FRIDAY NIGHT GO THOUGH?
*deleted post incorrect information
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
dac1227 said:
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
are you already on 2.3.4.91 ?
chamoy said:
are you already on 2.3.4.91 ?
Click to expand...
Click to collapse
No, I couldn't get the zip for 4.91 to flash for some reason so I did Neutrino 2.5 after sever data formats.
update: on on GB 4.5, same problem persists
SOLVED
How did you solve the issue?
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Well the issue was less solved but minimized in the end.
After many fastboot formats and CWM flashes, I ended up fruitcaking back to 2.3.4, that's when the problem started to be less of a hassle; meaning the screen would come back on and buttons/soft-keys were again responsive and a battery pull wasn't needed.
I re-installed Turls ICS and the problem is still present, but it doesn't hinder making or receiving calls, I just hold my breath with each.
I'm suspecting that when flashing either the kernels or roms, things are not getting cleaned and formatted as well as they ought to be. I know there is a universal CWM zip floating around somewhere (seen it in the skyrocket forum). We've had similar issues in the skyrocket forum where remnants of previous flashes were being persistent, or resistant to format attempts.
I messed with it for hours trying to fix so I cannot say for sure what I did to make it a non-immediate issue, but if others describe like problems I try and help.
xscottishx27 said:
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Click to expand...
Click to collapse
I was having the issue with Neutrino 2.1, 2.5; Turl ICS, and stock 2.3.4. The latter seemed to be the most effective method I employed to fix, without bricking.
Hey folks,
My wife's MyTouch 4G has suddenly started locking once it goes to sleep. I cannot wake it up at all without popping the battery
here's what I've tried
- Removing potential problem apps
- Hard Reset
- Clearing all items in recovery (cache, delvik(sp?), battery stats, etc..)
- SIM swap with my phone (also a MyTouch 4g)
The only thing I didn't do was try a different ROM, only because her and I are using the same phone, and my install is working perfectly fine (Awesome ICS 3.6). Any other suggestions before I look at getting a new phone?
Thanks!
RickoT said:
Hey folks,
My wife's MyTouch 4G has suddenly started locking once it goes to sleep. I cannot wake it up at all without popping the battery
here's what I've tried
- Removing potential problem apps
- Hard Reset
- Clearing all items in recovery (cache, delvik(sp?), battery stats, etc..)
- SIM swap with my phone (also a MyTouch 4g)
The only thing I didn't do was try a different ROM, only because her and I are using the same phone, and my install is working perfectly fine (Awesome ICS 3.6). Any other suggestions before I look at getting a new phone?
Thanks!
Click to expand...
Click to collapse
(1)
Try flashing a new kernel
(2)
Try a new rom Awesome ICS is very Outdated. (Yes in working on an update but its outdated)
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
I will try this, I have never flashed a kernel before,I usually use whatever comes with the rom, any suggestions on a particular kernel?
...Awesome... said:
(1)
Try flashing a new kernel
(2)
Try a new rom Awesome ICS is very Outdated. (Yes in working on an update but its outdated)
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
Click to expand...
Click to collapse
RickoT said:
I will try this, I have never flashed a kernel before,I usually use whatever comes with the rom, any suggestions on a particular kernel?
Click to expand...
Click to collapse
Personally I like Frosted Cherry There are a few more here in Awesomes OP HERE though. If one doesnt seem to work give the others a shot.
Well, sadly I did a restore on her phone, and now it just locks up on boot and never gets to the setup process for your account. Then I tried another rom and it complained about an unexpected offset (different numbers each time). Then I found this post.. http://forum.xda-developers.com/showthread.php?t=1394238
Followed the instructions to restore to the factory OS... now it doesnt get past the boot animation, or goes to sleep during it which requires a battery pop. What the guy explained in the post about the eMMC chip going bad exactly describes the behavior of her phone, so I am thinking it is that. We ordered her a Samsung Galaxy S III ($600) last night after spending about 4 hrs trying to get the phone to even boot to the OS.
Sadly I think its toasted
thanks for all the help/suggestions though, I may use them on my phone since mine is still alive and kicking with no issues (*knock on wood*)
~Rick
RickoT said:
Well, sadly I did a restore on her phone, and now it just locks up on boot and never gets to the setup process for your account. Then I tried another rom and it complained about an unexpected offset (different numbers each time). Then I found this post.. http://forum.xda-developers.com/showthread.php?t=1394238
Followed the instructions to restore to the factory OS... now it doesnt get past the boot animation, or goes to sleep during it which requires a battery pop. What the guy explained in the post about the eMMC chip going bad exactly describes the behavior of her phone, so I am thinking it is that. We ordered her a Samsung Galaxy S III ($600) last night after spending about 4 hrs trying to get the phone to even boot to the OS.
Sadly I think its toasted
thanks for all the help/suggestions though, I may use them on my phone since mine is still alive and kicking with no issues (*knock on wood*)
~Rick
Click to expand...
Click to collapse
Hopefully the samsung works well for you. Personally i've never heard of a "Bad Chip" phone acting that way in particular. When you boot into HBoot (Power and Vol Up at the same time) do you still have S=Off?????