Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas
Jonnibravo said:
Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas
Click to expand...
Click to collapse
Could you post a log of this? Could you also provide some more details about your set-up (a2sd? swap? comcache? spl/recovery?) and how did you get to this point (did you wipe before flash? did you run any back-up apps, what were you doing when it happened?)
Once we have that info we should be able to figure it out.
I started out with th jesus freak rom then I decieded to flash the cyanogens 3.6.8.1, I had trouble with the market because I hadn't wiped first, I did that and all was well for at least 5 days. I created an ext2 partition for apps2sd but I'm not sure if that worked. Then on the Saturday 6 days later I put fotmob on my phone so I could keep an eye on the opening premiership season put the phone in my pocket whilst at the football and 2 hours later the phone screen was dead, nobody could call me tho I know the phone was operating and booting only t mobile manage to get through, I tried a reboot, then took the sim card out and the screen went back to normal but was stuck on the splash screen. I tried fixing file ext but came as error asomething about the super block being unreadable tried manually but didn't work, tried backup still stuck, reflashed worked fine for. 20 hours then it happened again this time I wasn't doing anything with the phone no programs other than the usual running in the background, this time I removed the sim card and the phone went back to normal again for about 4 hours then it happened again this time removing the sim didn't work.straight away but eventually it came good again.
Its now 11 15 and its running fine again. I have noticed that I now only have one ringtone (dream theme) and one notification tone and I'm getting a few force closes tho I not sure what they are I will report them if and when I see them
you need to get audio resources and unzip to the sd card all the ringers. search xda for audio resources
The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening
Jonnibravo said:
The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening
Click to expand...
Click to collapse
Because you lost your ringtones, it sounds like your SD card is acting funny, I would format it using this guide (make only 2 partitions for the time being, fat32 and ext3).
See if that works...May be complete reflash with wipe wouldn't be a bad idea neither.
That's all I can suggest at this point, I'll need to see a log to be anymore specific, but try this out, sounds like you've got nothing to loose
Good luck.
Thanks for your reply I am very greatful, I have tried a different sd card without setting up partitions and it still happens. I think the latter is true and a complete reflash is definately the thing to do.
I think this may be a hardware issue because as I mentioned it only happens when it has been in my pocket for a while, perhaps it is overheating or something.
I'll try a complete reflash and let you know if it happens again.
Wipe, re-flash, reformat your sd (or take it out altogether, just to rule it out see what happens... This is all I can tell you....
good luck
Related
Hi,
I have JF 1.51 and its been running pretty well for a long time now. untill today when I was on the phone and it suddenly semi--rebooted, what I mean by that is it didnt go all the way back to the T-Mobile G1 screen, but only to the android screen and it doesnt stay their for a long time only for a couple of seconds and then the phone is operational again !! it only takes about 10-15 sec. from Android screen to fully operational with a network signal !
Happened three times already, and I havent installed any new apps that could have made this !
My only guess is overheating? I checked the bat. temp. the first time and it was around 42 C so i thought it could have overheated since I was charging and talking at the same time. But then the second time I was at 32 C when it started rebooting, but it was also charging.
So Any ideas ?
Weees said:
Hi,
I have JF 1.51 and its been running pretty well for a long time now. untill today when I was on the phone and it suddenly semi--rebooted, what I mean by that is it didnt go all the way back to the T-Mobile G1 screen, but only to the android screen and it doesnt stay their for a long time only for a couple of seconds and then the phone is operational again !! it only takes about 10-15 sec. from Android screen to fully operational with a network signal !
Happened three times already, and I havent installed any new apps that could have made this !
My only guess is overheating? I checked the bat. temp. the first time and it was around 42 C so i thought it could have overheated since I was charging and talking at the same time. But then the second time I was at 32 C when it started rebooting, but it was also charging.
So Any ideas ?
Click to expand...
Click to collapse
Sounds like a Kernal oops. Wipe and re-flash, you should be fine.
Ouch!! Cummon man.....their gotta be something else I can do besides a wipe!!
I just wiped and reflashed about a week ago because my SD got corrupted, and doing it all over again now......is really a pain in the ass
format your sd card then wipe and reflash. It should not corrupt your sd card. I suggest flashing the cyanogen recovery image 1.3.1 because it will make your life 10x simpler...
Good luck
format your sd card then wipe and reflash. It should not corrupt your sd card. I suggest flashing the cyanogen recovery image 1.3.1 because it will make your life 10x simpler...
Good luck
Thanx guys for the replies.......im reflashing now, the situation got out of hand the rebooting started happening more and more untill the phone got unusable. it reboots eveyr min now. So yea I got no other option.
Thanx again, and yea im trying with the Cyanogen image.
Hi guys, I have had a G1 for over a year now, and it has been rooted for that long. I began using cyanogen's mods since 4.1 or so, and they have been rock solid until recently, when I upgraded from 4.2.6 to 4.2.7. Ever since that upgrade, my phone has been "freezing" and rebooting at seemingly random intervals.
First, let me try to define what I mean by freezing: this usually occurs when the phone is put to sleep, and it just refuses to wake up. The screen remains black, however my notification LEDs continue to flash (if they were flashing before). Sometimes, the phone freezes while I am using it; buttons stop responding, and opening/closing the keyboard does not change orientation. The phone usually gradually slows down to a crawl before this type of display-on freeze happens. In both cases, I am able to restart the phone by pressing call+end+menu buttons.
For the restarts: these started happening recently, I'll guess after 4.2.9. This always happen while I am using the phone. It'll pause for a second, like it's frozen, then restart back to the G1 boot screen a few seconds later.
I have tried wiping, repartitioning my SD card from scratch, using the phone without any of my apps installed, etc. The only thing that seems to fix this is if I downgrade back to 4.2.6. I have tried to narrow this down to the best of my ability, but I still cannot figure out the cause. My question is, how can I begin to troubleshoot this? Is there a log or some way for me to see what is the last thing the phone tried to do before it froze/rebooted? Right now, I don't even know where to begin.
well for the phone freezing it MIGHT be too many apps running in the background and eating up CPU usage...download advanced task killer from the market, it allows you to close apps that run in the background.
as for the random reboots, i am almost certain it has to do with the rom you are on. there should be an app called "log collecter" in your app tray, it comes with the rom, try and get the logcat from it when your phone reboots, and send that logcat to cyanogen via the link he provides on his thread.
2 things that I can think about:
1. Wipe you dalvik-cache
if that does not fix it
2. This may be a good time to re-format the ext 2/3/4 partition of your card and do a complete wipe.
I have this exact problem, it first started with random sd card errors "removed sd card" with an sd card inserted, and now the black screen of death, I reformatted and repartitioned my 8gb transcend class 6 card and flashed latest cyanogen. Today I got the black screen again so I used nandroid and went back to cyan 4.0.4, I still got the black screen freeze running old rom but so far sd card is working so not sure what the cause is, bad sd card? I just got this card a month ago... or phone going bad?
yeah, i get the freeze, its usually when i am running multiple resource eating apps. Try advanced task killer for a convenient notification bar click away from closing apps.
I also get the other problem where it wont wake up! Seems like we are running into the same problems under the same ROM. When it doesnt wake up i usually wait a few seconds and try pressing other buttons than the menu button to wake it up when its not turning on. A combination of waiting 5 seconds and trying a different button usually wakes it up.
Hey guys, thanks for the logcat info.
The most frustrating part about this problem is that it is unpredictable; it just happens when it feel like it and is impossible for me to reproduce, therefore I cannot figure out the cause nor can I tell whether or not any changes I make have any effect.
I do have ATK, and I use it regularly. It still doesn't stop this from happening. In fact, I installed ATK in order to try to solve this, which means before this started occuring, I did not even have ATK installed nor did I have this problem.
Can anyone tell if there were any significant changes from cyanogens 4.2.6 to 4.2.7? I see the changelogs, but most of it doesn't really mean anything to me because I don't understand what its talking about.
Yeah I usually get the freeze after installing a new rom onto my htc dream 32a. I just take out the battery and put it back in. Then I reboot and have no problems after that.
try going back to previous rom you had and see if the problem still exists... could possibly be an issue with latest update for rom...
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Sound's like Kernel panic. Wipe everything and install soemthing stable like cyanogens 4.2.15.1 or dwangs rom. Didn't know there was anything worng with SuperD's kernel though.
jaekim708 said:
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Click to expand...
Click to collapse
Since the rom relies on apps to sd I would guess the ext is borked and maybe the fat32 as well. I would reformat the whole thing to fat 32 then reformat to ext2 or 3. Load Dwangs rom for testing (easier to get running just as a test).
So I wiped my SD (ext4, dalvik, fat32) and tried cyanogen. Then I tried Pays. Reboot problem's gone, but neither of them is reading my SD card.
I'm assuming its just a matter of backing up the SD and repartitioning? I'll try that next when I have time.
Thanks for the help guys! Lastly, any ideas on why this happened? It'd be hard to pinpoint the exact reason, but I'm assuming I'm not the only one who had this problem - how did other people get to the situation I'm in?
I wiped all of my SD, repartitioned, wiped the phone, flashed AOSP 1.6. w/ root and "expansion" pack.
Reboots are less frequent, but they still occur too often. They don't occur by themselves - its always when I'm using my phone.
It seems that it reboots more when its connected to my computer. The SD isn't mounted, but the simple fact that its connected seems to trigger reboots more frequently. Is this a coincidence or can a USB cord trigger reboots?
Help please
EDIT: The phone just made an audible cracking sound as it rebooted - like someone stepping on gravel. Hardware issue?
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging