Hi.
A relative has a Optimus Black which didn't recognice his SIM card anymore. After some research, I reflashed V10E, fixed his IMEI and I solved that problem.
My problem now is that touch buttons stop working if I put any other firmware. I've tried official V20S and V30B, with smartflash, and upgrading to IZS v0.4 with V30B baseband using the V10E recovery, and every combination I try fails: after maybe a couple of touches, soft buttons don't work anymore. Of course, I've tried all kind of wipes.
If I go back to V10E, they work again, but they are not as responsive as they used to be.
I've found that thread with the same problem in V28c, but I'm opening a new one as I've found the problem happens in many firmwares. Please merge the two threads if you think that's better
I've also found a thread in AC regarding that problem, but adding "device_provisioned=1" in settings.db didn't work either.
Thanks!
Until someone solves this problem you could use a NavBar as a workaround.
Sent from my LG-P970 using xda app-developers app
I am using Original 4.04 ICS...And same while charging soft keys works fine...other than its unresponsive most of the time..Please help...It happened after 4.04 Upgrade..Prior to that It was working fine...
Related
I am considering upgrading to 2.3.4 on my galaxy mini to solve the "sleep of death" problem... is anyone out there who has upgraded to 2.3.4 still having the "sleep of death" problem?
Whats sleep of death problem ?
It's when the phone is still "on" but will not wake up. The only way to get it working is to take out the battery. Many are reporting this happening every day or two.
Happens on i9000 for me, I just keep powerbutton pressed until it reboots. No need to remove battery.
I think i need to do a factory reset on phone + sd card someday, maybe it resolves it.
this happened to me too. just reset phone and when it starts, try to use the phone or just simply tap the phone every time it tries to sleep (anything works as long it doesn't sleep)... just keep on doing this for about 30min? or more
(make yourself busy while doing this cuz its gonna be boring just tapping)
I think it's related to hardware problem (not confirmed yet anyway)... Don't believe that "upgrade" could be the solution..
I actually hope so!
GT-S5570 on Train
I just upgraded today using kies.... now when I try to start up it never gets past the step where it shows the "Samsung Galaxy Mini" text. Creating another thread for this problem.
With CheckFUSDownloader (thanks to Luffarjoh - search 3D) you can download the archive used to update your fw and, so, reflash it with Odin (even more times if needed)...
GT-S5570 on the road
Doc_cheilvenerdi.org said:
I think it's related to hardware problem (not confirmed yet anyway)... Don't believe that "upgrade" could be the solution..
I actually hope so!
GT-S5570 on Train
Click to expand...
Click to collapse
Nope, it's not hardware related. Never had a SOD since I used tjstyle's CM7.
Early Gingerbread firmware from Samsung has SOD too, but I think the latest versions doesn't.
Official firmware is now on 2.3.5, FYI.
If I can't get passed the logo screen what is the best way to get my firmware information? The guides say I need this info to choose the right rom.
Thanks!
This is a Froyo problem, didn't happen in Gingerbread :3
Yeah, had the same problem when on Froyo, after flashing GB2.3.4 the problem hasn't occured.
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Cheshire-Cat said:
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Click to expand...
Click to collapse
try in stock rom/eclair about a week ,I think it is about nAa issue !!
just full wipe and flash stock rom..........using flash tools......or try using song update service........
binhari said:
just full wipe and flash stock rom..........using flash tools......or try using song update service........
Click to expand...
Click to collapse
I did, as I stated before. Still not working properly.
What I don't understand is how flashing a new kernel/ROM can break it in a way that not even flashing back stock Eclair solves the problem. I can only think of hardware failure but... it would be akin to a computer failing because you installed a different version of Windows.
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
illusionist.h1 said:
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
Click to expand...
Click to collapse
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Cheshire-Cat said:
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Click to expand...
Click to collapse
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
illusionist.h1 said:
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
Click to expand...
Click to collapse
I don't know exactly how ROM flashing works -- I've seen a "backing up system files" message, and I think that there's a reason why the stock 2.1 image is about 200 MB while CM7 ROMs rarely exceed 100 MB. I guess that some files are kept. Maybe if one or more of those files (say, a driver) is replaced with an incompatible version... but then, flashing stock should solve it. Maybe someone can shed a bit more light on the subject?
Another possibility is software-caused hardware failure, where some kind of misconfiguration physically damages the hardware. It's very uncommon, but who knows.
Hi,
my P990 has a big problem.
for a while no one can call me or i can make a call.
my research gave following results:
enable 2G only: i can take/make calls, mms not working
enable 3G: no one can call me/ i can not make calls - internet is working
Statusmessages: Network busy
Caller gets routed to mailbox or gets busy-signal
i thought, there might be a rom issue or mistake with bb,
i was using pac19.9.0
made full restore with progmaq-default-cm-10-20121105 - problem persists
reverted back to gb with all features: gb partitioning, gb-bl, gb-rom - problem persists
changed several times bb from v10d to v20s, v20m, v30b, v28g, v20b (with 4 file-flash) - problem persists
yesterday tried going to ICS 28g - problem persists
has anyone any idea?
... i don't know what else to try
Have you tried a sim from a different network/carrier?
Sent from my LG-P990 using Tapatalk 2
yes i tried - problem is the same with different network/carrier
Is your IMEI displayed correctly? Look in About phone->Status or enter *#06# in the dialler to check.
Sent from my LG-P990 using Tapatalk 2
yes, also already checked.
imei shown in info is same as under battery
Then I've got nothing. Sorry, but you've already done everything I would have suggested.
Hopefully somebody else will have an idea
Sent from my LG-P990 using Tapatalk 2
thx 4 your help....
someone else with an idea?
Hey guys it works again!!!
when i went sleeping there i got an idea ...
there was something i haven't tried ...
flashing full original kdz from lg
so i downloaded several versions, i got a lot of errors when flashing kdz with lg-offline-flash
so extracted and tried with smartflash an after a lot of tries ... i flashed at least goodbye-rom to try if it works
and it worked now - but i lost my imei - so went to hiddenmenu, activate cp-usb and typed in my imei...
now all is working again ... i'm so happy, i'm feeling glad, i got sunshine in my head .......
2-3 weeks ago i updated my lg p990 to ics v30a using smart flash. and soon after upgrading i fond that ics is creating problems.
it crashes and phones reboots and dis happens all the time. sometimes it reboots when i am entering my sim pin. sometimes when am working on net and someone calls i pick up the phone reboots. i was so fu**ed up that i decided to root it bt that too didnt work.
What i used :-
1--> superoneclick --- it didnt work.
2--> root unlocker-- didnt work
3--> android root -- didnt work
4-->z4root -- didnt work
5--> even tried that bin4ry stuff that too didnt work. asks for restore i press restore and the shell runs forever.
6--> tried AIO toolkit.
rooted the custom rom. bt wtf problem still persists i seriously want to just root my phone please please just help me.. nothing seems to work exept the frequent rebooting of my phone.
shashank926 said:
2-3 weeks ago i updated my lg p990 to ics v30a using smart flash. and soon after upgrading i fond that ics is creating problems.
it crashes and phones reboots and dis happens all the time. sometimes it reboots when i am entering my sim pin.
Click to expand...
Click to collapse
I have same problem. Sometimes Phone freeze or restart or shutdown. Many times I have to take off battery to starts it again.
I uninstall all apps but problem goes on only with ROM's apps.
hi friends need help .
Last night i rooted my galaxy note with cwm.tar recovery and superuser.
everything was working fine until i downloaded rom manager and did something, i dont remember (perhaps flashed rom ) and my device restarted after that my capacitve back button and menu button stopped working and lights are showing on always even i tried to disable it from setting. I flashed to stock rom ics and jelly bean but still problem not solved please help me friends. i sure its not hardware issue any suggestion ?
galaxy note shve160s.
OK here's you're first problem, this is not the thread for your device. Second you may need to use Odin to flash your original stock ROM. Your stock firmware can be found at www.sammobile.com or samfirmware.com. If that doesn't work it maybe a hardware problem. Next time search XDA for your phone's model number. This thread is for SGH-T879. Good luck. P.S. don't use ROM manager to flash CWM If your exact phone isn't listed. You're lucky you didn't brick your phone.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
thank you it didnt solved my problem perhaps its hardware related problem.. unlucky me