Database Develop

[CM9] Investigation on Bootloops

Hey folks,
being stuck in bootloops is one of the most annoying things for us powerusers.
Therefore I want to investigate a little bit deeper into this topic.
The normal procedure of "solving" the bootloops for me was flashing a base Gingerbread ROM by Ficeto (Mostly JVT) via ODIN, disabling Lagfix, entering CWM & flashing ICS again.
But one time (about 2 weeks ago) I had no time to go through this process, so I took the battery out of the phone (to abord the bootprocess & shut the phone down), placed it in again & putted the phone back in it's pocket.
About one hour later when I looked at it by accident (wanted to check the clock & forgot that it was bootlooping) the phone was fully booted & back to normal.
so the last 4 times my GT-i9000 (running nightlys of CM9) got stuck on the Bootscreen coming again & again, I took the battery out, placed it in again & let it bootloop for a while & after about 20 minutes baaam my SGS was properly booted?!
So my question/request is for you if you are stuck in bootloops:
[highlight]Please try the following:
1. Take the battery out & place it in again
2. Start the phone again
3. wait, wait, wait & be patient
4. Tell me if the problem solved itself or if after more than 2 hours of bootlooping nothing happened [/highlight]
if it didn't please tell me how long you've waited, what caused the looping & which nightly etc you where running!
just for clarification: with bootloops i mean being stuck on the Samsung Galaxy S / Cyanogenmod Screen where it is written in plain text which appears before you can enter recovery or the normal bootanimation appears. When my phone was/is bootlooping I also have no chance to enter Recovery. & I also know that it sounds strange that BL should solve themselves, but please try it!
[edit] I also read some time ago that there where other people with the same experience, this is why I opened a thread & I'm sure this is not a thing related to only my phone

I experienced something similar , also with CM9 . Phone working very hard , so i restarted it , but after the Galaxy S GT i9000 screen , the CM9 blue boot loaded for about 10 minutes and nothing , so I decided to enter in recovery ( I removed the battery , waited a minute , inserted it in the phone , and the recovery didn't work . Waited 10 minutes , and after that the recovery worked , and I reflashed CM9 , because it was the only rom I had in the internal SD card .

About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey

Thomas. said:
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Click to expand...
Click to collapse
It would be nice if you could tell exactly what you did, if more people would do that we might be able to figure out why this thing happens to you and why it doesn't happen to me.
when i flash:
*phone not connected to pc or charger
*running stock kernel
*16 gb micro sdcard mounted
*all sorts of battery percentage, from 10 to 100 percent
*reboot recovery by terminal command "reboot recovery"
*format /cache
*flash the build from /mnt/sdcard/download
*flash gapps from same location
*run a script that wipes dalvic, removes several sounds and unwanted apps and fixes permission
*format /cache again
*reboot
I know this is a pretty weird procedure and it's in no way an advice to anyone, it is just an example of giving details that might lead to a common factor for bootloops.
Taptalked u see

Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !

BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Thanks for your post!
What caused the bootloops?

fipsib said:
Thanks for your post!
What caused the bootloops?
Click to expand...
Click to collapse
1st time I got bootlooploop was [15/Jan/2012] I was trying to boot into Recovery via power button so I could upgrade from Build 12 to Build 13.
2nd time [2/April/2012]I was on AOKP B28 & I had booted into Recovery to wipe cache & dalvik & after successfully wiping, the bootloop came when I hit the 'Reboot' option to start the phone.
(AGAINST better judgement - since first bll I had avoided wiping cache & dalvik)

jep. I also had bootloop problems by wiping cache and dalvik cache. I was on SlimICS flashed midnight kernel. Everything was working just right but CPU scaling had some bugs for me so i removed init.d scripts went into recovery wiped cache and dalvik cache...and boom....bootloop :/. Now I'm back on CM7 because this is a rather annoying problem....

BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Can you link me CM7 kernel for Odin? thanks

farid993 said:
Can you link me CM7 kernel for Odin? thanks
Click to expand...
Click to collapse
Yep, here it is,
View attachment 1012442
This worked for me both times
[remember to leave UNCHECKED
Ensure Reboot, Repart, F-Reset]
Then boot into Recovery and restore Nandroid - no need to be flashing gingerbread.

Ever since the first nightly, I have been plagued by bootloops. Usually formatting /system, /data and /cache helped. But not this time. I tried to install the 19/4 nightly, and had gotten into bootloops. Yes, I have used custom kernels before.
However, even clearing init.d, clearing NSTools, flashing from FixRecovery, the cm7 kernel, even flashing with Heimdall (flashing stock kernel and custom kernel) could not get me out of the loop. Note: I tried the method as described in the OP.
What I finally did was format everything, excluding ext-sd. Format internal SD as well, after backing up some files. And BAM! That was it! Something on the SD corrupted the install. No bootloops, can even install custom kernel, no problem.
So, that may be a tip for people not able to get out of the bootloop, or experiencing constant bootloops.

Hey it's under Devs investigation now:
http://forum.xda-developers.com/showthread.php?t=1627689

My galaxy with CM9 started to bootloop yesterday, no way to enter recovery
I'll make you know in a couple of hours if something change leaving it on ..
If nothing change, is there a place where I can find CM9 kernel to flash with odin ?
thanks

Read Bejda's post, one post above yours.
Taptalked u see

wooops didnt see the second page of the thread
anyway leaving it there to bootloop didnt solve the problem
flashing semaphore kernel seems yes

Lg bricked?Noob mistake..

Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip

Mitzu' said:
Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip
Click to expand...
Click to collapse
I recall reading something about using NVFlash to force the stock rom on and allowing to recover from a bricking.
I'll defer to someone with experience in fixing bricked phones though.

Thank you...now..it wont even start, even when i plug-in the charger..it had pretty low battery..i am pretty ducked..

You have to reflash it with KDZ recovery method. Look up google and you'll get it working. I did this the first time too (what a bad joke to say "this is not a ROM")...

I'm sure you can still enter Cwm if you hold down volume- while pressing power button until it the Cwm menu appears.
Sent from my Optimus 2X using xda premium

First of all, don't worry, O2X is pretty unbrickable...at least in the level you're messing with it!
If you have recovery installed, you should be able to reboot into recovery : press and hold vol down button, then power button until you see blue halo of LG. before that, download another ROM and put it in your external SDcard. Flash that ROM.
You can also download and flash the original firmware of LG by using smartflash. You can find those in ANDROID DEVELOPMENT section!
Also check KDZ recovery!!

Thank you..it worked with recovery mode..i had back-ups. I got a bit scared because when i pressed vol_dwn+ shut down button..after i release the 2nd button, it turned off...but i menaged to make it. Again, thank you for help.
====================
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?

Mitzu' said:
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?
Click to expand...
Click to collapse
The common mistake for new people is that they restore entire nandroid backup after flashing ROM. CWM doesn't have option to backup DATA only, so you have to restore DATA from nandroid backup using Titanium Backup etc.
Try this:
1. Restore into fully functioning ROM(+data) if you don't have already
2. Reboot to recovery
3. Format /system
4. Flash new ROM
5. Clear cache and dalvik cache
6. Check if phone successfully boots
7. Flash Gapps if needed.
8. DO NOT DO ANY RESTORES AFTER STEP 1!!
9. If it doesn't work out, try another ROM. There may be some error with the file!!

installed native 10.2 and 10.1 still no recovery..

just got this 8gb model hd for like 80 bucks and super happy with it... like it even better then my nexus.. but..
i went a head and installed native 10.2 humming bird on it.. and for the most part every thing works quite well..
but i cannot access recovery.. when i try by the advanced menu reboot.. all i get is the orginal logo... and the big Nook button graphic saying that reboot has failed power off and on... no access to cwm recovery... and when i try the power on hold nook home button for 4 seconds it just keeps loading 10.2... other then the no recovery issue every thing loads and works fine...
any ideas?

scuzzo said:
just got this 8gb model hd for like 80 bucks and super happy with it... like it even better then my nexus.. but..
i went a head and installed native 10.2 humming bird on it.. and for the most part every thing works quite well..
but i cannot access recovery.. when i try by the advanced menu reboot.. all i get is the orginal logo... and the big Nook button graphic saying that reboot has failed power off and on... no access to cwm recovery... and when i try the power on hold nook home button for 4 seconds it just keeps loading 10.2... other then the no recovery issue every thing loads and works fine..
any ideas?
Click to expand...
Click to collapse
Your problem is you have not installed the CWM recovery to internal memory. It does not come as part of CM. You must install it separately. Look in the dummies guide or verygreen's native install thread.
Sent from my Galaxy Tab 2 using XDA Premium

[Q] Sony Xperia TX stuck in bootloop after beats audio installer

I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!

darinthereal said:
I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!
Click to expand...
Click to collapse
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?

yes I have an external sd card
Antiga Prime said:
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?
Click to expand...
Click to collapse
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.

also...
darinthereal said:
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.
Click to expand...
Click to collapse
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!

darinthereal said:
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!
Click to expand...
Click to collapse
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/

Antiga Prime said:
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/
Click to expand...
Click to collapse
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!

darinthereal said:
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
Well, directions still apply to TWRP; wipe /data and /cache, flash files in the order posted previously, then reboot. Good luck.

I love you!
darinthereal said:
yes the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. Thanks! I'm going to try this. I erased the os last night. Before all of this i installed one click scroll from googleplay. It worked perfectly but it install teamwin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok i'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
i love you thank you how do i thank matt?!!!!!!!!!

darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
Glad to be of help. If you must, just clicking on the "Thanks" button on a post is good, that's what it's for. And you'll have to probably find one of matt's posts too (don't know who you're talking about) and do the same, I guess.

THANKS!
Where is the thanks button? Lol

darinthereal said:
Where is the thanks button? Lol
Click to expand...
Click to collapse
Under each post, left side of the screen.

THANKS!
darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
JUST CLICKED EVERY THANKS BUTTON THAT I COULD FIND THANK GOD FOR YOU! I had to come to my laptop the thanks button don't show in my mobile boat browser weird. Again thank you dearly Antiga Prime, cool name btw!

cm12 wont enter recovery

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.