[Q] Help...My phone is totally bricked

[TunNaing]

I recently flash custom rom from http://forum.xda-developers.com/showthread.php?t=2463675 step by step.
after that my phone turn off and won't turn on, i tried on hard reset button, power + vol up key and cannot enter flash mode.
is there any way to solve..please help..

 

[ffp.]

Try flash stock ftf. To enter flashmode you must plug USB cable and press volume down+power. The LED will blink red then green. You're in a boot loop or your phone doesnt even shows anything?

 

[Just2Cause]

Try flash stock ftf. To enter flashmode you must plug USB cable and press volume down+power. The LED will blink red then green. You're in a boot loop or your phone doesnt even shows anything?

....cannot enter flash mode.
....

Obviously he can't go to flash mode...

 

[TagEHeuer]

Power button and volume up x3? Should feel the phone vibrate.

When you connect it to your PC, does it stay connected? If so, you can do a reset with PCcompanion.

 

[ffp.]

Flashmode is power button and volume DOWN, not volume up. He may be doing wrong...

 

[TagEHeuer]

Flashmode is power button and volume DOWN, not volume up. He may be doing wrong...

Wasn't giving him the commands to Flashmode, just wanted to see after doing that if his phone would reboot. :good:

 

[kiumoneoh]

same here, the phone wouldn't respond to the red hard reset, flash mode, or power + 3x vol up.

Any thoughts?

 

[wsdy0001]

same as you ， thanks monx®。I waist about US$ 130 to change my c6903's motherbroad. This is my first time bricked an android phone , and have to repair hardware. I had try every thing i can do，even open the phone and charge the battery manually. sorry for my pool english，i'm in P.R.C.

 

[TunNaing]

thanks for helps and suggestion

i already tried flashmode, fastbootmode, the phone doesn't respond anything and doesn't even charge with wall charger.
Now i have to look for new phone and wait for a solution..

 

[olokos]

I flashed his rom and it works great. YOU and only YOU did something wrong. You can't blame anyone for your mistakes.

Try to hold power and volume up not like some of you said 3xvolume up. Then it should vibrate 3 times... Then you should try holding down volume down and plugging in a USB cable while holding vol down. It should go into flash mode.
If that doesn't work then try pressing small Square with off writing under the right flap and then try to boot into flash mode the same way with vol down.
If this doesn't work then your phone truly is bricked.
It might have happened because you could flash for example C6903 on a C6943 phone. I think that this is exactly what you did by blindly following the steps without actually reading the entire thread.

Have a good day.

Wysłane z mojego C6903 przy użyciu Tapatalka

 

[TunNaing]

Yes it may be, mine was on ihackers v2.0 rom and it's run great.
After that i flashed this rom and it's in boot loop and again i flashed it to stock .534 and rooted with vroot and flash with cwm recovery.
After flashing second time it turn off and never come back.
I don't blame on anyone, I did blame on my self may be i did the wrong steps on flashing.

 

[Rekoil]

I doubt the issue is related to monx's ROM, too many others have had 4.3 related issues with symptoms identical to yours for it to be a coincidence. I reckon there is something seriously wrong with the 4.3 release (likely related to battery) which is presenting with these symptoms on some peoples devices. I'd try to get it repaired from Sony before replacing motherboards out of your own pocket. Most likely they are not even gonna check what ROM is on the mainboard since seemingly they are unable to access it themselves, and if they can, then they can repair it and wont charge you $300.

 

[Just2Cause]

Yeah, going to Sony service center is a must before trying anything related to opening the device and change some parts.

Here in MEA, I asked someone from Sony service center if rooting voids my warranty, he said no. So I asked about unlocking bootloader and he said "Even if you change the OS your warranty won't be void". :silly:

I really doubt that he knows what he's talking about :silly:, but it's good to take it to service center as long as it's still under warranty.


Regards,
~J2C

 

[wsdy0001]

LOCKED BOOTLOADER

BACKUP any critical data to microSD
Copy this rom zip package to microSD
Flash stock Sony's firmware (FTF) 14.1.G.1.534 using flashtools if u r not currently running on this fw version
Root using any available method (VROOT recommended)
Install ONLY THIS recovery (TWRP) unpack & read readme.txt for instructions | check for superuser prompt (if any) [vroot is using its own supersuser app]
Reboot in recovery, do factory reset & install rom until finish
Skip (x) steps if u already running same base firmware with latest monxDIFIED base rom. Else, proceed.
(x) Turn off device. (Hold power button + vol up until vibrates 3 times) [or use recovery turn off device option, if any]
(x) Flash latest Sony's firmware (FTF) matching current latest monxDIFIED base rom using latest flashtools. UNCHECK all WIPE options and CHECK all EXCLUDE options except KERNEL & BASEBAND to get latest matched kernel & baseband.
(x) for upgrading from Android 4.2.2 to 4.3 UNCKECK all WIPE options and CHECK only SYSTEM & TA in EXCLUDE options
（This is a new step added by him later. I didn't do this）
(x) Turn on phone. Done.


========================================

I did all the action, and then the phone completely bricked

I use Android phones for three years, flash ROM for numerous times,and never needed repairs.

Buy this phone it took me a month's salary, now you can understand why I so angry?

My phone does not warranty. I had to spend about $ 130 to replace the motherboard.

If i can go to SONY sale , it might takes me about 2,000 yuan, about $ 300.

I endured the pain, spent a week looking for solutions, but no effect, or even open the phone and re-plug the battery, do not work.

YES! He does not work for me, I did not pay him money, but he produced a ROM without examination BUG carefully,

there are so many people's Z1 scrapped, we can not complain about it?

 

[wsdy0001]

Have you try to flash it down? or Reset your mobile?

I searched all similar cases, about LT28 and Google nexus4, or even completely identical performance failures, still can not fix my phone.

Also, I was an electronic product development engineer, I was able to skillfully operate Android phones, know how to update the ROM / Recovery / Kernel / unlock and lock Bootloader, or even modify apk files by myself. After the phone into a brick, I've tried all the known way to repair.

Finally, I open the phone, charging the battery, and then the phone absolutely no response. No flashing red light when charging. At least now you know, open the back cover can not be repaired. Hurry to the maintenance department, there is no other way, at least I think so.

 

[jamespmi]

FYI
http://forum.xda-developers.com/showthread.php?t=2588979

For the ones having a "bricked" phone.
I post this link because I'm still convinced your device isn't bricked. It just changes it's state so Windows doesn't recognize the device well on faulty driver installations and isn't able to detect the Fastboot mode... This is a new approach of facilitating the installation of those drivers...

 

[wsdy0001]

FYI
http://forum.xda-developers.com/showthread.php?t=2588979

For the ones having a "bricked" phone.
I post this link because I'm still convinced your device isn't bricked. It just changes it's state so Windows doesn't recognize the device well on faulty driver installations and isn't able to detect the Fastboot mode... This is a new approach of facilitating the installation of those drivers...

Flashtool's LOGS

29/058/2013 17:58:44 - INFO - Connected device (Device Id):
29/058/2013 17:58:45 - INFO - USB \ VID_0FCE & PID_D19A \ 6 & 4817B6D & 0 & 4 Driver installed: true
29/058/2013 17:58:45 - INFO - HID \ VID_0FCE & PID_D19A \ 7 & 195E558B & 0 & 0000 Driver installed: true
29/058/2013 17:58:45 - INFO - ADB mode device list:
29/058/2013 17:58:45 - INFO - None
29/058/2013 17:58:45 - INFO - fastboot mode device list:
29/058/2013 17:58:45 - INFO - None
29/059/2013 17:59:27 - INFO - Device disconnected



After flashing the ROM, the phone does not have any reaction, whether you press any key or key combination.

No blue light mode or green light mode, the screen never turns on. Etc.

After the battery is depleted, plug in the charger, the red light will blink once a second.

If you use the IPAD charger to charge, the red light will stay on for about 20 minutes, then turn off.

After plugging the computer will recognize the USB input device.

Flashtool Report: device is connected but not open USB debugging mode.

That's all phenomenon.

After re-plug the charged battery, Windows no longer has any reaction


========================

My English is not very good, I can only use Google translation software to respond, I hope you can understand. After all, machine translation sucks. Either Chinese or English translation.

I hope I have helped you.

 

[jamespmi]

Flashtool's LOGS

29/058/2013 17:58:44 - INFO - Connected device (Device Id):
29/058/2013 17:58:45 - INFO - USB \ VID_0FCE & PID_D19A \ 6 & 4817B6D & 0 & 4 Driver installed: true
29/058/2013 17:58:45 - INFO - HID \ VID_0FCE & PID_D19A \ 7 & 195E558B & 0 & 0000 Driver installed: true
29/058/2013 17:58:45 - INFO - ADB mode device list:
29/058/2013 17:58:45 - INFO - None
29/058/2013 17:58:45 - INFO - fastboot mode device list:
29/058/2013 17:58:45 - INFO - None
29/059/2013 17:59:27 - INFO - Device disconnected



After flashing the ROM, the phone does not have any reaction, whether you press any key or key combination.

No blue light mode or green light mode, the screen never turns on. Etc.

After the battery is depleted, plug in the charger, the red light will blink once a second.

If you use the IPAD charger to charge, the red light will stay on for about 20 minutes, then turn off.

After plugging the computer will recognize the USB input device.

Flashtool Report: device is connected but not open USB debugging mode.

That's all phenomenon.

After re-plug the charged battery, Windows no longer has any reaction


========================

My English is not very good, I can only use Google translation software to respond, I hope you can understand. After all, machine translation sucks. Either Chinese or English translation.

I hope I have helped you.

I understood you perfectly. It was just for your information as Windows ADB installation is quite a headache...

If your phone isn't entering Fastboot there has still to be a possibility to get Sony SUS Recovery working. But the Windows ADB drivers have to tell the proper state and this is not always guaranteed even you think you have the right ones installed as it worked before on other flash attempts. Similar stories happened to Xperias Tablets with the PureDriver STS R5A ADB driver...
Folks having problems with their bricked phone have two possibilities: give it a try or staring at a bricked phone.

29/058/2013 17:58:45 - INFO - ADB mode device list:
29/058/2013 17:58:45 - INFO - None <--- NOT RECOGNIZED
29/058/2013 17:58:45 - INFO - fastboot mode device list:
29/058/2013 17:58:45 - INFO - None <--- NOT RECOGNIZED
29/059/2013 17:59:27 - INFO - Device disconnected

 

[xasbo]

i already tried flashmode, fastbootmode, the phone doesn't respond anything and doesn't even charge with wall charger.
Now i have to look for new phone and wait for a solution..

It sounds like you killed the battery while flashing, not the phone entirely. It may be possible to either replace the battery or bring it back to life by forcing it to charge. This may also be the same problem @wsdy0001 is having, but he has complicated the matter by trying many things, so I'm not sure.

I don't know the specifications for this battery, so I cannot tell you how to charge it manually.

 

[Meni30]

LOCKED BOOTLOADER

BACKUP any critical data to microSD
Copy this rom zip package to microSD
Flash stock Sony's firmware (FTF) 14.1.G.1.534 using flashtools if u r not currently running on this fw version
Root using any available method (VROOT recommended)
Install ONLY THIS recovery (TWRP) unpack & read readme.txt for instructions | check for superuser prompt (if any) [vroot is using its own supersuser app]
Reboot in recovery, do factory reset & install rom until finish
Skip (x) steps if u already running same base firmware with latest monxDIFIED base rom. Else, proceed.
(x) Turn off device. (Hold power button + vol up until vibrates 3 times) [or use recovery turn off device option, if any]
(x) Flash latest Sony's firmware (FTF) matching current latest monxDIFIED base rom using latest flashtools. UNCHECK all WIPE options and CHECK all EXCLUDE options except KERNEL & BASEBAND to get latest matched kernel & baseband.
(x) for upgrading from Android 4.2.2 to 4.3 UNCKECK all WIPE options and CHECK only SYSTEM & TA in EXCLUDE options
（This is a new step added by him later. I didn't do this）
(x) Turn on phone. Done.


========================================

I did all the action, and then the phone completely bricked

I use Android phones for three years, flash ROM for numerous times,and never needed repairs.

Buy this phone it took me a month's salary, now you can understand why I so angry?

My phone does not warranty. I had to spend about $ 130 to replace the motherboard.

If i can go to SONY sale , it might takes me about 2,000 yuan, about $ 300.

I endured the pain, spent a week looking for solutions, but no effect, or even open the phone and re-plug the battery, do not work.

YES! He does not work for me, I did not pay him money, but he produced a ROM without examination BUG carefully,

there are so many people's Z1 scrapped, we can not complain about it?

Where did u bought the motherboard can u tell me please because i need it too for mine ?