Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,739,156 Members 46,462 Now Online
XDA Developers Android and Mobile Development Forum
View Poll Results: What is the bricked phone model and bootloader status?
C6902 bootloader unlock not allowed 5 1.90%
C6902 bootloader unlock allowed/not unlocked 20 7.60%
C6902 bootloader unlocked 21 7.98%
C6903 bootloader unlock not allowed 28 10.65%
C6903 bootloader unlock allowed/not unlocked 75 28.52%
C6903 bootloader unlocked 65 24.71%
C6906 bootloader unlock not allowed 29 11.03%
C6906 bootloader unlock allowed/not unlocked 8 3.04%
C6906 bootloader unlocked 2 0.76%
C6943 bootloader unlock not allowed 0 0%
C6943 bootloader unlock allowed/not unlocked 8 3.04%
C6943 bootloader unlocked 2 0.76%
Voters: 263. You may not vote on this poll

[WARNING!] [FIX!] [BRICKFEST CLUB] How to NOT Hard Brick your Xperia Z1!

Tip us?
 
zeppelinrox
Old
(Last edited by zeppelinrox; 13th February 2014 at 01:46 AM.)
#1  
zeppelinrox's Avatar
Senior Member - OP
Thanks Meter 21072
Posts: 9,312
Join Date: Dec 2010
Location: IN THE FREAKIN' OP

 
DONATE TO ME
Exclamation [WARNING!] [FIX!] [BRICKFEST CLUB] How to NOT Hard Brick your Xperia Z1!

UPDATE: THERE IS NOW A HARD BRICK FIX!!
Thanks to @the_laser and @vovanx500

To PREVENT a Hard Brick, READ THIS ENTIRE POST!

Take part in the poll ONLY if your phone cannot be revived
ie. Pressing Volume Up + Power does NOT work and you can't get into flashmode. (If that works, it's not a hard brick)


It's NOT a hard brick if you can get into flash mode.
It's NOT a hard brick if you see the Sony logo.
It's NOT a hard brick if you see ANY life on the screen.
It's NOT a hard brick if you get a led colour that isn't red.

And if it's NOT a hardbrick go HERE to fix it.
Or just flash an ftf from HERE and wipe all / exclude nothing ie. Go with Flashtool's default settings.

But if it's really hard bricked and if took part in the poll... join the club...



...The Brickfest Club

WARNINGS!

Warning 1. Use LATEST Flashtool! (v0.9.11 is DANGEROUS when flashing 4.3 ROMS)
Warning 2. When updating from a 4.2.2 ROM (*534 or *257 ftfs) to 4.3 (*290/*136 ftf), in Flashtool, DO NOT flash only the kernel and baseband from your chosen 290/136 ftf (the last step).

Flash EVERYTHING EXCEPT SYSTEM!


Read this post in which I elaborate as to why.
Basically, there's a 4.3 (290/136 ftf) kernel incompatibility with some aspects of 4.2.2 (534 and 257 ftfs).
I strongly suspect a mismatching ELABEL or BOOTBUNDLE to be the reason in most bricks. MOST likely it's the BOOTBUNDLE.
There's also some funny business regarding the battery level being misread.

So always be sure, when flashing parts of a 290 or 136 ftf, you flash, at the very least:
KERNEL, ELABEL, BOOTBUNDLE, AND BASEBAND so that there is no risk of a mismatch.
Let's refer to it as the KEBB group. Easy to remember :P
Quote:
How to update from 4.2.2 ROMs (534 or 257 ftf base) to 4.3 ROMs (290 or 136 ftf base)
Quote:
1. Go to recovery and do a factory reset.
2. Flash the 4.3 ROM
3. (Optional). Reflash recovery just in case it got wiped from step 2.
4. Using the LATEST Flashtool, select a 290/136 ftf to flash.
5. In the last box, ONLY EXCLUDE SYSTEM (ie. select only SYSTEM and leave all other boxes unchecked. In this area, items with NO checkmark get flashed.)
Hopefully, the above mini guide will reduce the brick frequency
OK so it seems there is alot of bricking going on lately so I don't feel super retarded anymore.
And it seems to happen even when the user does everything right.

So I think it would be a good idea to try and figure out a pattern to it and determine how and why it happens.

So if you got bricked, post the pertinent details

Here's mine:

Phone model - C6906
Method used - FlashTool version - 0.9.13.0
FTF file used - C6906_14.2.A.0.290_Generic CA.ftf
Battery Level - Quite full. Over 80% for sure.
How it got bricked - Flashed the Canadian Generic 290 kernel on a Canadian stock rooted 534.

================
Original OP below
================

So I was experimenting with getting 4.3 rooted or at least have the latest bells and whistles on a properly rooted rom.

I thought that I'd try mixing and matching things maybe flash a new 4.3 stock rom, do a backup, flash a 534 and root it and restore 4.3 apps.

Not the best idea but I figure no big deal if it didn't work since I can just flash a stock ftf, right?

So I was tired... and I carelessly flashed a 4.3 stock kernel on a rooted 534.

I unplugged the phone and it's totally dead.
Doesn't power on, no lights, can't get back into flash mode.
Power + volume up = nothing. No vibration.
Tried the red hard reset button... still nothing.

The phone was pretty much fully charged at the time but leaving it plugged into a wall charger to see if anything good happens.

edit: after leaving it plugged into a wall charger for about 24 hrs, the red light started blinking but no matter what I do, I can't get into flashmode.
The Following 24 Users Say Thank You to zeppelinrox For This Useful Post: [ Click to Expand ]
 
dancress
Old
(Last edited by dancress; 18th December 2013 at 07:03 AM.)
#2  
Member
Thanks Meter 5
Posts: 38
Join Date: Jun 2010
Quote:
Originally Posted by zeppelinrox View Post
So I was experimenting with getting 4.3 rooted or at least have the latest bells and whistles on a properly rooted rom.

I thought that I'd try mixing and matching things maybe flash a new 4.3 stock rom, do a backup, flash a 534 and root it and restore 4.3 apps.

Not the best idea but I figure no big deal if it didn't work since I can just flash a stock ftf, right?

So I was tired... and I carelessly flashed a 4.3 stock kernel on a rooted 534.

I unplugged the phone and it's totally dead.
Doesn't power on, no lights, can't get back into flash mode.
Power + volume up = nothing. No vibration.
Tried the red hard reset button... still nothing.

The phone was pretty much fully charged at the time.

Of course I googled "xperia hard brick" but most results are not really about hard bricks

I hope somebody with more experience with xperia's has any ideas...
I just kinda did a similar thing to my Tablet Z. I was able to revive it with a neat trick I was pointed to on this forum. It goes like this:

- Press Power + Volume up for a few seconds (8 I think). This should hard reset it. I don't know about the Z1 but on other Xperias you'll get a visual cue, like the LED blinking three times in a row or something.
- Charge it for an hour. Don't touch. Brick operations are bad on the battery.
- Try turning it on (Flash/Fastboot Mode ie. Volume down or up + connecting it to USB)
- Once you're in you are set for for a rescue operation using Flashtool or PC Companion. Z1 doesn't need to boot fully for those to work. You'll find a zillion tutorials on how to use those tools right here.

Saved my XTZ since I had flashed a corrupted recovery.
 
n0bleINtP
Old
#3  
n0bleINtP's Avatar
Member
Thanks Meter 18
Posts: 33
Join Date: Sep 2013
Location: Perth AU
I think I did a similar thing to a Z Ultra. Flashed generic EU stock 4.3 firmware (14.2.A.0.290), FTF image with flashtool, and it is really dead. Like yours no response to anything: hard reset via red button or Power+Up Vol, no response or connection via USB to fastboot or flash mode, no charge light, no lights of any kind, no buzz, no vibration, no heat or warmth when on the charger. Phone was nearly fully charged prior.

Assume TA got borked somehow but don't really know how. Flashtool lets you do some pretty dumb things - but always you can get into fastboot and fix it. I don't expect a resolution - pretty sure it is dead. Stuff happens.
The Following User Says Thank You to n0bleINtP For This Useful Post: [ Click to Expand ]
 
zeppelinrox
Old
(Last edited by zeppelinrox; 18th December 2013 at 03:07 PM.)
#4  
zeppelinrox's Avatar
Senior Member - OP
Thanks Meter 21072
Posts: 9,312
Join Date: Dec 2010
Location: IN THE FREAKIN' OP

 
DONATE TO ME
Yeah I think the mismatched kernel thinks that the battery is dead so nothing happens.
I'm leaving it plugged into a wall charger tho and see if the red led eventually turns on.

Oh I hadn't seen this thread before.
I'm not the only one.
http://forum.xda-developers.com/show....php?t=2572515
The Following 2 Users Say Thank You to zeppelinrox For This Useful Post: [ Click to Expand ]
 
n0bleINtP
Old
#5  
n0bleINtP's Avatar
Member
Thanks Meter 18
Posts: 33
Join Date: Sep 2013
Location: Perth AU
Quote:
Originally Posted by zeppelinrox View Post
Oh I hadn't seen this thread before.
I'm not the only one.
http://forum.xda-developers.com/show....php?t=2572515
Thank you for the heads up on that thread - seems to be the same issue. I'll connect USB port to the charger overnight and pray. There may be some hope after all.
 
zeppelinrox
Old
#6  
zeppelinrox's Avatar
Senior Member - OP
Thanks Meter 21072
Posts: 9,312
Join Date: Dec 2010
Location: IN THE FREAKIN' OP

 
DONATE TO ME
Instead of opening a new thread, I decided to used this one.
Please read the revised OP and post if you got bricked and take part in the poll.
 
dft601
Old
#7  
dft601's Avatar
Member
Thanks Meter 7
Posts: 71
Join Date: Feb 2005
Location: Stuttgart
Here's mine:

Phone model - C6903
Method used - FlashTool version - 0.9.13.0
FTF file used - C6903_14.2.A.0.290_Customized NCB 1276-9897 (Nordic Combined).ftf
Battery Level - Over 70% .

How it got bricked - Flashed HONAMI_430_290_MONX_030000b_REL.zip
Than flashed above mentioned FTF file ONLY Baseband and Kernel as far as I remember... Did it step by step from an explanation
The Following 2 Users Say Thank You to dft601 For This Useful Post: [ Click to Expand ]
 
VyZard
Old
#8  
Member
Thanks Meter 4
Posts: 31
Join Date: Dec 2013
Phone model - C6903
Method used - FlashTool version - 0.9.13.0
FTF file used - 14.2.A.0.290 Generic NCB (Unbranded/Nordic)
Battery Level - 75%
How it got bricked - flashed monx's rom, then this ftf, only kernel and baseband...

I don't know if the blinking red light is a sign of life but nothing seems to work.Your guess?
And I have a question, since rooting voids warranty, if my phone is bricked, will they get me a new one? Cause since it's bricked they cant tell?
The Following 2 Users Say Thank You to VyZard For This Useful Post: [ Click to Expand ]
 
8geek
Old
#9  
Member
Thanks Meter 20
Posts: 71
Join Date: Mar 2013
Phone model - C6903
Method used - FlashTool version - 0.9.13.0
FTF file used - A Stripped_C6903_.290.ftf
Battery Level - 70% at the very least.
How it got bricked - was on my backed up .257 rooted (or was it .534, but rooted still). Attempted to update to .290 via flashing (via recovery). Flashed the stripped FTF for matching kernel/baseband. BAM.
 
Poesini
Old
#10  
Senior Member
Thanks Meter 54
Posts: 374
Join Date: Apr 2012
Location: Cali

 
DONATE TO ME
Phone model - C6906
Method used - FlashTool version - 0.9.13.0
FTF file used - C6906_14.2.A.0.290_Generic CA.ftf
Battery Level - Around 70%.
How it got bricked - Flashed a C6906 kernel after flashing a modded stock ROM 4.3 (RomAur if i think which is C6903)

Had to return for warranty... Getting a new one in 3 days or so

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes