[Q] Z1C flashing red light - Xperia Z1 Compact Q&A, Help & Troubleshooting

sorry for my english
i have 2 xperia Z1 compact i used a full phone backup from TeamWin Recovery Project from my old one and tryed to aplly it to the new one, but when i finished updates the phone didn't start anymore
when i plug it into the charger usb or computer it starts blinking in red .
phone wont turn on, tried the red button off button, tried the power and volume button, when in charge it keeps flashing a red light, no vibration and nothing detected on computer.
i tried s1tool to repair it after connecting testpoint but i got a message saying " MINOR ERROR [ 0x80080021_, err: 0017 ] --------- error while uploading final HDR block"
PROCESSING ...
1/2/2015 3:59:06 PM SERIAL NUMBER : 1B9C3C06
1/2/2015 3:59:06 PM HARDWARE ID : 04000100E1007B00
1/2/2015 3:59:06 PM HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
1/2/2015 3:59:06 PM Emergency loader uploaded ...
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
1/2/2015 3:59:07 PM LOADER AID: 0004
1/2/2015 3:59:07 PM DEVICE ID: 063C9C1B
1/2/2015 3:59:07 PM FLASH ID: "0011/01000010"
1/2/2015 3:59:07 PM LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM WRITING PACKAGES ...
1/2/2015 3:59:07 PM Processing package
1/2/2015 3:59:07 PM C:\Users\BBMT\Desktop\fw\amami_testpoint.SIN_FILE_SET
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM MINOR ERROR [ 0x80080021_, err: 0017 ]
1/2/2015 3:59:07 PM error while uploading final HDR block
1/2/2015 3:59:07 PM Break.
1/2/2015 3:59:07 PM FINISHED"
, what can I do?
thanks for helping

bbmt22 said:
sorry for my english
i have 2 xperia Z1 compact i used a full phone backup from TeamWin Recovery Project from my old one and tryed to aplly it to the new one, but when i finished updates the phone didn't start anymore
when i plug it into the charger usb or computer it starts blinking in red .
phone wont turn on, tried the red button off button, tried the power and volume button, when in charge it keeps flashing a red light, no vibration and nothing detected on computer.
i tried s1tool to repair it after connecting testpoint but i got a message saying " MINOR ERROR [ 0x80080021_, err: 0017 ] --------- error while uploading final HDR block"
PROCESSING ...
1/2/2015 3:59:06 PM SERIAL NUMBER : 1B9C3C06
1/2/2015 3:59:06 PM HARDWARE ID : 04000100E1007B00
1/2/2015 3:59:06 PM HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
1/2/2015 3:59:06 PM Emergency loader uploaded ...
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
1/2/2015 3:59:07 PM LOADER AID: 0004
1/2/2015 3:59:07 PM DEVICE ID: 063C9C1B
1/2/2015 3:59:07 PM FLASH ID: "0011/01000010"
1/2/2015 3:59:07 PM LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM WRITING PACKAGES ...
1/2/2015 3:59:07 PM Processing package
1/2/2015 3:59:07 PM C:\Users\BBMT\Desktop\fw\amami_testpoint.SIN_FILE_SET
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM MINOR ERROR [ 0x80080021_, err: 0017 ]
1/2/2015 3:59:07 PM error while uploading final HDR block
1/2/2015 3:59:07 PM Break.
1/2/2015 3:59:07 PM FINISHED"
, what can I do?
thanks for helping
Click to expand...
Click to collapse
Hey!
To My phone it happened too and I managed to fix it ONLY from service. They changed the motherboard and the battery was DEAD too. It happens when you try to restore thing in too LOW battery level. The battry just running empty and you cant charge it again, because its LITHIUM battery and these batterys dont like to run empty. They can die after that.
Hope you get your phone changed from service, if you have warranty(like I was).
Peace for all!!!

hey happend to me 2 days ago when I tried to install a custom rom
what I did: I startet flashtool on my pc connected the phone .. used volume up + power to shut it down .. and then ( i cant remember ) just used the volume down button or volume down + power ..
'why ? because I was not able to connect via usb to PC because the phone wasnt booting at all .. BUT I was able to enter fastboot and I recognized this via flashtool .. then; I installed a complete stock TFT
another option is to start sony companion, click on update then on repair .. follow the instructions .. shut down your phone with vol up + power and try to enter fastboot , companion will recognize your phone. if this happens just follow the companion instructions .. ( helped me first time I installed a wrong tft ( z1 instead of z1c )
best
bob

BobderDritte said:
hey happend to me 2 days ago when I tried to install a custom rom
what I did: I startet flashtool on my pc connected the phone .. used volume up + power to shut it down .. and then ( i cant remember ) just used the volume down button or volume down + power ..
'why ? because I was not able to connect via usb to PC because the phone wasnt booting at all .. BUT I was able to enter fastboot and I recognized this via flashtool .. then; I installed a complete stock TFT
another option is to start sony companion, click on update then on repair .. follow the instructions .. shut down your phone with vol up + power and try to enter fastboot , companion will recognize your phone. if this happens just follow the companion instructions .. ( helped me first time I installed a wrong tft ( z1 instead of z1c )
best
bob
Click to expand...
Click to collapse
Hey!
Nice to Hear that its end to you in easy way, but for me nothing worked and I am not new in flashing or fastboot. Just nothing worked not comparsion or what ever. They sayed in service that battery was dead and for that reason it fryed somehow the mothrbord too.
Good if to othrer people this ending normally, like soft brick.
Peace for all!!!

casiocas said:
Hey!
Nice to Hear that its end to you in easy way, but for me nothing worked and I am not new in flashing or fastboot. Just nothing worked not comparsion or what ever. They sayed in service that battery was dead and for that reason it fryed somehow the mothrbord too.
Good if to othrer people this ending normalli, like soft brick.
Peace for all!!!
Click to expand...
Click to collapse
I am sorry for you .
I am also flashing for years roms and stuff, playing around with multiple devices.
The day before yesterday I really thought I bricked my first device.
What I actually did, after starting flashtool, I played around with the hard buttons ( phone was plugged id ) until I recogniced that flashtool recogniced the device
But I tried to charged the xperia befor for at least 2 hours ( red light was blinking all the time )
I dont believe that you brick / destroy your phone that way !

bbmt22 said:
sorry for my english
i have 2 xperia Z1 compact i used a full phone backup from TeamWin Recovery Project from my old one and tryed to aplly it to the new one, but when i finished updates the phone didn't start anymore
when i plug it into the charger usb or computer it starts blinking in red .
phone wont turn on, tried the red button off button, tried the power and volume button, when in charge it keeps flashing a red light, no vibration and nothing detected on computer.
i tried s1tool to repair it after connecting testpoint but i got a message saying " MINOR ERROR [ 0x80080021_, err: 0017 ] --------- error while uploading final HDR block"
PROCESSING ...
1/2/2015 3:59:06 PM SERIAL NUMBER : 1B9C3C06
1/2/2015 3:59:06 PM HARDWARE ID : 04000100E1007B00
1/2/2015 3:59:06 PM HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
1/2/2015 3:59:06 PM Emergency loader uploaded ...
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
1/2/2015 3:59:07 PM LOADER AID: 0004
1/2/2015 3:59:07 PM DEVICE ID: 063C9C1B
1/2/2015 3:59:07 PM FLASH ID: "0011/01000010"
1/2/2015 3:59:07 PM LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM WRITING PACKAGES ...
1/2/2015 3:59:07 PM Processing package
1/2/2015 3:59:07 PM C:\Users\BBMT\Desktop\fw\amami_testpoint.SIN_FILE_SET
1/2/2015 3:59:07 PM
1/2/2015 3:59:07 PM MINOR ERROR [ 0x80080021_, err: 0017 ]
1/2/2015 3:59:07 PM error while uploading final HDR block
1/2/2015 3:59:07 PM Break.
1/2/2015 3:59:07 PM FINISHED"
, what can I do?
thanks for helping
Click to expand...
Click to collapse
At least you still have one

BobderDritte said:
I am sorry for you .
I am also flashing for years roms and stuff, playing around with multiple devices.
The day before yesterday I really thought I bricked my first device.
What I actually did, after starting flashtool, I played around with the hard buttons ( phone was plugged id ) until I recogniced that flashtool recogniced the device
But I tried to charged the xperia befor for at least 2 hours ( red light was blinking all the time )
I dont believe that you brick / destroy your phone that way !
Click to expand...
Click to collapse
Hey!
I was charging it like 4 hours, nothing, then trying it with pc,to flash or fastboot, but Nothing, then charged like 10 hours(red light flashing all the time. I saved from disaster like this my old xperia Acro S), but still nothing. After that I charged it like 20 and still nothing. It Not worked for me.
Peace for all!!!

casiocas said:
Hey!
Nice to Hear that its end to you in easy way, but for me nothing worked and I am not new in flashing or fastboot. Just nothing worked not comparsion or what ever. They sayed in service that battery was dead and for that reason it fryed somehow the mothrbord too.
Good if to othrer people this ending normally, like soft brick.
Peace for all!!!
Click to expand...
Click to collapse
casiocas said:
Hey!
I was charging it like 4 hours, nothing, then trying it with pc,to flash or fastboot, but Nothing, then charged like 10 hours(red light flashing all the time. I saved from disaster like this my old xperia Acro S), but still nothing. After that I charged it like 20 and still nothing. It Not worked for me.
Peace for all!!!
Click to expand...
Click to collapse
ok .. sorry to hear
peace

casiocas said:
Hey!
I was charging it like 4 hours, nothing, then trying it with pc,to flash or fastboot, but Nothing, then charged like 10 hours(red light flashing all the time. I saved from disaster like this my old xperia Acro S), but still nothing. After that I charged it like 20 and still nothing. It Not worked for me.
Peace for all!!!
Click to expand...
Click to collapse
Better late than never..
My Z1c has this bug on a regular basis. What helps here is: hit the reset button (next to the sim card, press for 5 secs). Sometimes I have to do it twice.
Afterwards it starts charging (constant red light, no flashing one), and after another 10-20 minutes I can boot it up again.
I suspect it's some sort of hardware bug. I tried approx 10 different cables on different PCs and different wallplugs. The only thing that works reliably is the wicked chili car adapter together with a sony cable - absolutely no issues with that one. If I need the phone fully charged FAST, I take it into the car, lol.

t.kay said:
Better late than never..
My Z1c has this bug on a regular basis. What helps here is: hit the reset button (next to the sim card, press for 5 secs). Sometimes I have to do it twice.
Afterwards it starts charging (constant red light, no flashing one), and after another 10-20 minutes I can boot it up again.
I suspect it's some sort of hardware bug. I tried approx 10 different cables on different PCs and different wallplugs. The only thing that works reliably is the wicked chili car adapter together with a sony cable - absolutely no issues with that one. If I need the phone fully charged FAST, I take it into the car, lol.
Click to expand...
Click to collapse
XD never heared of that... Funny

Related

HELPPPP! My SX66 Dead

10-01-2007, 10:44 PM
Hi ...
is Helmi,Mamaich or everyone else kind enough to help me ?
i just had many errors and decides to erase my rom ...
then i got the password by monitoring the usb port while flashing new rom...
but rom's didn't flash to my device carefully.
i opened MTTY and used this commands to erase ROM :
password ~~~~b~~~0SQ~e000
erase A0000000 1E00000 (i think it's entire of my ROM)
removed phone from cradle and soft reset , and my phone dead ! ...
no power up, no bootloader screen, nothing ! just a black screen while i'm doing anything ...
usb no longer recognize my device ... and flashing tools neither !
HELP PLZZZZZZZZZzz, i'm in a bad trouble

Help recover from HARD BRICK

Hi
I was asked to fix a dead Sony phone, the label says Model: D5503, so I assume it's a Z1 Compact, I'm am a noob with smartphones, I have spent the last week googling for a solution, and here's where I am at:
I have tried all combinations of keys, no sign of life, except for the red LED. PCcompanion nor Flashtool couldn't detect it. The only way it is detected by the PC is by the testpoint method, and it is detected as "SOMC Flash device".
I have tried the testpoint method and S1tools from another post on this site, this is what I get:
will use Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
PROCESSING ...
SERIAL NUMBER : FF911606
HARDWARE ID : 04000100E1007B00
PRODUCT DETECTED: "MSM8974 OEM1 fused"
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: DEAD
DEVICE ID: 061691FF
FLASH ID: "0015/01000001"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
WRITING PACKAGES ...
Processing package
E:\Documents and Settings\Administrateur\Bureau\fw\amami_testpoint.sin_file_set
WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_RHINE1.2_LA1.04_19
PARSING: "DEVELOPMENT"
value OTP_LOCK_STATUS_1 : UNLOCKED, match UNLOCKED
PROCESSING : dbi_S1_Boot_MSM8974_Rhine1.2_19_AID_1_S1-SDI2-TEST-B316-PID1-0001-SDI_S1-BOOT-TEST-B316-0001-MMC.sin
MINOR ERROR [ 0x80080021_, err: 0017 ]
error while uploading final HDR block
Break.
FINISHED
Elapsed:21 secs.
I have downloaded a 1Gb file named: "D5503_14.4.A.0.108_Central Europe (1280-7864).ftf"
I have been playing with zipping files from it and renaming the zip to SIN_FILE_SET. S1tools was able to process the files and flash them (I guess), but the phone is still dead.
The owner is an illiterate, so I doubt the problem originally happened due to a flashing gone bad.
I obviously have no backups of any kind, no TrimArea, nothing.
Questions:
1. Is it still possible to revive this device ?
2.Is it a question of zipping the right files in a SIN_FILE_SET?
Thanks for reading.

Help !! HardBrick Redmi Note 5 pro

"i'm sorry about my english "
today i tried to flash stock rom and my little brother pluged out the cable when it's working.
my phone is dead !!
no logo, no booting, no recovery and no fastboot detecting
i tried to open the back cover and enter EDL mode but no luck.
phone screen is lighting up with grey light, that's it, nothing else
any one can help me ?
" Update "
I managed to start edl mode via test points and i have the right driver listed in device manager (Qualcom HS-USB QDLoader 9008)
but when i'm trying to flash rom show me messgae " read Hello packet "
and it's ended with message " write time out, maybe device was disconnected "
tried to change folder location and installing another version of miflash and still have the same error "
any advice ?
miflash log
[5:21:52 PM COM3]:MiFlash 2018.11.15.0
[5:21:52 PM COM3]:flash in thread name:COM3,id:5
[5:21:52 PM COM3]:sw in images
[5:21:52 PM COM3]:flash in thread name:COM3,id:5
[5:21:52 PM COM3]:[COM3]:start flash.
[5:21:53 PM COM3]:cannot receive hello packet,MiFlash is trying to reset status!
[5:21:54 PM COM3]:try to reset status.
[5:21:56 PM COM3]:write time out try agian 1
[5:21:58 PM COM3]:write time out try agian 2
[5:22:01 PM COM3]:write time out try agian 3
[5:22:03 PM COM3]:write time out try agian 4
[5:22:06 PM COM3]:write time out try agian 5
[5:22:08 PM COM3]:write time out try agian 6
[5:22:11 PM COM3]:write time out try agian 7
[5:22:11 PM COM3]:error:The write timed out.
[5:22:11 PM COM3]:System.Exception: write time out,maybe device was disconnected.
at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count)
at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count)
at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[5:22:11 PM COM3]:no provision exit:COM3
[5:22:12 PM COM3]:flashSuccess False
[5:22:12 PM COM3]:isFactory False CheckCPUID False
[5:22:12 PM COM3]:before:flashSuccess is False set IsUpdate:True set IsDone True
[5:22:12 PM COM3]:after:flashSuccess is False set IsUpdate:false set IsDone true
" solved "
i have beed nsolved my issu by entring EDL mode, then open miflash and download anti_test_note5 rom
first try faild, but when i restart again and enter edl mode again, miflash detect my phone and starting flash the rom.
then flashed the stock rom, finaly my phone come back to life

"The system has been destroyed"

Just got my mi 9 SE bricked through an OTA update.
I think I already tried most of the suggestions around:
- xiaomimiflash
- miflashpro
- mipcsuite
- xiaomitool
- xiaomitool v2
Also tried both available ROMs in miui website.
Locked bootloader, and I can enter fastboot mode.
How am I supposed to fix this? I need my phone back.
you dont... send it back to seller
---------- Post added at 03:35 PM ---------- Previous post was at 03:22 PM ----------
or bring it to a mi service center. that is the official response at the moment https://c.mi.com/thread-2251372-2-1.html
laviniu_c said:
you dont... send it back to seller
---------- Post added at 03:35 PM ---------- Previous post was at 03:22 PM ----------
or bring it to a mi service center. that is the official response at the moment https://c.mi.com/thread-2251372-2-1.html
Click to expand...
Click to collapse
the problem is that not even the seller has a solution.
Xiaomi on it's best, I can assure that it was the last xiaomi phone i bought
found a temporary solution:
- boot into fastboot mode. press volume down and power until you see the mi bunny.
- install and run minimal adb & fastboot on a pc
- plug phone to pc
- run "fastboot devices" you should see a line with device id & fastboot
- run "fastboot continue"
It will return to the previous version and you wont lose anything.
quick update/question:
anyone with 201903 working ota? or 201904 failing? (the manufacturing date is printed on the phone box back, bottom right near the sn barcode)
Yes, it’s work for me. But it must be repeated at each start. I fix it if I do a factory data reset ? Sorry for my bad English

can't boot into mass storage mode

Ive tried nearly every version of wpinternals but it will not boot into mass storage mode, fails to find a flashing profile :crying:
I selected the 'download all' option to download my ffu etc. Fails with this error in the screenshot:
Any ideas??
Device: Lumia 950
O, ****, i broke my neck.
Disconect phone, start wpi, retry.
---------- Post added at 07:11 PM ---------- Previous post was at 07:11 PM ----------
O, ****, i broke my neck.
Disconect phone, start wpi, retry.
augustinionut said:
O, ****, i broke my neck.
Disconect phone, start wpi, retry.
---------- Post added at 07:11 PM ---------- Previous post was at 07:11 PM ----------
O, ****, i broke my neck.
Disconect phone, start wpi, retry.
Click to expand...
Click to collapse
Sorry bro???
Do it again.
augustinionut said:
Do it again.
Click to expand...
Click to collapse
?Oh , man , I've tried it!! Is it worth trying the qcomm driver??
All the drivers are installed by wdrt.
augustinionut said:
All the drivers are installed by wdrt.
Click to expand...
Click to collapse
The 950 isn't being connected in mass storage mode!!! I wanna unlock bootloader, surely there's a solution!! It does step 1 of unlock, tries to boot to mass storage and just keeps rebooting finalizing in the 'failed to write to pipe' error. It's not 'connecting'. Is this a known prob with the 950???
Try with a clean version of WPinternals by deleting the configuration file in "ProgramData\WPInternals" and using version 2.8.
titi66200 said:
Try with a clean version of WPinternals by deleting the configuration file in "ProgramData\WPInternals" and using version 2.8.
Click to expand...
Click to collapse
Ok I'll try it after I downgrade. Again
Here's the log of fail to enter mass storage mode on my 950. I'm probably not the only one hope someone can figure it out.
update! I was able to unlock my 950 by removing sdcard
The 950 is now running arm64 windows ten:victory:

Categories

Resources