Database Develop

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.

*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.

Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app

Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX

http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app

SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.

Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.

When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.

SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.

[Q] Can't boot to recovery or download mode, Bootloader seems to be locked as well.

I have a Samsung SIII mini, Latin version (i8190L) and use it with the Virginity Rom, since the version 8, updating everytime a new one comes out.
Never had a problem whatsoever. I flashed the recently out Virginity V12 with aroma installer just to update. I backed up everything so I could make all of the wipes and then flashed it as new. The thing is that I chose the Honami Xperia Keyboard and I didn't like it because it was working somewhat buggy. So I tried (after just a couple of days) to reboot to recovery, to reflash the rom, just using the traditional S4 keyboard. To my surprise. I couldn't.
I can't boot to recovery, I can't boot to download and the bootloader seems to be locked as well. When finishing the installation and rebooting the device just after v12 was installed, the recovery gave me as a final option if I wanted to disable recovery boot, to which I chose no.
I tried rebooting using the button combination, but everytime I do, it just boots normally, as if I only had held down the power button. I tried also to use the built in reboot menu, which has an option to reboot to recovery or download, and either of them had success.
I don't know what to do, I don't want to be without recovery or download mode, in case i need them. Is this some kind of brick? the device is working perfectly, all of the apps work, and the ROM works fine, so I can fully use my device.
Also, I read on a previous post of a person who couldn't get into recovery but could get into download, he was told to delete the system file "install-recovery.sh" and then flash romracer's recovery via fastboot. I did delete the file, but fastboot did not work for me, it just kept saying "waiting for device" however my phone was connected and USB debbugging active.
Can you please help me?
Also, sorry if my english is bad, not a native speaker, and sorry if I'm too "noobbish" i'm relatively new to this stuff.

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.

Sony ZR rebooting after Resurrection Remix M v.5.7.3

Hi all,
I have a big problem with my phone.
I wanted to try out Resurrection Remix on my phone.
I installed twrp-3.0.2-0-dogo.img with fastboot.
After reboot i saw the Teamwin logo and then i did a full wipe of everything, except SD Card (like i always do when i install a custom rom)
Then i installed Resurrection Remix M v.5.7.3.zip from sd and gapps, then wiped cache and pressed reboot.
No error with flashing, when the phone booted and i saw some logo's, took like 2-3 minutes and then the phone went off and started to reboot and reboot, had to take the battery off to let it stop.
Since then my phone isn't working properly, i tried to flash different kinds of stock roms with flash tool including wipe options.
No errors with flashing, but the phone still doesn't boot or it goes off after Sony logo then i leave the battery out for 10 mins or so then it starts and it looks normal, i can install aps, i can call, but the first time when i reboot my phone with this new install it's back to rebooting. I tried to leave my battery out for 10 hours but it doesn't help.
I tried to relock my bootloader and then unlock it again.
If i tried to install twrp-3.0.2-0-dogo.img it's going to reboot also, i tried airless or evomix kernel, then recovery starts but when i try to install a custom rom zip, and try to flash it my phone reboots after 5 seconds.
And now i don't know what to do anymore, so please anyone? help?
Thanks in advance!

did you try installing stock rom with flashtool ?

What was your android version when you first flash TWRP 3.0.2 recovery?If you are coming from stock lollipop then you should flash TWRP 3.0.2 (.228).Make sure you unlocked phone bootloader.Use advance clean in the recovery,select all except sd card and clean all.Then try flashing RR Rom again.Do wipe cache/Delvik after flashing RR Rom and before flashing GAPPS.

falptekin said:
did you try installing stock rom with flashtool ?
Click to expand...
Click to collapse
Yes, i tried atleast :
C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf
C5503_10.6.A.0.454_HK.ftf
C5503_10.7.A.0.228_TR.ftf
And used all wipe options.
I used Emma tool, after that i removed the battery from the phone for 48 hours, then it booted the second time. I charged the battery and i left it like this for a few hours, then i tried to reboot but it went off after 20 seconds, tried to boot again but it goes off after Sony logo.

Røbin said:
What was your android version when you first flash TWRP 3.0.2 recovery?If you are coming from stock lollipop then you should flash TWRP 3.0.2 (.228).Make sure you unlocked phone bootloader.Use advance clean in the recovery,select all except sd card and clean all.Then try flashing RR Rom again.Do wipe cache/Delvik after flashing RR Rom and before flashing GAPPS.
Click to expand...
Click to collapse
My version was CM 13 (cm-13.0-20160801-UNOFFICIAL-dogo.zip) that was working very well, but before i flashed RR i did advanced cleaning and i checked everything except SD Card and USB OTG and a factory reset and after flashing pressed wipe cache/dalvik and then i rebooted.
The phone is off now without battery. This Sony doesn't have recovery, buttons aren't working and they never did, i can only flash twrp with fastboot wich makes it only boot into recovery and then i used this to flash custom roms.
I only started to flash custom roms about a month ago because someone gave me this Sony ZR, i bought a new original battery for it but when i call on speaker there is some underwater bubbling sound and i also wanted marshmallow and i hoped this may fix the bubbling sound, with CM 13 the sound was already better but didn't fix it completely.
TWRP won't let me flash anything anymore, it's starting to flash but after 5 seconds it reboots back into recovery.
Edit: Is it possible that there is still stuff in the RAM that is causing problems?
Edit: I thought i'm going to this phone another try. I installed twrp-3.0.2-0-dogo.img and it boots, also this version didn't want to boot anymore but now it does. I wiped everything, also SD Card, i checked everything is empty. Before i couldn't wipe my SD Card anymore and in Windows all files showed double and i couldn't copy files. Going to charge it first and think about what i want try to flash. Wipe cache/dalvik and then flash gapps is a good idea.
Edit: it almost charged now, when it charged i will remove the battery again for the night, i will decide later what i'm going to do.

Fuchsia said:
My version was CM 13 (cm-13.0-20160801-UNOFFICIAL-dogo.zip) that was working very well, but before i flashed RR i did advanced cleaning and i checked everything except SD Card and USB OTG and a factory reset and after flashing pressed wipe cache/dalvik and then i rebooted.
The phone is off now without battery. This Sony doesn't have recovery, buttons aren't working and they never did, i can only flash twrp with fastboot wich makes it only boot into recovery and then i used this to flash custom roms.
I only started to flash custom roms about a month ago because someone gave me this Sony ZR, i bought a new original battery for it but when i call on speaker there is some underwater bubbling sound and i also wanted marshmallow and i hoped this may fix the bubbling sound, with CM 13 the sound was already better but didn't fix it completely.
TWRP won't let me flash anything anymore, it's starting to flash but after 5 seconds it reboots back into recovery.
Edit: Is it possible that there is still stuff in the RAM that is causing problems?
Edit: I thought i'm going to this phone another try. I installed twrp-3.0.2-0-dogo.img and it boots, also this version didn't want to boot anymore but now it does. I wiped everything, also SD Card, i checked everything is empty. Before i couldn't wipe my SD Card anymore and in Windows all files showed double and i couldn't copy files. Going to charge it first and think about what i want try to flash. Wipe cache/dalvik and then flash gapps is a good idea.
Edit: it almost charged now, when it charged i will remove the battery again for the night, i will decide later what i'm going to do.
Click to expand...
Click to collapse
Someone maybe played with your phone in underwater to cause bubbling sound.I don't see any hardware problem in your phone.You maybe did something wrong or anything else that your phone behaving like this.Listen,You first flash a stock rom.Lollipop would be better because you can flash flashable twrp 3.0.2(.228) via flash fire or flashify app.I once tried flashing twrp img through fastboot and it caused bootloop.So I always use flashable zip.Fastboot for emergency.And try to reformatting your system pertition.I hope this will work or you'll need expert developer to help you.Maybe Daedroza can help you if my sugg. don't work.

Røbin said:
Someone maybe played with your phone in underwater to cause bubbling sound.I don't see any hardware problem in your phone.You maybe did something wrong or anything else that your phone behaving like this.Listen,You first flash a stock rom.Lollipop would be better because you can flash flashable twrp 3.0.2(.228) via flash fire or flashify app.I once tried flashing twrp img through fastboot and it caused bootloop.So I always use flashable zip.Fastboot for emergency.And try to reformatting your system pertition.I hope this will work or you'll need expert developer to help you.Maybe Daedroza can help you if my sugg. don't work.
Click to expand...
Click to collapse
The bubbling sound is a known issue with some Sony smartphones, on google i have read more stories about this problem, not only zr but also other Z models. The problem is caused by the second mic i think, if i use loudspeaker when calling and i lay the phone on the back the sound is much better. I saw on other thread about this, http://forum.xda-developers.com/xperia-zr/help/disable-mic-t3434997
On YouTube you can find many movies about this, for example https://www.youtube.com/watch?v=fC6JbuQJ_gg
It's really annoying for the other person to hear these sounds when you are calling. They need to listen very carefully to understand you, but it's only when you call on speaker.
When i wanted to flash a custom rom for the first time i wanted to do this with apps on my phone. I rooted my phone with kingroot and used an app to check if the phone was really rooted. I installed twrp app and tried to install recovery but it gave an error. I tried to install recovery with Flashify but then it says that the recovery partition is not present. When i try to flash with Flashify it says it's going to reboot into recovery but then the the phone boots like normal. The only way for me to get a recovery on the phone is just flashing with fastboot or using flashtool. Doomlord kernel and XZDualrecovery don't boot, only twrp is working.

Fuchsia said:
The bubbling sound is a known issue with some Sony smartphones, on google i have read more stories about this problem, not only zr but also other Z models. The problem is caused by the second mic i think, if i use loudspeaker when calling and i lay the phone on the back the sound is much better. I saw on other thread about this, http://forum.xda-developers.com/xperia-zr/help/disable-mic-t3434997
On YouTube you can find many movies about this, for example https://www.youtube.com/watch?v=fC6JbuQJ_gg
It's really annoying for the other person to hear these sounds when you are calling. They need to listen very carefully to understand you, but it's only when you call on speaker.
When i wanted to flash a custom rom for the first time i wanted to do this with apps on my phone. I rooted my phone with kingroot and used an app to check if the phone was really rooted. I installed twrp app and tried to install recovery but it gave an error. I tried to install recovery with Flashify but then it says that the recovery partition is not present. When i try to flash with Flashify it says it's going to reboot into recovery but then the the phone boots like normal. The only way for me to get a recovery on the phone is just flashing with fastboot or using flashtool. Doomlord kernel and XZDualrecovery don't boot, only twrp is working.
Click to expand...
Click to collapse
First of all change the kingroot with supersu.Kingroot root access control not so stable.Download selinux mode changer to set in permissive mode.If you are at LP version,twrp app won't install recovery or support it.flash twrp3.0.2(.228) via flashify or different flashing app.selinux permissive mode will let you to go to recovery mode.By the way,xzdualrecovery is for locked bootloader and should boot without any problem.I don't know it will work on unlocked bootloader or not.So try your best what I have told and this is all I have to share from my own experience.

Røbin said:
First of all change the kingroot with supersu.Kingroot root access control not so stable.Download selinux mode changer to set in permissive mode.If you are at LP version,twrp app won't install recovery or support it.flash twrp3.0.2(.228) via flashify or different flashing app.selinux permissive mode will let you to go to recovery mode.By the way,xzdualrecovery is for locked bootloader and should boot without any problem.I don't know it will work on unlocked bootloader or not.So try your best what I have told and this is all I have to share from my own experience.
Click to expand...
Click to collapse
I flashed the latest Lollipop and it's back to rebooting, i see the sony logo and before it says powered by android it goes off. I removed the battery again, i will try to root the phone and use selinux mode changer when it's booting. It wil take atleast 12 hours without battery before it boots.

Fuchsia said:
I flashed the latest Lollipop and it's back to rebooting, i see the sony logo and before it says powered by android it goes off. I removed the battery again, i will try to root the phone and use selinux mode changer when it's booting. It wil take atleast 12 hours without battery before it boots.
Click to expand...
Click to collapse
Is there any problem with your phone?Did you experiment your phone too much?I don't get it,why after flashing stock rom via flashtool gives you bootloops if no error showed up while flashing!!Is this your battery problem?And I think so because few months ago my phone battery heavily damaged and therefor It don't charge and my phone didn't bootup but bootlooping.I first thought it was my mistake to flash rom incorrectly.So i had to flash stock rom via flashtool to go back to normal but unfortunetly PC don't recoznige my phone not even fastboot.I was worried and couldn't do anything and went to service center,they changed the battery with new one and my phone comes to life again.Mainly this was for my local charger fault.it also damaged in that day too.SO brought a orginal sony charger.But you said you brought a new battery too then how come you face bootloops.well if there is no error message shows up I can't help you with anything.Only better expert member can help you.By the way you can collect log via adeb fastboot if your phone fastboot mod work.
Here is the inst:
1. Install the Android Debug Bridge using http://developer.android.com/tools/help/adb.html
2. Instructions on installing Android Debug Bridge are located here:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android- debug-bridge-utility
3. Run the following commands:
“adb logcat -c" (This clears the logs.)
4. Reproduce the issue.
5. Then, run the following command to capture the logs in a file:
“adb logcat -d > Name_of_Log_File.txt"
maybe it will gives some clues what is happening.

Røbin said:
Is there any problem with your phone?Did you experiment your phone too much?I don't get it,why after flashing stock rom via flashtool gives you bootloops if no error showed up while flashing!!Is this your battery problem?And I think so because few months ago my phone battery heavily damaged and therefor It don't charge and my phone didn't bootup but bootlooping.I first thought it was my mistake to flash rom incorrectly.So i had to flash stock rom via flashtool to go back to normal but unfortunetly PC don't recoznige my phone not even fastboot.I was worried and couldn't do anything and went to service center,they changed the battery with new one and my phone comes to life again.Mainly this was for my local charger fault.it also damaged in that day too.SO brought a orginal sony charger.But you said you brought a new battery too then how come you face bootloops.well if there is no error message shows up I can't help you with anything.Only better expert member can help you.By the way you can collect log via adeb fastboot if your phone fastboot mod work.
Here is the inst:
1. Install the Android Debug Bridge using http://developer.android.com/tools/help/adb.html
2. Instructions on installing Android Debug Bridge are located here:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android- debug-bridge-utility
3. Run the following commands:
“adb logcat -c" (This clears the logs.)
4. Reproduce the issue.
5. Then, run the following command to capture the logs in a file:
“adb logcat -d > Name_of_Log_File.txt"
maybe it will gives some clues what is happening.
Click to expand...
Click to collapse
I tried my old battery and it boots, already booted up 3x times. I never thought it maybe the battery because it's only 2 months old. Thanks so much for your help.
I tried to install recovery with selinux permissive mode and flashify but i stil can't install recovery.
It says: Partition not found, your recovery partition couldn't be found. You won't be able to flash recovery images. You can stil flash zip files.
I don't think it's possible to have recovery on this phone, atleast not the normal way.
Edit: I flashed RR and it's working fine. I'm so happy it's working again, i never really used this old battery but i think it's not so bad at all. I only lost 8% battery with flashing and booting RR. I never really thought it was the battery because it was charging normal, i used it for 2 months or something without problems.

Fuchsia said:
I tried my old battery and it boots, already booted up 3x times. I never thought it maybe the battery because it's only 2 months old. Thanks so much for your help.
I tried to install recovery with selinux permissive mode and flashify but i stil can't install recovery.
It says: Partition not found, your recovery partition couldn't be found. You won't be able to flash recovery images. You can stil flash zip files.
I don't think it's possible to have recovery on this phone, atleast not the normal way.
Edit: I flashed RR and it's working fine. I'm so happy it's working again, i never really used this old battery but i think it's not so bad at all. I only lost 8% battery with flashing and booting RR. I never really thought it was the battery because it was charging normal, i used it for 2 months or something without problems.
Click to expand...
Click to collapse
If it was a battery problem then change it or carefully use it.And the error you are facing is because the latest flashify has some bugs.But now as you are already using RR MM rom.You can download twrp app and use this app to install recovery.

Røbin said:
If it was a battery problem then change it or carefully use it.And the error you are facing is because the latest flashify has some bugs.But now as you are already using RR MM rom.You can download twrp app and use this app to install recovery.
Click to expand...
Click to collapse
I tried to install recovery, flashify hangs all the time, twrp app gives an error when i try to install recovery and flashfire says there is no partition for this image. I thought i'll do a factory reset in RR and when the phone rebooted i saw twrp. I tried with pressing the buttons when booting but no luck. I used reboot into recovery option and it worked. This is the first custom rom that gave my phone recovery.
I will throw the battery away and use the old battery, i can always buy a new one later.

Fuchsia said:
I tried to install recovery, flashify hangs all the time, twrp app gives an error when i try to install recovery and flashfire says there is no partition for this image. I thought i'll do a factory reset in RR and when the phone rebooted i saw twrp. I tried with pressing the buttons when booting but no luck. I used reboot into recovery option and it worked. This is the first custom rom that gave my phone recovery.
I will throw the battery away and use the old battery, i can always buy a new one later.
Click to expand...
Click to collapse
OH!So that the old recovery occupied all the recovery partition space that you are unable to install twrp recovery.But old recovery should be replaced by new recovery,that's strange.well I don't know how did this happen but don't use fastboot to install recovery or anything else,It's for emergency.I'm not fully familiar with fastboot though,I tried once before and caused trouble. I hope your troubles are gone now.

Røbin said:
OH!So that the old recovery occupied all the recovery partition space that you are unable to install twrp recovery.But old recovery should be replaced by new recovery,that's strange.well I don't know how did this happen but don't use fastboot to install recovery or anything else,It's for emergency.I'm not fully familiar with fastboot though,I tried once before and caused trouble. I hope your troubles are gone now.
Click to expand...
Click to collapse
My phone don't have any partition recovery, i tried 100x times with stock rom to boot recovery, with buttons, with apps that boot in recovery. I do have recovery with RR rom, but it's not in the recovery partition. I tried Tesla, CM 13, XOSP but still no recovery. I tried to boot recovery with all roms, but it doesn't matter. It's fine now, been playing a bit with RR and it's a nice rom. Thank you for helping.

rooted OP3 w/ cm13 & TWRP: Normal & recovery boot black screen, `adb devices` empty.

rooted OP3 w/ cm13 & TWRP: Normal & recovery boot black screen, `adb devices` empty.
Hi everybody,
I've got a rooted OP3 with CM13, TWRP & OpenGAPPS installed. I recently installed cm13 2016-11-25 nightly. After that, google play services kept crashing. So I tried to reinstall GAPPS via recovery mode only to find out booting into recovery mode ends up in a black screen. Normal booting still worked. Then I though maybe 2016-11-30 nightly would fix the problem and downloaded the images via settings -> update and rebooted via click on the downloaded image file. But of course booting into recovery still wouldn't work. But now even the normal boot ends up in a black screen.
To add insult to injury: When booting into fastboot mode `adb devices` list stay empty. (which I know worked when installing cm13 first).
Any idea what I could try next?
Niko.

ende42 said:
Hi everybody,
I've got a rooted OP3 with CM13, TWRP & OpenGAPPS installed. I recently installed cm13 2016-11-25 nightly. After that, google play services kept crashing. So I tried to reinstall GAPPS via recovery mode only to find out booting into recovery mode ends up in a black screen. Normal booting still worked. Then I though maybe 2016-11-30 nightly would fix the problem and downloaded the images via settings -> update and rebooted via click on the downloaded image file. But of course booting into recovery still wouldn't work. But now even the normal boot ends up in a black screen.
To add insult to injury: When booting into fastboot mode `adb devices` list stay empty. (which I know worked when installing cm13 first).
Any idea what I could try next?
Niko.
Click to expand...
Click to collapse
1. Download new firmware from here (3.2.8 or OpenBeta 7) and TWRP (at least 3.1.0-2.22, don't have an original link, found one here).
2. Boot into fastboot (power+volume up button)
3. Flash recovery: "fastboot flash recovery twrprecoveryname.img" (without ")
4. Try booting into the recovery now.
If OK:
5. Flash new firmware.
6. Boot into your ROM.
7. Should be good to go.
If booting into the recovery doesn't work, try another TWRP, for example this one (it doesn't work with encryption yet tho).

Thanks for your help. Flashing twrp via fastboot did work.
I flashed twrp-3.0.2-1.28-oneplus3, twrp-3.0.2-1-oneplus3 and twrp-3.0.2-22-oneplus3. With all three: About a second after selecting "Recovery" in the "Options menu" I'm back at the boot screen (where I again can enter the "Options menu"). The same happens if I choose "Power off" or "Restart" in the "Options menu".
When I don't enter the "Options menu" and just let the phone continue I get the "1+ POWERED BY android" splash screen for 10 seconds and then the screen goes black.
Any other ideas?

Ok. Now it worked. I used twrp-3.0.2-22-oneplus3.img. I may have missed the "recovery"-part in your instructions "fastboot flash recovery twrprecoveryname.img" when I tried it first. *facepalm*
Thanks for you help! Niko.