Greetings all, recently I have rooted and flashed Cyanogenmod 10.1 nightly to my GT-i9300 but a couple of days ago I started to get random reboot loops, the screen waking and sleeping on its own, etc. I tried flashing several other AOSP based roms such as AOKP and Carbon with no success. Today while I was in the car I noticed that if I just extremely lightly touch the power button it will function as it should, however if I press it normally it starts messing up again. I'm not sure if this is a problem with the 3.0 kernel of the roms I've flashed or if it's simply a faulty power button but I would like some enlightenment so I can make my phone usable again, cheers
Hey there.
whats the android version of your rom? 4.2 or 4.1?
i had almost the same problem with my S3 when i flashed a rom with android 4.2
it seems like on the 9300 the hardware isnt able to work properly with 4.2 8if i imagine this info correctly)
after wipe and installing 4.1 everything was fine again.
i hope this may help you
Related
Hello folks, first post, hope you can help.
My phone has a very specific problem that happens with every rom BUT with AOKP.
When the phone is on idle it just gets stuck, black screen, button lights are on. Only thing to do is pull the battery out. It also happened with the stock rom, so I tried to unroot it and give it to sprint but they couldn't take it because of a small crack on the screen(been there forever).
I came back home and tried to flash it with a custom rom again, and recovery was broken, so I flashed recovery on the device 3 times before it started working again.
I randomly chose AOKP and it was working pretty well, although it slowed down lately a lot. I tried to install JB on it recently and the problem returned, so I tried CM9 again, CM10 even tried Bugless Beast, same thing. I keep going back to the backup I have of AOKP and it's the only one that doesn't crash my phone.
I've attached the phone information so you guys can see exactly which built I'm running.
Bump.
Please help me fix my phone, I'm really at loss how to solve this problem,
Do you turn deep idle on? If so that could be the problem......when u flash a new rom, as your setting everything up, make sure deep idle is turned off.....the option is under advanced in the cm roms .......hope that helps
10....0011....10101
hii... I have a very strange problem....
I have an unlocked device and I have had pretty much every stock based rom that was published (from hydro to cleanerom 2.7) working perfectly....
The problem is when I try to use any cm based roms (cm10, baked, paranoid etc..) they work fine... but…….. When I connect the stock asus charger to the device, the screen immediately goes blank and can’t be turned on again... (Sometimes it turns on but as I unlock my lock screen,
it becomes black again).
As I disconnect the charger, I can go back to use the device normally...
Please help… I would like to move on to other roms and have the ability to charge the device while using it…
Thanks!! )
Hi, I recently got a certified like new replacement VZW GS3 which freezes 10-15mins after the screen goes black while at the lock screen. To fix it at that point I have to pull the battery and turn the device on again. Buttons pressed while in this state do nothing, not even cause the menu keys to light up
Here is the sequence of events since taking it out of the box
Recieved it as 4.1.2 stock jellybean
Rooted, CWM Recovery, Unlocked bootloader - followed this guide - 29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii on rootwiki (can't post links)
Clean flashed Cleanrom 6 RC2, noticed the lockscreen freeze issue
Flashed lean kernel to see if it was a kernel issue
Clean flashed Liquidsmooth 2.4 to see if it persisted on other roms, it did
Odined back to full stock - issue persisted
Accepted new update that was released today - issue persisted.
The issue does not appear to happen when plugged into the charger.
I am now preparing the phone to send back to Verizon, but I am wondering if anyone has any suggestions. Based on google searches it seems that it is a hardware issue because changing roms/kernels/ going back to stock did not fix it.
I have been successfully running custom lollipop rom's from november, but couple of weeks ago it changed.
I installed some new rom to my OPO, can't remember what. It installed and run fine, but when I disconnected the usb cable connected to pc it freezed and started bootlooping. Phone sometimes boots to os but freezes immediately and bootloops again. If I connect it back to pc, everything works fine.
I managed to get it working by restoring to stock and locking bootloader with OneToolkit for OS X. But there were some problems; the screen wouldn't rotate, battery drains a lot faster, like in 10 hours with very little use, and many more. I unlocked bootloader, installed custom recovery and rooted, nothing changed, but when I installed different rom bootloop starts again. I've tried with many roms. It does'n matter if I install the rom with usb connected or not.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
With these two guides the phone works normally, but still can't use any other roms.
"make_ext4fs /dev/block/mmcblk0p15" fix didn't do anything.
Any similar problems?
Sorry for my bad english.
I am facing the same problem.
Someone please help us fix this problem.
Do you have the latest firmware flashed? That is a requirement for most LP ROMS lately. It normally posted on the first post of the ROM's forums, its also included in the lastest CM12 nightlies from what I've read.
I have a rooted 5113 running Android 4.1.1. Haven't used it for a long time and have not installed a custom rom. Kernel number is 3.0.31-523998. Whenever the screen times out, the tab 2 turns off, and I have to hit the power button button and the volume button at the same time to restart it. Does anyone have any idea as to how, I can prevent the tab from turning off when the screen times out.
Also, my ultimate goal is to upgrade to KitKat so that I will have mirroring. If I install KItKat, is that likely to get rid of the shut off problem. Thanks for any help that can be provided. Should and that I have Titanium Pro.
decijp said:
I have a rooted 5113 running Android 4.1.1. Haven't used it for a long time and have not installed a custom rom. Kernel number is 3.0.31-523998. Whenever the screen times out, the tab 2 turns off, and I have to hit the power button button and the volume button at the same time to restart it. Does anyone have any idea as to how, I can prevent the tab from turning off when the screen times out.
Also, my ultimate goal is to upgrade to KitKat so that I will have mirroring. If I install KItKat, is that likely to get rid of the shut off problem. Thanks for any help that can be provided. Should and that I have Titanium Pro.
Click to expand...
Click to collapse
you should upgrade the tab to the latest stock jb rom 4.2.2, then try the custom rom, the tab has reached to marshmallow, you can try kitkat, LP and M. they are all pretty much stable than the stock. not every Rom supports mirroring.
Billysam,
Thanks for your reply. With the kludge of a system that I have, I decided to use factory reset. That solved the time out problem. Now, I will attempt to re-root it.