Develop Bugs

[Q] Z1C flashing red light

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

Nexus 7 bricked ? Nothing helped

Hello Community,
for learning programming skills, I bought an ASUS/Google Nexus 7 Wi-Fi 32 GB (2013).
All I wanted is to reset it to factroy defaults, so I chose to reset it (Android 5.01). The tablet rebooted. The screen showed the message "Deleting..." for about 10 hours, afterwards it showed an android robot with a red triangle containing an exclamation mark. It boots in a endless loop between Deleting-screen and trianlge-screen.
After reading a lot of "helpful" thread in different forums, I installed android developer tools and android studio under Win10.
I booted the Nexus 7 into bootloader mode (Power + Volume down, bootloader flo-04.05) and typed in: fastboot devices, which showed a serial number.
Later I typed: fastboot oem unlock. Windows tells me the tool "erases user data".
This erasing never takes an end. I inrterrupted it, which led to a message: "Status read failed (too many links)".
I tried:
- different USB ports
- different non-original micro-USB-cables (Amazon, Kindle-cables)
- executing fastboot as administrator (executing cmd.exe as admin)
The android tools installed to "c:\Users\NAME\local\Android\..."
The android studio installed to "f:\Programs\Android..."
The device manager tells me Win10 recognized an "Android device" -> "Android bootloader interface" Version 11.0.
At this moment I´m very dissapointed about this tablet and the complexity of solving problems.
Would be great if some tips can help bringing this device back to life for developing.

Hi try the wug fresh toolkit. This tool is amazing. Search for it & watch some videos. All the best.
---------- Post added at 02:29 PM ---------- Previous post was at 02:18 PM ----------
nexus root toolkit . wugfresh.com

Ok, Need a Little help with that tool.
It´s a Nexus 7 2013 Wi-Fi tablet, but I never saw the Build number. I think it´s an Android 5.1.1.
But, I hope it doesn´t matter. How can I just unlock it for flashing a new Android-Image ?
---------- Post added at 07:37 PM ---------- Previous post was at 07:06 PM ----------
WUGFRESH doesn´t work.
sending bootloader
sending boot
erasing Cache
sending recovery
erasing System
All of this gets the message: FAILED (remote: bootloader is locked)..
Is there anyone who can help ? I just want to develope using this device.

Tried solving the problem for several days now.
Wugfresh doesn´t work because of the locked bootloader.
ODIN3 seems to be the wrong program for this.
Now I installed android sdk platform-tools under Mac OS X 10.11.
Fastboot devices works, fastboot erase cache does work, too.
But, I interrupted fastboot oem unlock at "erasing userdata" after 10 hours. Under Win10 I got the message "status read failed (too many links)".
Now, using Mac OS X, I got: "ERROR: usb_read failed with status e00002ed. FAILED (status read failed (No such file or directory))".
Did I unterrupt the oem unlock (after 10 hours für 32 GB erasing userdata) way too early ?
Would be very great if someone gives me the right hint for solving this problem.

Hm, is anything wrong ?
Can hardly imagine that no one is able to help a newbie...
Thought, Android is an open platform with a lot of help...

blebbens said:
Hm, is anything wrong ?
Can hardly imagine that no one is able to help a newbie...
Thought, Android is an open platform with a lot of help...
Click to expand...
Click to collapse
Hey, I think a lot of the guys are off trying to get MM to work on their N7 - systems images came out yesterday
Unfortunately I have something very similar to you so I hope your will be ok
Was the bootloader unlocked before you tried this ?
Wugfresh has an "unlock bootloader" option - have you tried this ?
If so can you cut and paste the error messages you are getting please ?

Ok, I came up with this problem before MM launch.
The screen I see with Power and Volume down pressed tells me, the device is locked.
Wugfresh tells me all of its tries failed because of a locked bootloader.
The tool is not able to unlock the bootloader. My reply #3 told about this problem...
I am so... dissapointed and a bit angry. Nothing works...

"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

My Mi Max 3 got bricked after doing a OTA update, totally dead, how to do EDL?

The background
My mi max 3 decided to do a ota update overnight and then it got hard bricked. While charging the charge light no longer goes on and all manner of button pressing does not get any response. All 3 buttons, power and volume up/down all do nothing. The phone appears totally dead.I tried the various button combinations while a usb cable to the pc was plugged in. The phone is not rooted, it was never installed with any custom roms, and has been using the global stock rom since day 1 in sep 2018. The last ROM I was on was global stable 10.3.3.0 PEDMIXM.
What I've done
I managed to get my xiaomi account authorized, and then I used miflash 2018.5.28 to flash the latest global stable ROM 10.3.3.0 PEDMIXM, but the flashing kept going and did not stop even after more than 10 minutes.
I also got many 'cannot receive hello packet' errors.
Now when I try to reflash again, I get a message saying my account is not authorized.
My phone is still dead, totally black screen with no charging light when charging.
Can anyone help? I tried opening but I can't figure out how to do it, it's too tight. I can't send it to the service center either, as this is an export set and they insist that they will only fix local sets. If there is someone who can assist remotely I can pay a fee too! But only if it works.

Tried to reset by shortcut buttons? This will reset your device and data will be lost. You can back up files via fastboot.
Do you have unlocked bootloader?
If so
1) Flash TWRP and then a Rom, like Xiaomi.eu the latest versions.
If no
2) Try to unlock even with the broken Rom. If you have your linked Xiaomi account, you can get it. You can change the OEM unlock flag by fastboot. If you can, go back to step 1.
If nothing works, then you have to go to the authorized or through the test point.
I always unlock my devices, because in case of errors, I can resurrect them through TWRP.
Good luck.
PS. Try logging in with a Xiaomi account at Xiaomi Tools.
---------- Post added at 02:48 PM ---------- Previous post was at 02:38 PM ----------
There are some contacts over the internet that connects to your machine via Team Viewer and log in with an authorized Xiaomi Tools account and you will be able to pass a new Rom.
Search the internet and Xiaomi forums.
Perhaps this is the fastest and safest way.
Generally this service is charged but pays off.

I maybe have a solution for you. I am going to write you instructions later today with some modded files you can try out.
---------- Post added at 11:09 AM ---------- Previous post was at 10:54 AM ----------
Try this
1. download MIUI 10 V10.0.3.0.OEDCNFH and extract it to folder with a short name (less then 7 characters)
http://bigota.d.miui.com/V10.0.3.0.OEDCNFH/nitrogen_images_V10.0.3.0.OEDCNFH_20180914.0000.00_8.1_cn_e343c7cf58.tgz
2. download "Bypass EDL Auth replace file from fastboot version.zip"
https://mega.nz/#!GIo22IAA!FZGxQaw0dIieQhvvAsFlpclIXmKm-tb_4576Q12yffQ
3. extract "Bypass EDL Auth replace file from fastboot version.zip to a temporary location and replace the file prog_emmc_firehose_Sdm660_ddr.elf in the MIUI 10 V10.0.3.0.OEDCNFH firmware folder.
4. try flashing again with Bypass EDL Auth replace file from "Bypass EDL Auth replace file from fasstboot version\MiFlash2018-5-28-0\XiaoMiFlash.exe"
Good luck. Hope it works for you I have not tried it myself

Soft unbrick
TRY THIS! I SOMEHOW UNBRICKED MY DEVICE
CREDITS TO XDA FORUM
(https://forum.xda-developers.com/mi-max-3/help/guess-somewhat-kinda-bricked-nitrogen-t3848922)
First, check if your phone is being detected as Qualcomm HS-USB QDLoader 9008 (if not do test point https://en.miui.com/thread-3765172-1-1.html)
Second Install Xioami Mi Flasher Beta Version
(http://en.miui.com/thread-281979-1-1.html)
Third download this flash boot ROM
(http://bigota.d.miui.com/V9.6.12.0....EDCNFD_20180820.0000.00_8.1_cn_5e8d0ddf88.tgz)
Forth Unzipped the .tgz file and get/move the .tar file to C:\ (Computer Disk Drive)
Fifth, Rename the .tar file to MiMax3.tar
Sixth, extract the file
Seventh, Open the Xiaomi Mi Flash Tool Beta Version then locate the file Mimax3 (C:\Mimax3\nitrogen_images_V9.6.12.0.OEDCNFD_20180820.0000.00_8.1_cn)
Eighth Select Clean All and Flash
If error occured long press the power button and release it once sound connected, refresh or close the Mi Flashtool then flash
I hope this one can work. My Mi Max 3 is working again.

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: