Hello, after running the LP downgrade script provided in AICP thread to downgrade my bootloader to LP, it hangs at ASUS logo (splashscreen, not bootanimation). Before that I was running Dirty Unicorn. After that, i used xFSTK to unbrick and it reboots to fastboot. But it shows serial number 01234....DEF (i know it's normal) and product name changed to Z00A while mine is Z008. I'm sure i used the correct xFSTK files from amtech.vn. I used AFT to flash, the fastboot status line show different commands and stopped at RESULT: OK. After that, it doesn't flash anymore despite AFT still running. When I disconnected my Z008 and rebooted to bootloader again (@fanfan54) mentioned it in his unbricking thread), it shows USB logo and I unbrick again like above. After AFT and RESULT: OK, I disconnect and rebooted to fastboot, the serial number still like that and device was Z00A, not Z008. I tried AFT again and disconnect, reboot and now it shows USB logo!!
I unbrick by xFSTK then i loops the above steps, still can't unbrick. Now i plugged it to charge, it shows USB logo and the screen keeps on, so it heat up and annoy me very much
Please reply me soon. Thanks in advance:crying::crying:
I solved myself by this thread: http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Hello, my Asus zenfone 2 after a restart will not boot up anymore, once turned on, it will go to the Asus "in search of incredible logo" with "powered by android at the bottom" and will stay there for 1-3 minutes then turn off, vibrate in 2 little bursts and do the same thing it did before, and it never exits out of this stage, i have tried booting to fastboot (volume up and power) but nothing happens , i really need to use the phone and any help would be appreciated
Use xFSTK-Downloader tool before installing this tool, Install Intel SOC-Driver and Then XFSTK Dowloader and choose proper Recovery files for your model (ZE551ML and ZE550ML) it will repair the Bootloader and enable you to load into Normal Mode Recovery (Fastboot) from there you can try to Erase Cache and Data and try to rebot normal, if fail then try to install Raw Image with the help of Asus Flash Tool, all the tools and files are available in other Help forum with links...
-------------
Press Thanks Button, If i am Helped you
-------------
eimantuks6 ...have u got out of these problem from that helper post... i am also having same issue like u along a issue that when i complete power down phone and connect charger changing won't start phone boot and stuck on asus logo and repeat ... not for a sec charging symbol displays
---------- Post added at 07:25 PM ---------- Previous post was at 07:03 PM ----------
k576... when i flash files through xFSTK-Downloader "FW DnX" and "IFWI" get successfully and phone quickly boots and stuck on asus logo but os image status reconnecting ... and failed ..... display should be displayed flag symbol only after three files are flashed but my device is flashing only two files and booting ... i have used unlock app so i display white screen on boot .... is that white screen errors...
i have previously hard unbricked zenfone 2 no display only vibrate issue....
I have managed to fix the problem
So after hours of messing around with this i came up to a tutorial on youtube which i will link, he provides the files etc and a full tutorial, one thing i did encounter however is the xfstk etc programs do not want to work on anything other than windows 7, so i ended up running them in a virtual machine inside my desktop
right so as a new user i am not able to paste new links so either type in "Asus zenfone 2 stuck on asus logo", the video is by "Nimish David Mathew" or just paste this after youtube.com. "/watch?v=9FsdnIrnQYA"
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
audit13 said:
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Click to expand...
Click to collapse
timbernot said:
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
Click to expand...
Click to collapse
Thank you for your answers! Last hours been trying to flash the stock ROM back. However, when getting into bootloader, adb devices and fastboot devices don't show the device. Or it even freezes and gets into reboot loops again. So this is why I'm stuck, nothing seems to be working from all the guides and things I'm reading.
So precisely:
- Power off bootlooping device by holding power button
- Power on by holding PWR + VOL UP
- When vibrating: release PWR keep holding VOL UP
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
So what can I try to make connection?
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
timbernot said:
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
Click to expand...
Click to collapse
The bootloader in shows the following:
IFWI version: 0094.0173
SERIAL_NUMBER = F8AZFG0152** (couldn't read the last 2 digits as the device rebooted again). Also sometimes the SN shows 012345689ABCDEF.
I've much trouble keeping the device in bootloader. Last tryings it keeps shutting down after couple of seconds in the menu.
EDIT:
So far the device seems to stay in bootloader mode now. I can cycle through the options normal boot, recovery etc. Below the screen it shows Continue the fastboot process in blue text. I've inserted the USB cable but have been unable to get "fastboot devices" to show any device. ASUS Flashtool also doesn't do anything.
I'm going to try to find a micro SD adapter so I can try flashing stock rom in TWRP from the phone itself (would that be something that could work or is this phone fubar?)
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
timbernot said:
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
Click to expand...
Click to collapse
Thank you for your support! Will try again.
I have MM not LP.
I don't understand your reply correctly I think so here is what I think you say?:
I should obtain LP rom for ZE551ML
Next, enter bootloader via buttons PWR & VOL UP after 10 seconds being off !
When in the bootloader, - power and vol + (short press or long?) , when in bootloader ->
I connect USB to computer, flash the file using AFT if I make connection. -- flash raw (raw = LP ROM from ASUS) with AFT (asus flash tool )
Thanks again for your help
j4y_ha said:
Thank you for your support! Will try again.
I have MM not LP.
Thanks again for your help
Click to expand...
Click to collapse
IFWI version: 0094.0173 is LP, NOT M
follow my first reply:good:
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
No1
Hi there , in TWRP select reboot then power off .
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
no2
Enter bootloader via buttons after 10 seconds being off !
no3
When in bootloader you are on LP -- flash raw with AFT (asus flash tool )
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
j4y_ha said:
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
Click to expand...
Click to collapse
I'm taking wild guess here that you got wrong TWRP recovery installed somehow or something from M causing all these problems , when you get into bootloader again..Scroll to and select reboot bootloader and fastboot flash stock recovery for LP version you was on .
Then , I guess your problems will be over , where you will be able to flash raw in bootloader or in stock recovery , adb side load the firmware
Thanks for your quick anwer. Will try to get through it haha :good:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
j4y_ha said:
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
Click to expand...
Click to collapse
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Thank you for your thourough answer Ryankabir! Much appreciated. My answers are below. I will try your suggestions soon.
ryankabir said:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Click to expand...
Click to collapse
Yes I do know what I can do with it, but it just so complicating as there are different factors like the loops, not being able to get connections with USB. I mean, it is not totally bricked since sometimes I can get into TWRP or bootloader.
ryankabir said:
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
Click to expand...
Click to collapse
Well, since the phone worked fine before the battery issue, there is some sort of link between the issues I would think. Maybe I've broken some hardware during the battery removal or did the booting into charging mode and on/off continously corrupt some memory leaving me with weird crashes & loops.
ryankabir said:
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
Click to expand...
Click to collapse
Although I'm not sure if I have the correct TWRP, it did flash CM13 correctly back in FEB 2016 and haven't found a need to update it ever since as it worked fine during the occasional update...
ryankabir said:
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Click to expand...
Click to collapse
No, D2W is not there. The phone is totally unresponsive to the power button as well as D2W. When in TWRP the touchscreen functions fine until it freezes at some random moment.
ryankabir said:
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
Click to expand...
Click to collapse
Yes I know what drivers are :good: - I've tried IntelSoc, Intel ASUS etc... all drivers that are somewhere mentioned I have installed. Before the charging problem I was able to connect the phone and access files fine as well.
ryankabir said:
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Click to expand...
Click to collapse
Thanks, will try more!
ryankabir said:
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Click to expand...
Click to collapse
TWRP is indeed fine and stable! However, it freezes and reboots my phone so in my particular situation it is currently not stable. Therefore the need to completely wipe the phone and start from fresh.
ryankabir said:
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Click to expand...
Click to collapse
Appreciate your POV. I know how it feels like if people ask for help for something they could have read easily somewhere. I'm thankfull for all the guides that people have written on here! I'm asking for help because in my situation the guides are not working and would like to have a full clean wipe of my phone and fix all possible software issues before trowing away the phone because of hardware fault.
ryankabir said:
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Click to expand...
Click to collapse
Thanks for the suggestion and will try this!
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
I've tried your guide but I still have been unable to get a connection with ASUS Flashtool. The phone does keep itself relatively stable in bootloader (don't know what fixed it) - I am able to cycle through normalboot, recovery options etc without it crashing. The bootloader shows "Continue the fastboot process". I have tried different drivers, while rebooting between install/uninstall of drivers.
Thanks again all for the help
@j4y_ha
Goodluck
timbernot said:
@j4y_ha
Goodluck
Click to expand...
Click to collapse
Right m8 , we gonna fix your phone .
Do not stray from this guide.
Stick to it and you will be more the wiser when you have finished .
1 boot to boot loader ...scroll to 'power off ' and select it.
2 Connect your phone to wall charger ...let it charge till full.
When that's done , we ready for next step
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Mmbl came about around July 16, he run cm 13 Feb 16.
.173 or .177 is unlocked or locked LP Boot loader.
xFSTK is to gain temp Boot loader.
He gets recognised in fastboot.
He can flash stock recovery .
He can sideload .
.
.
But
Can he ?
That's not sn ide btw
Well I'm not gonna dig too deep into the twrp touch issues (there could be conflicting drivers or even something weird i noticed in twrp302 anything below 20% batt (or if batstats corrupt) then the touch goes craycray.. so lets ignore that..
this thread is getting too heavy i won't have time - so - you can always backup ur data partition so no worries there.. nothing to lose..
one problem at a time.. as I said in first post my phone was bricked much worse i had mismatched fastdroidboot and bootimg and after pressing power on maybe 4-5 times.. it would only turn on once.. sometimes on and immediately off... sometimes on stuck on logo.. sometimes on and no logo but screen is black (corrupt splash)..
so lets just try to go baaaaaack to the futureeeeeee ... Ok I found the script I made (after 8 hours of trying EVERY combination from different guides I just took individual components and made my own.. ) -
I'm writing this in a hurry so please use my first reply to get the XFTS Ubrick Guide for the Files + get the LOLLIPOP One Click BL Unlock + Lollipop Raw image... Their Guide wants you to use Asus Flash but that program failed me every time... so I have got a differnt way to do it..
I'm copying this directly from my own script (so you can change if any paths/names different)... but do not change the order or sequence
Using OneClick (keep the unlock1234 files saved separately for later use)...
If you have these unlocked I just say do it again anyway - no harm...
Unlock Bootloader for LP Stock (even if you have MM you must downgrade by this same method)
Code:
#flash old droidboot for LP stock Bootloader
fastboot flash fastboot droidboot_2_20_40_197.img
fastboot reboot-bootloader
# must run reboot bootloader once with this droidboot before continuing - dn't skip this
# unlock bootloader (use files provided inside oneclick tool but instead of using their script, manually do it - more reliable)
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
#if you get failed/error at oem stop - reboot to Bootloader (VOLUP+Power long press -
Release power at Asus Logo or long vibration) and re-do the last step
#if all done so far
fastboot reboot-bootloader
#white Asus logo means unlocked loader
fastboot flash recovery twrp3.img
reboot-bootloader
#toggle Up to choose Recovery - quick tap VOLUP+Power
#twrp will start
install Custom_MM_Rom.zip
#likely it will fail giving IFW 7 error - (intentionally did NOT put MM BL here), so
install Asus_MM_WW_420_184.zip (stock on stock only)
#let it be fully done, verify working MM stock OS
#check if it works - *sign* test your touch screen quickly and in dev tools Keep Debugging ENabled
#then power off - or if you have more options directly choose reboot
#during reboot vibration hit VOLUP+P to Fastboot
####RE-DO Entire first half again
fastboot flash fastboot droidboot_2_20_40_184.img
fastboot reboot-bootloader
# must run once with this droidboot before continuing
# unlock bootloader
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
fastboot reboot-bootloader
#now only flash certain MM files (the rest should already be there from stock upgrade) - if you have different MM Img (if they release new one in future - all readers just need to ensure the TOKEN DNX IfW matching)
${FASTBOOTBINARY} flash splashscreen tools/splashscreen_551.img
fastboot flash token tools/bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
#should now see black splashscreen + little red error msg for 2 seconds
#entering twrp again by toggling Recovery-> VOLUP+P
install superuser.zip
wipe cache + data
install yourcustomROM.zip
ryankabir said:
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Click to expand...
Click to collapse
Hello Guys,
I need the RAW files to download please could anyone please indicate a link or upload the ROM please? I've been on my phone for more than 3 weeks and can not find anywhere.
Thank you very much for the attention of all. A big hug!
http://dlcdnet.asus.com/pub/ASUS/Ze...59.353408663.1494812275-1536164900.1482540343
BahaStriker said:
http://dlcdnet.asus.com/pub/ASUS/Ze...59.353408663.1494812275-1536164900.1482540343
Click to expand...
Click to collapse
Hello Baha Striker!
How did you get the flash in this ROM? What tool did you use? I'm trying to use QFIL because it was the only one that recognized my device. But I'm having trouble locating .XML to do the flash and finally fix my device.
My device does not turn on, it only recognizes in windows task manager like qualcomm hs-usb qdloader 9008. Thanks a lot for the help.
landognr said:
Hello Baha Striker!
How did you get the flash in this ROM? What tool did you use? I'm trying to use QFIL because it was the only one that recognized my device. But I'm having trouble locating .XML to do the flash and finally fix my device.
My device does not turn on, it only recognizes in windows task manager like qualcomm hs-usb qdloader 9008. Thanks a lot for the help.
Click to expand...
Click to collapse
Hey mate, I had the same issue before I know it seems that it's the only way that your phone get recognized with but in matter of fact if you keep trying to boot on fastboot it'll boot there eventually.. so keep trying the keys combination till it works and a reminder fastboot on this device is when it stays on Asus logo screen so when you get there just flash recovery and install your ROM like normal
BahaStriker said:
Hey mate, I had the same issue before I know it seems that it's the only way that your phone get recognized with but in matter of fact if you keep trying to boot on fastboot it'll boot there eventually.. so keep trying the keys combination till it works and a reminder fastboot on this device is when it stays on Asus logo screen so when you get there just flash recovery and install your ROM like normal
Click to expand...
Click to collapse
Ok friend, let me see if I get it. Do I keep trying until my phone goes into fastboot? Does he eventually enter? So all I have to do is press the power button + vol up and keep trying until an ASUS logo appears? Thank you so much for helping, my friend, God bless you!
BahaStriker said:
Hey mate, I had the same issue before I know it seems that it's the only way that your phone get recognized with but in matter of fact if you keep trying to boot on fastboot it'll boot there eventually.. so keep trying the keys combination till it works and a reminder fastboot on this device is when it stays on Asus logo screen so when you get there just flash recovery and install your ROM like normal
Click to expand...
Click to collapse
Hello Baha,
I tried today all day to make this device go into fastboot mode but I did not succeed. I try the combinations Power + vol up, Power + vol down, only power and all the buttons.
Could you kindly explain me better how you got into your device's fastboot mode? Was it connected to the charger or pc or was it disconnected?
Thank you
Fastboot mode :
1) Turn off the ASUS ZENFONE 3 DELUXE ZS570KL
2) Press and hold Volume Up button (do not release and continue to No.3)
3) Press and hold Power button (No.2 still continue press and hold), so now we hold Volume Up Button + Power Button together
4) Wait until vibrate appear at ASUS ZENFONE 3 DELUXE ZS570KL, then release Power button (do not release Volume Up button)
5) If we see Logo appear at LCD screen, then release Volume Up button (release all button now)
Alguma solução para nosso zenfone 3 deluxe ?
arquivos Qfil para zenfone 3 deluxe ?
Ok guys,just I need help ,I can get to the fasboot ,my pc recognize my Asus zenphone deluxe3 (2,15) I have ADB and fasboot instaled Just I tried many times flash twrp and no luck....my bootloader is locked and my Asus in in bootloop ...ale what I can do ,is just to boot in fasboot....so how can I instal twrp? Is there any chance?
quotation
WW-15.0210.1810.73 stock recovery & RAW
Database--https://drive.google.com/drive/folders/0By3NdBos6w6JZEloNDFMaDVxS0U
willinko23 said:
Ok guys,just I need help ,I can get to the fasboot ,my pc recognize my Asus zenphone deluxe3 (2,15) I have ADB and fasboot instaled Just I tried many times flash twrp and no luck....my bootloader is locked and my Asus in in bootloop ...ale what I can do ,is just to boot in fasboot....so how can I instal twrp? Is there any chance?
Click to expand...
Click to collapse
Same promlem, I hope somebody can help us out