C9603 Bootloop after using Flashtool - Xperia Z1 Q&A, Help & Troubleshooting

I'll try to give as much information as I can here.
I wanted to downgrade Android from 5.1.1 to 4.4 as Lollipop in general was giving me so many issues it was making my phone unusable. So I looked up as much as I could, downloaded the latest Flashtool and the 14.4.A.0.108 Central European 1 version of KitKat.
During the flashing process I did not select a wipe of userdata as I wanted to see if I could keep what was on my phone without having to do so. I also checked the box to wipe applogs, as I wasn't sure what that was and 'what was the harm?' I thought. I couldn't find anything about what that actually was, so I don't know.
Now it is stuck in a boot loop, but thankfully phone can be turned off. Flashtool is giving me an error when I try to flash it again, so all further details are below. This was my first time using Flashtools and doing anything of this kind, so please try to be nice. Thank you.
- Customisation Version 1276-4318_R2D (Not sure if this is relevant)
- Able to enter Flash Mode and Fastboot
- No recovery mode, Stock ROM with developer options but I think it has a locked bootloader (not really sure what this means)
- No SD card, but I backed up what I wanted to keep on the PC.
- All drivers for phone are up to date on computer, but Sony PC Companion (including repair mode) requires phone to be on and connected I believe.
- I tried to flash it again but this time wiping everything, except Flashtool gives error of 'Processing of loader.sin finished with errors' and then aborts the flashing process.
EDIT: Finally successfully flashed 4.4 to the phone.
Now I have a couple of new problems.
1. The screen keeps randomly clicking/moving itself.
2. My back/home/etc buttons at the bottom of the screen still aren't responding quickly, and I get quite a bit of lag using them.

it is due to dirty flash, I guess, reflash with wiping selected and it should be OK

Related

[Q] How to repair/restore?

Hi,
The Whole Story (skipable but it contains the details):
I wanted to install a custom ROM on my xPeria SP. I knew I had to root my phone so I went to the tutorial ( http://forum.xda-developers.com/showthread.php?t=2440375 ) for this. Everything went well and I managed to root. (I
Now, since I wanted kitkat 4.4 ROM, I searched for another tutorial. (http://techbeasts.com/2013/11/30/install-android-4-4-kitkat-cm-11-custom-rom-on-sony-xperia-sp/. )
It said I needed an unlocked bootloader. So I managed to do this as well.... I think. I hadn't checked this.
It also said that i needed the clockwordrecoverymod. Therefore I followed this tutorial. (http://techbeasts.com/2013/11/18/ho...ony-xperia-sp-on-12-0-a-2-254-firmware-guide/).
Then I went on with the Kitkat tutorial. I did every step until VII. I had to deconnect my phone to insert an SD-card. I tried to turn on my phone and it had a bootloop: The Sony logo appeared, then the colourful waves, then it got stuck and it started over again.
I tried whether I could boot in CWM but that didn't work either. I still could connect in fastboot mode so I tried te reinstall the CWM via another website. (http://editandroid.blogspot.be/2013/06/sony-xperia-sp-install-custom.html). I flashed the kernel like they said, then deconnected my phone.
The Problem:
Now I can't put it in fastboot or flash mode. I can start it up but everytime I do, it get's stuck at some point (like when turning on the wifi or browsing through the playstore) and reboots itself or I have to wait a long time before it works again. Also all the factory settings are restored and all data is wiped out.
Is there any way I can fix this?
Extra information:
-Windows Vista 32Bit
-C5303 Model
-Yes, I've used a couple times the Hard restore.
-Flashtool by Androxyde used
EDIT: I can go into flash/fastboot mode

[Q] Help needed: tried to install Cyanogen 11, can't boot.

Hello all! So, I tried to install CM11, the one on this post.
Went into CWM, did Wipe data factory reset and formatted /system. when I tried installing the rom, it said operation aborted and it could not install it. No biggie, the post says to install cm10.2 before doing so.
So i Powered the phone off to copy the file over to the SD. To my surprise, now I can't get into CWM, Philz, TWRP, fastboot or flashmode. Whenever I press the back pin to power the phone off, it turns back on automatically before I have time to press the key and connect the USB cable. Furthermore, when I manage to do it quick enouhg, the green led lights up, but it fades away after 10ish seconds only to display the sony logo again, and a "can't recognize USB device" popup comes up in my PC. I've used flashtool with this same pc in the past, so I don't know what that is about. Also, whenever I try installng flashtool drivers again, just in case 2 things happen:
there is no xperia SP device listed and whatever i select it fails to install.
What can I do now? I had 4.3 with the eXistenZ Ultra ROM before all of this.
Damm, this is the first time this happens to me, I've been swapping roms for ever, and this is not even the first phone i do this in, had a galaxy s2 and a wildfire S before. I feel like such a noob
UPDATE!:
So I finally managed to fix it. I posted this after about 8-9 hours of trying to get into fastboot on the 3 different pcs in my household, all had the drivers at some point and i've worked with them and fastboot and this same phone previously, so I figured they'd still work. They didn't, I couldnot even get SUS to work. So i went to a 4th PC, installed SUS and the needed drivers and it only took like 40 minutes worth of tries. I'm in the software download part of the SUS, i'll keep this updated!
UPDATE2!:
So, it finished downloading but it suddenly disconnected, tried again for about 10 minutes and then got it going again. Downloaded the second time and installed it successfully. Leaving this up for future reference!
Bottomline: if you can't get into flashmode, try on as many PCs as you have available for at least 30 minutes each.
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Th3Duck said:
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Click to expand...
Click to collapse
No problem, it kinda sorted itself out by brute force connections :> Dammed sony, locking the bootloaders for real. I even got the sim unlock code from my phone company and it's still not bootloader unlockable at the phone settings, even though i can now get any sim i want in it -.-

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.

Blank screen on a flashed Sony Xperia Z1

So I attempted to flash the following ROM http://forum.xda-developers.com/xpe...-5-1-1-ftf-pre-rooted-file-t3200955?nocache=1 on a Z1C I purchased used from a local store using FlashTool in Linux. The FTF applied successfully, but upon reboot the screen doesn't display anything.
I can issue reboot commands via FlashTool and the phone reboots (I can see the detection status change in FlashTool) and if I reboot and hold power+vol down, It says it's entering Flashboot mode (but oddly, the light on the phone doesn't turn blue like it use to in Flashmode. It does change colours when charging).
The bootloader for this phone is locked and cannot be unlocked due to the carrier (arg! I didn't even realize this was a thing. This is the first Android phone out of all the ones I've owned dating back to my HTC Evo4G, where it is impossible to unlock the bootloader), so I have to use a stock rom/kernel. Since I can't run Cyanogen, all I want is the Stock Rom with Su/Root.
Anyone know why my display isn't working? I've also tried flashing the FTF file with data and cache wipe and still no dice. What am I doing wrong. What rom should I be using. I also forgot to make a backup of the ROM before I installed this FTF
Use XperiFirm to download a Z1C specific FTF and flash that. This is a D5503, right? The FTF you linked is for C690x devices.
If the phone is soft bricked, the display probably won't do anything. If you mishandled the mobile (dropped, hit, whatever), it's possible you caused hardware damage.
edit: @Saluu describes the exact problem you have here: http://forum.xda-developers.com/showpost.php?p=62931738&postcount=7

Sony Xperia SP stuck on Sony logo screen, can't open recovery, flashtool also fails

Having gotten a spare Xperia SP, I decided to venture into the realm of flashing custom ROMs. This was the first time I did anything of this sort with an Android device. So, here is what I did to it today:
At first, I successfully rooted, installed recovery and flashed CM12. After fiddling with it for about an hour and not finding anything super exciting, I decided to try out other ROMs. I did a facotry reset, wiped the data and cache, and was about to flash CM11 (I forgot that it required an unlocked bootloader, which I don't have, and the recovery console told me so). Maybe at this point I should have just reflashed CM12, but I chose (not even sure why at this point) to exit recovery instead. After this, the phone keeps getting stuck on the Sony logo (although on the second attempt to turn it on, it did display a screen showing that wrench icon, indicating some sort of configuration activity going on, but never moved past that either). I tried flashing two different stock ftf roms with flashtool, both fail with this error: Processing of system.sin finished with errors. One of them will cause the phone to shut off after about a minute on the logo instead of remaining stuck on it indefinitely.
Maybe I should mention that this phone did not exactly work flawlessly for some time, even before I started experimenting with it. Here are the main things that I can remember it doing:
-Lags on even the basic functions, apps often crashing, despite doing a very recent hard reset.
-Battery drains very fast sometimes (like going from 55% to 0 in about 2 hours with almost no usage).
-A few months ago, it would periodically freeze and reboot itself, but that problem seemed to disappear with time.
Did I do something stupid to that phone, or are there internal/hardware problems that have manifested themselves in this way? I won't be horribly upset if I killed it (after all, knowing that something of this sort may happen was exactly the reason why I was not doing all this on my main phone), but I certainly would like to get it back up and running.
Download Flashtool v0.9.18.6 from official site.
Option 1: Flash stock.
or,
Option 2: Flash tangerine-7.1.elf via 'fastboot mode' to directly get TWRP, then flash any ROM you want.
https://dl.cubeserver.eu/TechnoSparks/tangerine-stuffs/tangerine-7.1.elf
nandan21 said:
Download Flashtool v0.9.18.6 from official site.
Option 1: Flash stock.
or,
Option 2: Flash tangerine-7.1.elf via 'fastboot mode' to directly get TWRP, then flash any ROM you want.
]
Click to expand...
Click to collapse
Thank you for your reply. I have a few questions:
I downloaded the flashtool version that you mentioned (from the official site), but avast detected malware in it. Should version 9.19.8, the one I tried yesterday, work fine?
What is exactly considered "stock rom"? Is it exclusively the version your phone came with, or is it firmware of any version/carrier branding, as longs as it is made for your phone model by the manufacuter?
It looks like my phone actually won't stay in flash mode. I select fastboot mode in flashtool, a window pops up asking me to plug in the phone. I press the volume down button and plug it in, the LED glows bright green, but nothing happens in flashtool. After a few seconds, the LED goes red and the Sony logo appears on the phones screen (as if it was going to turn on), and my computer makes a sound as if the phone was ejected. The phone shuts off a minute later, goes into flash mode again, and the cycle repeats.
UPDATE
Nevermind everything I wrote before, I was able to successfully re-flash stock. Turns out I did in fact have some crappy version of flashtool that didn't work, and I found anolder version without malware.
Strangely, the infected flashtool version was the one I dowloaded from the official site... Something is fishy here.
Anyways, thanks a bunch for your help!
MrDroid15 said:
Thank you for your reply. I have a few questions:
I downloaded the flashtool version that you mentioned (from the official site), but avast detected malware in it. Should version 9.19.8, the one I tried yesterday, work fine?
What is exactly considered "stock rom"? Is it exclusively the version your phone came with, or is it firmware of any version/carrier branding, as longs as it is made for your phone model by the manufacuter?
It looks like my phone actually won't stay in flash mode. I select fastboot mode in flashtool, a window pops up asking me to plug in the phone. I press the volume down button and plug it in, the LED glows bright green, but nothing happens in flashtool. After a few seconds, the LED goes red and the Sony logo appears on the phones screen (as if it was going to turn on), and my computer makes a sound as if the phone was ejected. The phone shuts off a minute later, goes into flash mode again, and the cycle repeats.
Click to expand...
Click to collapse
Use flashtool 0.9.19.8 because that is what everyone is recommending now, Stock rom defines as what it originally comes from your phone which is manufactured by sony. To get into fastboot mode turn off your phone by taking off the cover off your xperia sp and use a pin or pen to press into a small dot and you will get 3 vibrations.
This guide is not written by me, so give credit to chris10286
Step 1. Download a kernel with twrp embedded im sure I used dooms kernel as far as I remember. There are many others just do a simple google of xperia sp kernel with recovery.
Step 2 . take phone case off the back hold button in on lower bottom for 10 seconds you will get 3 vibrations . good leave it at that.
Step 4 . open flashtool let it load completely. Now plug USB into your phone also have it into your PC ! Whilst plugging in hold down volume button to enter flashmode your phone should be green . hold up for fast boot mode which is blue either too let's you flash a kernel but fast boot mode requires "elf" kernel.
Step 5. Locate kernel install and then boot phone up whilst press the volume up button as its booting recovery mode will be accessed now flash rom of your choice or use Sony PC suite to go back to stock. Make sure you have stock kernel and bootloader locked or else it won't let you..
Use this thread to help you since i had the similar problem which involved my phone: http://forum.xda-developers.com/showthread.php?p=63660062#post63660062
If none of my methods work please ask zenith to help you or ask anyone in the xperia sp forum to help you since im not a developer but ran into a similar problem to yours.
I hope this helps you out in someway as it did me good luck.
Thanks Nandan
Thank you, I very much appreciate that you took the time to write this long post to help me out. As I mentioned in an earlier post, I found a solution to my problem - by using flashtool 9.18.6 (the one that wasn't working was actually newer).

Categories

Resources