Hi All,
I've been a lurker on these pages for quite some time. Thank you for all the wonderful info!
I've having a lot of fun here on my own and think it's about time I invited you to the party....
I have a ZX 6603. It was on .434 when I rooted it, the bootloader has always been locked.
I never really got to know why it was only accessable thru the VM, tho' now I have ideas about that... which are irrelevant here, tho' I am mentioning it because it has always been a little bit 'quirky'.
Anyways, about an hour after rooting it (some weeks ago), I loaded a font on to it which promptly crashed it into a boot loop. Hoo ray.
PC companion was the only thing that saved it - so I move up to .253 :groan: and resign myself to flashing it backwatds to get my root, at a later date. Oh well...
From then on, it starts not wanting to know about the PC.
Unless the thing is turned off when connecting via USB, it did absolutely nothing to acknowledge the PC - not even charge the battery!
So after a bit of leaving it alone, I decided I'd had enough of this nonsense and went back to the task of flashing it back to .434 (forgive me if I got the numbers wrong here...) by flashtool.
That was this afternoon.
Ok, So flashtool had kittens and crashed the VM. From then on, it has only given 'Sony' then switched itself off. It also does that repeatedly whilst attached via USB (tapping it's foot)... It does do hard reset inasmuch as giving the three shakes without starting. It does connect by both fastboot and flashmode, which is beter than I got last time it went down.
I'd learned quite a bit in recent weeks, so I plucked up the confidence to install Flashtool into Linux.
Here, I was greeted with a crash, tho' thankfully only of the tool itself.
I began to doubt the integrity of the ftf and downloaded another.
Flashtool then gave a better performance, claiming a checksum error before giving up on the exercize (see quote below).
19/022/2013 18:22:00 - INFO - <- This level is successfully initialized
19/022/2013 18:22:00 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
19/022/2013 18:22:00 - INFO - libusb version 1.0.15
19/022/2013 18:22:06 - INFO - Device connected in flash mode
19/022/2013 18:22:10 - INFO - Device disconnected
19/022/2013 18:22:16 - INFO - Selected C6603 / 10.1.A.1.434 / UK unbranded
19/022/2013 18:22:16 - INFO - Preparing files for flashing
19/024/2013 18:24:07 - INFO - Please connect your device into flashmode.
19/024/2013 18:24:28 - INFO - Device connected in flash mode
19/024/2013 18:24:29 - INFO - Opening device for R/W
19/024/2013 18:24:34 - INFO - Device ready for R/W.
19/024/2013 18:24:34 - INFO - Reading device information
19/024/2013 18:24:34 - INFO - Unable to read from phone after having opened it.
19/024/2013 18:24:34 - INFO - trying to continue anyway
19/024/2013 18:24:34 - INFO - Start Flashing
19/024/2013 18:24:34 - INFO - Processing loader
19/024/2013 18:24:53 - INFO - Checking header
19/024/2013 18:24:54 - INFO - Ending flash session
19/024/2013 18:24:54 - ERROR - S1 Header checksum Error
19/024/2013 18:24:54 - ERROR - Error flashing. Aborted
19/024/2013 18:24:59 - INFO - Device connected in flash mode
19/025/2013 18:25:24 - INFO - Device disconnected
So I went over to the VM and kicked PC companion in the ribs to get the XZ back to life... round and round - I was starting to feel dizzy.
And now the fun begins!
PC companion goes thru it's paces, arrives at the chequered flag, claims an error and aborts. I allowed a second chance before calling it a day and deciding to write you all about how much fun I was having and wondering if anyone has a clue of where to go at it from here? Should I start mixing cement?
Regards and gratitude,
Zz
One little question, do you have all important drivers installed?(Xperia Z, Fastboot and Flash mode)
You may need to disable force driver signing.
If you need private help, you could Send me a pm and I see if i can help you.
And why didn't you leave it at newest Stock, it's rootable too.
Sent from my Dualbooted XZ
Ciapa1 said:
One little question, do you have all important drivers installed?(Xperia Z, Fastboot and Flash mode)
You may need to disable force driver signing.
If you need private help, you could Send me a pm and I see if i can help you.
And why didn't you leave it at newest Stock, it's rootable too.
Sent from my Dualbooted XZ
Click to expand...
Click to collapse
Hi and thanx for dropping by. Dualbooted XZ? Oooo! :drools:
I have installed fastboot and flashmode on the VM - yet still getting the hang of tinkering about underneath Linux' hood and have been reluctant about risking a brick on an uncertainty. I get device recognition on terminal, tho' no hint at making a connection thru the UI and thus folder tree. I have also done my best to install adb tho' I am uncertain how to confirm what's going on with that one. I did expect great things and saw none.
To save processor and memory, I run winXP on the VM thus am spared the tangles of driver signing on later releases - meh, I use Windoze only when there is no other (or painless) way to go about achieving an end result until XP is no longer uasble or I get around to making a dualboot.
I read (mid- August), they were backflashing out of .253 and I simply went with that, supported by the aforementioned misery of poor PC recognition AND (I forgot to mention this, earlier) **the fact that when it was updated via PC Companion last time, the updater crashed mid progress and stayed like that for hours***. In the end, I had to cross my fingers and pull the plug. Yes, it worked, tho' I have never felt convinced that I had a tightly running system, supported again by it's little aversion to PC connectivity.
Zz
To your FT log:
Are you sure ur ftf is not damaged?
To your main problem:
Does your phone gets recognized in Fastboot?
If yes, you can Try to unlock the BL(Warning: if you do it the official way, it will wipe all your data on the phone(data partition and SD)), flash Cyanogenmod boot.img(Kernel and Recovery are included, so it needs unlocked BL)
Then Try to wipe data, cache and dalvik cache from CWM. Now see if it boots.
If still not booting, flash a Custom Rom like Pac or "stock" CM10.1
Then it should boot.
Hope it works for you, if you're unsure, ask before doing anything. It could completely brick your device.
Sent from my Dualbooted XZ
Your suggestion sounds reasonable, thank you.
Yes, recognized in fastboot.
I will take it thru your list in order, (beginning with another ftf) and let you know how it goes, without bricking it.
Do not unlock your bootloader with a bricked phone.
I would suggest to try another pc with Windows7,use the latest flashtool,and try different firmwares.
You may also download sony update service and try.
Sent from my C6603 using xda premium
Okay.
So far all I have done is to d/l another copy of the same ftf, and a German version of the same release to produce same result with the flashtool.
Sony Updater gives an error whenever it goes thru it's motions, so this option is not available, unless the W7 PC will make a difference?
Hmmm....
Slowly slowly... treading slowly.
Any search I have put in for a flashtool checksum error comes up empty.
We're treading unknown territory here... (Lions, and tigers, and bears! oh NO!)
So every ftf gives checksum errors?
If yes, then it seems there is sth on your device.
Maybe Try a Dualbooted install of Windows 7 or 8(you can remove it after trying out everything)
Else there seems to be No way around unlocking BL(i Did it on my GF's XZ with boot problems(stuck at Sony Logo too) And got it working this way)
Hope we find a way to bring your device back to life
Sent from my Dualbooted XZ
Surprising result!
After hammering it with flashtool UK, DE and ES versions of many flavours, I threw XZ back onto PC companion for something to do whilst I was waiting for copies of W7 to arrive... and the flash took. I am now the somewhat reserved and humiliated owner of build number 10.3.1.A.0.244, praying that I have paid all of my noob dues for the time being.
Many thanks,
Zz
The even greater news is that it's going back onto charge when plugged into the PC - still not recognized by the linux UI, which is somethign more for me to learn - yet is happily recognized by the Windoze VM.
PC Companion welcomes XZ with a warm smile and the 'My Computer' file tree is fully accessable - just like it was out of the box. It may have been painful, tho' result has been worth it.
:joyful dancing:
I'm happy that your device is under the livings again. So it recognized it again in PCC? Then i can just say you Had luck or your windoze vm a bad day^^
Have fun with your reborn XZ
Sent from my Dualbooted XZ
Ciapa1 said:
I'm happy that your device is under the livings again. So it recognized it again in PCC? Then i can just say you Had luck or your windoze vm a bad day^^
Have fun with your reborn XZ
Sent from my Dualbooted XZ
Click to expand...
Click to collapse
Yes, recognized in PC, charging and all that it should. I am still not getting folder access on linux, yet yes via the VM - which is the pest that it always was, yet I'm still smiling nonetheless, counting myself lucky.
1. do not mess around your phone with vm, always use real physical machines. The vm interface may induce too many issues that may never be correctly diagnosed.
2. use the original usb cable and the usb port directly from the back panel of your computer.
3. when you are flashing your phone, do not play around with your computer before the tool finishes its job.
4. always save a copy of the tft decrypt from your pcc when you upgrade your device, this stock tft (which you produce by yourself) can save you much trouble if anything happens to your phone when you make fun with it.
5. if your computer cannot recognize your phone, then uninstall, reboot, and re-install everything on your computer. The chance of your computer messing around is much higher than your phone bootloader going wrong.
6. get use to use Flashtool when your phone is free of trouble, rather than using Flashtool for the first time when your phone is bricked.
Related
[SOLVED] !
aditional info:
- baseband_015 2.1.1.A.0.6 X8i
- bootloader unlocked
- everything ****s up when i tried (a big mistake) to flash nAa-14 (for x10)
the story:
hi, i was doing this tutorial http://forum.xda-developers.com/showthread.php?t=1350484
but, in the part where i have to flash the kernel, and the mistake whas that i have the x10 kernel, not the x8.
now, each time i want to flash using flashtool, i got this error message:
17/014/2013 23:14:19 - ERROR - C:\Flashtool;custom;root;ftkit.tar : Not found
i can't use seuz becouse i have the bootloader locked, and i can't unlock it becouse i can't flash
):!!!!, i searched a little in google, and everywhere say's that flashtool is the ultimate solution, i'm a little scared... , help plz
EDIT:
reinstalled flashtool (but this time in desktop), i got the same error
ERROR - C:\Users\lcjury\Desktop\Flashtool;custom;root;ftkit.tar Not found
so, i put the .tar file on the Desktop with this name "Flashtool;custom;root;ftkit.tar", but still without flashing, i got this output:
17/033/2013 23:33:33 - INFO - Please connect your device into flashmode.
17/033/2013 23:33:41 - INFO - Device connected with USB debugging on
17/033/2013 23:33:42 - INFO - Connected device : E15
17/033/2013 23:33:42 - INFO - Installed version of busybox : N/A
17/033/2013 23:33:42 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29.6-nAa-14 / Build number : 2.1.1.A.0.6
17/033/2013 23:33:42 - INFO - Pushing C:\Users\lcjury\Desktop\Flashtool\.\devices\E15\busybox\1.20.2\busybox to /data/local/tmp/busybox
17/033/2013 23:33:43 - INFO - Installing toolbox to device...
17/033/2013 23:33:43 - INFO - Pushing C:\Users\lcjury\Desktop\Flashtool;custom;root;ftkit.tar to /data/local/tmp
17/033/2013 23:33:43 - INFO - Running installftkit as root thru sysrun
17/033/2013 23:33:43 - INFO - Root Access Allowed
[SOLVED]!!!
it's really strange, for some reason, if i try to turn on my xperia, the green led turn on, and turn off really fast, and then the screen turn on, and then turn off... if i try to do it again, nothing happend. but if i take out the battery, and put it again i cant restart the same process... knowing that, i trie to take out the battery, put it on, and flash from there... but the first time it failed:
18/027/2013 00:27:06 - ERROR -
18/027/2013 00:27:06 - ERROR - Error flashing. Aborted
but in that moment, the green led still's on, i hope that if (i think that the green leds say's that the xperia is somekind of "directly" connected to the pc ) i trie to flash again, and it works !!!
i'm really happy...
something more...
somebody could think that i spend 1 hour trying to fix this, well.. i really spend all the day ): now i will try to put ginger again !
lcjury said:
hi, i was doing this tutorial http://forum.xda-developers.com/showthread.php?t=1350484
but, in the part where i have to flash the kernel, and the mistake whas that i have the x10 kernel, not the x8.
now, each time i want to flash using flashtool, i got this error message:
17/014/2013 23:14:19 - ERROR - C:\Flashtool;custom;root;ftkit.tar : Not found
i can't use seuz becouse i have the bootloader locked, and i can't unlock it becouse i can't flash
):!!!!, i searched a little in google, and everywhere say's that flashtool is the ultimate solution, i'm a little scared... , help plz
Click to expand...
Click to collapse
How you flashed kernel on locked bootloader
If bootloader is locked best solution is PC companion
Sent from my X8
Gogeta said:
How you flashed kernel on locked bootloader
If bootloader is locked best solution is PC companion
Sent from my X8
Click to expand...
Click to collapse
"i can't use seuz becouse i have the bootloader locked"
i forgot to say, that now, the xperia don't turn on, while i press the bottom, the screen lights turn on only for one second.
You can use PCC...it doesnt matter that you have unlocked bootlaoder
Here is a GUIDE HOW TO UNBRICK
Xperia x8 totaly dead
Hi all,
I need help in regard with Xperia x8. I tried to flash it using the latest Flashtool 0.9.13.0, in the flashtool window I had the only option x10 V1 BLRelock. I went ahead following the steps, everything seemed ok, asked to disconnect the cable and the phone not responding al all.
Lately I realised that I did not load the correct firmware/option....
I followed this tutorial but is not working for me. The phone is totally dead.
Any other option left, before throwing it?
Any help is welcome.
Emy12 said:
Hi all,
I need help in regard with Xperia x8. I tried to flash it using the latest Flashtool 0.9.13.0, in the flashtool window I had the only option x10 V1 BLRelock. I went ahead following the steps, everything seemed ok, asked to disconnect the cable and the phone not responding al all.
Lately I realised that I did not load the correct firmware/option....
I followed this tutorial but is not working for me. The phone is totally dead.
Any other option left, before throwing it?
Any help is welcome.
Click to expand...
Click to collapse
Hi, Emy12. Have you checked out the unbricking part here? If you want to, you can download the Stock ROM here (courtesy of BlackRabbit1703 through 8cpaiw) and flash it to unbrick your X8.
Red_Acid said:
Hi, Emy12. Have you checked out the unbricking part here? If you want to, you can download the Stock ROM here (courtesy of BlackRabbit1703 through 8cpaiw) and flash it to unbrick your X8.
Click to expand...
Click to collapse
Thank you for replay.
The problem is I can not power it at all, no life of it whatsoever, is totally dead, is not charging neither.
I went the a shop that deals with mobile phone stuff and they can not do anything, said that can not connect to the pc, it might be the power connector faulty, but no, is not faulty for sure. I do not think the flash tool damaged the connector socket.
It worked perfectly prior the problem.
I only did what I already stated in my previous post. I do not think there is a way to recover it.
I have to decide what I am going to do with it. I found for €20 a X8 in good working order , just the case is bad. The one I have is spotless except it stopped working. I am thinking to get it and change the board....
I will see now.
Emy12 said:
Thank you for replay.
The problem is I can not power it at all, no life of it whatsoever, is totally dead, is not charging neither.
I went the a shop that deals with mobile phone stuff and they can not do anything, said that can not connect to the pc, it might be the power connector faulty, but no, is not faulty for sure. I do not think the flash tool damaged the connector socket.
It worked perfectly prior the problem.
I only did what I already stated in my previous post. I do not think there is a way to recover it.
I have to decide what I am going to do with it. I found for €20 a X8 in good working order , just the case is bad. The one I have is spotless except it stopped working. I am thinking to get it and change the board....
I will see now.
Click to expand...
Click to collapse
The only option is to take it to Sony...
Sent from my E15i using Tapatalk 2
Gogeta said:
The only option is to take it to Sony...
Sent from my E15i using Tapatalk 2
Click to expand...
Click to collapse
Well, Sony? Will charge me a lot to fix it. I do not see how they will fix it, maybe to change the board or have other ways to do it.
I will give them a call to see how much will charge me.
I think it will be more than €20 the price for used one and swap the board.
hi all
I think I probably know the answer to this but just to make sure..
I have for a long time had gregs Assaye-V2.0.1, which was great but was starting to slow down somewhat. so for my sins I tried with CM 10(.1 i think) still not quite sure about the differences between cm10 versions, but I digress.
anyway I put cm 10.1. I tried both FXP and so called stable CM release and its been a nightmare.
GPS problems, camera problems, browser problems - basically multiple reboots daily making the phone pretty much unusable. so thinking that I would like to get back to the beginning. I would like to maintain root and retain CWM but avoid the standard bloat that comes with stock roms.
Happy to bung a custom kernel on there, not after massive speed as I don't play games, battery life and reliability are paramount for me.
I wonder if someone could recommend the best way to go about this, and possibly a FTF/Kerne/ROM to go with that recommendation.
is it worth re-locking the bootloader for instance? can you even do that and maintain root.. ? so many questions - sorry I have gotten rather out of touch.
I would stick Assaye on again but seems it hasn't moved for quite some time and not sure if there is a better option.
any help very much appreciated
just to be clear - my current situation is:
Xperia T bought from Phones 4U
rooted
unlocked bootloader
currently running CM 10.1
thanks
nat
Thanks for using my rom, I hope it worked fine for you
In order to go back to stock you MUST relock the bootloader. Or you can flash doomkernel (which is for stock roms) and before you let it boot properly go into recovery and flash a stock based rom
If you relock the bootloader your phone will bootloop on CM if you try to turn it on, don't worry, just run pccompanion and force a repair of the software.
Then your phone will be exactly the same as when you took it of the box, so you can start again..
EDIT
My rom never updated because it was always just for me, and I was happy with it, now I have a Z1 and my daughter has my T, she hates my rom ;( and insists on CM
hi greg
thanks for the reply
guess I would be happy with a stock based rom to retain root. could you recommend one - other than your own?
which as it happens I am bunging back on as i type this...
thanks
also how do I set the buttons back to the original ones..?
sur eI have asked this before but cant find the answer...
To get back to original stock then once you have locked the bootloader just run pccompanion and force a repair of you r software in software update,
To get the button back to stock just push a stock systemUI.apk to system/app or better still install xposed framework and xblast module.
I think it works on the T, try it
http://forum.xda-developers.com/showthread.php?t=1574401
then with the xblast module you gat a choice of buttons plus a load of other options as well
hi
so, I flashed the ftf re-lock bootloader.
all appeared to go well but....
I have been trying to no avail to get pc companion to run a repair.
the phone will not turn on, all I get when i hit the power is the led flashes red briefly twice, I can keep holding the power and it will keep doing a double rad flash every second or so.
when I plug into the pc - as part of the repair process - ie. holding down vol + power. I get a windows sound for connecting then another for disconnecting - I havent of course actually pulled it out at this point.
any ideas?
guessing its just not getting the green led for flashmode thus pc companion is not going to run a repair...
any other suggestions..?
thanks
edit: seems it has connected with a green led now.. however - it does not stay connected long enough for pc companion to fully download the update and i have to start all over again..
is there any way I can download the update separately and sort it that way..
Leave it on charge on your wall charger for the rest of the day, then try pccompanion later tonight
hi
thanks for the replies.
I had left it charging all last night. seems that it will only stay in flashmode for a short time, which isnt long enough to complete the flashing
the downloading part of the pc companion had completed and it was doing to pc -> phone bit, but never completes as green light goes off before it finishes..
I will leave it charging again overnight, but fear the worst.
presumably flashing a stock ftf with flashtool would achieve similar results?
will give that a go too and see how it goes..
hoping that I could run pc companion after doing that if it works?
n
xda-nat said:
hi
thanks for the replies.
I had left it charging all last night. seems that it will only stay in flashmode for a short time, which isnt long enough to complete the flashing
the downloading part of the pc companion had completed and it was doing to pc -> phone bit, but never completes as green light goes off before it finishes..
I will leave it charging again overnight, but fear the worst.
presumably flashing a stock ftf with flashtool would achieve similar results?
will give that a go too and see how it goes..
hoping that I could run pc companion after doing that if it works?
n
Click to expand...
Click to collapse
if lfashtool works then yes...but not sure what your issue is here...
finally success, managed to use flashtool to flash parts of the ftf at a time, left it charging overnight and booted up fine in the a.m.
then have just ran pc companion to get a fresh stock one on.
thing is even though I have done that, it has still kept all the random folders on the internal storage, is there any way to clear them. PC companion says it will wipe them but it doesnt seem to have done so..
thanks
nat
xda-nat said:
finally success, managed to use flashtool to flash parts of the ftf at a time, left it charging overnight and booted up fine in the a.m.
then have just ran pc companion to get a fresh stock one on.
thing is even though I have done that, it has still kept all the random folders on the internal storage, is there any way to clear them. PC companion says it will wipe them but it doesnt seem to have done so..
thanks
nat
Click to expand...
Click to collapse
Backup everything you want to save to your pc, then format internal storage in settings
Glad to hear you have it working again
Hi all. I'm quite desperate about rooting my device as I couldn't get it working in two days.
My firmware version is 12.0.A.2.254.
I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2440375
On Windows 8.1, Flashtool does not detect the device in Flash mode. The notification light goes green, but nothing happens with Flashtool.
On Windows 8, the result was just like above.
Later I read about driver signature enforcement in Windows 8 and I admit that it was not enabled, so maybe that was the problem.
On Windows XP, Flashtool says the following:
03/005/2014 01:05:24 - INFO - Processing loader.sin
03/005/2014 01:05:24 - INFO - Checking header
03/005/2014 01:05:24 - INFO - Ending flash session
03/005/2014 01:05:24 - ERROR -
03/005/2014 01:05:24 - ERROR - Error flashing. Aborted
03/005/2014 01:05:25 - ERROR - Drivers need to be installed for connected device.
03/005/2014 01:05:25 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
PC Companion and the drivers that came with Flashtool were installed in both cases.
Please share any thoughts - or, if you were able to root your device with the same firmware version, say how and on which OS! Thanks!
maxify said:
Please share any thoughts - or, if you were able to root your device with the same firmware version, say how and on which OS! Thanks!
Click to expand...
Click to collapse
Hey,
Just read DoomLords tutorial, the whole thread, I believe there are many people with the same question and it's answered.
Are you sure you installed the flash tool drivers on the XP machine? (I would use XP or win7, not win8 for this).
Also try this:
Connect your Xperia SP via USB. (Don't forget to enable USB Debugging)
Then run the Software (http://adbdriver.com/downloads/) and choose your phone, which should be listed in the list.
Ok, I did it all over again on Windows 7 and... I'm excited to have my device rooted now.
There were two attempts, the first time Flashtool again threw an error, but at the same time Windows installed some driver itself and then everything went all right.
Thanks, Robin>Hood!
maxify said:
Ok, I did it all over again on Windows 7 and... I'm excited to have my device rooted now.
There were two attempts, the first time Flashtool again threw an error, but at the same time Windows installed some driver itself and then everything went all right.
Thanks, Robin>Hood!
Click to expand...
Click to collapse
Yeah windows 8 and 8.1 gives massive problems you can do it eventually but it will take longer then just installing windows 7 on your computer!
maxify said:
Ok, I did it all over again on Windows 7 and... I'm excited to have my device rooted now.
There were two attempts, the first time Flashtool again threw an error, but at the same time Windows installed some driver itself and then everything went all right.
Thanks, Robin>Hood!
Click to expand...
Click to collapse
Glad it worked out for you! Enjoy your rooted phone and the many options of the Xposed Framework!
Or you could give Cyanogenmod a try, I use CM10.1 29.10.2013 build as it is super stable for me
Next time, don't forget to use the search option, typing the right key words will help you a lot on these fora! Enjoy
Right, to start off ive had the XZ for a while now, (was a replacement for a damaged one mid last year). My problem is i think ive bricked it, (absolutely devastated ...) i would love to hear from some more experienced users who could possibly help me in my situation.
On my memory card i have a few different roms backed up for me to restore to at my leisure, (pac rom, beanstalk rom, stock 4.3, stock 4.3 with unlocked bootloader, cyanagenmod..) i use the latest dual recovery (twrp and clockwork).
Now here is my problem and how it occured....
I was running stock 4.3, with locked bootloader, rooted.....I booted to twrp recovery, in there i had a choice of roms to restore from, without thinking i restored a backup of cyanagenmod FROM MY Girlfriends xperia z, (was digging through my laptop last week to clear things up and seen a cyanagen mod backup... thought it was from this xz so put it on my memory card... .
So now ive wrote a cyanagenmod restore point which was made on my girlfriends xperia z which was an unlocked bootloader onto my current one, which was a locked bootloader.
When it happened last night i had around 50 % battery.
The phone shows very little signs of life. when plugged into wall charger it gives a flashing red led, around every second or so.
When connected to Flashtool (latest one) it connects in flashmode, thats without pressing and holding down, (get same results if i press and hold down also.
The phone will not connect in Fastboot mode (up and plug usb in).
Holding power and up for 10, 20, 30 seconds does nothing but blink a red led at me.
It is recognized in windows (7,32bit) but will connect for a while then disconnect, then re connect then disconnect etc...
I do have full backups (made in twrp) of full stock rom, i have full backup of my T.A partition. im wondering if there is anyone on here had anything similar to this and successfully brought it back from the brink ? Only done without my phone for today and im lost without it....
here is a log of what happens in flashtool when im plugged in..... trying to flash a generic unbranded sony ftf.....
03/009/2014 19:09:34 - INFO - <- This level is successfully initialized
03/009/2014 19:09:34 - INFO - Flashtool Version 0.9.16.0 built on 19-04-2014 19:00:00
03/009/2014 19:09:46 - INFO - Checking if changes have been made to devices folder.
03/009/2014 19:09:59 - INFO - Pulling changes from github
03/010/2014 19:10:00 - INFO - Devices sync finished.
03/010/2014 19:10:05 - INFO - Device disconnected
03/010/2014 19:10:18 - INFO - Selected Bundle for Sony Xperia Z (C6603). FW release : 10.4.1.B.0.101. Customization : Generic UK
03/010/2014 19:10:18 - INFO - Preparing files for flashing
03/010/2014 19:10:35 - INFO - Device connected in flash mode
03/011/2014 19:11:25 - INFO - Please connect your device into flashmode.
03/011/2014 19:11:26 - INFO - Opening device for R/W
03/011/2014 19:11:26 - INFO - Reading device information
03/011/2014 19:11:36 - INFO - Unable to read from phone after having opened it.
03/011/2014 19:11:36 - INFO - trying to continue anyway
03/011/2014 19:11:36 - INFO - Start Flashing
03/011/2014 19:11:36 - INFO - Processing loader.sin
03/011/2014 19:11:36 - INFO - Checking header
03/011/2014 19:11:36 - ERROR - Processing of loader.sin finished with errors.
03/011/2014 19:11:36 - INFO - Ending flash session
03/011/2014 19:11:36 - ERROR - Error in processHeader : 2 : The system cannot find the file specified.
03/011/2014 19:11:36 - ERROR - Error flashing. Aborted
03/011/2014 19:11:36 - INFO - Device disconnected
03/011/2014 19:11:51 - INFO - Device connected in flash mode
03/012/2014 19:12:52 - INFO - Device disconnected
03/013/2014 19:13:01 - INFO - Device connected in flash mode
03/014/2014 19:14:02 - INFO - Device disconnected
03/014/2014 19:14:04 - INFO - Device connected in flash mode
You could try to flash a recovery..... Maybe it'll work.... As long as your pc detects it, there's a chance to get it back to life..
How ?
St.Jimmy90 said:
You could try to flash a recovery..... Maybe it'll work.... As long as your pc detects it, there's a chance to get it back to life..
Click to expand...
Click to collapse
Would you be kind enough to help me do it Sir ?
I have no clue how to do it, im a guide man.... if its written down i can follow instructions easliy...
safcscon said:
Would you be kind enough to help me do it Sir ?
I have no clue how to do it, im a guide man.... if its written down i can follow instructions easliy...
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z/general/ub-lb-xzdualrecovery-xperia-z-qa-thread-t2477769
I'm afraid though, that this one needs a working phone...
You could also try to just flash the kernel..... Use flashmode and exclude anything but the kernel....
Or you extract the stock kernel and flash it via fastboot mode...
Try unlocking your bootloader. The fact that you flashed a backup including a custom kernel while locked could be the cause of your problems.
Edit - Sorry, my bad. I didn't see that you said you cannot enter fastboot.
Question - Did you restore the TA partition from your girlfriend's phone to your phone? If so, there is nothing you can do, unfortunately.
Sent from my C6603 using Tapatalk
T A partition
kingvortex said:
Try unlocking your bootloader. The fact that you flashed a backup including a custom kernel while locked could be the cause of your problems.
Edit - Sorry, my bad. I didn't see that you said you cannot enter fastboot.
Question - Did you restore the TA partition from your girlfriend's phone to your phone? If so, there is nothing you can do, unfortunately.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Im afraid i did, when in twrp it gave me the option of what to restore, i checked all of the boxes.
So your saying theres nothing that can be done for this z now ? wonder what sony would charge for a replacement or have you any idea if sony can fix it ? sorry for all the questions, its like loosing an arm not being able to boot my phone up
Unfortunately, it's hard bricked and I'm not sure any service centre has the tools to restore it. You could just take it in and say it stopped working, I suppose. They may offer you a reduced cost replacement if you're still under warranty.
Sent from my C6603 using Tapatalk
Info
kingvortex said:
Unfortunately, it's hard bricked and I'm not sure any service centre has the tools to restore it. You could just take it in and say it stopped working, I suppose. They may offer you a reduced cost replacement if you're still under warranty.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
yer i thought so, well looks like ill have to go without for just under a full year as thats when my upgrade is due, and just my luck the years warranty finished 3 weeks ago looks like a cheapo to get me through the year. Thanks for your help.
safcscon said:
yer i thought so, well looks like ill have to go without for just under a full year as thats when my upgrade is due, and just my luck the years warranty finished 3 weeks ago looks like a cheapo to get me through the year. Thanks for your help.
Click to expand...
Click to collapse
Well don't feel sad, you didn't loose your girlfriend
The flashing red led under normal circumstances would indicate a low battery state and charging
Now i'm presuming that you've tried the soft and hard resets with the power and volume buttons to no avail
The fact that your PC will not recognize the phone would also point to this ie. low battery state
I had a similar problem meself ,but the guy who had owned the phone before me had taken the back cover off,so i disconnected the battery to try to stop this cycle of on/off
Now this dint work for me
So im im scratching me head and trying to work out the next move
So i brought for £6 of ebay a replacement battery now this fixed my problem as soon as i plugged the phone in to charge the red led went solid so it was taking the charge,when fully charged ie. greed led i pressed the power button and the phone started up in the normal way
Now i appreciate that you might not want to take off your rear cover and the battery out
So as a backup I brought one of these
http://www.ebay.co.uk/itm/4200mAh-E...lePhonesCasesPouches&var=&hash=item3f29034d76
Which when fully charged will also give you access to the USB port and maybe (hopefully)your PC so enabling you to flash it
Good luck
Oadbylad said:
The flashing red led under normal circumstances would indicate a low battery state and charging
The fact that your PC will not recognize the phone would also point to this ie. low battery state
Click to expand...
Click to collapse
I know you're trying to help, but a new battery will not fix this issue. He flashed another device's TA partition to his phone. That causes an unrecoverable hard brick. The bootloader performs checks on content in the TA when you power the device on and if it doesn't find the correct hashed keys, then it halts boot. There is no way to correct this.
Sent from my C6603 using Tapatalk
battery
kingvortex said:
I know you're trying to help, but a new battery will not fix this issue. He flashed another device's TA partition to his phone. That causes an unrecoverable hard brick. The bootloader performs checks on content in the TA when you power the device on and if it doesn't find the correct hashed keys, then it halts boot. There is no way to correct this.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Yes, im quite sure another battery would not fix this issue. I think my best and cheapest route would be to buy another xz with a smashed screen and swap the motherboards over, thanks to all who have tried to help. If only i could desolder the chip with the TA partition and hot boot it in her phone, wouldnt know which chip to do this with and if it would even work...
kingvortex said:
I know you're trying to help, but a new battery will not fix this issue. He flashed another device's TA partition to his phone. That causes an unrecoverable hard brick. The bootloader performs checks on content in the TA when you power the device on and if it doesn't find the correct hashed keys, then it halts boot. There is no way to correct this.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Surely this is the problem
By doing what he as theres no OS on the phone and thereby nothing to control the charging cycle hence the on/off cycle
and the battery is just running down and the PC won't recognize the phone
By disconnecting the battery its the biggest hard reset of all
By replacing it with an external source/or new battery hopefully the PC will acknowledge the phone and a reflash can be done
Just my take on it
Its worth a try and not as defeatist
I know for sure it worked for me
Oadbylad said:
Surely this is the problem
By doing what he as theres no OS on the phone and thereby nothing to control the charging cycle hence the on/off cycle
and the battery is just running down and the PC won't recognize the phone
By disconnecting the battery its the biggest hard reset of all
By replacing it with an external source/or new battery hopefully the PC will acknowledge the phone and a reflash can be done
Just my take on it
Its worth a try and not as defeatist
I know for sure it worked for me
Click to expand...
Click to collapse
He says that he flashed his girlfriend's TA partition onto his phone.
Flashing a TA partition from another device hard bricks your phone 100% of the time. No exceptions. There is no way back from it.
Please read up on what I'm saying before disputing it further. Thanks.
Sent from my C6603 using Tapatalk
kingvortex said:
He says that he flashed his girlfriend's TA partition onto his phone.
Flashing a TA partition from another device hard bricks your phone 100% of the time. No exceptions. There is no way back from it.
Please read up on what I'm saying before disputing it further. Thanks.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Just been raking around in my draw and came across my old Xperia Z (as in the one discussed here). I had a little google around and it seems there is a way to fix it now, I've successfully re flashed my t a partition with the backup I made with setool, (used another program called ta_gen which converted my ta backup into sin file). Still actually trying to get through all the posts to bring it back from the dead, just wondering if you have came across this info, if im missing anything and what your thoughts are ? Cheers
I was doing bunch of stuff i dont think it matters if do,tell me...Anyways my phone DEAD i cant do anything it just vibrates when u plug it in pc flashtool dont recognize it and EVEN pc companion idk what to...
Is this the end,did i just lost my phon
I had Sony z1 4.2.2 it was bootloader unlocked and rooted and last thing was cwm on and it died (((((
kefi999 said:
I was doing bunch of stuff i dont think it matters if do,tell me...Anyways my phone DEAD i cant do anything it just vibrates when u plug it in pc flashtool dont recognize it and EVEN pc companion idk what to...
Is this the end,did i just lost my phon
I had Sony z1 4.2.2 it was bootloader unlocked and rooted and last thing was cwm on and it died (((((
Click to expand...
Click to collapse
Can you enter fastboot mode?
dedei said:
Can you enter fastboot mode?
Click to expand...
Click to collapse
Nope i press volume down and then plug in cable with flashtool on just to see it doesen't work,not even notification light works WTF heres flashtool log
26/001/2014 18:01:32 - INFO - Flashtool Version 0.9.16.1 built on 06-16-2014 23:00:00
26/001/2014 18:01:32 - INFO - Executing search strategies to find proxy selector
26/001/2014 18:01:33 - INFO - No proxy found for IE. Trying next one
26/001/2014 18:01:33 - ERROR - Error parsing settingsprefs.js (The system cannot find the file specified)
26/001/2014 18:01:33 - INFO - Strategy firefox failed trying next one : java.io.FileNotFoundException: prefs.js (The system cannot find the file specified)
26/001/2014 18:01:33 - INFO - No proxy found for java. Trying next one
26/001/2014 18:01:33 - INFO - Syncing devices from github
26/001/2014 18:01:33 - INFO - Pulling changes
26/001/2014 18:01:37 - INFO - Devices sync finished.
26/001/2014 18:01:44 - INFO - Device connected with USB debugging off
26/001/2014 18:01:44 - INFO - For 2011 devices line, be sure you are not in MTP mode
26/001/2014 18:01:45 - INFO - Device disconnected
26/001/2014 18:01:53 - INFO - Device connected with USB debugging off
26/001/2014 18:01:53 - INFO - For 2011 devices line, be sure you are not in MTP mode
26/001/2014 18:01:59 - INFO - Device disconnected
Hmm weird. What exactly did you do?
dedei said:
Can you enter fastboot mode?
Click to expand...
Click to collapse
Bro it seems my screen is still on WTF ???
and i called my self and its ringing wtf is going on here ? can someone u help
Try hard resetting it (power + volume up till it vibrates 3 times) then try rebooting it.
dedei said:
Hmm weird. What exactly did you do?
Click to expand...
Click to collapse
so downgraded from 4.4.4 to 4.2 to root,i rooted phone then backed up my keys so i dont lose them when i unlock boot loader then i used pcc to update to 4.4.4 so i can unlock bootloader then i lost root and then downgraded again so i can root i rooted my phone and then used v3 kernel from doom to instal cwm,i didnt know how to open that .bin file so i flashed it and it worked i got into cwm and then just reobted it asked me if i want sth about to back last kernel idk i said no and then it reboted and i turend it on once and boom black sscreen of death
dedei said:
try hard resetting it (power + volume up till it vibrates 3 times) then try rebooting it.
Click to expand...
Click to collapse
its aliveeeeeeeee ty man
kefi999 said:
its aliveeeeeeeee ty man
Click to expand...
Click to collapse
Glad to help!
@kefi999
After following your posts about this today in the several threads you have been posting in I want to give you some very useful advice
STOP
Read the guides and tutorial threads, especially the newer ones. You seem to be randomly flashing stuff with out any real understanding and that is the quickest way to end up with a hardbrick.
Take some to time to understand what you are doing, then you will see that what you have been doing is superfluous e.g downgrading to root, its not needed anymore
Please do not try and do this blindly, take some time and learn. It was the best bit of advice given to me and I hope you take it on board as well
u are 100% right i am sry for spaming all over the place i just freaked out SRY
kefi999 said:
u are 100% right i am sry for spaming all over the place i just freaked out SRY
Click to expand...
Click to collapse
You don't have to be sorry, he's not saying anything about spamming in here. Xda is the place to be and to get help regarding android. His point is that you should try to learn and understand what are you doing with your phone because if you do something wrong when you're rushing like this then it's a straight way to actually kill your phone.
He just wants you to learn instead of rushing so you wouldn't do any harm to your device.
Quick example of how can u kill your phone:
Flash ftf file from Z ultra to Z1. Phone is most propably dead.
Just don't rush and try to learn what actually are you doing and you'll be fine.
hahaha