Hello,
From 2 month, i have a problem with screencast on a chromecast.
The connexion is successful my phone screen is displayed on TV but if I put my phone in sleep, I can't wake it. The phone restore the default background image and alternate black screen and defaut background, i can only reboot phone ...
I make some update, with clean flash but problem is always here ...
Rom : Carbon ROM build by Stellix (20150531)
Kernel : ElementalX 2.11
Someone else have this problem ?
Thanks
Related
plz help me
i installed a cracked SPB 3D prog on my nexus S GT-i9032
and the device froze i waited 4 several min and noting
so i switched it off tried to restart it it want throw
1. Google logo
2. the nexus s animated logo and then nothing it got suck there
so i inserted my usb cable and the phone worked with the usb pop up screen tried going to the home screen nothing black
the battery and wifi and signal and notifications working
main menu and everything else not working
i can get calls but i cant go to the phone app
or any other app
i want to the fastboot mode
and tried the recovery option (reboots to Google then the droied begins reinstalling the SW the a ( ! ) sign appears and every thing stops
my phone is not rooted and i dont want to root it or lose my warranty
i really need ur help
i updated the last 2.3.6 update
boot loader ver -I9020XXKA3
BASEBAND VER -I9020XXKF1
HW VER -REV 52
LOCK STATE - LOCKED
THANKS GUYS
hi
i have problem after downgrade from 4.1.2 (stock) to 4.0.3 (stock) on my p3100.
when i turn on my tab2 lock screen is always portrait
after unlock screen is returning to landscape ( screen rotation is disable).
how can i fix it?
I tried flash my tab to cm10.1 and i got boot screen like a foto ,but lock screen look normal.
I tried flash with PIT file and the same problem.
P.S before upgrade to 4.1.2 every was fine . I used 4.0.3
P.S 2 sorry for my mistakes I hope You know what i tried to tell
Please help me
Greetings Tom
Boot animation like that on cyanogenmod is a known issue. Codeworkx set is as a low priority fix.
Also the second pic hav you tried 4.0.4 instead?
Hi can anyone help me? I had flashed elementalx kernel in chroma rom, after some hours the screen has had some glitches. after an hour later I took the phone from mypocket and the screen is switched on , but remains black. I try with the various toolkit to reflesh stock rom , but the screen remain black
Hold the power button for 10 seconds or until your device force reboots , also what rom did you have and what kernel before you flash elementalx and how did you flashed it?
Hello, today I updated my phone to the latest CM13 Nightly and it was going well. Then my AK Kernel Updater notified me to update the Kernel so I did. After rebooting my phone, it is stuck on the AK Kernel screen for a few minuted (2 - 5 minutes) then my screen turns black but my phone is still running in the background but I cannot view the screen (I can use the buttons and can press icons on the screen randomly) Any tips without wiping my phone from it's data?
ronaldonater said:
Hello, today I updated my phone to the latest CM13 Nightly and it was going well. Then my AK Kernel Updater notified me to update the Kernel so I did. After rebooting my phone, it is stuck on the AK Kernel screen for a few minuted (2 - 5 minutes) then my screen turns black but my phone is still running in the background but I cannot view the screen (I can use the buttons and can press icons on the screen randomly) Any tips without wiping my phone from it's data?
Click to expand...
Click to collapse
Wipe system and reflash ROM + gapps should be back on stock kernel then
Sent from my A0001 using Tapatalk
If you made a Nandroid backup before, just hold down the power button until the phone hard shuts down, boot into recovery, and restore your old backup
Just dirty flash over your ROM. It will change the kernel to it's stock state. This is what I do every time I'm running into a problem like this.
There is no ak kernel for CM13. Just check next time the thread.
Hi Guys,
Prelude : 2 months back, my pure stock Moto G experienced i guess a battery drain and refused to start the next time onwards. When it was powered on, it just got stuck on the M Logo of the bootup. After the help from @lost101 & others, i was able to flash the custom recovery & rom and got the phone to bootup atleast although faced the same issue which i'll be writing below now.
Since that event has happened, everytime I flash a custom rom, the installation happens without any glitch which includes the rom.zip & gapps_pico.zip. Now when the ROM bootups, the startup screen shows up after which it starts optimizing apps. That's where is the issue starts.
For eg. optimizing app x (single digit) of 101, it doesn't goes beyond that point even after waiting for 15-20 mins or so, and i've to manually reboot using the power button after which again the optimizing apps screen comes up and this time the figure is optimizing app xx of 16/17, and in this turn the phone successfully boots up to the setup screen and works as normal. But after a few moments when i'm done setting up all my apps and everything, random issues turn up for eg. the notification quick tiles won't drop down. And when i restart the handset, again it shows the optimizing apps screen, the phones boots up to home screen but random issues pertain.
I've tried ROM's like Stock Debloated (5.1.1) , CrDroid, CyanPOP, RessurectionRemix all based on 6.0.1.
Before installing any ROM, i do an advanced wipe and all format the data. Right now the handset is running CyanPOP but the main issue is i'm unable to access the notification dropdown. It doesn't goes beyond the header.
One more thing, I installed RR (xt1022 specfic) with same pico_gapps on my Moto E & the rom booted up in no time and working as smooth as butter till date with no issues whatsoever.
I'll be helpful if some one can diagnose the issue. Thanks
BBThumbHealer.
Did you try flash stock firmware and then flash a costum ROM ?
@Eurofighter_ty : when the issue first happened, what I remember is that I tried installing the debloated stock ROM of 5.1.1 and not the pure stock having all the unnecessary gapps. And similar issue was encountered. Same thing happened with other custom ROMs.
Today I've now reverted to a previous version of CrDroid 6.0.1 released in April and it at least runs fine when in use although a reboot causes the same issue. However, CrDroid June update and CyanPOP had the issue in which the quick tiles didn't drop down along with refusal of bootup.
Try to flash the stock ROM via fastboot with all files