Database Users

Messed up mako(Resolved)

I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app

anoymonos said:
I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.

----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
gee2012 said:
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.
Click to expand...
Click to collapse
any other suggestions

anoymonos said:
----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
any other suggestions
Click to expand...
Click to collapse
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore

gee2012 said:
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore
Click to expand...
Click to collapse
ya but no red andriod appeared it just stayed in fastboot mode

anoymonos said:
ya but no red andriod appeared it just stayed in fastboot mode
Click to expand...
Click to collapse
Close CF Auto root, disconnect and reconnect usb and open CF Auto root again and try again.
If that doesn`t work flash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img in fastboot and flash this superSU zip http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip in recovery

I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app

anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Do a data factory reset in recovery, wipe cache and reboot. And try rooting again after you enabled usb debugging.

anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
PS: If you have no rom/etc due to erasure, you can 'adb push' the zip files to /sdcard while in recovery.

C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
kbeezie said:
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
Click to expand...
Click to collapse

anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.

anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
Dude why you are flasing a bootloader!

kbeezie said:
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.
Click to expand...
Click to collapse
i have folled this link and am syuck at flashing bootloader.http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
basically all i can access is fastboot

This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.

zephiK said:
This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.
Click to expand...
Click to collapse
thats the problem it wont let me flash anything through fastboot

anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
Do a data factory reset/ wipe cache in recovery and reboot.

anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051

gee2012 said:
Do a data factory reset/ wipe cache in recovery and reboot.
Click to expand...
Click to collapse
i dont have a recovery everything got wiped

zephiK said:
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051
Click to expand...
Click to collapse
yes proper drivers installed. Just unrooted and relocked old nexus 4 for return and then tried to root and unlock new one and it **** on me

It probably will if you use the proper syntax since you have to tell it which partition.
If you go and grab the TWRP 2.5.0.0 recovery image from their website for mako, you can use the following
fastboot flash recovery nameofrecovery.img
Making sure there are 4 parts as the word recovery is part of the command.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
Thus why you download one and flash. It's nearly impossible to hard brick a Nexus. Just helps not to receive panic. Take a couple breaths and figure out the proper commands.
Sent from my Nexus 7 using XDA Premium HD app

No acess to bootloader/Recovery

Hi Guys,
I had some problems with my beloved zenfone 2. Now i can´t enter in bootloader and recovery, but phone boots normaly.
The thing is it seems the partitions are cracked. My last hope was flashing a new recovery and bootloader with the images i got from this thread: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 using some programs to flash direct from phone (Tried with "recovery flasher" and "rom installer") but on "rom installer" app shows #ERROR: cannot locate recovery partition:
The history was : I rooted my phone using the zenfone toolkit, then started a wipe cache partition, which didn´t work and i forced off. After that i can´t made any adb connection - i can go to bootloader but doesn´t find my device and can´t write anything - , but i made TWRP recovery work using the "tethered recovery" as show in http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532 and flash the original stock rom. ADB/fastboot still don´t work. After that i entered in TWRP again using the same method and inserted Superuser.zip there, rooting my device. After root i lost Bootloader, but still can go to recovery (using TWRP and CVM programs which have the option "reboot to recovery"), which was still useless since it recognize my phone but adb sideload still don´t work. I even tried the MOFD_update thing - copying the entire rom to sd card and renaming to MOFD update but it shows it can´t update. Then i tried to flash TWRP using the TWRP app and the only thing i did it was lost my recovey too.
Now when i try to go to bootloader only shows the UsB logo (the trident), The same happen if i try to go to recovery by apps.
I think i´ll have to fix partitions mannually, using only phone, but i have no ideia how. Can anyone know what can i do?
Thanks in advance

You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.

Trident logo means brick phone...be careful nextime

Mononon said:
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Click to expand...
Click to collapse
Thanks Anyway. One thing i don´t understand is why my phone is booting normal. I know i´ll have issues when an update come, but it´s booting normaly

pato2015 said:
Trident logo means brick phone...be careful nextime
Click to expand...
Click to collapse
I hope i will have nextime...

you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app

ityoung said:
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
Click to expand...
Click to collapse
i´m trying to flash recovery.img from android. I can boot only for sistem. I can´t boot to bootloader or recovery. I´m trying a lot of apps which says it can flash a recovery from a running android, but none of them works
I also tried the Shuame like you said on another thread, but it doesn´t work. Thanks for your help

It might be possible to do something from a terminal window on your phone, but you would need to take advice from someone who knows what they are doing as I'm only theorizing rather than speaking from any position of knowledge.
Sent from my ASUS_Z00AD using Tapatalk

Is your bootloader unlocked?

dodongobongo said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. The problems started on my second boot after rooting, i had no chance to unlock bootloader too. I think if i had i can flash a custom recovery using TWRP or CVM apps and flash everything else again, but no, i can´t do that either.

As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app

yakub234go said:
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you Sooo much.
Now i have my recovery back, is there a way i can get bootloader back again using commands like that ? (and one bootloader i can use adb\fastboot ?)
I assume now i can use adb/sideload or MOFUPDATE.zip way (inserting an flashable rom with this name in my memory card so the system will flash like an update when i enter in recovery), but i don´t know what exactly i need to do (and what archives i have to use) to have a bootloader again, considering all ways to unbrick zenfone 2 needs fastboot. If i do that with stock Asus rom i can download from asus site will i have bootloader (and acess to fastboot) again? I´m afraid to do that and lose my root acess and still have no fastboot option. With root at least i can use terminal. I´m really afraid of flashing something that really hardbrick my phone since i have no fastboot, only root.
Can i unlock bootloader using terminal ? Maybe it´s safe if i unlock bootloader and then wipe TWRP using only TWRP app. After that i can flash other rooms and always have TWRP to fix if something goes wrong.
Sorry if i´m bothering. And thank you soo much for your help

I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app

yakub234go said:
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you again. Sorry about my insecurities, but i´m still worry. I rooted my phone at first time using the rootkit, one step there says i have to click "checkbeforeaction.bat" which will say i can go with root if i see 1234567ABCDEF as my phone. After that i can´t use adb anymore.
I don´t know why my phone changed to 1234567ABCDEF, i´m not sure if this is the reason i can´t use ADB. After recover my recovery yesterday (thanks for you) i checked "adb devices" on sideload and still shows 1234567ABCDEF. Still afraid to flash a stock rom and the only thing will change is i lost my root.
Maybe it´s a silly questions, but To use sideload i need a .img or a .zip file ? the stock room will flash stock recovery and stock bootloader again? Will i see 1234567ABCDEF again? Can i sideload a pre-rooted room ?Can i sideload just droidboot.img, boot.img and recovery.img? will it be placed on correct place on my phone? I´m really afraid of doing something wrong again.

Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app

yakub234go said:
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
i don´t understand your last phrase "&abt that serial no i think its fine"
You said never flash anything with your bootloader locked. I didn´t unlock my bootloader
Can i flash the image from this thread (item 3.1 method 1) ? http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596

Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app

yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Didn´t work to...
Shows on computer:
"error: protocol fault <no status>
On phone
"you need adb 1.0.32 or newer to sideload to this device.
installation aborted.
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/last_locale
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/command
I´m pretty sure i have the correct adb

yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Other thing that can be important:
When on adb sideload, if i request adb devices shows :
Emulator-5554 offline
0123456789ABCDEF sideload
Thats not my phone, again. What is that 012345ABCDEF thing ? can i fix that ?

Try using diff pc
& i forgot to mention u should unroot before flashing
Sent from my Karbonn A1+ Super using XDA Free mobile app

In need of urgent help with recovery-fastboot-droidboot corrupt zenfone 5 (a502cg)

Hello guys. I bricked my asus zenfone t00k (a502cg) after flashing a version of twrp custom recovery and factory resetting the device. Pc recognizes it as ISoc and cloverview when i install intel usb driver and ISoc driver. I can't enter recovery, fastboot or droidboot using combinations. Adb and fastboot do not recognize it either. The unbrick do not work, it gives windriver error (usb_bulk_read) error. I'm in urgent need of helping hands. Please sombody help me or those having the same device kindly extract dnx.bin, iwfi.bin, osdnx.bin and fastboot.pos.bin via adb commands and share them. Thanks in advance... please contact me via: [email protected]

RainyNight85 said:
Hello guys. I bricked my asus zenfone t00k (a502cg) after flashing a version of twrp custom recovery and factory resetting the device. Pc recognizes it as ISoc and cloverview when i install intel usb driver and ISoc driver. I can't enter recovery, fastboot or droidboot using combinations. Adb and fastboot do not recognize it either. The unbrick do not work, it gives windriver error (usb_bulk_read) error. I'm in urgent need of helping hands. Please sombody help me or those having the same device kindly extract dnx.bin, iwfi.bin, osdnx.bin and fastboot.pos.bin via adb commands and share them. Thanks in advance... please contact me via: [email protected]
Click to expand...
Click to collapse
Try this A502CG Debrick Secure
https://drive.google.com/file/d/0B0AFmAAcGS5xaVlMRUoxRGpndkk/view?usp=drivesdk
Sent from my ASUS_T00F using XDA-Developers mobile app

Has it been tested and proven to work with a502cg? Thanks by the way. I'm gonna give it a try and let you know about the result.

Dear member,
Brother, shall I change the sbin extension to bin? Xfstk asks for bin extension?

Dear member,
Brother, shall I change the sbin extension to bin? Xfstk asks for bin extension?

RainyNight85 said:
Brother, shall I change the sbin extension to bin? Xfstk asks for bin extension?
Click to expand...
Click to collapse
How you use that? With xfstk?
1. Power off your phone.
2. Press and hold vol down
3. Connect to pc, it will detect cloverview
4. Release vol down.
5. Extract a502cg debrick secure to adb folder, and run sec_xfstk.bat. it will load fastboot temporary.
In your adb must have boot, recovery and fastboot imgs.
6. Adb cmd run
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Hope it work
Sent from my ASUS_T00F using XDA-Developers mobile app

Thanks
Thanks a lot, but the thing is device is not recognized by adb/fastboot, so this pack will still flash fastboot and recovery?

RainyNight85 said:
Brother, shall I change the sbin extension to bin? Xfstk asks for bin extension?
Click to expand...
Click to collapse
For use with xfstk yes you have to rename them
Sent from my ASUS_T00F using XDA-Developers mobile app

Thank you so much
Thanks a lot bro. I'm gonna try my chances and get back to you soon.

One last thing to ask: shall I use recovery, fastboot of the version 2.21.40.29?

RainyNight85 said:
Thanks a lot bro. I'm gonna try my chances and get back to you soon.
Click to expand...
Click to collapse
I think you already have complete debrick folder before. Here is the complete folder, just exctract to any folder, put boot, fastboot and recovery imgs. Now run sec_xfstk.bat
After your phone detected do adb cmd.
Here the complete debrick for a502cg
https://drive.google.com/file/d/0B0AFmAAcGS5xRllXa3dET1YyOHc/view?usp=drivesdk
Sent from my ASUS_T00F using XDA-Developers mobile app

Brother, still the same. İ run sec_xfstk nothing pops up, no command prompt window at all. When i type adb devices, it only states list of devices attached. What do you think have i done wrong?

RainyNight85 said:
Brother, still the same. İ run sec_xfstk nothing pops up, no command prompt window at all. When i type adb devices, it only states list of devices attached. What do you think have i done wrong?
Click to expand...
Click to collapse
What current firmware your phone now?
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
What current firmware your phone now?
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Dont know exactly, but something ending with 53 i think.

RainyNight85 said:
Dont know exactly, but something ending with 53 i think.
Click to expand...
Click to collapse
1. Make sure isocusb driver installed. Get .53.zip from asus web. Extract it and get recovery.img, fastboot/droidboot.img and boot.img put into a folder name it a502cg.
2. Extract a502cg debrick.rar form my last link i sent to you, put them all together in a502cg folder.
3. Power off your phone. Press and hold vol down, connect it to pc. It will detect as cloverview. Now release vol down. Usb logo will show up.
4. Click xsftk.bat. Droidboot will load temporary to your phone.
5. Now open adb cmd in a502cg folder and run cmd.
Sent from my ASUS_T00F using XDA-Developers mobile app
---------- Post added at 18:21 ---------- Previous post was at 18:10 ----------
RainyNight85 said:
Thanks a lot, but the thing is device is not recognized by adb/fastboot, so this pack will still flash fastboot and recovery?
Click to expand...
Click to collapse
Yes adb will not recognize your phone, since we are on cloverview mode. After your run xsftk.bat droidboot will load to your phone temporary. Now your phone will recognize by adb. Then run adb cmd.
Sent from my ASUS_T00F using XDA-Developers mobile app
---------- Post added at 18:22 ---------- Previous post was at 18:21 ----------
RainyNight85 said:
One last thing to ask: shall I use recovery, fastboot of the version 2.21.40.29?
Click to expand...
Click to collapse
Any firmware can be use to this debrick. We just need the img inside, to recover your broken recovery
Sent from my ASUS_T00F using XDA-Developers mobile app

Reply
Should the img file of an version work?

RainyNight85 said:
Should the img file of an version work?
Click to expand...
Click to collapse
Yes it work, but make sure it from the original stock
Sent from my ASUS_T00F using XDA-Developers mobile app

Sure it is
İts stock. Downloaded from asus official website. İt saw device after pressing vol down as cloverview and isoc, but no usb logo appeared?

RainyNight85 said:
İts stock. Downloaded from asus official website. İt saw device after pressing vol down as cloverview and isoc, but no usb logo appeared?
Click to expand...
Click to collapse
Click xstk.bat
Sent from my ASUS_T00F using XDA-Developers mobile app

Alreasy did, error occured. Let me give you the log file

Need Help Bro. My asus zenfone 5 stuck at Asus logo and wont boot

I have asus zenfone 5 T00F , i just using it for daily use, after that i root it and no problem.. unroot it also no problem, after a month using it, suddenly some app crash then i reboot it..
when reboot it it stuck at Asus Logo.
i can go to the bootloader but the imei and serial number was not correct , (i attach some picture about it)
already tried this
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455 and
http://forum.xda-developers.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645 but it also not working.
my recovery said E: Error cant mount cache and etc (i also attach picture about it)
any kind of solution ? already searching at asus forum also dont find solution
Thanks before.. and sorry if my english is so bad

Try this Method
De-grade to Kitkat by downloading Kitkat firmware UL-ASUS_T00F-WW-2.22.40.540-user ( Kitkat).
Then Extract Fastboot.img, Boot.img and recovery.img
flash these files throufgh fastboot, for that downoad minimal adb tools and connect your phone through usb when in fastboot mode
flash these files by clicking right while holding shift on the ADB tools folder in Blank space and choose Open command window here .
then type these 4 commands :
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader [wait for the fastboot mode to reopen in phone then]
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after these 4 commands go to recovery through selecting recovery from fastboot.
In recovery, select Update from adb. Now copy firmware.zip in that ADB tools folder which is UL-ASUS_T00F-WW-2.22.40.540-user.zip and rename it to update.zip for ease.
now type in Cmd :
adb sideload update.zip
after this clear data/cache in phone and Your phone will boot.

bludyvenom said:
Try this Method
De-grade to Kitkat by downloading Kitkat firmware UL-ASUS_T00F-WW-2.22.40.540-user ( Kitkat).
Then Extract Fastboot.img, Boot.img and recovery.img
flash these files throufgh fastboot, for that downoad minimal adb tools and connect your phone through usb when in fastboot mode
flash these files by clicking right while holding shift on the ADB tools folder in Blank space and choose Open command window here .
then type these 4 commands :
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader [wait for the fastboot mode to reopen in phone then]
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after these 4 commands go to recovery through selecting recovery from fastboot.
In recovery, select Update from adb. Now copy firmware.zip in that ADB tools folder which is UL-ASUS_T00F-WW-2.22.40.540-user.zip and rename it to update.zip for ease.
now type in Cmd :
adb sideload update.zip
after this clear data/cache in phone and Your phone will boot.
Click to expand...
Click to collapse
Already tried that and also not working bro , i attach some picture about it.
adb sideload not flashing the firmware and just stopped with /cache mount error

xbeelzx said:
I have asus zenfone 5 T00F , i just using it for daily use, after that i root it and no problem.. unroot it also no problem, after a month using it, suddenly some app crash then i reboot it..
when reboot it it stuck at Asus Logo.
i can go to the bootloader but the imei and serial number was not correct , (i attach some picture about it)
already tried this
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455 and
http://forum.xda-developers.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645 but it also not working.
my recovery said E: Error cant mount cache and etc (i also attach picture about it)
any kind of solution ? already searching at asus forum also dont find solution
Thanks before.. and sorry if my english is so bad
Click to expand...
Click to collapse
Your phone partition has broke need to repartition. Try this http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
Choose nr 13 Zenfone Rescue
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
Your phone partition has broke need to repartition. Try this http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
Choose nr 13 Zenfone Rescue
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
already try nr 13 bro. when i press 13, the xfstk running.. when it want to repartitioning emmc (maybe it should automatically enter bootloader), i manually enter the bootloader then the script running , some error occured and when it finish flashing same error still occured x,x
i attach some picture about it

xbeelzx said:
already try nr 13 bro. when i press 13, the xfstk running.. when it want to repartitioning emmc (maybe it should automatically enter bootloader), i manually enter the bootloader then the script running , some error occured and when it finish flashing same error still occured x,x
i attach some picture about it
Click to expand...
Click to collapse
How is the result when you finish it?
I didnt see something wrong in there.
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
How is the result when you finish it?
I didnt see something wrong in there.
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
still stuck at asus logo bro, and recovery still error mount cache

[Root] Using Tethered TWRP to root Android 6.0.1 ZE551ML with locked bootloader

**** This is a modified post with detailed explanation and different files. The original post was made by @samcjtasi at here. *****
If you installed Android 6 from locked Lollipop Bootloader or forgot to unlock the bootloader before the installation and all you need is to root the device, this is a guide for you.
I did unlocked my Bootloader when I was on 168 with Asus unlock app. I flashed 194 raw file via Asus Flash tool which locked my bootloader. I installed MM via adb sideload and I had MM with Locked bootloader. I used this method to root my phone.
I am sure you'd already known that rooting the phone (acquiring the administrative rights for your own phone) will void the phone warranty.
With this method,
1. You do not need to downgrade your MM bootloader to Lollipop, unlock it, install twrp and root the phone, and then upgrade back to MM.
2. You do not need to install the TWRP. You will be running the TWRP from the tethered mode so your stock recovery will be intact.
3. SuperSu initial installation will modify some files in your boot partition in order to re-direct the system request to the SuperSu, as such In case you want to receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
4. Make sure your phone has battery 80% or more.
Requirements:
1. USB drivers for Asus have to be installed in the computer and your computer should recognize and can do the file transfers between the computer and your phone. You can get the drivers here. You will need to allow the file transfer from your phone when prompt.
2. Android debug bridge (ADB) has to be installed in your computer. I used ADB version 1.0.32. Some knowledge in using DOS and ADB is a plus.
3. Your phone should have the developer option enable and usb debugging should be checked in the developer option tab.
4. You need to know how to use the TWRP. There are a couple videos on youtube explaining about using TWRP.
The Files you need for the root.
1. TWRP - you can download the latest twrp file from here. The latest is ver 3.0.20. You could use older 2.8 versions if you want it.
2. SuperSu installer - I did try with latest SuperSu without success as such use the SuperSu patched by @shakalaca . Get the BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0.zip file here.
Steps:
1. Copy the downloaded TWRP to the directory that you install the ADB. (If you do not want to type long file name in adb, rename it to twrp.img. )
2. Connect your phone to the computer and copy the SuperSu installer to the phone internal memory or the external SD card.
3. Open the command prompt windows with administrative rights. (Without admin right ADB will not work properly).
4. Go to the ADB directory using the cd command. (e.g. cd\, cd adb, etc...)
5. Start the ADB environment by typing "adb start-server" . (without the quotation marks of course). You should see ****the demon started successfully*** message.
6. If you want to check your phone connection in adb, you can type "adb devices" to see your phone is recognized in ADB environment. You should see your phone serial no. and status .
7. Boot the phone to bootloader by typing "adb reboot-bootloader". The phone should vibrate and go into the fastboot mode. Wait till your phone get in the fastboot mode before you proceed.
8. Give the command to boot the phone to the twrp by typing "fastboot boot twrp.img". (If you did not change the name of the image file you need to type or copy and paste the whole file name).
You will see the message saying like-
"downloading 'boot.img' .....
OKAY [0.668s]
booting.....
OKAY [0.450s]
finished. total time: 1.120s "
The phone will vibrate twice and the Asus Logo with black splash screen will appear. The phone is start booting with TWRP image.
9. Unplug the phone from the computer. (If within 30 sec your phone should not start booting to TWRP. you can press and release the power button to go to the normal boot mode or press and release the volume-up key to go to the recovery mode. The TWRP should start by then.)
10. In TWRP install the SuperSu file by tapping install option. (I am sure you remember where you put the SuperSU installer zip file)
11. When the SuperSu installation is completed you will see the message saying like " You will see the your phone has failed verification message and reboot a couple times". Please remember that.
12. Clear the Dalvik cache and then reboot the phone. (You can reboot the phone without clearing the dalvik cache if you want).
Your phone will reboot and you will see the triangle saying like "your phone has failed verification" message and then automatically reboot the phone, showing up the message again. It would happen two to three times and you phone will be booted to the system. (You will not see that error message anymore in the upcoming boots).
Now your phone is rooted. You can check it by installing and running the app like root-chekcer.
Good luck.

Even with the command to boot into twrp from fast boot mine still boots into stock recovery
Sent from my ASUS_Z00AD using Tapatalk

sci05 said:
Even with the command to boot into twrp from fast boot mine still boots into stock recovery
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
It should not be go to stock recovery. The command is to boot with twrp.img.
Did you see message "booting ok finsihed" in the adb window?
Once you see that message, you can unplug the phone from the computer and twrp should be boot within 30 sec.

I finally found the time to update, everything went smooth but I'm having problems booting the twrp
I've tried several twrp from the guides but none worked
In cmd it says
Downloading boot.img
Okay
Booting...
Okay
Finished
C:\
The phone reboots but it goes to the dead droid screen.
I'm using adb and fastboot from adb-setup-1.4.3
IntelAndroidDriver1.10.0 and I've selected this version for the device in device manager.
The so is win 10 prof, I'm starting cmd as administrator.
I tried unplugging the phone and leaving it connected.
Also I'm using the 550 version, I've tried twrps from several threads for 550 and 551 (even tho twrp has merged both phones)
Am I missing something?
A little ot :
I need root 'couse adaway but I thought I would just use the twrp file manager to swap the default hosts file with the one I had in L.
It should work, right?
Sent from my ASUS_Z008D

sway8966 said:
It should not be go to stock recovery. The command is to boot with twrp.img.
Did you see message "booting ok finsihed" in the adb window?
Once you see that message, you can unplug the phone from the computer and twrp should be boot within 30 sec.
Click to expand...
Click to collapse
Yup says boot ok bit it boots into the dead android which is the load screen of the stock recovery. Press vol up and power and stock recovery menu appears.
Sent from my ASUS_Z00AD using Tapatalk

Acca85 said:
I finally found the time to update, everything went smooth but I'm having problems booting the twrp
I've tried several twrp from the guides but none worked
In cmd it says
Downloading boot.img
Okay
Booting...
Okay
Finished
C:\
The phone reboots but it goes to the dead droid screen.
I'm using adb and fastboot from adb-setup-1.4.3
IntelAndroidDriver1.10.0 and I've selected this version for the device in device manager.
The so is win 10 prof, I'm starting cmd as administrator.
I tried unplugging the phone and leaving it connected.
Also I'm using the 550 version, I've tried twrps from several threads for 550 and 551 (even tho twrp has merged both phones)
Am I missing something?
A little ot :
I need root 'couse adaway but I thought I would just use the twrp file manager to swap the default hosts file with the one I had in L.
It should work, right?
Sent from my ASUS_Z008D
Click to expand...
Click to collapse
The guide was written from the experience working with 551ML but it should work for the 550ML I think.
I am also using the Win10 Prof and my adb has a date of 3/30/2015.
I downloaded the latest twrp from the teamwin site. I did not use the twrp mentioned in this forum because they did not work for me. (The purpose of this guide is to use TWRP as temporary and not to install on the phone as such we do not need the signed TWRP ).
In the original thread some mentioned about going to the stock recovery (dead droid with red triangle) as such I put the instruction to press the power button or press the volumn-up button to go to the recovery mode. Actually, they are not required. If everything works, your phone should start booting with the twrp image.

sci05 said:
Yup says boot ok bit it boots into the dead android which is the load screen of the stock recovery. Press vol up and power and stock recovery menu appears.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you saw the message booting .... and ok your phone should be start booting to TWRP not the recovery. The command was to boot the phone with TWRP image. Try to download the TWRP image again from the teamwin site.

If someone just need root for Adaway, just don't, it is not required anymore since you can use other adblocker without root. Just install Block this and you're on: https://block-this.com
Sent from my Asus Zenfone 2 using XDA Labs
---------- Post added at 02:05 AM ---------- Previous post was at 02:03 AM ----------
Will this root method unlock definitely the boot loader as the other methods around here for MM?
Sent from my Asus Zenfone 2 using XDA Labs

sway8966 said:
If you saw the message booting .... and ok your phone should be start booting to TWRP not the recovery. The command was to boot the phone with TWRP image. Try to download the TWRP image again from the teamwin site.
Click to expand...
Click to collapse
I used the latest twrp. Should I use a different one?
Sent from my ASUS_Z00AD using Tapatalk

sci05 said:
I used the latest twrp. Should I use a different one?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you are using latest twrp directly downloaded from the teamwin site and if you are following the steps that I mentioned you should be OK. The only thing different could be the ADB version. Try different adb version or try this on the different computer.

Thanks. I got systemless root by this method.

fred_gaou said:
If someone just need root for Adaway, just don't, it is not required anymore since you can use other adblocker without root. Just install Block this and you're on: https://block-this.com
Sent from my Asus Zenfone 2 using XDA Labs
---------- Post added at 02:05 AM ---------- Previous post was at 02:03 AM ----------
Will this root method unlock definitely the boot loader as the other methods around here for MM?
Sent from my Asus Zenfone 2 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reminder, I'm using this until I get twrp to boot.
I tried adb 1.0.36 that should be the latest but it didn't work. I'll try on win7 or something.
If someone that succeeded could do
Adb version
Fastboot --version
And report here I'd be grateful.
Edit:
I've tried win 7 too but without luck.
Sent from my ASUS_Z008D

I confirm - it doesn't work. I have too "dead droid" and "No command" below.
Windows 10 Pro, ADB 1.4.3. Asus Zenfone 2 ZE551ML 4GB/32GB/Z3580 stock firmware 4.21.40.134.

ok, so how to install xposed framework?

Hi,
Does it reset the phone (apps, documents, accounts,...) ?
Tks !

This will probably not work. In other for it to work and be able to boot into twrp, I had to unlock the bootloader first, because the "fastboot boot twrp.zip" command wouldn't work unless I did so

CBT38 said:
Hi,
Does it reset the phone (apps, documents, accounts,...) ?
Tks !
Click to expand...
Click to collapse
No it does not. The procedure is to boot with twrp image temporarily.

jman0 said:
This will probably not work. In other for it to work and be able to boot into twrp, I had to unlock the bootloader first, because the "fastboot boot twrp.zip" command wouldn't work unless I did so
Click to expand...
Click to collapse
It work for me though. If you unlocked your bootloader you do not need this method. You can simply install the twrp to your recovery partition.

I can confirm it does not work with a locked bootloader, it boots into the dead droid screen.

Can i install Xposed with threded recovery