Related
Well heres the story. I flashed cyanogen 6.0 and all was great,fast,smooth,perfect... Then it all went downhill. The backlight cut out. After wiping,reflashing,doing everything possible as far as that it was still the same.
I soon figured out that if i lock my phone while it was closed, then slid it open and hit menu the backlight would turn on, but it will not work when its not slid open at all.
Problem #2
As i have been dealing with the first problem and i dont have alot of time to fix it because of work and all, it grew even worse. Now when i do what i was doing to get the backlight to come on, The phone will randomly freeze/backlight wont come on at all/ Screen wont even come on.
When i turn on the phone sometimes the screen wont even come on but the backlight will and it wont get anywhere."blank lit black screen no tmobile g1 logo"
This also happens when i go to recovery using home+power. I remedy that by taking out the battery and starting the phone till it works.
Could someone please help me out here i dont really have to much to spend on a new phone and it would be great if i can get this one going like it should again.
you need to wipe before reinstall
if you have armonR, you wipe everything the wipe menu and flash the rom and the flash gapp-3
ive done that many times, hasnt solved anything. i dont know whats going on..getting to the point where i might just break down and get a htc hd2 and put android on it
Try flashing the Defanged Base (which you can find on the cyanogen wiki) then flash the Rom again.
to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.
tank65 said:
to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.
Click to expand...
Click to collapse
You lucky f***! How are you liking it? I was thinking about getting one soon but i havent talked to anyone with one. Is there anything you dont like about it?
I've checked and some says that I need to replace it but as I dont have much cash I wanna make sure that my screen needs replacing.
My bro got me an old G1. And its screen starts to behave quite odd recently. Sometimes I cant touch anything, or it just keeps pressing itself. (In cases like when I'm typing it will types it self bunch of letters in the mid and bottom lines (the asd-zxc lines) And when things happen I have to turn off the screen and wake it again. Problem resolved temporarily.
And it happens daily, if not nearly all day
So please anyone that got experiences or advices please tell me is it the screen's fault? And should I replace it?
Thank you for your attention!
P.S: I know that nothing can live forever...
I had similar problems. It happened when my battery was low... Im pretty sure it was just my ROM being buggy.
Thank you for responding
But I dont think so. I changed to dwang's rom (donut as I remember) and it still were "lagged" like that so I flash back to CM 6.1.2. So I dont think that's the roms' fault.
And about the battery... Im not sure. Sometimes when the batts gets lower I got better responds .. quite unpredictable
And what did you do?
I attempted to install a new ROM, failed. Tried to recover my back up, and now I'm learning to fastboot. :/
After the install failed, and I had a fresh instal of my ROM running, it seemed to stop.
I also noticed that it only did it when I had the keyboard opened.
Aww I'm not lucky as you are.
Since I've installed 4 roms but none of them fixes it. I'm thinking of changing the radio Im not sure though...
Just see what other people have to say
Still no clue...
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
thelistening said:
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
Click to expand...
Click to collapse
Try to upgrade to the 27.08 Radio/SPL combo. Follow all of the instructions contained within that post. It will suggest you also re-install your recovery. Do it. Once all of this is said and done, if its a software issue, it should be solved.
I had this same issue prior to the upgrade, and all is fine now. Mine didn't FC tho. If I touched the bottom of the screen, it would select something at the top. any questions or a perfect walkthrough, my direct email to my cell is in my info on the left.
<<<<<<<<<< Over there.
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
thelistening said:
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
Click to expand...
Click to collapse
Oh crap. You have the funky color camera?! That might actually be a hardware issue. But we can certainly try this out. I have the gTalk PC app, and it's up and running now if you wanna run through this.
Hello everyone,
As the title says, my tab s6 860 just stopped detecting my keyboard case out of nowhere, last night I just leave it on the desk like I usually do, and the next morning as I was going to use it it just wasn't detected at all. I tried reboot, turning it off and leave it like so, I went as far as doing a factory reset with no luck
I've read that for some people it worked after any of those steps, but so far I'm out of luck... I think (or hope) for this issue to be software related as it was working fine Andis not as if it fell or anything.
Also, I read Bout the possibility of this issue to be solved via an update on the keyboard firmware, but the problem is that no one seems to know how to trigger that update as it just happens when the tablet detects the keyboard. Somewhere in the Samsung forum someone mentioned that this update is managed by an application named Applinker, but there is no way to manually trigger it for it to update the keyboard firmware...
Please if anyone know how to solve it or have any possible solution or suggestion, let me know.
You most likely tried it but don't see it specifcally mentioned so just in case, you also tried removing/reattaching it? (Pull of/click on?)
Mine every now and then seems to loose connection as well but just popping it of and on usually fixes that.
yeah I tried that as if there were no tomorrow and it didn't work at the time, but it start working today, like I tried all morning with no luck, and during the afternoon I tried attaching it again and it just worked....I'm glad it works again , but it's still a pain not knowing the root cause of the problem
Hey all! New here. I just soft bricked my phone, i woke up to it not booting. I tried various fw in Odin, but no success. This is my day to day use phone, I don't have anything else, so I'd like to make it work again ASAP, hopefully without factory reset.
Hi
what manipulation did you do to get there before flashing a lot of stuff in odin?
I've been just pressing the buttons all around, then I read about Odin, so I tried it. Now my battery died, let's see if I can get to wipe the cache...
Update: no success. Is there a way to get it into recovery? the old volume up+bixby doesn't seem to work.
Sometimes its because the recovery itself is error so that button combination is not working..
Charge your battery until full, then factory reset it with odin, let see if that works
But before you do that make sure you download correct fw that match your phone model. dont try all fw available there, make sure you download fw for SM N950F..
Well it worked and it broke again... Back to square one.
Your infos are kinda vague.
Did you modify your phone and it got triggered by user-action, or did it hit the fan by itself?
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
fzoli469 said:
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
Click to expand...
Click to collapse
This was happening to me too before my phone just started bootlooping to recovery
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
fzoli469 said:
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
Click to expand...
Click to collapse
Try changing build prop, ro.config.tima to 0