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?
Hi.
I've been searching for a solution on how to fix my phone for already almost a year now. I didn't even do anything to it, no custom recoveries or OS (wanted to get CM, but at the time it wasn't available on it, not sure if now is).
The problem - the phone is stuck in a bootloop with an empty battery. The battery wasn't empty at the beginning, but it died in the process of trying to make it work, since the only thing I can boot is "fastboot&rescue" mode, in which the phone doesn't charge - how sweet. Now, I've read just about every thread here on how to flash custom (and original) recoveries, all the DLOAD folder versions and everything, and somewhere in between all that I found that it's impossible to flash anything if the battery is low (or totally empty).
The question - how do I charge the battery if it doesn't boot in anything other than fastboot, and when I plug it in the wall it just loops and loops and loops, and doesn't even charge? It's also impossible to turn it off while it's plugged in the charger. WTF, Huawei, really?
Any help appreciated. Cheers,
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
l3Nni said:
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
Click to expand...
Click to collapse
No, can't boot into recovery, only fastboot. If I could, I guess I would've already fixed it, heh.
I actually got it to charge, at least that's what I think. There was a *.bat script somewhere here that was repeatedly doing these two things:
1) fastboot getvar battery-voltage
2) fastboot reboot-bootloader
So, I ran that (while the phone was plugged in my computer and running fastboot mode), and it began looping and looping and looping. Left it like that for the night. Now, in the morning, when I unplugged it and tried to do someting, the red "battery low" LED wasn't glowing/blinking anymore! Since "fastboot getvar battery-voltage" returned an error all the time (remote: command not allowed), I don't exactly know how much power I have in it, but I'll just leave it like that for a day or two now, and then try some of the methods I've already tried before. Got any new ones I could try?
I already removed the back and removed the battery - wanted to see if I can charge it externally, but has a very small connector to connect it to the mother board, and I can't just put it in any external charger - I actually didn't find any external chargers that can charge the battery of this phone, really strange.
About the warranty - don't even care anymore. Somehow I managed to get a small crack on the glass on the back of the phone just a few days after getting it. Screen is not damaged, just the back cover. And, you don't know Latvia, but this is how it goes here. I took it to a repair shop - the one I needed to take my device for warranty repair. However, in Latvia that means it's just an another small repair shop, which just happens to have a contract with the company who sold me the phone (mobile phone operator). So, they take my phone, say they'll do a diagnostic and get back to me. Three weeks pass, and they call me telling that the only thing they can do is replace the motherboard, which is gonna cost me about 250 euros. That, or nothing. I don't agree. That means, if I don't agree to their suggested method of repairing, I have to pay for the diagnostic (about 20 euros).
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Just flashed TWRP 2.8.1.0, it's already getting better. Now when I tried turning it on in recovery mode, it's not just simply bootlooping all the time, but is stuck on the Huawei logo. At least I hope that's better If I try to turn it on normally it just bootloops again. Omg omg omg.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
edzjins said:
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
Click to expand...
Click to collapse
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
SiulGKT said:
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
Click to expand...
Click to collapse
Hi. Yes, bootloader unlocked, 100% sure. Have tried flashing the stock recovery, no changes. Tried to find the b135 now - I actually failed to find a real, valid download link! All I found were some russian ****up sites, which downloaded some russian ****ing malware! WTF? I'm about to give up on this phone. Just destroy it with all my hate for it. **** this ****ing piece of **** to hell. There is no hope, and **** my life. Whatever.
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Ziolek67 said:
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
edzjins said:
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Click to expand...
Click to collapse
Than you probably have EMUI 2.3 ROM version.
Try flashing B135 recovery from here.
Next try to install B135 ROM from this link.
l3Nni said:
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
Click to expand...
Click to collapse
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
edzjins said:
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
Click to expand...
Click to collapse
B135 recovery
http://forum.xda-developers.com/ascend-p7/general/trying-to-update-rom-1-2-t3222485
I uploaded it couple days ago...
OK, I left it "charging" for 2 days straight, hoping maybe battery was too low to flash partitions or whatever. Just wanted to make sure the battery is charged enough. I can't check the voltage or the percentage, because "fastboot getvar battery-voltage" always says that it's forbidden, no permissions, whatever.
So, I left it to charge for 2 days, and now I tested all the things you guys have posted here. Carefully, one by one. Every fastboot flash command returned success, but in the end nothing changed. Doesn't matter which recovery and/or boot I flash, it's just stupidly bootlooping all the time. Nada.
Finally, you can buy a defect P7 (with a broken screen or anything like this) for pretty low money on eBay and change the motherboard.
But I could also understand it well if you just throw it out of the window.. You had really bad luck.
Probably i have the same problem..... You solve yours problem with this ?
Nop, didn't solve the bootloop. I managed to get a donor phone for 55eur though, which had a bent body and wasn't functioning well because of that, and the screen was a bit cracked too. So I did a motherboard swap. Worked perfectly, but the battery connector protecting case screw doesn't hold in anymore, so sometimes it just turns off because it loses connection, or something. I tried to fasten it with some duct tape, hoped it'd help, and put a hard case on it - got better, but still fails sometimes.
I try give it back on warranty, i hope thei repair it.
I am in the EXACT same boat as edzjins. I have wasted 4 days of my precocious life trying to flash stuff on a phone with a completely dead battery.
I just doesn't work, period!
The only possible fix is to buy a new battery, replace the old one, and after the new battery is installed, have all of the flashing software ready to go and fired up before the new battery dies, too!
Its a time game.
Just like edzjins, there was a brief period of time when I thought I could stop the bootloop via TWRP recovery, but was unable to and the battery completely died.
Be wary of trying to flash "EdXposed" framework with TWRP. Instead, flash it only through Magisk.
I have learned the hard way : (
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