ZE551ML unable to Unbrick - ZenFone 2 General

Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link https://www.youtube.com/watch?v=BJPEc1NG_k8&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.

Linx91 said:
Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link
&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.
Click to expand...
Click to collapse
same here brother...i am stucked from last night..getting no help nowhere..really upset..plz let me know if you figure out something.

Which raw file version are u using

Related

[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recovery

DO NOT FLASH HYDROGEN ROMS ON HELIUM, OR YOU GONNA HAVE A HARDBRICK.
IN CASE YOU HAVE ONE, HERE IS THE SOLUTION.
This was tested with Xiaomi Mi Max 128GB helium and localized rom from xiaomi eu.
I am not responsible for bricked devices or anything else. So at your own risk:
1. Install official MiPhone drivers
2. Download and install MiFash beta.
3. Download and unpack TWRP for miflash: 32gb or 64-128gb thanks @Abdess76.
4. Download ROM for your device, I recommend to try this one. You can install RR/CM Rom as well.
5. Run MiFlash with admin rights.
6. Turn off the phone, plug the cable to PC and halfway to the phone.
7. At the same time press Volume + and Volume - and plug in the cable.
8. Refresh MiFlash phone should show up. (If it didn't then make sure you did it right and u got drivers)
9. Navigate to your unpacked TWRP and flash it.
10. Now, boot ur phone with volume up. It's a bit slow. If it's stuck on miui logo, just release button and wait.
From here start to pay more attention:
11. TWRP can ask for password, press cancel and allow modifications by moving slider.
If you just need ROOT and your current rom, skip to the step 16. Also there is a recovery from boot in system folder. If you won't remove it, recovery may be replaced with stock one after reboot. Keep it that way if you want OTAs.
12. Format data.
13. Enable MTP and put modified zip in your phone.
14. Go to mounts and unmount system **
15. Flash your rom.
16. Flash latest supersu.
17. Reboot the phone.
In case u got NO OS message, then it means that u probably ignored step 15.
Also first boot may take like 15-20 minutes, since eu rom is deodexed.
Just to be sure, after installation mount system partition and navigate to the /system folder using TWRP's file manager and make sure it's not empty.
* In my case system didn't install because script could mount system partition since it was already mounted.
P.S. In order to update, you need to install OTA for offical rom via TWRP. Then without rebooting flash SuperSU, and finally using TWRP's file manager navigate to system folder and delete file named recovery from boot. Doing so will keep root and recovery.
Thank you so much for the guide! I will try it tonite
Waiting for boot loader is just too long..
WOW!!!! Just, wow..... I can not believe it but it worked like a charm. It took me forever to figure out my issue with the drivers, but after solving that I followed you step-by-step. And, lo and behold, it WORKED! Note for other users, Twrp took about a minute or two to finally boot up and it took me personally about 15-20 minutes before MIUI 8 finally booted. Just wait it out and you should have the amazing results that Doom Slayer has so graciously provided you
THANK YOU!!!!
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
flywithme said:
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
Click to expand...
Click to collapse
Yeah, dirty flash is you keep your data and format system and caches .
Clean flash is u format data as well.
The thing is that u have root, and ur phone is also secured. It's linked to ur Mi account, while it's locked. It's better to keep that way
Theoretically If you will ignore steps from 12 to 16. (Maybe u can ignore data formatting too)
Then you can get a ROOT and TWRP on your current rom.
And also theoretically while on miui 8 rom ,u can try to unlock bootloader without waiting.
Try this manual.
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Open it up and remove battery for a few minutes, then try again from step 6...
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Which rom did u flash, give the link please.
Are u sure it's for your version? It can be a broken file as well.
Does the device connects when u hold both volume buttons?
It's called emergency download mode, u can istall rom with miflasher.
There is a testpoint method also.
All u need is a pic from this post on http://4pda.ru/forum/index.php?showtopic=749580&st=700#entry51154086
U need to disconect battery, connect testpoint to battery and flash ur device with miflash.
After that let it charge, since this in your state phone consumes battery.
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
agreusar said:
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
Click to expand...
Click to collapse
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Doom Slayer said:
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Click to expand...
Click to collapse
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
agreusar said:
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
Click to expand...
Click to collapse
Well, I guess system was mounted and it gived u the error,but formatted it.
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
alain belay said:
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
Click to expand...
Click to collapse
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Updated tutorial.
Uploaded TWRP for helium, so you don't need to edit updater script anymore, since script will get correct model.
Now you can try to get root on your current rom and unlock bootloader without Xiaomi's confirmation.
People having helium with unlocked bootloader may also have problems installing roms from xiaomi eu, if they have TWRP from hydrogen.
You may update using my recovery.img from archive using fastboot, or TWRP(will also work for locked bootloader).
Doom Slayer said:
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Click to expand...
Click to collapse
hi Doom. Thank you for reply. But what do you mean by " disable drivers signature". I did not do anything but install the drivers and when I am on what I think is EDL mode(screen isi black) the driver is recognized as Qualcomm HS-USB QDLoader 9008(COM20).
Anyway, I will give another try and let you know. Thank you again.
---------- Post added at 09:14 AM ---------- Previous post was at 08:22 AM ----------
I followed your guide and I could get the twrp installed. So I tried to install rom(following your link). It said rebooting in 5 seconds, and then nothing. The screen is black, no power anymore, no logo, no vibes, and no life at all.
I cannot get any more reaction from it. I plugged it to my pc, but nothing is connected. I was so happy with twrp working... Any idea?...
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
alain belay said:
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
Click to expand...
Click to collapse
Looks like you installed hydrogen TWRP and that caused all your problems.
I've been very careful to install the helium twrp from this thread...

asus zenfone 2 bricked while updating to marshmallow by TWRP RECOVERY

Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Follow the steps:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Same happend to me, can't even unbrick it.
Z00A bricked
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
kazzot17 said:
Same happend to me, can't even unbrick it.
Click to expand...
Click to collapse
Did you and all others who are having trouble with the zenfone make sure to flash any custom kernel for your rom?? If one is available.. Just a suggestion.. Make sure you're trying to flash the right device and exact model, any follow any guides properly. Go back over and read each step thoroughly just to rule out any steps you may have missed along the way
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
Sent from Sony Xperia Z5 E6653
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Yeah, I got that far. I'm hoping for a way to unbrick it now.
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
I was on stock rom.
TheTecXpert said:
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
[email protected] said:
I was on stock rom.
Click to expand...
Click to collapse
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
That is what I'd like to do but I have not found a way to do that.
TheTecXpert said:
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
same here
Ok ... first of all..
Do you have all the necessary files on your external SD CARD ready??
------------------If yes then continue on-------------------
1. Open up adb and fastboot with admin privileges..
2. connect your device to your PC in ADB mode
3. in ADB cmd type adb reboot bootloader
***If you have already completed step 4 below previously and you are sure you already have a custom recovery (TWRP) installed on your device, then skip straight to step 5***
4 fastboot flash recovery [nameofrecovery].img (Without the brackets and also Make sure The Recovery.img file is SPECIFICALLY for your MODEL.. ***ZE550ML***
5. While your device is still connected to your PC in either ADB or fastboot mode
in ADB just type the following command below
(if connected via adb) - adb reboot recovery or adb boot recovery
(If connected via fastboot) - fastboot reboot recovery or fastboot boot recovery
IF you device reboots in to TWRP successfully, then all you need to do from this point is...
1. wipe data/Factory reset
2. wipe cache partition
3. reboot now.
you should now be able to boot your device like normal
good luck
let the process complete.. after factory reset is complete proceed
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
t00lshed said:
same here
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
utsav.goswami1986 said:
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
t00lshed said:
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
Click to expand...
Click to collapse
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
sukhwant717 said:
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
Click to expand...
Click to collapse
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
t00lshed said:
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
Click to expand...
Click to collapse
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
sukhwant717 said:
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
Click to expand...
Click to collapse
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
t00lshed said:
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
Click to expand...
Click to collapse
can you please upload xFSTK log file
you are using windows 10 did you disabled driver signature enforcement before installing xFSTK and driver?

Probable brickage of TN7

Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839

Fastboot broken?

I'd installed TWRP and was playing with some ROMs/Kernels when I hit a boot loop. I then used Flashtool ("Emma") to restore to factory. I haven't been able to send Fastboot commands since. I was wondering if anyone here might be able to point me in the right direction to help me sort this out.
When I connect the phone while holding volume up I still get a blue LED, but when I try to send a fastboot command besides "help", I get "waiting for any device" on Windows. On Mac, Terminal just hangs. I've been able to get the Mac to return the device ID using the "devices" command, but this is intermittent. Normally even this command causes Terminal to hang.
ADB debugging is "on". Flashtool works. ADB commands work. The phone can boot without issue. I can successfully get "fastboot help" to work.
What I've tried:
wiping the Mac HD, installing a fresh OS and installing the latest version of Fastboot from the SDK
Installing the Windows drivers directly from Sony and the latest Platform Tools directly from Google
Running "sudo fastboot" from Terminal on the Mac
Using various usb ports on both machines
Rebooting both machines between steps
Reflashing both Marshmallow and Nouget using Flashtool.
The USB cable I'm using is the one included with the phone. I could issue fast boot commands over this cable a few days ago.
Anyone got any ideas about what I've done wrong here? I'm really confused and I'd like to get rooted again if at all possible.
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
ondrejvaroscak said:
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
Click to expand...
Click to collapse
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
I got that error last time I updated, and was puzzled but tried to leave the phone in flash mode (green led) and flash it again. (I did not unplug the phone so I did not see the result of the first flash) This did leave flashtool without the initial phone info, checking for root and all that but this time the firmware flashed. I did include the fsc file into the ftf, I have no idea if it was a fluke or something but second flash with the phone already in flash mode worked. I know it sounds crazy but It might be worth a shot. Other than that it sounds like a bad cable with the inconsistent fastboot behavior but then again you could flash with Emma, which in turn should not affect fastboot. Odd.
88% said:
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
Click to expand...
Click to collapse
I would definitely try diferrent cable!
The Software update error means there is inconsistency in flash memory and bootloader fails to load initial image after flash. Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode. Then let it boot and when it work, flash your desired version of firmware..
So I tried a number of images built from Xperifirm downloads and finally got one of them to flash properly. I'm not sure if this was due to the specific image or if I just got lucky, but my phone can boot again!
ondrejvaroscak said:
I would definitely try diferrent cable!
Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode.
Click to expand...
Click to collapse
OK, I can try that. Just to confirm, is this a step that I should still take given that I can boot now? While I can boot, I still can't get into Fastboot through Terminal. I was successfully able to get a device ID using the "fastboot devices" command once, but running this command a second time caused a full system freeze on my desktop.
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
edit: I ran into this issue again and noticed that I missed a step in my original reply. In order to get Fastboot working again, I needed to connect using adb and tell the phone to remember my computer on the prompt.
88% said:
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
Click to expand...
Click to collapse
thanks for posting the cause/what you did to fix it.
it might help others, which is what the community is about.

Unable to hack Asus Zenfone Laser 2 [ZE550KL - Z00L - Z00LD]

Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Uhm... no replies till now?
i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help
When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere
I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.
Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.
These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.

Categories

Resources