Develop Bugs

A bit harder than a soft brick

Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?

mikla90 said:
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
Click to expand...
Click to collapse
hope you can access fastboot. if yes you can install recovery and ifwi files from fastboot

How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.

Using xfstk tool
mikla90 said:
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Click to expand...
Click to collapse
open Xfstk Tool and click Tab -MRD/AO/BO +MOOR Ao+CRC then go to settings under option menu - enable GP Flag Override Option and Enter value - 0x80000807 and save (OK), then choose files -
FW Dnx - dnx_fwr.bin
IFWI - ifwi.bin
OS IMAGE - droidboot_dnx.img.POS_sign.bin
AND connect phone, press begin and Xfstk tool detect the phone and install the required files and you will able to get Normal Fastboot mode and install the firmware by fastboot / Asus Flash tool / or -SDUPDATE Zip file.
-------------------
Press Thanks Button, If i am helped you
-------------------

In the end, after about 20 times, XFSTK did flash what should have. Now, I'm back in business. I changed nothing, just kept trying.

Bricked ZE550ML I need help no USB logo neither vibrations

Hi,
My phone : ZE550ML
When I tried to update the TWRP recovery I installed .img file then everything collapsed.
My phone was only booting in bootloader, even if I chose normal boot.
I tried to install another .img file and since my phone doesn't want to do anything. No asus logo, no usb logo, no color nothing.
When I press power button nothing happen however how long I press even with volume button.
I charged it for a day long then I tried like a lot of times this procedure : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 .
(Surprisingly when I connect my phone to my computer sometimes the xfstk software recognize it)
But I always get : FW+OS download did not complete because of limit reconnecting to device attempt number reached.
Does someone have any idea ?

Problem with M HORSE S80 and SP Flash Tool

Hello, I have a big with SP Flash Tool and my chinese phone M HORSE S80 :
ROM for M HORSE S80 (as known with Mpie N9700 name too, it's a generic phone) :
I a new user, so I can't post links but you can type in Google, M horse s80 rom, and go to needrom link
-In June 2016 (dates are important), I tried to flash my M HORSE S80 on my MacBook on Windows 7 32 Bit, it flashs ok the first time, I tried this a second time, but flash stops, and my phone won't power on . I tired several times, but I can't finish the flash, even if I format the NAND Flash.
-During few months, I keep the phone on shelve, and in January 2017, I retry this, with the same method, the same rom, etc ... and, it's strange but it's works the first time, when phones power on, there is a button for wipe cache partition and data partition, I click on this button and it's boots perfectly.
-This Sunday, I tired to flash the phone, but it's dosen't works. I will explain this :
+I tried differents OS and computers, Windows XP, 7, 10 on my Dell computer; 7 on my Mac, and it's dosen't works, I reinstalled clean Windows 7 10-15 times on my PC/Mac
+I can say something : When Preloader VCOM drivers was freshly install, SP Flash Tools recognize this driver as VCOM Drivers for 3-4 times, and after it changes automatically (only VCOM)
+Another thing : When SP Flash Tool is very speedy to flash the phone, phone is automatically disconnected and I have 4008 error (like in June 2016) . But When the program flash very slowly, flash goes to 100 percents, and say green tick. There is more chance to have a working phone in this situation.
+I know this is the good rom, because I flash this in January and it's works perfectly before
+I don't know if it this a hard brick or soft brick phone, because, When I try to power on with good battery, nothing happen in the screen, but when I connect to computer, phone is reconigzed .
+But when I put good battery and I turn on, Flashlight is activated for milliseconds. And when I tried to do another reflash, now flashlight is not activated, but phones vibrates for milliseconds.
+I tried to dissasemble the phone, to disconnect all cables ( screen, wifi, etc ...), and put another battery of another m horse phone, and it's dosen't work
+At the begin, when I flash for the second time, I can see the boot screen, phones tries to boot (I can see the animation and the boot sound for milliseconds, and there is a bootloop, and when I wait 10 minutes after, screen goes black)
+I tried to follow the instructions exactly, but it dosen't work (for example you need to press volume - button when it's flashing)
+I tried every combinaison for go in recovery mode, but there is no access to recovery mode (but there is a recovery mode when I go in mediatek update program, when I'm in Android)
+I tried new, old, etc ... of SP Flash Tool
+I tried differents USB cables
So, I don't know what SP Flash Tool and my phone do, i don't know why it's works in January and not in April or June, maybe i think that i need to wait few months for try to repair the phone, but I want to repair this phone, and I indicate all what I do, so help me please .
Thank you for reading.
PS : I'm French, so it's difficult to me for talking in English.

Resolved problem
Hello, today, I can say I finally resolve my phone problem : I think this is the solution :
-You need to dissasemble the phone
-Place a fan on the motherboard of the phone (The NAND Flash is very hot, so this is why the phone disconnects automatically when you flash the phone)
-After this the flash should go at 100 percents
-Then try to download ZOPO 6560 ROM (the KitKat version)
-Extract userdata and cache file from the ROM
-Put this in SP Flash Tools, and then flash only these 2 files
-When it's done, power on the phone, and try to wait few bigs minutes, normally it's should work, but if it's didn't work, try to do something with cache and userdata files, I don't know
So this is my solution that I want to share if there is some bricked-china phones

bricked zenfone 2 ZE551ML

Hi,
long story short:
- worked for few hours, then refused to start, black screen, just vibrating
- bought it from my mom, by the time I got to see her, too late to retrun the phone. Seems like was a chinese import (I'm in France) so no ASUS support and too late to return it to seller...
- so tried to unbrick it following https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785.
- Got the first steps ok (xfstk done)
- time to unzipthe stuff etc, phone turned off and PC rebooted for whatever reason
Where I'm at right now:
- nothing happens, not a vibration, not a detection in device manager, nothing... (I charged it)
-When plugged into computer, after a while, gets hot (more than battery charging, means CPU working like hell?)
Seems like dead for good? any hope to "reanimate it" at least to the fastboot to resume the precedure?
Thx much for your help, buying another one would be ... super sad and difficult
Cheers!

Try to flash using asus flash tool.
1. Download the lollipop raw firmware.
2. Asus flash tool
3. Drivers .
Now start the flashtool then select your device model from list then browse for the raw file that downloaded.
Now connect phone in boot loader mode.
Then click start it will take some time to flash. During flashing phone restarts at that time again boot it to bootloader mode.
You will loose total internal storage data.

R.sahane1 said:
Now connect phone in boot loader mode.
Click to expand...
Click to collapse
that's the issue, can't enter bootloader mode (phone remains completely dead even if charged, no vibration, screen remains black etc)
thx anyway

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.

I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical

wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?

I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.

I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.

When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.

With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.

I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.

Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.