Database Develop

Please Help To Unbrick My Xperia Z!!

Hi I have a C6603... rooted and running on ExistenZ ROM 4.5
I updated to V5 (Android 4.3/.569 firmware) successfully but without SIM card. Due to my OCD, I decided after putting my SIM card in, to do a factory reset on CWM, followed by reboot.
At the "Reboot System Now" screen, CWM asks me if I wanna retain root on device. I then realized I should just flash whole V5 zip, and SuperUser fix zip then run the ROM as normal. Thus I selected "Go Back"
In this instant, the phone shut down and when reboot, it stuck at SONY logo screen and refuses to boot into anything. I used Flashtool to flash .569 and .67 kernels but both doesn't work.
I also tried PC Companion and tried to "repair" the phone but since it can't even boot the programme just says the phone isn't connected.
What should I do now? I just need to be able to enter recovery..

waterballoon said:
Hi I have a C6603... rooted and running on ExistenZ ROM 4.5
I updated to V5 (Android 4.3/.569 firmware) successfully but without SIM card. Due to my OCD, I decided after putting my SIM card in, to do a factory reset on CWM, followed by reboot.
At the "Reboot System Now" screen, CWM asks me if I wanna retain root on device. I then realized I should just flash whole V5 zip, and SuperUser fix zip then run the ROM as normal. Thus I selected "Go Back"
In this instant, the phone shut down and when reboot, it stuck at SONY logo screen and refuses to boot into anything. I used Flashtool to flash .569 and .67 kernels but both doesn't work.
I also tried PC Companion and tried to "repair" the phone but since it can't even boot the programme just says the phone isn't connected.
What should I do now? I just need to be able to enter recovery..
Click to expand...
Click to collapse
Try SUS, Sony Update Service. But I think you will loose your data, if I remember right.
Otherwise, what says flashtool If you try to flash the .67 firmware, not just the Kernel?

gripfly said:
Try SUS, Sony Update Service. But I think you will loose your data, if I remember right.
Otherwise, what says flashtool If you try to flash the .67 firmware, not just the Kernel?
Click to expand...
Click to collapse
ahhhhh didn't think of flashing firmware!! I found a rooted 4.3/.569 firmware... managed to flash it. booting into it now. thank you so much for reminder

Need help bricked phone :(

i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,

After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck

Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?

eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!

Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.

eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup

Bricked my Xperia T when flashing new ROM

EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)

NO surrender
Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)
Click to expand...
Click to collapse
When a mistake is always better to return to the " factory " ROM before trying again . I recommend using flashtool . through fastboot , put his boot.img and then a flash the stock rom
I have a TX, roms and testing step that you like . but if the PC recognizes there is hope.
I'm using the google translator . : P

Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
Click to expand...
Click to collapse
You need to flash a stock ftf.
Keep us updated on how far.

sublinker said:
You need to flash a stock ftf.
Keep us updated on how far.
Click to expand...
Click to collapse
With flashing stockrom I meant flashing stock ftf, sorry for that.

Should I throw the phone away?

Okay. I'm gonna keep it short.
Model: z3c (d5803)
Used FlashTool for mac and tried to flash a new firmware. Don't know why but things went from and the phone started to bootloop.
I managed with the help of FlashTool to get CWM working. However, when I download a ROM such as for example this one http://forum.xda-developers.com/z3-compact/development/d5803-23-2-1-62-slim-t3127115 and try to install the zip from within CWM, I don't get an error message but it doesn't seem like nothing is happening.
When I then clear the cache and reboot the phone, it just get stuck at the sony text screen.
Any help would be appreciated
Thanks

jacobsthlm said:
Okay. I'm gonna keep it short.
Model: z3c (d5803)
Used FlashTool for mac and tried to flash a new firmware. Don't know why but things went from and the phone started to bootloop.
I managed with the help of FlashTool to get CWM working. However, when I download a ROM such as for example this one http://forum.xda-developers.com/z3-compact/development/d5803-23-2-1-62-slim-t3127115 and try to install the zip from within CWM, I don't get an error message but it doesn't seem like nothing is happening.
When I then clear the cache and reboot the phone, it just get stuck at the sony text screen.
Any help would be appreciated
Thanks
Click to expand...
Click to collapse
You are struck on Sony Logo, that means your phone don't have ROM to boot up. Make a clean flash of your ROM.zip
1. Enter into recovery
2. Wipe (data+system+cache+dalvic cache)
3. Install ROM.zip
4. Wipe cache + Dalvic cache
5. Reboot
Note: .ftf could not be flashed through recovery
If something goes wrong, let me know.
Regards,
hitman-xda

Bootloop, cannot flash a new ROM

Hi everyone,
I really need help, I have tried everything I could think of and nothing works. So if someone more knowledgeable could help me, that would be great.
I followed the instructions in this thread https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
and everything went ok until I flashed a new ROM.
Current situation : Bootloop when I power up. Can still access TWRP recovery. Phone is recognized by flashtool/xperia companion/emma.
Tried to flash a new ROM with flashtool->error (can't read byte value), I tried de/re-installing flashtool and the drivers and different ROMs, always the same result
Tried to repair with xperia companion->error, can't complete
Tried emma->phone is locked
Tried sideloading ROM to flash through TWRP-> error
I don't understand how, even if I flashed a corrupted ROM, it could prevent me from flashing a new one over it?
Any ideas?
Thank you.

You can try xflasher tool as well.
https://forum.xda-developers.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634
But be warned - this is for more experienced users. I never tried it but it sounds like to be very powerfull.
For questions ask in xflasher thread... I never used it up to now...
But sometimes it helps to wipe cache/dalvik AND data from TWRP. Yes - all your data is away then!
Not nice to loose data but a bootable phone is even better...
Or flash again full ftf via flashtool. Wipe APPS_LOG/USERDATA (check boxes) but do not flash simlock.ta (if its there) !!!
This will wipe all your data as well..... While flashing, say NO to "fcs-script" popup.

. .

Thanks for the replies.
I tried different USB cable/port, no change.
I always selected to wipe everything in flashtool. I just got the phone so there was none of my data to save.
I will look at xflasher although, as you said, it looks intimidating...

. .