hello, i have a big problem :S
15 min ago i unlocked my wt19i with the x unlock tool (test point mode) and everything was working , so i decided to change the rom ( i was on real ics v5) so i downloaded it restarted via CWM but i made a big mistake i installed the unlocked bootloader version before unlocking it :S
And now the Phone is stuck on the sony logo and dont want to go on recovery or download mode (power button + volume up/down)
I dont know what to do :S
EDIT: ok so i put it in flashmode with flashtool and tried the "Unbricking Xperia 2011 Package" but didnt work here is the log
04/022/2012 16:22:48 - INFO - Device connected in flash mode
04/023/2012 16:23:10 - INFO - Selected Xperia_2011_FreeXperia_ALL.ftf
04/023/2012 16:23:10 - INFO - Preparing files for flashing
04/023/2012 16:23:10 - INFO - Please connect your device into flashmode.
04/023/2012 16:23:11 - INFO - Opening device for R/W
04/023/2012 16:23:11 - INFO - Reading device information
04/023/2012 16:23:11 - INFO - Phone ready for flashmode operations.
04/023/2012 16:23:11 - INFO - Start Flashing
04/023/2012 16:23:11 - INFO - Flashing loader
04/023/2012 16:23:14 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
04/023/2012 16:23:14 - INFO - Flashing preset.ta
04/023/2012 16:23:14 - INFO - Writing TA unit : [00, 00, 08, FD, 00, 00, 00, 02, 00, 00]
04/023/2012 16:23:14 - INFO - Ending flash session
04/023/2012 16:23:14 - INFO - Flashing finished.
04/023/2012 16:23:14 - INFO - Please wait. Phone will reboot
still not working...
EDIT 2 : than you all of you you helped me PROBLEM SOLVED.
flash any custom ics kernel
Flash the stock rom.
drakruka said:
hello, i have a big problem :S
15 min ago i unlocked my wt19i with the x unlock tool (test point mode) and everything was working , so i decided to change the rom ( i was on real ics v5) so i downloaded it restarted via CWM but i made a big mistake i installed the unlocked bootloader version before unlocking it :S
And now the Phone is stuck on the sony logo and dont want to go on recovery or download mode (power button + volume up/down)
I dont know what to do :S
EDIT: ok so i put it in flashmode with flashtool and tried the "Unbricking Xperia 2011 Package" but didnt work here is the log
04/022/2012 16:22:48 - INFO - Device connected in flash mode
04/023/2012 16:23:10 - INFO - Selected Xperia_2011_FreeXperia_ALL.ftf
04/023/2012 16:23:10 - INFO - Preparing files for flashing
04/023/2012 16:23:10 - INFO - Please connect your device into flashmode.
04/023/2012 16:23:11 - INFO - Opening device for R/W
04/023/2012 16:23:11 - INFO - Reading device information
04/023/2012 16:23:11 - INFO - Phone ready for flashmode operations.
04/023/2012 16:23:11 - INFO - Start Flashing
04/023/2012 16:23:11 - INFO - Flashing loader
04/023/2012 16:23:14 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
04/023/2012 16:23:14 - INFO - Flashing preset.ta
04/023/2012 16:23:14 - INFO - Writing TA unit : [00, 00, 08, FD, 00, 00, 00, 02, 00, 00]
04/023/2012 16:23:14 - INFO - Ending flash session
04/023/2012 16:23:14 - INFO - Flashing finished.
04/023/2012 16:23:14 - INFO - Please wait. Phone will reboot
still not working...
Click to expand...
Click to collapse
if u found a way to relock ur bootloader and repair ur phone via SONY UPDATE SERVICE it will be okay
Bootloader status rooted means the bootloader is unlocked.
Now you have tried to unbrick it but this unbricking ftf was only if you did an ota update.
Please start all over again.
1) Flash the ics stock rom for your device.
2) Boot it up, it must work.
3) Push the rom installation zip to your sd card
4) Flash the kernel of the rom you want to install
5) Boot in cwm -> wipe data/factory reset -> wipe cache -> dalvik cache (in advanced menu) -> if in the rom thread required, format system, too (mounts and storage menu)
6) Install the zip of the rom
7) If required (like on cyanogenmod) flash the gapps
8) Reboot and enjoy
This should work :good:
mihahn said:
Bootloader status rooted means the bootloader is unlocked.
Now you have tried to unbrick it but this unbricking ftf was only if you did an ota update.
Please start all over again.
1) Flash the ics stock rom for your device.
2) Boot it up, it must work.
3) Push the rom installation zip to your sd card
4) Flash the kernel of the rom you want to install
5) Boot in cwm -> wipe data/factory reset -> wipe cache -> dalvik cache (in advanced menu) -> if in the rom thread required, format system, too (mounts and storage menu)
6) Install the zip of the rom
7) If required (like on cyanogenmod) flash the gapps
8) Reboot and enjoy
This should work :good:
Click to expand...
Click to collapse
i flashed the stock rom and rooted it and then i was thinking how to reinstall the rom so i saw you post you helped me a lot thank you
drakruka said:
i flashed the stock rom and rooted it and then i was thinking how to reinstall the rom so i saw you post you helped me a lot thank you
Click to expand...
Click to collapse
Any questions, just ask and we'll try to help you
If I helped you, hit thanks please! :good:
Sent from my Sk17i running Jelly Bean
So i got my xperia z2 from o2 and wanted to debrand it, followed this tutorial:
http://www.xperiablog.net/2014/06/01/debrand-your-xperia-z2-tutorial/
But, it wont flash the firmware, its stuck here, when i start the phone i get an error that the software update has failed and to connect to my computer.
This is what im getting in Flashtool64;
03/040/2014 16:40:16 - INFO - <- This level is successfully initialized
03/040/2014 16:40:16 - INFO - Flashtool Version 0.9.10.2beta4 built on 2013-03-21 19:00:00
03/040/2014 16:40:21 - INFO - Device connected in flash mode
03/040/2014 16:40:25 - INFO - Selected D6503 / 17.1.A.2.55 / EURO_LTE
03/040/2014 16:40:25 - INFO - Preparing files for flashing
03/041/2014 16:41:11 - INFO - Please connect your device into flashmode.
03/041/2014 16:41:15 - INFO - Opening device for R/W
03/041/2014 16:41:15 - INFO - Reading device information
Ive started it over and over and it just gets stuck at this step, help
03/058/2014 16:58:40 - INFO - Device disconnected
03/058/2014 16:58:48 - INFO - Please connect your device into flashmode.
03/059/2014 16:59:00 - INFO - Device connected in flash mode
03/059/2014 16:59:01 - INFO - Opening device for R/W
03/059/2014 16:59:01 - INFO - Reading device information
03/059/2014 16:59:01 - INFO - Phone ready for flashmode operations.
03/059/2014 16:59:01 - INFO - Current device : D6503 - BH90CUJA16 - 1281-4648_R5A - 1278-4770_17.1.1.A.0.402 - EURO-LTE_17.1.1.A.0.402
03/059/2014 16:59:01 - INFO - Start Flashing
03/059/2014 16:59:01 - INFO - Processing loader
03/059/2014 16:59:01 - INFO - Checking header
03/059/2014 16:59:01 - INFO - Flashing data
03/059/2014 16:59:01 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_12 / Bootloader status : NOT_ROOTABLE
03/059/2014 16:59:02 - INFO - Processing partition-image.sin
03/059/2014 16:59:02 - INFO - Checking header
03/059/2014 16:59:02 - INFO - Flashing data
03/059/2014 16:59:02 - INFO - Flashing cust-reset.ta
03/059/2014 16:59:02 - INFO - Writing TA unit : [00, 00, 08, A4, 00, 00, 00, 0E, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
03/059/2014 16:59:02 - INFO - Processing kernel.sin
03/059/2014 16:59:02 - INFO - Checking header
03/059/2014 16:59:02 - INFO - Flashing data
03/059/2014 16:59:03 - INFO - Processing fotakernel.sin
03/059/2014 16:59:03 - INFO - Checking header
03/059/2014 16:59:03 - INFO - Flashing data
03/059/2014 16:59:05 - INFO - Processing fota-reset.ta
now its stuck at this
I'm not familiar with flashing on Z2 but I would try with latest flashtool.
Sent from my C6903 using Tapatalk
Double check it's the correct firmware
Try a different usb port
could be http://forum.xda-developers.com/showpost.php?p=32207092&postcount=7
BTW...flashing ftf on unrooted, unlocked device isn't good idea.
There were many bricked Z1 devices...
I flashed million ftf's and all went well but just want you to know that...
As I said, I'm quite sure you are using old flashtool.
Sent from my C6903 using Tapatalk
funky0308 said:
BTW...flashing ftf on unrooted, unlocked device isn't good idea.
There were many bricked Z1 devices...
I flashed million ftf's and all went well but just want you to know that...
As I said, I'm quite sure you are using old flashtool.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
From my understanding, FlashTool is designed(not only) to flash original firmware on unlocked, unrooted phones. If you follow the instruction carefully, you have all the drivers installed correctly, etc it should work.
raducanmihai said:
From my understanding, FlashTool is designed(not only) to flash original firmware on unlocked, unrooted phones. If you follow the instruction carefully, you have all the drivers installed correctly, etc it should work.
Click to expand...
Click to collapse
Why unlocked?
I'm using it without any problems on LB but for Z1 and Z2 you have to use latest version, I think it's v. 16
Sent from my C6903 using Tapatalk
funky0308 said:
Why unlocked?
I'm using it without any problems on LB but for Z1 and Z2 you have to use latest version, I think it's v. 16
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Sorry, my mistake. I meant to say "locked and unrooted".
I was trying to make a point that the quoted post (many Z1s bricked by flashing rtf on unlocked, unrooted) doesn't make sense.
Hey guys,
Yes, yes! I know this topic has been asked 100 000 times, and I have even googled, and tried to research, but honestly... everything is so freaking confusing! The information is so mixed up!
From what I understand is that you need to root your phone in order to back up your TA Partition, but the problem is some devices has newer firmware model, which in this case isn't possible to backup TA Partition, unless you root, but then you have to unlock your bootloader which means you will loose the DRM Keys! There is of course way to root your phone, but then you must either be super lucky buying a new phone which has old firmware, or you have to downgrade.
Now, I am using the Xperia Z Ultra C6833 - Build Number: 14.1B.1.510, and from what I understand there is a way to root your phone, but then you cannot back up TA Partition. In this case, this makes no sense how to solve this problem. I even have heard you can download a chinese application, but from what I heard, they are steaing your IMEI numbers, and adding virus on it (true, or not?)
I have tried to use the Backup-TA-9.11, which doesn't work by the way, because root is required, and the Flash Tools by following the instruction turning on the Switch to Pro ---> Advanced--> Trim Area---> Back Up (doesn't work, because the color is grey).
I have even tried to take a look to downgrade the firmware, but the problem is that you will have to flash your phone, but this requires root or something, yes? (sorry for not understanding exactly this this problem, because to mix information around on the net).
Now, as you see, I really have dilemma, and I don't think I am the only one who have the problem with this. I am almost giving up to root this phone, like SRS no joke! Been researching couple of hours, and this is driving me nuts!
Hopefully someone could please help me and someone else around the world who have same problems like I do! Sorry for writing not very tidy, but hope you guys understand the idea what I am talking about here!
Thanks!
Ciex said:
Hey guys,
Yes, yes! I know this topic has been asked 100 000 times, and I have even googled, and tried to research, but honestly... everything is so freaking confusing! The information is so mixed up!
From what I understand is that you need to root your phone in order to back up your TA Partition, but the problem is some devices has newer firmware model, which in this case isn't possible to backup TA Partition, unless you root, but then you have to unlock your bootloader which means you will loose the DRM Keys! There is of course way to root your phone, but then you must either be super lucky buying a new phone which has old firmware, or you have to downgrade.
Now, I am using the Xperia Z Ultra C6833 - Build Number: 14.1B.1.510, and from what I understand there is a way to root your phone, but then you cannot back up TA Partition. In this case, this makes no sense how to solve this problem. I even have heard you can download a chinese application, but from what I heard, they are steaing your IMEI numbers, and adding virus on it (true, or not?)
I have tried to use the Backup-TA-9.11, which doesn't work by the way, because root is required, and the Flash Tools by following the instruction turning on the Switch to Pro ---> Advanced--> Trim Area---> Back Up (doesn't work, because the color is grey).
I have even tried to take a look to downgrade the firmware, but the problem is that you will have to flash your phone, but this requires root or something, yes? (sorry for not understanding exactly this this problem, because to mix information around on the net).
Now, as you see, I really have dilemma, and I don't think I am the only one who have the problem with this. I am almost giving up to root this phone, like SRS no joke! Been researching couple of hours, and this is driving me nuts!
Hopefully someone could please help me and someone else around the world who have same problems like I do! Sorry for writing not very tidy, but hope you guys understand the idea what I am talking about here!
Thanks!
Click to expand...
Click to collapse
You have almost the oldest firmware on earth on the phone, almost any method would root it, hell it's probably so full of security holes that if you blew on the phone you could feel it on the back
At the moment the latest 14.4.a.0.108 is easy to root with easyroot or [NUT]'s recovery installer, then just back up the TA. You can either update to the latest firmware using PC companion or flashing a FTF with the latest xxx.16.1 version of flashtool (http://flashtool.net)
So:
Upgrade to 14.4.a.0.108
Root
Backup TA
???
Profit
Really appreciate your answer. A Question, when I Googled the 14.4.a.0.108. It seems like this firmware is also compatible for Xperia Z1 and the other model as well. You sure this will be safe by using this firmware on Xperia Z Ultra?
For some reason I cannot Flash. I get error message:
15/025/2014 21:25:56 - INFO - <- This level is successfully initialized
15/025/2014 21:25:56 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
15/026/2014 21:26:01 - INFO - Device disconnected
15/026/2014 21:26:51 - INFO - Device connected with USB debugging off
15/026/2014 21:26:51 - INFO - For 2011 devices line, be sure you are not in MTP mode
15/026/2014 21:26:51 - INFO - Device connected with USB debugging on
15/026/2014 21:26:52 - INFO - Connected device : Sony Xperia Z Ultra
15/026/2014 21:26:52 - INFO - Installed version of busybox : N/A
15/026/2014 21:26:52 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-perf-gde8296d-02194-ga2561a5 / Build number : 14.1.B.1.510
15/028/2014 21:28:15 - INFO - Selected null
15/028/2014 21:28:15 - INFO - Flash canceled
15/028/2014 21:28:38 - INFO - Selected Bundle for Sony Xperia Z Ultra (C6833). FW release : 14.4.A.0.108. Customization : 1275-9426
15/028/2014 21:28:38 - INFO - Preparing files for flashing
15/029/2014 21:29:07 - INFO - Device disconnected
15/029/2014 21:29:10 - INFO - Device connected in flash mode
15/029/2014 21:29:21 - INFO - Device disconnected
15/029/2014 21:29:29 - INFO - Device connected in flash mode
15/029/2014 21:29:47 - INFO - Selected Bundle for Sony Xperia Z Ultra (C6833). FW release : 14.4.A.0.108. Customization : 1275-9426
15/029/2014 21:29:47 - INFO - Preparing files for flashing
15/029/2014 21:29:47 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\system.sin
15/029/2014 21:29:47 - INFO - Cannot open bundle. Flash operation canceled
15/030/2014 21:30:07 - INFO - Selected Bundle for Sony Xperia Z Ultra (C6833). FW release : 14.4.A.0.108. Customization : 1275-9426
15/030/2014 21:30:07 - INFO - Preparing files for flashing
15/030/2014 21:30:07 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
15/030/2014 21:30:07 - INFO - Cannot open bundle. Flash operation canceled
15/030/2014 21:30:08 - INFO - Please connect your device into flashmode.
15/030/2014 21:30:08 - INFO - Opening device for R/W
15/030/2014 21:30:09 - INFO - Reading device information
15/030/2014 21:30:09 - INFO - Phone ready for flashmode operations.
15/030/2014 21:30:09 - INFO - Current device : C6833 - EP7334DKJD - 1276-1245_R9A - 1274-7565_14.1.B.1.510 - EURO-LTE_14.1.B.1.510
15/030/2014 21:30:09 - INFO - Start Flashing
15/030/2014 21:30:09 - INFO - Processing loader.sin
15/030/2014 21:30:09 - INFO - Checking header
15/030/2014 21:30:09 - INFO - Flashing data
15/030/2014 21:30:09 - INFO - Loader : S1_Root_6732 - Version : LOADER_RELEASE_MSM8974_28_AID_4 / Boot version : S1_Boot_MSM8974_LA1.0_56-A / Bootloader status : ROOTABLE
15/030/2014 21:30:09 - INFO - Processing partition-image.sin
15/030/2014 21:30:09 - INFO - Checking header
15/030/2014 21:30:09 - INFO - Flashing data
15/030/2014 21:30:09 - INFO - Parsing boot delivery
15/030/2014 21:30:09 - INFO - Phone boot version : S1_Boot_MSM8974_LA1.0_56-A. Boot delivery version : S1_Boot_MSM8974_Rhine1.2_LA1.04_19
15/030/2014 21:30:09 - INFO - Going to flash boot delivery
15/030/2014 21:30:09 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:09 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Flashing Togari_S1BootConfig_MiscTA_130115_1430.ta
15/030/2014 21:30:10 - INFO - Writing TA unit : [00, 00, 08, 4F, 00, 00, 00, 49, 1A, CE, 1D, 00, 01, 00, 04, 05, 00, 02, 02, 51, 00, 10, 03, 00, 02, 04, 02, 05, 00, 01, 03, 02, 00, 10, 05, 00, 03, 03, 05, 00, 10, 0A, 00, 02, 00, A9, 09, BE, BA, A9, 09, 00, 00, 04, 00, 03, 00, 02, 00, 04, 00, 04, 00, B0, 04, 0E, 00, 06, 00, B8, 0B, 01, 4B, 00, 00, 00, 03, 96, 00, 2C, 01]
15/030/2014 21:30:10 - INFO - Writing TA unit : [00, 00, 08, FD, 00, 00, 00, 01, 00]
15/030/2014 21:30:10 - INFO - Processing dbi_S1_Boot_MSM8974_Rhine1.2_19_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Processing s1sbl_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Processing sbl1_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Processing tz_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:11 - INFO - Processing kernel.sin
15/030/2014 21:30:11 - INFO - Checking header
15/030/2014 21:30:11 - INFO - Flashing data
15/030/2014 21:30:13 - INFO - Processing rpm.sin
15/030/2014 21:30:13 - INFO - Checking header
15/030/2014 21:30:13 - INFO - Flashing data
15/030/2014 21:30:13 - INFO - Processing fotakernel.sin
15/030/2014 21:30:13 - INFO - Checking header
15/030/2014 21:30:13 - INFO - Flashing data
15/030/2014 21:30:15 - INFO - Ending flash session
15/030/2014 21:30:15 - ERROR - C:\Flashtool\.\firmwares\prepared\amss_fs_2.sin (The system cannot find the file specified)
15/030/2014 21:30:15 - ERROR - Error flashing. Aborted
15/030/2014 21:30:15 - INFO - Device connected in flash mode
15/030/2014 21:30:15 - INFO - Device disconnected
15/030/2014 21:30:21 - INFO - Device connected in flash mode
15/030/2014 21:30:33 - INFO - Log written to C:\Flashtool\flashtool_2014-07-15_09-25-56.log
check paths "ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\system.sin":
I managed to fix it!
Just a another quick question. It seems my phone doesn't have mobile data on, even I turned the it on.
Does it have something to do with the kernel or something?
You may need to reenter your apns or redownloaf them if your with a network.
Sent from my C6833 using XDA Premium 4 mobile app
Hi guys,
i noticed there's not a single guide out there about this issue, so i'd decided to make one.
This guide is for those who have these problems:
the sony xperia z2 tablet won't boot up, turn on, no led notification when plugged in the wall charger, can't turn on, dead tablet, won't charge, etc...)
Fix:
if the above issues applied to u, please follow this guide:
1. download all the files for your specific z2 tablet version, im sorry i couldn't post link here, because its my first post, just do a googe search for "Guide to installing Xperia Lollipop using XperiFirm and Flashtool".
2. make sure to let the tablet sit for a day or 2, to let the battery discharged completely.
3. make sure the wall charger is working, its better to have multiple charger with different amps output, when one charger is not working, try another one with different output.
4. after the battery is completely discharged, plug in the charger, it should now charge again, if not try different amps out charger and usb cable, after it started charging again, don't turn it on or u must follow everything again to get it to charge again, because its a software problem, let it charge for about 40%, remember don't charge it too much or u have to wait longer for the battery to discharged, if u do decide to turn on the tablet, which will stays dead if u turn it off again, so please don't turn it on.
5. flash the firmware, your tablet is fixed, enjoy !!!!!!!!!!
update: it has nothing to do with the software, i even tried flashing all official rom version, i mean it does works, but the problem will return after a few days.
6. if the problem is still not fixed, open the tablet and unplugged the battery connector and plug the charger then reconnect battery connector, and it will come back to life instantly without waiting days for the battery to discharged.
7. coming soon....
I hope u find this guide helpful, because it took me a whole week to figure it out myself, i could't find any guide on the net which was helpful.
Thanks.
Best regards,
kn2020
Hello,
I have same issue. Its been months the Tablet is dead, I have been trying a lot of methods to start the Tablet. Unfortunately the crappy tablet is not being started, I am going to try your method tommo and will update you, thanks for writing this.
Hope this will work.
surya57 said:
Hello,
I have same issue. Its been months the Tablet is dead, I have been trying a lot of methods to start the Tablet. Unfortunately the crappy tablet is not being started, I am going to try your method tommo and will update you, thanks for writing this.
Hope this will work.
Click to expand...
Click to collapse
Did you fix it?
helmuthsorellana said:
Did you fix it?
Click to expand...
Click to collapse
No tablet wont charge at all. I see a red LED for a couple of minutes and thats it. It shuts off. This is all I get, no matter what I try. I tried everything, including freezing the tablet for 3hrs.
The tablet is a just a dead peice right now.
surya57 said:
No tablet wont charge at all. I see a red LED for a couple of minutes and thats it. It shuts off. This is all I get, no matter what I try. I tried everything, including freezing the tablet for 3hrs.
The tablet is a just a dead peice right now.
Click to expand...
Click to collapse
have you tried repairing it trough the xperia companion app connecting your pc directly to your router? by using the Ethernet cable some users said that they fixed the sleep of death issue trying this method lot of times till it went through; if your tablet does not enter the flashmode you can try leaving the tablet connected to your pc for an
hour, sometimes it automarically enters into flashmode, sometimes you need to unplug it and connect it by holding the -volume button and then pluggin your cablet while still holding down.
helmuthsorellana said:
have you tried repairing it trough the xperia companion app connecting your pc directly to your router? by using the Ethernet cable some users said that they fixed the sleep of death issue trying this method lot of times till it went through; if your tablet does not enter the flashmode you can try leaving the tablet connected to your pc for an
hour, sometimes it automarically enters into flashmode, sometimes you need to unplug it and connect it by holding the -volume button and then pluggin your cablet while still holding down.
Click to expand...
Click to collapse
I have tried repairing the tablet using the PC companion however it will not detect at all, I tried multiple times. What do you mean by connecting the ether net cable, I dint get you? Could you please tell the exact steps or share that post with the steps. I will be glad to try them. I just want my tablet to come back to life.
surya57 said:
I have tried repairing the tablet using the PC companion however it will not detect at all, I tried multiple times. What do you mean by connecting the ether net cable, I dint get you? Could you please tell the exact steps or share that post with the steps. I will be glad to try them. I just want my tablet to come back to life.
Click to expand...
Click to collapse
these are the Steps : 1. Unistall Xperia Companion
2. Download again the Xperia Companion
3. Install the Xperia Companion and connect de PC to the wire ethernet (not wireless)
4. Shutdown the Phone
5. In Xperia Companion select Fix the software
6. When the software say, push volume down button and connect the phone
7. Continue the next steps until Xperia Companin start to fix the phone.
its from this post: https://talk.sonymobile.com/t5/PC-Mac-Software/UEUpdateFailed-UE-2005/td-p/1141152/page/2
this guy too: https://talk.sonymobile.com/t5/PC-Mac-Software/UEUpdateFailed/td-p/1115690/page/3
https://talk.sonymobile.com/t5/PC-Mac-Software/UEUpdateFailed/td-p/1115690/page/4
https://talk.sonymobile.com/t5/Xper...me-quot-error-update-failed-quot/td-p/1018335 this guy says that If you are using Windows 8/8.1 or a 64bit operating system then adjust the settings for PC Companion and run in compatibility mode and chose Windows 7 or XP but i got windows 10....
---------- Post added at 08:57 PM ---------- Previous post was at 08:47 PM ----------
also try restarting your pc then disable antivirus, run xperia pc companion as admin. the error message points to a connection error with the update server so that means something blocking the application, try plz, i cant do it because of work
helmuthsorellana said:
these are the Steps : 1. Unistall Xperia Companion
2. Download again the Xperia Companion
3. Install the Xperia Companion and connect de PC to the wire ethernet (not wireless)
4. Shutdown the Phone
5. In Xperia Companion select Fix the software
6. When the software say, push volume down button and connect the phone
7. Continue the next steps until Xperia Companin start to fix the phone.
its from this post: https://talk.sonymobile.com/t5/PC-Mac-Software/UEUpdateFailed-UE-2005/td-p/1141152/page/2
this guy too: https://talk.sonymobile.com/t5/PC-Mac-Software/UEUpdateFailed/td-p/1115690/page/3
https://talk.sonymobile.com/t5/PC-Mac-Software/UEUpdateFailed/td-p/1115690/page/4
https://talk.sonymobile.com/t5/Xper...me-quot-error-update-failed-quot/td-p/1018335 this guy says that If you are using Windows 8/8.1 or a 64bit operating system then adjust the settings for PC Companion and run in compatibility mode and chose Windows 7 or XP but i got windows 10....
---------- Post added at 08:57 PM ---------- Previous post was at 08:47 PM ----------
also try restarting your pc then disable antivirus, run xperia pc companion as admin. the error message points to a connection error with the update server so that means something blocking the application, try plz, i cant do it because of work
Click to expand...
Click to collapse
Hello,
I have tried it several times and even now with a PC with Ethernet, the thing is the tablet is dead and bricked. The only thing I am seeing is a red LED for a few min, that too when I connect it after a gap like a couple of days. The LED stays for about 15-20 min and goes off, I have to repeat it again after a few days for the LED to show up. If I connect it to the PC at any point of time. The PC is not detecting the Tablet. I have tried it many times and fed up doing it. I dont know what is so wrong with the tablet. In the mean time I have tried charging the Tablet with different AMP output chargers as well, so far no luck. The same red LED repeats.
Do you have any updates on this so far? Please let me know if so.
surya57 said:
Hello,
I have tried it several times and even now with a PC with Ethernet, the thing is the tablet is dead and bricked. The only thing I am seeing is a red LED for a few min, that too when I connect it after a gap like a couple of days. The LED stays for about 15-20 min and goes off, I have to repeat it again after a few days for the LED to show up. If I connect it to the PC at any point of time. The PC is not detecting the Tablet. I have tried it many times and fed up doing it. I dont know what is so wrong with the tablet. In the mean time I have tried charging the Tablet with different AMP output chargers as well, so far no luck. The same red LED repeats.
Do you have any updates on this so far? Please let me know if so.
Click to expand...
Click to collapse
because of my work i have not tried these steps yet but i tried something using flashtool, i can flash the ftf file but excluding the system, when i try to flash excluding all other files but not the system.sin file, it does not go through, it reaches like 70% or 75% of the process then the tablet get disconnected and i get the error ''processing of system.sin finished with error. error 31, a device attached to the system is not functioning.'' I think it cant be flashed because the amount of apps inside the system.sin takes a lot to be flashed; i wonder if someone can modify it to reduce the size of the file; when do so and then i put in on charge my tablet shows the error message ''software update failed, please connect to the computer and try again'' what makes me think at least it works(tablet), but when i put it on the charger only shows that message and never appears the battery icon; i also tried unpacking ftf file and flashing files 1 by 1 using ADB but the one that I'm unable to flash stills the system.sin file, hope this help someone:
https://forum.xda-developers.com/xperia-sp/help/sin-error-flashtool-t2846599
I saw another post that i will look for it later, the guys said the were able to flash the ftf file using two flashtools version, the 1st one you need to flash ftf excluding system.sin file using flashtool version 0.9.18, then you need to uninstall flashtool and install an older one wich i don't remember the version, as i said i will look for it later.
Please try this method: https://forum.xda-developers.com/xperia-sp/help/sin-error-flashtool-t2846599 and this one too plz: https://www.youtube.com/watch?v=kGklpifG0yA
helmuthsorellana said:
because of my work i have not tried these steps yet but i tried something using flashtool, i can flash the ftf file but excluding the system, when i try to flash excluding all other files but not the system.sin file, it does not go through, it reaches like 70% or 75% of the process then the tablet get disconnected and i get the error ''processing of system.sin finished with error. error 31, a device attached to the system is not functioning.'' I think it cant be flashed because the amount of apps inside the system.sin takes a lot to be flashed; i wonder if someone can modify it to reduce the size of the file; when do so and then i put in on charge my tablet shows the error message ''software update failed, please connect to the computer and try again'' what makes me think at least it works(tablet), but when i put it on the charger only shows that message and never appears the battery icon; i also tried unpacking ftf file and flashing files 1 by 1 using ADB but the one that I'm unable to flash stills the system.sin file, hope this help someone:
https://forum.xda-developers.com/xperia-sp/help/sin-error-flashtool-t2846599
I saw another post that i will look for it later, the guys said the were able to flash the ftf file using two flashtools version, the 1st one you need to flash ftf excluding system.sin file using flashtool version 0.9.18, then you need to uninstall flashtool and install an older one wich i don't remember the version, as i said i will look for it later.
Please try this method: https://forum.xda-developers.com/xperia-sp/help/sin-error-flashtool-t2846599 and this one too plz: https://www.youtube.com/watch?v=kGklpifG0yA
Click to expand...
Click to collapse
Its good to know that you have a work around, the issue with me is, tablet is not being detected by the Flashtool or PC companion. Which makes it more bad.
There is no screen at all, not even backlight lights up. Just a solid red LED for a few min, then nothing. I will have a to wait for a couple of days again to see that red LED.
surya57 said:
Its good to know that you have a work around, the issue with me is, tablet is not being detected by the Flashtool or PC companion. Which makes it more bad.
There is no screen at all, not even backlight lights up. Just a solid red LED for a few min, then nothing. I will have a to wait for a couple of days again to see that red LED.
Click to expand...
Click to collapse
have you try leaving the tablet connected to the pc while flashtool request you to connect it? i always have to wait 15-25 minutes and automatically start the process but i get same error
Does anyone have Xperia Flashtool 0.6.6? i read some use were able to flash ftf using this flashtool version...
Great news guys, this may be the way to recover from sleep of death: what i did :
1-pres and hold volume down button+power and wait just 1 vibration.
2-Charged tablet 4 hours yesterday but i could not do the process till today.
3- I'm using windows 10 64 bit, uninstalled current flashtool version and deleted the folder located in Local/User/(your user name)/.Flashtool.
4-Restarted my pc pressing left **** in order to disable driver signature(see on youtobe).
5-Installed Flashtool 0.9.18.6 and sgp521, fastboot, flashmode drivers and i restarted pc 1 more time.
6-Opened the 64 bit flashtool.exe and connected the tablet and led keep red for 15 minutes.
7-nothing happened so i left it for an hour connected to the pc, after the hour with led the off i pressed and hold power button and immediately pressed and hold volume down and my tablet entered flashmode and saw the current tablet information and showed 01/011/2018 02:11:25 - INFO - Current device : SGP521 - CB512707UY - 1281-8152_R6A - 1278-4804_17.1.1.A.0.402 - GLOBAL-LTE_17.1.1.A.0.402 when i pressed on unlock bootloader, i did this to check what firmware version to download, i opened xperiafirm app and i searched the right one that starts with 1281-8152, ill post screenshots later...
8-with the right ftf file i started the flashing process and when the instruction prompted to connect my tablet to the pc during all the process i kept holding volume down and power buttons to ensure the tablet remain on because tablet gets disconnected after 2 or 3 minutes depending and if pressed both buttons it never power off so i kept pressing and holding volume down button and releasing power but for a second every 1 minute as i said before to ENSURE THE TABLET KEEPS ON DURING THE PROCESS.
Now my tablet powered on and showed the Android powered logo and the apps optimization process and then shut down, i pressed power button while i was charging the tablet and showed 1%, i turned it on one more time and it colud finish the apps optimization process and reached the set up screen and then shut down again, currently I'm charging it, ill keep updating this post....
Here is the flashtool Log:
01/037/2018 00:37:36 - INFO - Flashtool Version 0.9.18.6 built on 30-05-2015 22:30:00
01/037/2018 00:37:36 - INFO - Executing search strategies to find proxy selector
01/037/2018 00:37:40 - INFO - No proxy found for IE. Trying next one
01/037/2018 00:37:40 - INFO - Strategy firefox failed trying next one : No Firefox installation found
01/037/2018 00:37:40 - INFO - No proxy found for java. Trying next one
01/037/2018 00:37:41 - INFO - Syncing devices from github
01/037/2018 00:37:42 - INFO - Cloning devices repository
01/043/2018 00:43:39 - INFO - Devices sync finished.
01/043/2018 00:43:44 - INFO - Device disconnected
01/043/2018 00:43:48 - INFO - Downloading latest XperiFirm
01/057/2018 01:57:12 - INFO - Creating bundle for Xperia Z2 Tablet VMo HK SA AE KW 23.5.A.1.291
01/057/2018 01:57:13 - INFO - Adding fotakernel.sin to the bundle
01/057/2018 01:57:13 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\fotakernel_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
01/057/2018 01:57:15 - INFO - Adding kernel.sin to the bundle
01/057/2018 01:57:15 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
01/057/2018 01:57:17 - INFO - Adding system.sin to the bundle
01/057/2018 01:57:17 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\system_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
01/001/2018 02:01:37 - INFO - Adding fota-reset.ta to the bundle
01/001/2018 02:01:37 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\fota-reset.ta
01/001/2018 02:01:37 - INFO - Adding userdata.sin to the bundle
01/001/2018 02:01:37 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\userdata_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
01/002/2018 02:02:06 - INFO - Adding partition-image.sin to the bundle
01/002/2018 02:02:06 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\partition-image_S1-SW-LIVE-9C84-PID1-0006-MBR.sin
01/002/2018 02:02:06 - INFO - Adding amss_fs_2.sin to the bundle
01/002/2018 02:02:06 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\amss_fs_2_S1-MODEMSW-LIVE-9C84-PID1-0006-MMC.sin
01/002/2018 02:02:06 - INFO - Adding cache.sin to the bundle
01/002/2018 02:02:06 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\cache_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
01/002/2018 02:02:07 - INFO - Adding loader.sin to the bundle
01/002/2018 02:02:07 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\loader.sin
01/002/2018 02:02:07 - INFO - Adding cust-reset.ta to the bundle
01/002/2018 02:02:07 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\cust-reset.ta
01/002/2018 02:02:07 - INFO - Adding osv-restriction.ta to the bundle
01/002/2018 02:02:07 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\osv-restriction.ta
01/002/2018 02:02:07 - INFO - Adding apps_log.sin to the bundle
01/002/2018 02:02:07 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\apps_log_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
01/002/2018 02:02:07 - INFO - Adding auto-boot.ta to the bundle
01/002/2018 02:02:07 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\auto-boot.ta
01/002/2018 02:02:07 - INFO - Adding elabel-SGP521-row_201505192043.1_23.5.A.1.291.sin to the bundle
01/002/2018 02:02:07 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\elabel-SGP521-row_201505192043.1_23.5.A.1.291_S1-ELABEL-LIVE-9C84-PID1-0004-MMC.sin
01/002/2018 02:02:08 - INFO - Adding boot_delivery.xml to the bundle
01/002/2018 02:02:08 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\boot\boot_delivery.xml
01/002/2018 02:02:08 - INFO - Adding tz_S1_Boot_MSM8274AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BA0E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding Castor_S1BootConfig_MiscTA.ta to the bundle
01/002/2018 02:02:09 - INFO - Adding dbi_S1_Boot_MSM8274AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BA0E1-0001-SWID12_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding tz_S1_Boot_MSM8974AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007B80E1-0001-SWID07_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding s1sbl_S1_Boot_MSM8074AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BB0E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding rpm_S1_Boot_MSM8974AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007B80E1-0001-SWID0A_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding sbl1_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding sbl1_S1_Boot_MSM8974AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007B80E1-0001-SWID00_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding dbi_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding emmc_appsboot_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:09 - INFO - Adding s1sbl_S1_Boot_MSM8274AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BA0E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding s1sbl_S1_Boot_MSM8974AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007B80E1-0001-SWID65_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding tz_S1_Boot_MSM8074AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BB0E1-0001-SWID07_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding emmc_appsboot_S1_Boot_MSM8974AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007B80E1-0001-SWID09_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding tz_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding sbl1_S1_Boot_MSM8074AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BB0E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding tz_S1_Boot_MSM8274AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BA0E1-0001-SWID07_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding rpm_S1_Boot_MSM8074AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BB0E1-0001-SWID0A_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:10 - INFO - Adding sbl1_S1_Boot_MSM8074AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BB0E1-0001-SWID00_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding dbi_S1_Boot_MSM8974AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007B80E1-0001-SWID12_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding emmc_appsboot_S1_Boot_MSM8074AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BB0E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding rpm_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID0A-OEM1-AID4-DEBUG00_S1-RPMFW-LIVE-9C84-PID1-0005-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding dbi_S1_Boot_MSM8074AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BB0E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding s1sbl_S1_Boot_MSM8074AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BB0E1-0001-SWID65_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding emmc_appsboot_S1_Boot_MSM8074AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BB0E1-0001-SWID09_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding rpm_S1_Boot_MSM8274AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BA0E1-0001-SWID0A_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding sbl1_S1_Boot_MSM8274AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BA0E1-0001-SWID00_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:11 - INFO - Adding rpm_S1_Boot_MSM8074AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BB0E1-SWID0A-OEM1-AID4-DEBUG00_S1-RPMFW-LIVE-9C84-PID1-0005-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding rpm_S1_Boot_MSM8274AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BA0E1-SWID0A-OEM1-AID4-DEBUG00_S1-RPMFW-LIVE-9C84-PID1-0005-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding sbl1_S1_Boot_MSM8274AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BA0E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding s1sbl_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding dbi_S1_Boot_MSM8274AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BA0E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding emmc_appsboot_S1_Boot_MSM8274AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BA0E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding tz_S1_Boot_MSM8074AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007BB0E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding s1sbl_S1_Boot_MSM8274AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BA0E1-0001-SWID65_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:12 - INFO - Adding emmc_appsboot_S1_Boot_MSM8274AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BA0E1-0001-SWID09_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:13 - INFO - Adding dbi_S1_Boot_MSM8074AB_LA3_0_M_3_AID_1_MSM8974AB-TEST-HWID007BB0E1-0001-SWID12_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
01/002/2018 02:02:13 - INFO - Adding amss_fsg.sin to the bundle
01/002/2018 02:02:13 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\amss_fsg_S1-MODEMSW-LIVE-9C84-PID1-0006-MMC.sin
01/002/2018 02:02:13 - INFO - Adding b2b.sin to the bundle
01/002/2018 02:02:13 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\b2b_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
01/002/2018 02:02:14 - INFO - Adding amss_fs_1.sin to the bundle
01/002/2018 02:02:14 - INFO - Streaming from file : C:\Users\helmuths\.flashTool\firmwares\Downloads\SGP521_VMo HK SA AE KW_1281-8152_23.5.A.1.291_R5D\amss_fs_1_S1-MODEMSW-LIVE-9C84-PID1-0006-MMC.sin
01/002/2018 02:02:14 - INFO - Creating torrent file : C:\Users\helmuths\.flashTool\firmwares\SGP521_23.5.A.1.291_1281-8152_R5D.ftf.torrent
01/003/2018 02:03:14 - INFO - Torrent file creation finished
01/008/2018 02:08:25 - ERROR - root : this bundle is not valid
01/008/2018 02:08:26 - INFO - Selected Bundle for Sony Xperia Z2 Tablet (SGP521). FW release : 23.5.A.1.291. Customization : VMo HK SA AE KW
01/008/2018 02:08:26 - INFO - Preparing files for flashing
01/011/2018 02:11:10 - INFO - Please connect your device into flashmode.
01/011/2018 02:11:25 - INFO - Device connected in flash mode
01/011/2018 02:11:25 - INFO - Opening device for R/W
01/011/2018 02:11:25 - INFO - Reading device information
01/011/2018 02:11:25 - INFO - Phone ready for flashmode operations.
01/011/2018 02:11:25 - INFO - Current device : SGP521 - CB512707UY - 1281-8152_R6A - 1278-4804_17.1.1.A.0.402 - GLOBAL-LTE_17.1.1.A.0.402
01/011/2018 02:11:25 - INFO - Start Flashing
01/011/2018 02:11:25 - INFO - Processing loader.sin
01/011/2018 02:11:25 - INFO - Checking header
01/011/2018 02:11:25 - INFO - Flashing data
01/011/2018 02:11:26 - INFO - Processing of loader.sin finished.
01/011/2018 02:11:26 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AB_LA2.0.1_37-B / Bootloader status : ROOTABLE
01/011/2018 02:11:26 - INFO - Processing partition-image.sin
01/011/2018 02:11:26 - INFO - Checking header
01/011/2018 02:11:26 - INFO - Flashing data
01/011/2018 02:11:26 - INFO - Processing of partition-image.sin finished.
01/011/2018 02:11:26 - INFO - Parsing boot delivery
01/011/2018 02:11:26 - INFO - Phone boot version : S1_Boot_MSM8974AB_LA2.0.1_37-B. Boot delivery version : S1_Boot_MSM8974AB_LA3.0-M-3
01/011/2018 02:11:26 - INFO - Going to flash boot delivery
01/011/2018 02:11:27 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
01/011/2018 02:11:27 - INFO - Checking header
01/011/2018 02:11:27 - INFO - Flashing data
01/011/2018 02:11:27 - INFO - Processing of emmc_appsboot_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin finished.
01/011/2018 02:11:27 - INFO - Flashing Castor_S1BootConfig_MiscTA.ta to partition 2
01/011/2018 02:11:27 - INFO - Writing TA unit : [00, 00, 08, 4F, 00, 00, 00, 59, 1A, CE, 28, 00, 01, 00, 06, 05, 00, 02, 02, 08, 00, 10, 03, 00, 02, 04, 02, 05, 00, 01, 03, 02, 00, 10, 05, 00, 03, 03, 05, 00, 10, 05, 00, 05, 83, 02, 00, 10, 02, 00, 05, 85, 0A, 00, 02, 00, A9, 09, BE, BA, A9, 09, 00, 00, 04, 00, 03, 00, 02, 00, 04, 00, 04, 00, B0, 04, 0E, 00, 06, 00, B8, 0B, 01, 4B, 00, 00, 00, 03, 96, 00, 2C, 01, 03, 00, 09, 00, 01]
01/011/2018 02:11:27 - INFO - Writing TA unit : [00, 00, 08, FD, 00, 00, 00, 01, 00]
01/011/2018 02:11:27 - INFO - Processing dbi_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
01/011/2018 02:11:27 - INFO - Checking header
01/011/2018 02:11:27 - INFO - Flashing data
01/011/2018 02:11:27 - INFO - Processing of dbi_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin finished.
01/011/2018 02:11:27 - INFO - Processing s1sbl_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
01/011/2018 02:11:27 - INFO - Checking header
01/011/2018 02:11:27 - INFO - Flashing data
01/011/2018 02:11:27 - INFO - Processing of s1sbl_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin finished.
01/011/2018 02:11:27 - INFO - Processing tz_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
01/011/2018 02:11:27 - INFO - Checking header
01/011/2018 02:11:27 - INFO - Flashing data
01/011/2018 02:11:27 - INFO - Processing of tz_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin finished.
01/011/2018 02:11:27 - INFO - Processing sbl1_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
01/011/2018 02:11:27 - INFO - Checking header
01/011/2018 02:11:27 - INFO - Flashing data
01/011/2018 02:11:28 - INFO - Processing of sbl1_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin finished.
01/011/2018 02:11:28 - INFO - Processing rpm_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID0A-OEM1-AID4-DEBUG00_S1-RPMFW-LIVE-9C84-PID1-0005-MMC.sin
01/011/2018 02:11:28 - INFO - Checking header
01/011/2018 02:11:28 - INFO - Flashing data
01/011/2018 02:11:28 - INFO - Processing of rpm_S1_Boot_MSM8974AB_LA3_0_M_3_AID_4_PLATFORM-MSM8974AB-LIVE-HWID007B80E1-SWID0A-OEM1-AID4-DEBUG00_S1-RPMFW-LIVE-9C84-PID1-0005-MMC.sin finished.
01/011/2018 02:11:28 - INFO - Processing kernel.sin
01/011/2018 02:11:28 - INFO - Checking header
01/011/2018 02:11:28 - INFO - Flashing data
01/011/2018 02:11:30 - INFO - Processing of kernel.sin finished.
01/011/2018 02:11:30 - INFO - Processing fotakernel.sin
01/011/2018 02:11:31 - INFO - Checking header
01/011/2018 02:11:31 - INFO - Flashing data
01/011/2018 02:11:32 - INFO - Processing of fotakernel.sin finished.
01/011/2018 02:11:32 - INFO - Processing amss_fs_2.sin
01/011/2018 02:11:33 - INFO - Checking header
01/011/2018 02:11:33 - INFO - Flashing data
01/011/2018 02:11:33 - INFO - Processing of amss_fs_2.sin finished.
01/011/2018 02:11:33 - INFO - Processing amss_fsg.sin
01/011/2018 02:11:33 - INFO - Checking header
01/011/2018 02:11:33 - INFO - Flashing data
01/011/2018 02:11:33 - INFO - Processing of amss_fsg.sin finished.
01/011/2018 02:11:33 - INFO - Processing amss_fs_1.sin
01/011/2018 02:11:33 - INFO - Checking header
01/011/2018 02:11:33 - INFO - Flashing data
01/011/2018 02:11:33 - INFO - Processing of amss_fs_1.sin finished.
01/011/2018 02:11:33 - INFO - Processing b2b.sin
01/011/2018 02:11:33 - INFO - Checking header
01/011/2018 02:11:33 - INFO - Flashing data
01/011/2018 02:11:34 - INFO - Processing of b2b.sin finished.
01/011/2018 02:11:34 - INFO - Processing apps_log.sin
01/011/2018 02:11:34 - INFO - Checking header
01/011/2018 02:11:34 - INFO - Flashing data
01/011/2018 02:11:35 - INFO - Processing of apps_log.sin finished.
01/011/2018 02:11:35 - INFO - Processing cache.sin
01/011/2018 02:11:35 - INFO - Checking header
01/011/2018 02:11:35 - INFO - Flashing data
01/011/2018 02:11:36 - INFO - Processing of cache.sin finished.
01/011/2018 02:11:36 - INFO - Processing system.sin
01/011/2018 02:11:36 - INFO - Checking header
01/011/2018 02:11:36 - INFO - Flashing data
01/017/2018 02:17:13 - INFO - Processing of system.sin finished.
01/017/2018 02:17:13 - INFO - Processing userdata.sin
01/017/2018 02:17:13 - INFO - Checking header
01/017/2018 02:17:14 - INFO - Flashing data
01/017/2018 02:17:51 - INFO - Processing of userdata.sin finished.
01/017/2018 02:17:52 - INFO - Processing elabel-SGP521-row_201505192043.1_23.5.A.1.291.sin
01/017/2018 02:17:52 - INFO - Checking header
01/017/2018 02:17:52 - INFO - Flashing data
01/017/2018 02:17:54 - INFO - Processing of elabel-SGP521-row_201505192043.1_23.5.A.1.291.sin finished.
01/017/2018 02:17:54 - INFO - Writing TA unit : [00, 00, 08, FD, 00, 00, 00, 01, 01]
01/017/2018 02:17:54 - INFO - Flashing fota-reset.ta to partition 2
01/017/2018 02:17:54 - INFO - Writing TA unit : [00, 00, 09, 64, 00, 00, 00, 01, 00]
01/017/2018 02:17:54 - INFO - Flashing cust-reset.ta to partition 2
01/017/2018 02:17:54 - INFO - Custumization reset is now based on UI choice
01/017/2018 02:17:55 - INFO - Flashing osv-restriction.ta to partition 2
01/017/2018 02:17:55 - INFO - Writing TA unit : [00, 00, 09, 1A, 00, 00, 00, 01, 00]
01/017/2018 02:17:55 - INFO - Flashing auto-boot.ta to partition 2
01/017/2018 02:17:55 - INFO - Writing TA unit : [00, 00, 09, 07, 00, 00, 00, 01, 00]
01/017/2018 02:17:55 - INFO - Ending flash session
01/017/2018 02:17:55 - INFO - Flashing finished.
01/017/2018 02:17:55 - INFO - Please unplug and start your phone
01/017/2018 02:17:55 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
01/017/2018 02:17:55 - INFO - Device connected in flash mode
01/018/2018 02:18:01 - INFO - Device disconnected
01/018/2018 02:18:03 - INFO - Device connected in flash mode
01/018/2018 02:18:05 - INFO - Device disconnected
Hope this help y'all, greetings
---------- Post added at 07:00 AM ---------- Previous post was at 06:57 AM ----------
if u see i kept holding buttons for 10 minutes and my fingers hurt lol
hello, i left the tablet charging yesterday and today and charge percentage was 4%, then i saw that the red remains on for 3 minutes and then the tablet shuts down, after i saw that i pressed the power button and showed 5%, again after the led turned off i pressed power button and i got 6%, apparently this is the only way to get the tablet charger, idk if its a software problem cause i replaced battery on December when i had my tablet dead, when i turn the tablet on it shuts down exactly 1.55 m/s after gets in homescreen, tried disabling apps but i got no luck, then i researched on internet and i found this thread: https://talk.sonymobile.com/t5/Xperia-M5/M5-suddenly-shuts-off-every-10-minuts/m-p/1111220#M1513
see on page 46, it seems that the sudden shut down its related with the band frequencies, the problem may occur only with the provider that works on 2G and 3G at the same frequency of 900 Mhrz. Does anyone know how to disable the WCDMA-IMT 900mhz frequencie? engineering mode only works for MTK devices and i don't know how to do it on this one, i also tried entering the safe mode but no luck, thanks in advance.
here is a video but for the xperia m5 device https://www.youtube.com/watch?time_continue=14&v=tbPO4ni5_ks
helmuthsorellana said:
have you try leaving the tablet connected to the pc while flashtool request you to connect it? i always have to wait 15-25 minutes and automatically start the process but i get same error
Click to expand...
Click to collapse
Hello.
I have tried this as well, I left the Tablet for more than half an hour to the PC while Flashtool requested to connect. Still no luck
PC does not recognize the tablet at all, I just read your clear steps on how you flashed the FTF. For me the first step itself is a fail, my tablet does not vibrate when I press down + power keys. It just does nothing other than showing red LED fora few min and shuts off. Do you have any suggestions for my case? I really want this tablet to work..
surya57 said:
Hello.
I have tried this as well, I left the Tablet for more than half an hour to the PC while Flashtool requested to connect. Still no luck
PC does not recognize the tablet at all, I just read your clear steps on how you flashed the FTF. For me the first step itself is a fail, my tablet does not vibrate when I press down + power keys. It just does nothing other than showing red LED fora few min and shuts off. Do you have any suggestions for my case? I really want this tablet to work..
Click to expand...
Click to collapse
what i have read and i have not tried is to remove the batter cover and to unplug the battery connector and plug it back again, the would your last way to revive your tablet, also you can check (if you have tools) its not a voltage problem, have you tried to press the red button net the sim card slot while tablet is connected to the wall charger? try also on pc and then plug it back to the wall charger.
There were sometimes that my tablet did not response at all and what i did: i left my tablet placed vertically so the power button was always pressed to ensure the battery get completely drained, after that i plug it to wall charger and pressed red button while tablet was charging, and then i saw the first error message i was dealing with when i got this tablet: '''software update failed''.... and then i did what i posted before, hope this helps!
My Situation & Fix
Situation
1. The tablet screen/display had broken near a speaker (there is a hollow space under the bezel, and I was holding the tablet at the said spot)
2. I had ordered a original screen/display replacement on AliExpress and put away the tablet (delivery took nearly 2 months)
3. After I installed the new display, my tablet would not turn on or even charge
I made a choice in believing that the screen was fine and that the battery was dead-cold.
Here is what I did
1. connected the magnetic charger for about 24hours
2. held "power + vol up + vol down + reset (next to sim slot)" buttons till I could get any feedback (screen, led or vibrate) from the tablet - I got a single very-short vibrate after about 2-3 minutes (did not time it precisely as I had made up my mind to not let go off the buttons till I had gotten a feedback)
3. connected the magnetic charger again for about 24 hours
4. attempted a power up and voila, the screen indicated that power on not possible due to low battery
5. charged using USB in shut-down state till screen indicated full battery
During step 1 and 3, there was absolutely no response from the table (screen, led or vibrate). I was hardly hopeful for its revival but the response on step 2 kept me going.
I am so relieved that the screen is fine and the table too.