Database Develop

XZ in continious bootloop, no matter what i flash/do

Hi guys,
Device info:
Model C6603, Unlocked bootloader
So i have the following problem, my device is in a bootloop and i can't figure out what the exact issue is. I'm out of options at least.
First a little background on how it came to be: (scroll down for short overview)
Before official lolipop came out I've been on CM12.1 for a few months, cm-12-20141221-INFECTED-yuga to be exact. When official lolipop came out I installed C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB following the instructions, although i see the thread has been modified (name, updated etc.) the instructions are the same. I did not install Xposed yet, because i wanted to try stock+root first.
After a few weeks of normal use, i used google maps navigation. This worked fine but when i arrived at my destination and picked up my phone closed google maps app but then my phone crashed. It rebooted to the point where i had to enter my pincode, but every time i was entering my pin it crashed and after a few tries it dind't even got to the lock screen but only showed the sony logo and rebooted(bootloop). I noticed my device was getting hot and left it alone for a few minutes, after that i started my phone again and was able to use my phone again. Until I started google maps again for the way back and enabled gps it crashed again, the same thing happened the phone would reboot when entering my pin, the phone wasn't hot this time. I left the phone alone till i got home, put it on the charger and the next day my phone worked fine again.
A few days later i was outside in the sun whatsapping, when the same happened my phone crashed and rebooted when entering the pin or slightly after. The phone was feeling hot, also because it was exposed to the sun for a while, in TWRP recovery it showed temperatures around 70 degrees celsius (i don't know if this is too hot?). After i had left the device alone for a while and try to boot it up it got stuck in a bootloop (sony logo), after a night of charging it got to the point of entering the pin code again but crashed and got stuck in a bootloop again (sony logo). And since then i'm not able to get rid of this bootloop. However i could still get into recovery (TWRP).
First i tried to reinstall the rom, factory reset and flash via recovery: C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB
This worked, and the device booted up but after a while it crashed and got stuck in a bootloop again (sony logo).
So all summed up:
cm-12-20141221-INFECTED-yuga
>> C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB
>> Google maps navigation >> overheated >> bootloop (sony logo) >> charging night >> working >> whatsapping in bright sun >> overheating >> continuous bootloop (sony logo)
What i have tried:
- Tried booting without sim card, withoud sd but doesn't work
- Flash same rom via recovery C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB : Worked once, but then crashed and went back in bootloop, now when i flash this only Bootloop (sony logo)
- Flash updated version of http://forum.xda-developers.com/xperia-z/help/lollipop-5-0-2-10-6-0-454-pre-rooted-t3116205 via recovery : Bootloop (sony logo)
- Flash kernel via fastboot http://forum.xda-developers.com/xperia-z/development/kernel-unlocked-bootloaders-t3114234 : Only recovery works
- Flash stock kernel via fastboot: boot (sony logo) one time then turns off
- Flash stock lolipop (with and without bootloader unlocked) via latest Flashtool : Bootloop (sony logo)
- Flash stock lolipop via xperifirm (C6603_10.6.A.0.454_KPN Mobile NL) xperia (with and without bootloader unlocked) via latest Flashtool : Bootloop (sony logo)
- Flash stock kitkat (with and without bootloader unlocked) via Flashtool: Bootloop (sony logo)
- Relock bootloader and Sony PC companion restore latest firmware : Bootloop (sony logo)
- Restoring serveral backups from TRWP and Phillz touch but they all result in the same bootloop, while at the time the backups were made there were no problems.
I'm pretty much out of options and begin to thinking something was damaged when the device overheated or a bad partion of a kernel is still stuck in the devices kernel.
Does anyone had the same issue, if so how to fix it? Or another option i could try, maybe someone spotted anything i did wrong?
Current state:
Locked bootloader, stock lolipop 10.6.A.0.454 flashed via Sony PC Companion recovery
Boots into setup, after a few reboots I completed the setup. But still randomly reboots when trying to use some apps or in general leaving it in standby for a while (might be due instability).
Thanks in advantage,
Jonathan

So the only things that you do that do not result in a bootloop are flashing a kernel. Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel. Post result here...
Good luck

Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel.
Click to expand...
Click to collapse
Don't do this. It will wipe your data and flash everything but the kernel, therefore losing root etc.
If you want to flash a stock kernel, you must leave everything in the "Wipe" section unchecked, and check everything but "Kernel" in the "Exclude" section.
I don't think this will help anyway, being that you're already on a stock firmware flashed via Flashtool.

aaronkatrini said:
So the only things that you do that do not result in a bootloop are flashing a kernel. Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel. Post result here...
Good luck
Click to expand...
Click to collapse
Thanks for your fast reply, I think you meant: check everything but leave kernel unchecked (as kingvortex replied at the time of writing)? Since it is an 'Exclude' list. I flashed stock kernel, it shows the Sony logo and then shuts down. I used stock lolipop kernel from 'C6603_10.6.A.0.454_KPN' Mobile NL, and i also tried 'C6603_10.6.A.0.454_Customized CE1'. both have the same result.
I've got the most "life" after i restored my phone with pc companion to 10.6.A.0.454. Then, after being charged via the wall charger for a while, it boots up normally and goes into setup, since it is a complete restore. But crashed around the setup screen for wifi. The other options i tried do not come any further than showing the Sony logo, this stock one shows Sony logo >> android logo >> boot animation + sound.

I'm thinking it might be a case of a dead battery or battery controller of some sort. Because the phone only boots up normally, with stock android .454, when the phone is connected to the wall charger. Whenever i pull out the cable the phone crashes and reboots, also when not connected to the charger it gets stuck in a bootloop. However when the phone is connected to a charger and working for a while it still randomly crashes when using the device, sometimes these moments are suspicious because it sometimes reboots when enabling gps, wifi, mobile data or when starting an app, phone call or synchronizing accounts for instance. On a side note sometimes the battery percentage drops about 6-9 percent when rebooted one time or when crashed, also when i connect my phone to the charger the status led is red but when done showing the sony logo and when charging it turns green (or yellow, depends on battery percentage). This is why i think something internal is not working properly whether it is the battery or the battery controller, i don't know.
I still find it weird that the phone was in perfect condition before flashing .454 stock lolipop, it might be due to overheating that some components where damaged. At least i'm guessing this is the case because i know no other reason why it would show such behavior. Is there someone who has experienced something like this or another solution i might try?

In the mean time i bought a Z3, my XZ is definitely dead now after the battery has discharged and i can't charge it because it's constantly rebooting. However flashmode and fastboot are still working. Thanks for the replies. I might repair my XZ if i can get my hands on a cheap (broken) second hand and replace the internals, but i'll see.

Hi, i have the same problem... i cant charge and the constantly rebooting... and in my case also... when i try to flash any ROM, flashtool and Fastboot are stuck for 1 hour when try to flash system.sin (system.img)
i stop flashing after 1 hour... not sure if could finish after 2 hours :/
Cant use PC Companion because dont have charge in the phone (locked bootloader)
Any suggestion?

Z1 stuck in boot loop after fumbling my way around a Chinese recovery

So I recently tried updating MIUI v5 to MIUI v6. However, I stupidly opted for the FOTA update, rather than updating using recovery.
After running the update, my phone rebooted and it worked fine, MIUI v6 running great. However, because I'd updated using the in-built updater, my data and apps were still there from before. This was causing no-end of 'process stopped running' alerts, which drove me crazy after around 10 minutes.
Therefore, I decided to try and wipe my data. I went to the recovery menu and found that MIUI had installed its own Chinese recovery, my previous TeamWin one was gone. So I fumbled around and managed to find the 'Wipe data' etc. option, and chose it. I was presented with a couple more options which I didn't understand, and (stupidly) accepted both. This left me with a phone that would no longer boot past the 'Sony' logo. I was also unable to access the Chinese recovery menu.
Feeling a little worried at this point, I started to Google around for guides on how to flash a recovery back onto a phone stuck in a boot loop. After hours of searching, I decided it wasn't possible and instead follow a guide for fixing 'boot loops' through flashing an original Sony 'ftf' firmware using flashtool.
Now, the guide I was following was quite old, and provided a link to 'C6903_14.2.A.0.290_Global LTE' - so this is what I used to flash (which I'm now regretting). Before flashing, I was presented with some options, for which the guide I was following recommended I deselect the 'kernel' option. So I did this too.
After around 10-15 minutes and what seemed like a successful flash, I tried turning the phone on. This time, the Sony logo appears, then disappears to a black screen, and then the backlight turns off, followed by the Sony logo, then a black screen, then backlight turning off, etc. So slightly different behaviour to before, but still boot looping.
I think what may have happened is that MIUI includes an updated kernel, and through flashing the 14.2.A.0.290 firmware without a kernel, I've introduced some sort of incompatibility.
The problem I'm having now is getting another firmware onto the phone in order to resolve this. For some reason, despite flashtool recognising the phone being plugged in with flash mode, it refuses to load the firmware - I'm instead presented with the message:
"You must have the according fsc script to flash this device."
Does anyone know how I might be able to get around this? I admit to being a bit of a noob when it comes to flashing so have probably dug my own hole here, and seem to have left myself completely unable to work out what I need to do in order to get back out! Any help would be hugely appreciated.

Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!

langauld said:
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
Click to expand...
Click to collapse
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)

Just2Cause said:
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Click to expand...
Click to collapse
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.

langauld said:
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
Click to expand...
Click to collapse
Glad I could help.

need help, regarding xperia T lt30p cant turn on

hello everyone!
i have a few questions. and i have done my research yet i still find no solutions so i will ask here
this is my story...
-root,unlock bootloader,flash cm12 android 5.0.1, ran cm recovery
-running fine for around 2 weeks.
-in those 2 weeks there has been times where phone drained to 0 its battery, then charged it then it was fine
-suddenly one day. charged it after it drained completely. then wont turn on.would boot up to 'sony' screen then repeatedly reboot and do the same thing again.
-could enter recovery, but when trying to reflash rom, phone would reenter boot loop
-have tried charging for days.
-have tried removing battery, same thing
-then used flashtool, relocked bootloader, reflashed stock firware, now cant get into recovery, flash successful, yet phone still cant turn on pass sony screen.
is it a battery problem?

just to add, ever since the first time it started having this problem, i could never get the phone to turn on at all without plugging it in .

Hi Jetdin
had the same problem with my XT a year ago, when a powerbank somehow "nuked" the battery-logic... After that, I had the pleasure to know what a deep-discharge feels like :-/
To revive my XT, I had to replace the Firmware... I did it this way, maybe you can try a "factory reset", maybe it already works out for you...
1. loading it (turned off) 24h with original recharger (don't try to turn it on)
(1a - if you can reboot it to save apps, data, files - do it)
2. reboot into TWRP - and do a factory reset
...and try your XT; with luck, this already solved your problem... if not:
3. get the new image of your choice - i downloaded whiteneos 12.1 - works like a charm... and copy it to an sd-card
4. after (re)loading the XT - boot into TWRP - and install the new image...
...reboot and hope this solved the problem...
Good luck!!
Edit:
that it only stops at the sony-logo sounds like "operating system not working" - maybe a "higher" OS-version will do the trick?

Thanks for the reply theunlucky.
I have tried most of those.
The cm12 was on Android 5.0.1
The stock firmware for the Xperia T only goes up to JB huhu

Jetdin said:
Thanks for the reply theunlucky.
I have tried most of those.
The cm12 was on Android 5.0.1
The stock firmware for the Xperia T only goes up to JB huhu
Click to expand...
Click to collapse
you cant get pass the sony logo?
unlock your bootloader again
1. download whiteneos cm
2. extract the boot.img and flash it via fastbootmode
3. reboot
4. if you see a led hit vol + ( or vol - ) several times until the led color changes
5. now you should be in recovery... try to flash cm12.1 from whiteneo and reboot
Sent from my Xperia T using XDA Free mobile app

I can do that with a locked bootloader is it sir?
How do I relock my bootloader?or do the steps u give also unlock the bootloader?sorry for all the Qs

Data Partition always destroyed after turning off phone

Hello there.
I have a Huawei P9 (EVA-L09) with an unlocked bootloader and a custom ROM.
Since a few days I started experiencing something completely weird.
Every time I happen to turn off my phone (often only because the phone had gotten quite warm and I want it to cool down then) I then land in the boot animation and get stuck there. After forcefully rebooting the phone from there (about half of an hour) I held the Volume Up key for three seconds during the warning screen and eRecovery told me about the Data Partition to be badly damaged and it would be recommended to recover it.
There are two ways I can do from here (and also did):
First way is to let it recover using eRecovery, connect to my wireless connection, however the phone always tells me that there was a problem getting the package info for my phone. (Does Huawei stopped supporting the P9 eventually?)
The second way is to run TWRP and reinstall the custom ROM (In my case RROS 5.8.5 for my P9) and to never turn my phone off again. However this isn't always possible to keep it on since it also could happen that I'm not at home and my battery suddenly died.
Installing the stock ROM (or a custom ROM based on a stock ROM) however doesn't work. The stock ROM itself simply won't get installed, neither over the dload method or TWRP or fastboot and a custom ROM based on the stock ROM results in having my phone simply getting a black screen when locking it and then I need to reboot it to use it again.
What can I do? Could it be that my flash memory could be corrupted or something could have happened with one of the partitions of the phone?
Greetings.
EDIT: I managed to install a stock firmware using this link right here.
After the stock firmware was installed, doing a factory reset and wiping the cache every problem I mentioned above this edit vanished.

After restart device is bootlooped on mi.com logo

Hi,
Today my device was lagging and I restart it. Just after that I get the bootloop (showing MI.com logo). I can't open the recovery menu using the Power + Vol+ combination, but at least I could load FASTBOOT using Power + Vol-.
Using terminal command "fastboot reboot recovery" also doesn't help. I can't turn off the device as well - after some time showing me the logo device reboots again.
History - I have flashed my device ~1.5 year ago using OrangeFox + MIUI 11 raphael. The reason why I did it was my stock firmware didn't allow me to use NFC, there just was no option to enable it. After flashing everything was fine until today. Btw, device is unlocked. I am not sure what ROM version did use exactly because pretty much time passed already.
I spent a day googling for a solution, but didn't find anything.
What can be the reason? Is there a way to fix it?

If you haven't tried it yet, I'd suggest you flash your latest backup (if any) or flash the stock ROM again.

@TrulyPain no, I dont have any backup unfortunately.
Regarding the flashing stock ROM
1. Before I used OrangeFox to flash the device but now I cant boot recovery mode. Is there a safe way to do so?
2. Does only stock ROM fit? No custom?
Tried so many different approaches today. None of custom recoveries worked. I tried to use stock recovery - same result.
The only thing I didn't try is Mi Flash Pro stock ROM flash, but before that I wish to be sure I tried everything else.
Also, the repair specialist told me (remotely, he didn't check the device) that potentially it can be the memory hardware problem and advised me to visit Xiaomi official repair service. But.. it's pretty complicated for me currently.

romahaaa said:
Does only stock ROM fit? No custom?
Click to expand...
Click to collapse
I would recommend starting with the stock ROM as you can then more easily see if it is a hardware-related problem or not. Also, it sets a suitable environment for any custom ROM installed afterward. This, as many custom ROMs, don't contain all partitions and need some partitions to be written by the stock ROM, e.g., the "OEM" partition.
After you have installed stock ROM - if everything works fine - you can install any custom ROM of your choice following the recommended instructions.

We tried 2 difference ways to flash to phone using stock ROM, but no luck. Seems the problem was in the motherboard. Left it for repair, but.. doesn't mater already, as everything has lost. After that case I move to iPhone back - there would never happens this **** with data lost in unexpected cases.
Thanks for the help