Related
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
vite0150 said:
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
Click to expand...
Click to collapse
This is not common at least not for CM11.
I've been running CM11 nightlies since they started to roll out, currently running 20/12 without issues.
I would recommend going to recovery, back up, and erase system, data, cache and dalvik, then flashing CM11 nightly to start clean.
I've been running CM11 and Validus13 ROMs since they became available and never had this issue.
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
I don't recall wiping Cache, Dalvik, or Data after installing 4.4 ROMs.
vite0150 said:
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
Click to expand...
Click to collapse
You should totally clean cache and dalvik when flashing new roms (CM usually does this by itself anyways). Make sure you're cleaning these, won't hurt at all anyways.
Ok, make a factory reset after flashing... Also i see in some roms that i gotta mount system and other things, i never did that (i didn't saw that in the instructions of the two roms that I've tried...)
Also I used for this couple of days the stock rom just to check that it wasn't a hardware problem... worked flawless...
Right now i'll try valadus... I'll let you know how it goes
Update: valadus gave me a lot of errors... Something like it couldn't write on storage/cwm... And when it was aborted it says that cache can't be mounted... So i ended up installing cm11 (the same that i flashed before)
You're running the latest CWM or Philz recovery?
Philz
It's strange because I'm running the latest CWM and I can install the latest Validus13, Cyanfox, CM11, and Probam without a problem.
Flashed probam last night, and it survived the night! Only thing I changed from before was wiping again after flashing...
Thanks for ur help
Update:
In the morning i connected the phone to the charger, and now i went to see if it was fully charged and surprise!!! It happened again!
Maybe is the charger cause I'm using a generic, but why it doesn't happen on stock rom?
At this moment i will just leave it stock and put it for sale, don't want to keep dealing with this...
Hi guys,
A couple days ago i noticed that on stock (att) rom i wasn't getting bsod but i do was getting reboots when charging the phone (i don't know how i didn't noticed it before)...
So maybe someone can tell what are the specs of the original power brick (amps, input, output) to find a similar one and see if that can solve the problem
Edit:
Nvm i found a samsung charger... Now everything is working flawless on OSE rom
hey guys... this morining suddently my z1 turned off... and now it wont boot. The cm face shows up but after 2min it freezes. I tried to enter recovery but it wont happen. The LED turns purple.. i press the vol up button but nothin happen.. the phones starts booting normaly :/
i flashed twrp via fastboot but this was not a solution..
i'm on cm12-2015-01-30... any ideas?
same situation here bro
hmm.. maybe its possible to install cm only via fastboot? special files need?
Read this:
http://forum.xda-developers.com/showthread.php?t=3000822
http://forum.xda-developers.com/showthread.php?t=3002887
Sent with C6903 using Tapatalk 2
thanks.. but this wont wort for me. The volume up button doesnt bring me into recovery
same here! Cm12 update 31.01. installed, reboot at bootanimation stuck and can´t enter recovery ... will go fastboot
had the same problem....it was a hit and miss for me.....after a lot of tries recovery started rendomly at one.....but i was dumb enough to flash 30/01 nightly again ...then today morning after the hit and miss session when the recovery started....i took my sd card....replaced 30/01 nightly with 28/01 nightly....popped the card back and flashed it....voila...its working now.......hope you find a fix too..
dont know why... yesterday i flashed twrp via fastboot and it didnt work.. today i tried again and it worked! In recovery i wiped dalvik and cache, hit reboot and the system started! yay !
maybe the solution was twrp... philz touch didnt worked.. hope it will work for you guys
When you on Cm12 there is no TWRP it's the new Cyanogenmod Recovery. You can enter it by pressing the volume down and up button after the Sony logo pops up.
Got the same problem, have been trying many different recoveries, no success. Does anyone have a definite fix?
Also the same for me. Cyanogen logo freeze (or sometimes restart phone) and this for the nightly buids of 201500130, 20150131 and lastest 20150202.
I had to do a fresh wipe with an AOSP rom to install again CM12. The first boot was ok after fresh install but on reboot, the problem was getting back.
I'm going to revert to the 20150128 nightly and look out the next changelog to see if a fix will be available.
Okay. Look at the Cyanogenmod page. In the faq they say. "when the light is purple press volume up button" it works every time http://wiki.cyanogenmod.org/w/Honami_Info
Z1 wont boot proplerly - cant get into recovery
-Happy Feet- said:
Okay. Look at the Cyanogenmod page. In the faq they say. "when the light is purple press volume up button" it works every time
Click to expand...
Click to collapse
I've been trying that for days, and it very rearely works (mayvbe 2 or 3 rimes in as many days). My phone is in a real bad way - about 99.99% of the time its just stuck on the CM boot logo. Very occasionally I can get into recovery, but in order to get into my OS, I actually have to reflash CM. Simple boot from recovery never works.
I've tried installing fotaZ1_2.8.4.img (as suggested by a user on another thread) from fastboot, but can only get into that very rarely too.
I've also tried flashing the boot.img from the last few CM nightlies, but once again no joy.
This is getting real bad, as I've spent days reading threads on here and reflashing / resetting the phone! In fact my fingers are aching from stabbing at those damn power and volume buttons!
If anyone could please help or suggest a solution, I'd be eternally grateful. CM 12 is freaking great...when . if it works... ;-p
cheers
[edit]
Managed to get into TWRP, so decided to just wipe the phone completely, including int SD card. Thankfully TWRP has a file manager, so I could copy my stuff to my ext SD beforehand. Reflashed cm12-20150202 and it seems to be ok now. Done 3 or 4 test shutdowns, as well as reboots and its been booting ok so far. Getting into recovery still seems to be a bit touch and go though, but I can live with that for the time being I guess.
Any news here? I can't get into recovery mode, and my phone is now effectively "bricked".
-Happy Feet- said:
When you on Cm12 there is no TWRP it's the new Cyanogenmod Recovery. You can enter it by pressing the volume down and up button after the Sony logo pops up.
Click to expand...
Click to collapse
I upgraded from CM11 to a CM12 nightly (the one with the broken boot animation that hangs). Before upgrading I had TWRP, and could boot into recovery by holding volume down while turning on the phone. This is not working any more. Have tried a lot of different combinations, but nothing seems to work.
Please, if anyone can help, give me a tip.
Btw: my led never lights up, only after a few seconds, the Sony logo shows, then the broken boot animations starts.
What worked for me was to only press volume-up after the Sony logo had appeared and the LED shows purple briefly. I then cleared cache and dalvik and was able to boot.
I already had fotaZ1_2.8.4.img installed, and had rebooted one of the affected CM12 nightlies.
idle1 said:
Any news here? I can't get into recovery mode, and my phone is now effectively "bricked".
I upgraded from CM11 to a CM12 nightly (the one with the broken boot animation that hangs). Before upgrading I had TWRP, and could boot into recovery by holding volume down while turning on the phone. This is not working any more. Have tried a lot of different combinations, but nothing seems to work.
Please, if anyone can help, give me a tip.
Btw: my led never lights up, only after a few seconds, the Sony logo shows, then the broken boot animations starts.
Click to expand...
Click to collapse
you can enter recovery when you boot the Phone, plugin USB Cable and when the LED shows purple then hold the volume up button, that worked for me.
btw. Bootloop: flash the rom.zip again then it boots. after that install from playstore this Bootanimation: https://play.google.com/store/apps/details?id=de.appublic.cyanogenboot and install this animation. After that boot work fine and you can flash new updates without issue
Thank you very much, both of you. I could not get any of your tips to work, though this morning the strangest thing happened. When i got up, I suddenly heard the alarm ringing from my Z1. It was booted and seemed ok. I have no idea how it booted...
Anyway, now it's working again with todays nightly. Thanks again.
btw: I can now enter the new recovery (twrp is replaced by a CM one) by tapping vol-up while the Sony logo is showing. Rebooting directly into recovery from the OS does not work.
I recently rooted my droid turbo 32gb using sunshine root and kingroot. I successfully flashed Resurrection Remix Lollipop 5.1.1_r26.
However sometimes when the phone is idle in my pocket for awhile and i go to pull it out it is off. Also, it takes about a minute or so of pressing the power button to turn on. I also cleared the cache after flashing and reset everything. When i cleared the cache it seemed to work over night but turned off automatically during the day with more than sufficient battery life left. If anyone has any possible fixes, i would greatly appreciate it. Thanks in advance.
kernel problem
guccimcilroy said:
I recently rooted my droid turbo 32gb using sunshine root and kingroot. I successfully flashed Resurrection Remix Lollipop 5.1.1_r26.
However sometimes when the phone is idle in my pocket for awhile and i go to pull it out it is off. Also, it takes about a minute or so of pressing the power button to turn on. I also cleared the cache after flashing and reset everything. When i cleared the cache it seemed to work over night but turned off automatically during the day with more than sufficient battery life left. If anyone has any possible fixes, i would greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
I am not sure 100% but it may be kernel problem as support for xt1254 from stock kernel is added 3 days back in cm12.1 and RR is based of cm12.1
possible solution
1) try clean flash RR
2) if first does not solve flash CM12.1 (running very smooth without any bugs) until RR team update their ROM
It's probably RR rom. I had an issue with my Droid Ultra on dirty unicorns. Went back to cm 12 and it worked fine.
Sent from my XT1254 using Tapatalk
I am running resurrection remix fine on my droid turbo. For two days now I have had no issues. What I did is, in twrp, I did a factory reset, wiped dalvik and then cache. Then I flashed the ROM and then gapps. No more wipes. I booted it up from there and I've been stable ever since.
Thanks all. Went to cm 12. Now the GPS is the problem. Any fixes?
guccimcilroy said:
Thanks all. Went to cm 12. Now the GPS is the problem. Any fixes?
Click to expand...
Click to collapse
Yeah, freeze motogeofences in Titanium Backup and install TopNTP.
See this post:
http://forum.xda-developers.com/showpost.php?p=64109692&postcount=306
I was able to freeze georef then I installed TopNTP. however when it rebooted nothing changed. The GPS still didnt work. Do I have to flash again? Sorry I'm a noob
guccimcilroy said:
I was able to freeze georef then I installed TopNTP. however when it rebooted nothing changed. The GPS still didnt work. Do I have to flash again? Sorry I'm a noob
Click to expand...
Click to collapse
do you have "high accuracy" turned on?
Yeah. I turned it off when I froze it though
All you have to do is freeze georef then download TopNTP then reboot? Or am I missing a step
Do I have to go into stock to download topntp for it to work then flash cm 12.1 again?
Im at a loss here so I come to you guys in desperation. The home button and power button work fine in TWRP but do nothing in the actual operating system. Also the capacitive buttons dont light up or work for that matter. I havent succesfully flashed a custom rom yet as I kept having boot loop issues but I did a fresh install with kies and still no go. Anybody seen anything like this? Its a T-813 if that matters...
Today i updated magisk though the app (manager + magisk) and i ended up in a bootloop kind of state.
The loading screen with the green android and mi.com logo it seemed the colors are distorted (too bright - green is much more lighter colored).
When getting into system, it seems that while apps are showing, things like wifi, fingerprint, apps do not start, etc.pp and colors are distorted too, the phone will force a reboot, where the said loading screen will become endless (or once it took 10 minutes on the second reboot)...
i already tried installing previous magisk versions or uninstall it alltogether, as well as flash ROM, while flashing succeeded, the same problems prevail.
I also tried flashing newest firmware (drivers) but also no success.
What else could i try?
endrancer said:
Today i updated magisk though the app (manager + magisk) and i ended up in a bootloop kind of state.
The loading screen with the green android and mi.com logo it seemed the colors are distorted (too bright - green is much more lighter colored).
When getting into system, it seems that while apps are showing, things like wifi, fingerprint, apps do not start, etc.pp and colors are distorted too, the phone will force a reboot, where the said loading screen will become endless (or once it took 10 minutes on the second reboot)...
i already tried installing previous magisk versions or uninstall it alltogether, as well as flash ROM, while flashing succeeded, the same problems prevail.
I also tried flashing newest firmware (drivers) but also no success.
What else could i try?
Click to expand...
Click to collapse
Thats a known issue of latest canary built.
Only solution is to safe your data and do a fresh rom install.
After that you have to flash your boot.img. Then you can install magisk again. Please use magisk stable built.
ReeCorDs said:
Thats a known issue of latest canary built.
Only solution is to safe your data and do a fresh rom install.
After that you have to flash your boot.img. Then you can install magisk again. Please use magisk stable built.
Click to expand...
Click to collapse
Enter twrp
Then reboot to system*
I faced same issue