Database Users

X10's bricked so far...

Just wanting to start a count of how many X10's die from this rooting frenzy. Mine survives so 0 so far....

Pointless post!

Would be hard to brick with this root process unless you stupidly close cmd window or pull power/usb out while its doing its thing

I accidentally pulled the usb cable during step one, it gave me that exclamation mark when I tried turning it on, so I started over, and root worked fine, so afaik, its impossible to brick lol
Sent from my X10i using Tapatalk

There's a lot of people here (myself included) who have little to no experience with Android. So this thread might be a good idea to have to serve as a caution to less experienced users on the missteps of others.
Just my two cents...

You can't brick it with this type of root
Sent from my X10i using XDA App

MarylandCookie said:
Pointless post!
Click to expand...
Click to collapse
^^^ What he said

Its almost impossible to brick x10, unless you really want it and know what you are doing

feis said:
Its almost impossible to brick x10, unless you really want it and know what you are doing
Click to expand...
Click to collapse
Now that sounds like a challenge

I've bricked mine at least 4 times doing stupid things and not following instructions. But the flash tool or PC companion fixed it.
Bottom line: FOLLOW THE INSTRUCTIONS and search for an answer if you hit a wall.
PS, I'm not a dev and this is my first android phone
Sent from my SO-01B using XDA App

great news!
se = great hardware maker but crap software dreamer...

gavriel18 said:
I've bricked mine at least 4 times doing stupid things and not following instructions. But the flash tool or PC companion fixed it.
Bottom line: FOLLOW THE INSTRUCTIONS and search for an answer if you hit a wall.
PS, I'm not a dev and this is my first android phone
Sent from my SO-01B using XDA App
Click to expand...
Click to collapse
When you brick it, it becomes a brick. It's not recoverable any more and it's a paper weight. You can't really brick it more than once unless you have 4 x10's.
You can goof it up and it's easily fixed, as you mentioned by following the directions closely

I don't think it possible to brick the X10
bootloader is still there in case something turn wrong
someone to please confirm if what I'm saying is true or false

gavriel18 said:
I've bricked mine at least 4 times doing stupid things and not following instructions. But the flash tool or PC companion fixed it.
Bottom line: FOLLOW THE INSTRUCTIONS and search for an answer if you hit a wall.
PS, I'm not a dev and this is my first android phone
Sent from my SO-01B using XDA App
Click to expand...
Click to collapse
it's not a brick if you can fix it..
I think the only way you could "brick" it is if you rip out the battery while flashing the bootloader. Then you're screwed.

is my unbrickable? wait for solution...
In my case, I couldnt manage to update my X10i to flash OS or anything.
Actually, my Phone was "Bricked" while when I was updated by SEUS, the processing was stucked at about 25%, and it prompt "...lost connection...error occur..." then, i restart phone, only red led blinks every 2-3 sec. I realize it perhaps problem with battery, then i charge the battery overnight, and it was full charged. Now, when i turn it on, it shows green blink and a little vibration... and that is it, no any sign of booting...after try tens of time repairing, reinstalling through the SEUS and PC Comp. None of them worked...
I found your tools and guide on google, then download everything that needed for flash tool, I have latest JRE, PCC, SEUS installed, some stock ROM, Custom ROM.. downloaded. Also i did try to flash ROM of Ver. 1.6, 2.1, 2.2, 2.3. None got through the whole process, it all got stucked right after FLASHING LOADER...here is my log.
14/037/2011 01:37:12 - INFO - <- This level is successfully initialized
14/037/2011 01:37:49 - INFO - Preparing files for flashing
14/038/2011 01:38:34 - INFO - Searching Xperia....
14/038/2011 01:38:34 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&20A947A6&0&5
14/038/2011 01:38:34 - INFO - Start Flashing
14/038/2011 01:38:34 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
14/038/2011 01:38:34 - INFO - Flashing loader
14/039/2011 01:39:40 - INFO -
14/044/2011 01:44:02 - INFO - Flashing kernel.sin
14/045/2011 01:45:17 - ERROR - Error flashing. Aborted
14/045/2011 01:45:17 - INFO - Now unplug the device and power it on
14/045/2011 01:45:17 - INFO - Then go to application settings
14/045/2011 01:45:17 - INFO - turn on Unknown Sources and Debugging
I saw some video on youtube, they only use 4-5min to flash a new OS, but in my case it took my 5mins to flash a loader.sin (<10k.) it must be something wrong with my PC's config or Handset's hardware??? Could you give a hand on this, try to figure out what is causes for my X10i? I was totally pissed off these days. Using backup phone for a week, and lost all the contacts info on my phone...

IMHO, I don't think it is possible to actually brick the phone... Not yet anyways.
I have a feeling that the main boot process is governed by the bootloader itself (no bootloader - no boot) . When that gets cracked/released I think we will start to see actual brick's at that point. Until then I don't think it is possible.

kwonada said:
In my case, I couldnt manage to update my X10i to flash OS or anything.
Actually, my Phone was "Bricked" while when I was updated by SEUS, the processing was stucked at about 25%, and it prompt "...lost connection...error occur..." then, i restart phone, only red led blinks every 2-3 sec. I realize it perhaps problem with battery, then i charge the battery overnight, and it was full charged. Now, when i turn it on, it shows green blink and a little vibration... and that is it, no any sign of booting...after try tens of time repairing, reinstalling through the SEUS and PC Comp. None of them worked...
I found your tools and guide on google, then download everything that needed for flash tool, I have latest JRE, PCC, SEUS installed, some stock ROM, Custom ROM.. downloaded. Also i did try to flash ROM of Ver. 1.6, 2.1, 2.2, 2.3. None got through the whole process, it all got stucked right after FLASHING LOADER...here is my log.
14/037/2011 01:37:12 - INFO - <- This level is successfully initialized
14/037/2011 01:37:49 - INFO - Preparing files for flashing
14/038/2011 01:38:34 - INFO - Searching Xperia....
14/038/2011 01:38:34 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&20A947A6&0&5
14/038/2011 01:38:34 - INFO - Start Flashing
14/038/2011 01:38:34 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
14/038/2011 01:38:34 - INFO - Flashing loader
14/039/2011 01:39:40 - INFO -
14/044/2011 01:44:02 - INFO - Flashing kernel.sin
14/045/2011 01:45:17 - ERROR - Error flashing. Aborted
14/045/2011 01:45:17 - INFO - Now unplug the device and power it on
14/045/2011 01:45:17 - INFO - Then go to application settings
14/045/2011 01:45:17 - INFO - turn on Unknown Sources and Debugging
I saw some video on youtube, they only use 4-5min to flash a new OS, but in my case it took my 5mins to flash a loader.sin (<10k.) it must be something wrong with my PC's config or Handset's hardware??? Could you give a hand on this, try to figure out what is causes for my X10i? I was totally pissed off these days. Using backup phone for a week, and lost all the contacts info on my phone...
Click to expand...
Click to collapse
Interesting... From what I can tell it flashed the bootloader just fine (according to the log it only took just over a minute), but the kernel is failing to upload to the phone.
I'm not sure what would cause that. bad USB cable/connection? If possible try flashing it from a different computer to see if there is a difference.

Carlo_WPG said:
Interesting... From what I can tell it flashed the bootloader just fine (according to the log it only took just over a minute), but the kernel is failing to upload to the phone.
I'm not sure what would cause that. bad USB cable/connection? If possible try flashing it from a different computer to see if there is a difference.
Click to expand...
Click to collapse
Had this issue once, I think it was a power issue, pull the battery, hold the back button with the USB cable already plugged in put the battery back in.
Think that was the only problem.

Xperia E4 Dual bootloop

Hello, I've tried posting my problem elsewhere on xda without response so I'll give it a try in here. My phone shows the sony logo then reboots infinitely after rooting it and I searched everywhere for a solution but all I could do is get this message on flashtool:
06/056/2015 17:56:00 - INFO - Loader : S1_Root_2f8b - Version : MT6582_15 / Boot version : S1_Boot_MT6582_TC9SP_11 / Bootloader status : ROOTED
06/056/2015 17:56:00 - INFO - Transfer buffer size : 262144
06/056/2015 17:56:01 - INFO - You must have the according fsc script to flash this device.
06/056/2015 17:56:01 - INFO - Flashing finished.
06/056/2015 17:56:01 - INFO - Please unplug and start your phone
06/056/2015 17:56:01 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
It should be a driver problem but I have already installed adb drivers, specific drivers for e4 from sony website and flashtool, fastboot and jdm drivers from flashtool. I also tried switching usb ports and trying on other computers with the same results, and I'm 100% sure unknown sources and debug mode were checked last time the phone was in working condition.
I tried installing all drivers from flashtool's driver folder as well, still nothing. I dunno if it's relevant but the device is recognized as somc flash device in device manager. I'm using flashtool 0.9.19.0 as I read somewhere it works better for the e4 dual (even if it doesn't for me) and the latest version gives an IO exception error.
Any expert who can help me with the problem?
Edit: Bootloader is unlocked but the problem was the same before unlocking

Is there really no way of fixing my phone? Please help. . .

Anyone?

Can someone enlighten me? Now the battery is dead too... phone won't charge anymore.

ZeroJoe said:
Can someone enlighten me? Now the battery is dead too... phone won't charge anymore.
Click to expand...
Click to collapse
too bad i didn't see this thread previously.
hello friend,
I too have the same problem now.
i tried to change the build .prop and ended in bootloop today.
i have a similar message
"16/028/2015 15:28:57 - INFO - Please connect your device into flashmode.
16/029/2015 15:29:08 - INFO - Device disconnected
16/029/2015 15:29:13 - INFO - Bootloader unlock canceled
16/029/2015 15:29:50 - INFO - Device connected with USB debugging off
16/029/2015 15:29:50 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I tried to change the usb debugging settings through adb ,it is not working.
the internal storage and sdcard are not mounting. :crying::crying:
I think we will have to get help from sony support and the thread Xperia E4 Development by LeonXperiaXC
Did you try out the sony pc companion ? it is supposed to work as my device has a locked boot loader . but it is not working either.

dushandiaz said:
Did you try out the sony pc companion? it is supposed to work as my device has a locked boot loader . but it is not working either.
Click to expand...
Click to collapse
Yes I did that, device not supported, and that was even before I unlocked the bootloader.
I gave up fixing it some days ago, seeing that neither sony nor xda helped, and I can't afford a new one for now. Please let me know if you do manage to fix it, as I will check here from time to time, good luck to you.

ZeroJoe said:
Yes I did that, device not supported, and that was even before I unlocked the bootloader.
I gave up fixing it some days ago, seeing that neither sony nor xda helped, and I can't afford a new one for now. Please let me know if you do manage to fix it, as I will check here from time to time, good luck to you.
Click to expand...
Click to collapse
As i couldn't fix the device,I gave the phone to the service center.they had fixed it .I will be getting the device on moday. :fingers-crossed:
By the way,i found some interesting fact why unbricking didn't work for our E4.
sony pc companion unbricked my previous device xperia E1,it is a snapdragon device.
I think mediatek devices can't be unbricked by sony pc companion and also flashtool by androxyde.
Xperia C cannot be unbricked by the both as well.it is a mtk 6589 device.
Xperia C has an unbrick method using a tool/software called WMshua perfect flash.
https://www.informationlord.com/ultimate-guide-to-fix-bricked-xperia-c/
I didn't try it because i was scared of hard bricking the device.
I think it might work.
plus for chinease mediatek devices there is another tool called spflashtool.
also learn to use the spflashtool .there is a begineers guide at mtkroms.com
http://www.mtkroms.com/2015/02/how-...howComment=1447795342637#c6494565355265496004
give it a try.
If you have warranty definitely get it repaired by the service center.
or try the above methods if you have no choice.
I hope you will get your device working as soon as possible. :good::good::good::fingers-crossed::fingers-crossed::fingers-crossed:
Good luck.

ZeroJoe said:
Is there really no way of fixing my phone? Please help. . .
Click to expand...
Click to collapse
Did you try to restore with pc companion
1.Open back case and found OFF lockup using pen shutdown the bootloop
2.Open pc companion then support zone
3.click update my phone
4.click restore phone/tablet
5.then choose Sony Xperia E4 dual (E2115) because i connected
or if you not connected preess other phone/tablet then Choose E2115
6.after downloading firmware and getting ready
7.Make sure you have 80 % of charge
8.Start you phone in Flashmode PWR+VOL-
9.Wait
10.prrrrooooffffiiiiiitttt!!!!!!
AND NOTE SP FLASH TOOL NEVER FLASH SONY XPERIA WITH MTK EXPECT FAKES

Hi! I have sony xperia e4 E2105 and yesterday it went into bootloop. I tried to flash stock firmware but the version I have doesn't see the tft file so I downloaded older version of flashtool and it recogniznes tft file but when I try to flash it says that it can't open bundle . I dont have custom recovery .Please help me!
Thank you

Lenovo Yoga tab 2 Won't turn off

I was trying flash my yoga tab 2 with Phone flash tool
I putted flash-BIOS-dvt.xml instead of flash.xml
Now it won't turn off I tried to hold the power buttom for 5 minutes and it still won't turn off
​

MohamedStar said:
I was trying flash my yoga tab 2 with Phone flash tool
I putted flash-BIOS-dvt.xml instead of flash.xml
Now it won't turn off I tried to hold the power buttom for 5 minutes and it still won't turn off
​
Click to expand...
Click to collapse
flashin DVT.xml is WRONG and most likely will hardbrick!
if you can still see the device in a fastboot devices commans then DO NOT power off

The flashing was done probably and after that the device won't turn off until now just black screen

Now the device turned off
but still open black screen
and won't open fastboot mode or recovery

I sent my tablet to warrenty service in my countery & they say it's a hardware problem
Is flashing DVT.xml could damdge the hardware and the motherboard?

no. that is bs what they told you.

ionioni said:
no. that is bs what they told you.
Click to expand...
Click to collapse
They told me that's a hardware problem and maybe damdge the motherboard
Is flashing the tablet disable my warranty service?

MohamedStar said:
They told me that's a hardware problem and maybe damdge the motherboard
Is flashing the tablet disable my warranty service?
Click to expand...
Click to collapse
it is NOT a hardware problem (is like saying that writing a file with random numbers on you usb flash will destroy it, idiotic)
it is a software problem (tho this is a 'special' software that loads from you bios chip at power on time and to distinct it among software is called 'firmware). the problem is that the software on your bios chip is not good for your tab and because of this the tab does not start (actually it starts but it will hang, i could explain why but this is not important for your objective)
to repair obviously you must 'flash' a good (compatible) software on your bios chip (same like when your tab needs a stock rom because you altered somehow the one on you emmc and no longer works properly), but the problem is that because the tab hangs right on start you have no way to interact with it using software tools (because it hangs on such an early stage not even the dnx module is loaded) and the only option available is to physically open (dismantle) the tab and program the bios with a correct version using a hardware programmer

ionioni said:
it is NOT a hardware problem (is like saying that writing a file with random numbers on you usb flash will destroy it, idiotic)
it is a software problem (tho this is a 'special' software that loads from you bios chip at power on time and to distinct it among software is called 'firmware). the problem is that the software on your bios chip is not good for your tab and because of this the tab does not start (actually it starts but it will hang, i could explain why but this is not important for your objective)
to repair obviously you must 'flash' a good (compatible) software on your bios chip (same like when your tab needs a stock rom because you altered somehow the one on you emmc and no longer works properly), but the problem is that because the tab hangs right on start you have no way to interact with it using software tools (because it hangs on such an early stage not even the dnx module is loaded) and the only option available is to physically open (dismantle) the tab and program the bios with a correct version using a hardware programmer
Click to expand...
Click to collapse
Really Thank you for that info bro :good:
They make me confused how flashing software could damage the hardware
Now I know how to answer if they told me that's a hardware problem.

MohamedStar said:
Really Thank you for that info bro :good:
They make me confused how flashing software could damage the hardware
Now I know how to answer if they told me that's a hardware problem.
Click to expand...
Click to collapse
as you might guess, others had your problem too, for eg @rajan2002 (you can read from here and the next ones and maybe some other stuff will clarify for you)

They fixed the tab for me, It now with android KitKat and won't make lollipop update.
And the battery also become only 5700 mAh and the health status is unknown in every battery status app.
Note: they told me that they replaced my tab motherboard.

MohamedStar said:
They fixed the tab for me, It now with android KitKat and won't make lollipop update.
And the battery also become only 5700 mAh and the health status is unknown in every battery status app.
Note: they told me that they replaced my tab motherboard.
Click to expand...
Click to collapse
you can try and flash a stock kitkat rom for your model (which one?) and see if it fixes the issue (it should). remember once you flashed the kitkat rom to configure a region code (enter Contacts and type ####6020# in the search box and select a country from the list that shows). since i don't know the model i don't know what capacity your battery should be.
they changed the motherboard either because they are idiots and don't know how to reprogram a bios (and that operation is anything but difficult at a service center) either so that they can charge more (if that was the case). a similar 'mandatory' repairing requirement by replacing the mb was given to @rajan2002 (read this post and the next ones) but as you can see if you read the posts once he reprogrammed the bios all was ok (i also tested various bios files, dvt included and never had problems coming back from the hard-brick with the hw programmer).

ionioni said:
you can try and flash a stock kitkat rom for your model (which one?) and see if it fixes the issue (it should). remember once you flashed the kitkat rom to configure a region code (enter Contacts and type ####6020# in the search box and select a country from the list that shows). since i don't know the model i don't know what capacity your battery should be.
they changed the motherboard either because they are idiots and don't know how to reprogram a bios (and that operation is anything but difficult at a service center) either so that they can charge more (if that was the case). a similar 'mandatory' repairing requirement by replacing the mb was given to @rajan2002 (read this post and the next ones) but as you can see if you read the posts once he reprogrammed the bios all was ok (i also tested various bios files, dvt included and never had problems coming back from the hard-brick with the hw programmer).
Click to expand...
Click to collapse
I really think that idiots
I'll gave it a try, but is it safe to flash it with the PC flash tool.

MohamedStar said:
I really think that idiots
I'll gave it a try, but is it safe to flash it with the PC flash tool.
Click to expand...
Click to collapse
as long as you use a known stock rom you're fine (use only flash.xml too) search in the other threads for a stock rom already reported as used by others for your model (still no indication from you on what model you have... so i guess is confidential stuff)

Sorry I forget to mention my tab model, it's Lenovo Yoga tablet 2 1050L

Phone flash tool doesn't detect the tablet on dnx mode, only detect it when it's open.
By the way I already downloaded (YT2-1050L_USR_S000225_1504220451_WW21_ROW).

MohamedStar said:
Phone flash tool doesn't detect the tablet on dnx mode, only detect it when it's open.
By the way I already downloaded (YT2-1050L_USR_S000225_1504220451_WW21_ROW).
Click to expand...
Click to collapse
go in fastboot mode and tell me what says under IFWI

ionioni said:
go in fastboot mode and tell me what says under IFWI
Click to expand...
Click to collapse
That's the Phone flash tool log:
02/13/16 12:37:06.984 INFO : Phone Flash Tool V 4.4.4-1 Win32 External (build on Mon Apr 28 09:56:35 UTC 2014)
02/13/16 12:37:06.984 INFO : Using xFSTK version: 1.5.3
02/13/16 12:37:07.640 INFO : Using Android Debug Bridge version 1.0.31
02/13/16 12:37:07.640 INFO : OS version detected: Windows 8 (x64)
02/13/16 12:37:08.469 INFO : Adb and fastboot binaries OK
02/13/16 12:37:08.469 INFO : Phone Flash Tool initialized successfully
02/13/16 12:37:08.484 INFO : Loading Flash file ...
02/13/16 12:37:08.484 INFO : Ready to flash!
02/13/16 12:38:29.449 INFO : Loading Flash file (C:/Users/Mohamed Saad/Desktop/YT2_10_row_lte-blankphone-user-YT2-1050L_USR_S000215_1503241130_WW21_ROW/flash.xml)
02/13/16 12:38:29.449 INFO : GP_Flag is set to 0x80000045
02/13/16 12:38:29.542 INFO : Ready to flash!
Click to expand...
Click to collapse

MohamedStar said:
That's the Phone flash tool log:
Click to expand...
Click to collapse
i was talking about starting your tab in fastboot (droidboot) mode and when at that screen (on your tab) check the IFWI entry

ionioni said:
i was talking about starting your tab in fastboot (droidboot) mode and when at that screen (on your tab) check the IFWI entry
Click to expand...
Click to collapse
I'm not sure what "IFWI" mean
but that's an image for phone flash tool
It was connected when the tablet was on,
When I turn it off, It'll be disconnected.
I tried to flash it while it open, the tool turned the tablet on fastboot mode but stuck on 0%.

Lenovo Yoga Tab 2 1050F - Boot Failed. EFI Hard drive

Flashing Stock ROM failed.
Now won't boot of course, nor I can access fastboot. It's gone.
After turning Tablet on shows: "Boot Failed. EFI Hard drive"
and straight after that: "Boot Succeeded - Enter Setup"
Then BIOS like or actually BIOS shows - Title - VALLEYVIEW CO PLATFORM...
How can I fix fastboot? Or Droid Boot? I didn't even know I had BIOS in background?
I guess all blame me because I had Rooted... Is it trashing Tablet next step? Cause I couldn't find anything. I just wanted to go back to Stock ROM.
Anyone saw somewhere how to bring back fastboot? Or make it boot-able anything useful?
In that BIOS there is Boot Manager option and offers
- EFI Hard drive - Device path : PciRoot (0x0) /Pci (0x17, 0x0) /Ctrl (0x0)
- EFI Internal Shell - Device path : MemoryPapped (0xB,0xFFF50000,0xFFF8FFFF) /FvFile(C...
Can I somehow go somewhere from here?
Device Manager
Boot Maintenance Manage - has option Boot From FIle
- Boot Next Value... I'm lost.
I'm browsing that bios all possible ways to find something useful, but with no success.. Please help.
EDIT1: I find out that holding Power button and BOTH volume keys will start FastBoot - But mine stucks on "FastBoot Starting..."

There is already thread on xda discussing what to do when you got UEFI screen. restore-kitkat-bios-830-1050-v2 tool is the answer.
I lost that thread, so I'll answer to mine thread:
My state was - tablet ended up in UEFI. Couldn't get through but I did on the end with novice mistakes. So, here is advice and mistakes which cost me some time.
Spot that you need to be in DnX mode - kk-tool says that - pressed Volume keys and power button. Then tablet says FastBoot Starting...
Do not run KK bios restore tool with Intel Phone Flash Tool opened. Close Intel Phone Flash Tool. Then run kk-tool and follow instructions.
Then use Intel Platform Flash Tool to flash ROM (you need android driver and USB driver). I have used and working (not first image but some other second download worked): YT2-1050F_S0198_150422_ROW. Then I have tried to update to Android Lollipop but install failure.. Killed KitKat.. I'll google more tomorrow.
Let me know if you find working ROM able to update all the way successfully to Lollipop.
Looks scary when you see grey-blue UEFI screen - Oh, I must screwed up pretty bad if I lost FastBoot... You might think something like that, like I did. But kk tool really kick-off and helped.

I have searched quite thoroughly in this forum but I can not seem to find the restore-kitkat-bios-830-1050-v2 tool . I have this same problem and can not get my 830LC running.

All-in_One stock & rooted Firmware YT2-1050L
prabuddhadg said:
I have searched quite thoroughly in this forum but I can not seem to find the restore-kitkat-bios-830-1050-v2 tool . I have this same problem and can not get my 830LC running.
Click to expand...
Click to collapse
Found some folders from my softbrick after updating to lollipop.
Unlock bootloader ! !
Have uploaded all Files and ROM's i found for YogaTab 2-1050L.
temp TWRP
Stock Firmware KitKat Android
Stock rooted Firmware KitKat Android
For me worked :
"YT2_10_row_lte-blankphone-user-YT2-1050L_USR_S000215_1503241130_WW21_ROW"
Follow Guide inside folders
Good luck & have fun
DOWNLOAD ON MEGA - h**ps: // mega.nz/#F!gZZQXYha!EJovY_v_dyciO7pct9w68Q

Updating this old thread. I found my 1050F tablet and it has the same problem. I tried to download the files from the latest link of the thread but the link is dead
If anyone has those files it would be useful to me (and surely others)

Phone doesn´t start anymore

Hey there,
after flashing a created boot.img I think my phone is bricked
Cannot start it anymore / no bootloader / no hardreset.
Evertime I connect it to my PC first the red LED flashes and get stuck at a green LED.
Flashtool shows "no Device" and no adb connection is working.
What did I wrong?
Is my phone bricked?
Kind regards,
Chris

dhchris said:
Hey there,
after flashing a created boot.img I think my phone is bricked
Cannot start it anymore / no bootloader / no hardreset.
Evertime I connect it to my PC first the red LED flashes and get stuck at a green LED.
Flashtool shows "no Device" and no adb connection is working.
What did I wrong?
Is my phone bricked?
Kind regards,
Chris
Click to expand...
Click to collapse
I don't think flashing boot img would hard brick. Have you tried connecting while pressing volume up and volume down? I have had situations with my old Xa where a bad flash zapped the battery to zero, and I wouldn't get any response plugging in the charger, etc, but I would try it with different cables and try holdings buttons while plugging, and it suddenly resurrected and started charging, (happened twice when Xposed N unofficial was first released)...

levone1 said:
I don't think flashing boot img would hard brick. Have you tried connecting while pressing volume up and volume down? I have had situations with my old Xa where a bad flash zapped the battery to zero, and I wouldn't get any response plugging in the charger, etc, but I would try it with different cables and try holdings buttons while plugging, and it suddenly resurrected and started charging, (happened twice when Xposed N unofficial was first released)...
Click to expand...
Click to collapse
hmm, I tried to connect in many ways, but nothing happens.
If I connect it to my charger, the red light flickers (red light to red dark to red light...)
or
it flickers from off to red to off to red...
Charging in this state over night takes no effect.
Under Flashtool the green light is on (device connected in falsh mode) and trying to flash a xperifirm-ftf:
28/041/2018 07:41:54 - INFO - Device connected in flash mode
28/042/2018 07:42:15 - INFO - Selected Bundle for Sony Xperia X Compact(F5321). FW release : 34.4.A.2.19. Customization : Customized DE
28/042/2018 07:42:15 - INFO - Preparing files for flashing
28/042/2018 07:42:48 - INFO - Please connect your device into flashmode.
28/042/2018 07:42:49 - INFO - Using Gordon gate drivers version 3.2.0.0
28/042/2018 07:42:49 - INFO - Opening device for R/W
28/042/2018 07:42:49 - INFO - Device ready for R/W.
28/042/2018 07:42:49 - INFO - Reading device information
28/042/2018 07:42:51 - INFO - Phone ready for flashmode operations.
28/042/2018 07:42:51 - INFO - Opening TA partition 2
28/043/2018 07:43:09 - INFO - Current device : D5803 - YT910ZASZ3 - 1289-4696_R5D - 1285-6521_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291
28/043/2018 07:43:09 - INFO - Closing TA partition
28/043/2018 07:43:11 - ERROR - The bundle does not match the connected device
28/043/2018 07:43:11 - INFO - Ending flash session
28/043/2018 07:43:16 - INFO - Device connected in flash mode
28/043/2018 07:43:16 - INFO - Device disconnected
28/043/2018 07:43:21 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
Sounds not so good :crying:

dhchris said:
hmm, I tried to connect in many ways, but nothing happens.
If I connect it to my charger, the red light flickers (red light to red dark to red light...)
or
it flickers from off to red to off to red...
Charging in this state over night takes no effect.
Under Flashtool the green light is on (device connected in falsh mode) and trying to flash a xperifirm-ftf:
Sounds not so good :crying:
Click to expand...
Click to collapse
Hey Guys,
now I found the mistake i´ve done.
I swapped the file.
Taken the wrong TA.img from my other phone.
Is there a way to get the phone back to life?

dhchris said:
Hey Guys,
now I found the mistake i´ve done.
I swapped the file.
Taken the wrong TA.img from my other phone.
Is there a way to get the phone back to life?
Click to expand...
Click to collapse
Did you try checking 'wipe' boxes in Flashtool? How did you flash the ta?

levone1 said:
Did you try checking 'wipe' boxes in Flashtool? How did you flash the ta?
Click to expand...
Click to collapse
Yes, tried this.
Flashed the TA manually by adb

dhchris said:
Yes, tried this.
Flashed the TA manually by adb
Click to expand...
Click to collapse
What, with dd command? Did you try to do it again with correct ta, or use adb to wipe?
Flashier wrong ta could be a big deal... I know with Z phones it was for sure a hard brick, but maybe there's hope.
Do you get the same error with Emma / Sony Companion?

Yes, dd-command.
I´m searching for my right Xc - TA.img file, but I cannot find it anymore.
adb-wipe didnt tried.
In worst case, I overwritten it by the old Z3 phones TA.
EMMA told me that the device could not be identified.
I think, that there´s no other way to get a new phone ;-(