hello i was running PA ROM and everything was working okay .. just now i flashed Purity ROM and the touch screen stopped working .. even in TWRP the touch screen doesnt work .. what might cause it ?? and is there anyway to fix it ??
Fastboot latest oos3
Sent from my ONE A2005 using Tapatalk
Related
Hello,
Has a way to dual boot the nexus 4 been developed yet? I tried looking around but didnt see anything. Surely it could be done since the nexus 7 can dual boot both Android and Ubuntu touch? Thanks in advance.
Dan
No.
Sent from my Nexus 4 using Tapatalk 2
Try this http://forum.xda-developers.com/showthread.php?t=2403992
[MOD][13AUG]Multi ROM for Nexus 4 | Multi Boot
But it still can't be use to dual boot with ubuntu yet.
Right now i'm trying Stock Rooted with PA 3.97 but when i try to update the second Rom in this case PA doesnt start besides this its great, thanks to this Recovery i did install another rom on my N4
Hi all
I can't get a Mobil/cell connection when using roms like pa or catalysm. I also don't get a pin request. On stock everything works fine, carbon Rom was also fine.
Any ideas?
Sent from my Nexus 7 using xda app-developers app
same here, with a Samsung Galaxy Note 2.
It happened with several Android 4.3 & 4.2.2 ROM (my fav is PA).
Finally I gave up und went back to stock and then to a slimmed near-stock 4.1.2 ROM (Thunder Lite).
Suddenly and ever since there are no call in/out problems anymore.
Conclusion: for my Samsung device I suspect driver/or radio incompatibilities. I'll wait for Sammy to release a proper 4.3 stock ROM.
But that shouldn't be a problem for Nexus 4.
ok i finally made it.
The Problem was the Recovery!! The latest teamwin recovery was installed. Now i changed to clockworkmod and everything is fine.
Mayby the recovery was the problem or something went wrong on install.
but now its working:victory:
I always use CWM and PhilZ Touch (based on CWM), and had never problems with the Recovery.
Guys plz help me out. I have got a weird problem with my note 3. I am on stock 4.4.2 NA6 rom rooted. I flashed halazsk universal5420 kernel using twrp recovery and cleared dalvik cache...on the first boot after flashing the kernel Everything seems working including Overclocking and undervolting...but eventually my phone starts heating up badly. And once I restart my phone...It has trouble waking up. After I lock and unlock it ..A black screen stays for a second or two...and my phone hotboots and the same problem continues...and the phone heats up really bad...I tried both 13b and 14b versions...none worked...plz help me out guys...I really want to use this kernel
Thank you!
Sent from my SM-N900 using Tapatalk
subham964 said:
Guys plz help me out. I have got a weird problem with my note 3. I am on stock 4.4.2 NA6 rom rooted. I flashed halazsk universal5420 kernel using twrp recovery and cleared dalvik cache...on the first boot after flashing the kernel Everything seems working including Overclocking and undervolting...but eventually my phone starts heating up badly. And once I restart my phone...It has trouble waking up. After I lock and unlock it ..A black screen stays for a second or two...and my phone hotboots and the same problem continues...and the phone heats up really bad...I tried both 13b and 14b versions...none worked...plz help me out guys...I really want to use this kernel
Thank you!
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
And what happens when you DO NOT overclock or undervolt? Some devices frown upon undervolting, lets use the default settings and monitor it from there....
Good luck!
Thanks
I face these problems even on stock settings...just after flashing kernel
Sent from my SM-N900 using Tapatalk
Hello every one ...I got new problem in my new phone s4 i9500 ..suddenly loss vibrat touch during using the phone in custom rom ...I flash sokp at first custom rom and got that issue then flash hassan rom based on stock at first flash the issue present but flash it again and then work after that flashed aicp rom and after some days today the vibrat gone even in recovery mode ...what can be the problem ? My phone still new 1month ago ..can it be from kernal philiz ?? Thanks for any suggestion
any suggestion or throw my phone from window ......software or hardware problem ?????
Hi Ammar,
I think your problem is in software. If I were you, I install cwm or twrp recovery, do all wipes including system, preload and internal memory, then flash the latest official firmware with Odin. If problem stands still, I do all wipes agaün and install the latest official firmware again. Even if this is does not work then I decide the problem is hardware based.
abdullahmk said:
Hi Ammar,
I think your problem is in software. If I were you, I install cwm or twrp recovery, do all wipes including system, preload and internal memory, then flash the latest official firmware with Odin. If problem stands still, I do all wipes agaün and install the latest official firmware again. Even if this is does not work then I decide the problem is hardware based.
Click to expand...
Click to collapse
thanks for reply my friend ...i will try by odin and see
Software problem mate.
Try coming back to the stock rom and revert.
It should work on the stock rom.
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
Software problem mate.
Try coming back to the stock rom and revert.
It should work on the stock rom.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
thanks ..i will try surly but what can be the problem from cm based custom roms or from apks if you know about that
ammarsg said:
thanks ..i will try surly but what can be the problem from cm based custom roms or from apks if you know about that
Click to expand...
Click to collapse
Well I cant comment on what went wrong.
I was on slim rom once and my vibration Intensity was tooo too low. Because of that was missing calls.
Or you can download an app for checking vibration. Once my proximity sensor and speaker stopped working, i ran a test and everything was back to normal.
Try test you android from the playstore and see if that test works.
Well here is the app
But again as I said, let us know if this is happening on the stock rom.
Sent from my GT-I9500 using XDA Free mobile app
Once my Wi-Fi stopped working on a Cyanogenmod based rom. I flased stock firmware many times but it didn't work. Then I installed cwm recovery and do all wipes then it worked. As you understand, such wierd things might happen sometimes that we couldn't understand.
i sent my phone to company and told me that vibrate engine is broken and they change it and now work good but what is the problem that caused this i dont know exactly ...as they said either by drop the phone or by water but non of these happend with my new phone
thanks guys for help
ammarsg said:
i sent my phone to company and told me that vibrate engine is broken and they change it and now work good but what is the problem that caused this i dont know exactly ...as they said either by drop the phone or by water but non of these happend with my new phone
thanks guys for help
Click to expand...
Click to collapse
We are human being and as you know human is not perfect. So anything produced by human is not perfect naturally. If you could't find a reason for fault of a device then this is the only and certain reason :laugh::good:
Hi, i really have big problem.
my phone has random reboots after trying to turn the screen on when its locked.
I can use the lockscreen around 30 times until i get a reboot. The screen doesnt even turn on. The phone vibrates and reboots.
On Lollipop everything worked fine,no random reboots or else.
I've got the newest BL and modem,otherwise i wouldnt have the chance to use the rom correctly.
I'm currently using Alexandrs rom , v3.2.
Can anyone help me?
Greets
Does this also happens on stock rom?
tapatalked
For me it works great with the same rom.
I also tried the ported version of MM on my G900F (G900M Marshmallow) and had the same problems.
Currently i am using alexandrs rom v3.2. I didnt try another MM rom.
Isnt there anyone who could help me? :'(
...
007gamer said:
I also tried the ported version of MM on my G900F (G900M Marshmallow) and had the same problems.
Currently i am using alexandrs rom v3.2. I didnt try another MM rom.
Isnt there anyone who could help me? :'(
Click to expand...
Click to collapse
I had the same issue with this ROM then I update to 3.3 version and I change my recovery to TWRP 3.0.2.2 test2. https://idlekernel.com/twrp/klte/testing/
And now this issue disappeared.
Sent from my SM-G900F using XDA-Developers mobile app
pepe100 said:
I had the same issue with this ROM then I update to 3.3 version and I change my recovery to TWRP 3.0.2.2 test2. https://idlekernel.com/twrp/klte/testing/
And now this issue disappeared.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
I still have this problem with twrp 3.0.2.2 test2 and last alexndr rom CPD7
I've also this problem with stock CPD7 rom an no modding.
I still have this problem on cpe2 any fix??? Thanx
Hi,
I also have the problem. There is one thing that looks like related: It only happens if you have the fingerprint reader enabled for unlocking. Is this the same for others?
I also tried latest CPEA ROM by alexandr -> no change. I did not update TWRP because this should be unrelated to lockscreen.
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
igorescu04 said:
For me it works great with the same rom.
Click to expand...
Click to collapse
Do you have fingerprint unlocking enabled? For me it only happens when it is enabled (e.g., when I am not at home). At home my phone unlocks automatically and I can unlock it as often as I want. When I need to use the fingerprint reader it reboots every 10 to 30 times.
I had random reboots on my device after updating from kitkat to marshmallow (stock, no root, over ota)
I didn't wipe after updating (I would suggest to wipe as the first step)
I came back to kitkat because I didn't like the new marshmallow ui (especially the white settings menu!) and because of the reboots. however after reverting to kk I don't have any reboots anymore. so i would suggest just to wipe everything and if it doesn't work go back to kitkat
Sent from my SM-G900F using XDA-Developers mobile app
It is a mm bug so we have to wait for a fix from Samsung
I am now trying CPF3 ROM (by Alexndr)
I have the same problem with 6.01 update
I made full wipe
&no solution
Abo_Moaaz said:
I have the same problem with 6.01 update
I made full wipe
&no solution
Click to expand...
Click to collapse
Which ROM version?
lets send samsung some emails about this problem, maybe they'll fix these bugs soon.
I am on stock CPEM and no problems any more flashed via odin over alexndr rom and it is fixed all CPXX roms caused reboot on lockscreen for me I will stick with stock
cheaterel said:
I am on stock CPEM and no problems any more flashed via odin over alexndr rom and it is fixed all CPXX roms caused reboot on lockscreen for me I will stick with stock
Click to expand...
Click to collapse
For me stock ROM has the same problem! This is why I went back to Alexndr ROM.
I just checked CPF3 release today. I was able to make it reboot on lockscreen again, but only when fingerprint reader is enabled. Does never happen without!
thetaphi said:
For me stock ROM has the same problem! This is why I went back to Alexndr ROM.
I just checked CPF3 release today. I was able to make it reboot on lockscreen again, but only when fingerprint reader is enabled. Does never happen without!
Click to expand...
Click to collapse
Ask Alexndr to make a CPEM rom I have 3 days with fingerprint enabled and no reboots
Ps :
Here it is the link http://www.sammobile.com/firmwares/download/75351/G900FXXU1CPEM_G900FROM1CPE3_ROM/ first firmware that works for me without random reboots
cheaterel said:
Ask Alexndr to make a CPEM rom I have 3 days with fingerprint enabled and no reboots
Ps :
Here it is the link http://www.sammobile.com/firmwares/download/75351/G900FXXU1CPEM_G900FROM1CPE3_ROM/ first firmware that works for me without random reboots
Click to expand...
Click to collapse
Stock firmware on unbranded fone is no option for me, because it does not have enabled VOLTE in Germany. The one with right CSC is still on Android 5.
I just tested stock ROM for a day, but gave up after doing a loop of "lock - unlock - fingerprint - lock- unlock - fingerprint - ...". Very easy to reproduce, you just need to do it about 20 times. So it has nothing to do with Alexndr.
The firmware version you mentioned is the same kernel and changelist as the recent Alexndr one.
Interestingly the reboots were slightly different with CPF3: Instead of just rebooting with only the button lights on but dark screen, in CPF3 it woke up partially, but screen stayed black, button lights on. But it did not reboot. To make it reboot you had to try to wake it up again. Before that it was rebooting after 2 seconds automatically.