Develop Bugs

Phone has no fastboot.

Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.

Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.

maciek90 said:
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
Click to expand...
Click to collapse
The phone HAS RECOVERY does NOT HAVE BOOTLOADER

Read entire message. I wrote that this tool probably can be used to flash fastboot too.
You can also try "dd" command from busybox. Check sticky section in Zenfone General forum how to use it.

xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
You shouldn't mess with stuff you don't understand

If you have recovery, can you get to recovery menu?
Droid on back with error underneath and where you have to hold power then up volume to get to recovery menu.

Ok, here is link to flash_image tool.
http://forum.xda-developers.com/showthread.php?t=902493
I used it to flash recovery on HTC Sensation, but it should work with fastboot on Zenfone too. The command should be "flash_image fastboot /path/to/droidboot.img"
I'm not sure if it will work, but you already have messed up fastboot so this shouldn't make it worse
The second option is "dd if=/path/to/droidboot.img of=/dev/block/by-name/fastboot" or "dd if=/path/to/droidboot.img of=/dev/block/mmcblk0p3" as fastboot is the third partition. You can execute this even in terminal emulator on phone. Of course I haven't check it, but it's listed in general section to flash recovery (fastboot is just another partition, so it should work too).
About going to recovery maybe you can type " reboot recovery" in terminal emulator or from pc "adb reboot recovery". I'm not sure if it uses fastboot to boot into recovery but it's worth trying.

xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
Find Your Solution Here

[551ml] flashboot FAILD (remote: flash_cmds error!) Im stuck in fastboot

HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.

I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!

Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.

Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk

This is not so, I sideloaded MM fine straight on .184
No problem sideloading

kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site

Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.

timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.

timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.

So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[

quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.

sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.

quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery

sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.

quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery

sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?

quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery

sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.

sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.

Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.

ZE551ml "continue the fastboot process" prompt in fastboot,can't boot into recovery

ZE551ml "continue the fastboot process" prompt in fastboot,can't boot into recovery
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.

Should use Asus flash tool. http://forum.xda-developers.com/showthread.php?t=3452082
Sent from my Zenfone 2 using Tapatalk

debopriyobasu said:
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload

sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload
Click to expand...
Click to collapse
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk

kenbo111 said:
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk
Click to expand...
Click to collapse
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...

sukhwant717 said:
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...
Click to expand...
Click to collapse
It was just a question.
Sent from my Zenfone 2 using Tapatalk

I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now

debopriyobasu said:
I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now
Click to expand...
Click to collapse
Good to know that was helpful.

Adb not working under fastboot mode

Trying to flash twrp in fastboot mode, but not having much success. Adb devices doesn't list my device and when i try fastboot flash recovery it says that it's written something but when i try to go to recovery mode after reboot it just takes me to the stock recovery which resets the phone.
Have latest lg drivers along with 15 second adb installer installed. Running win 10 x64.
Any idea how i can successfully install twrp?
Thanks

Spaceboy60 said:
Trying to flash twrp in fastboot mode, but not having much success. Adb devices doesn't list my device and when i try fastboot flash recovery it says that it's written something but when i try to go to recovery mode after reboot it just takes me to the stock recovery which resets the phone.
Have latest lg drivers along with 15 second adb installer installed. Running win 10 x64.
Any idea how i can successfully install twrp?
Thanks
Click to expand...
Click to collapse
Yea just read the main XDA twrp thread carefully! You did it wrong and its all there.
And fastboot is not adb! In fastboot mode you can't use adb
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Yea just read the main XDA twrp thread carefully! You did it wrong and its all there.
And fastboot is not adb! In fastboot mode you can't use adb
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok read through it, inc a couple of guides mentioned in that thread. Rebooted to bootloader no problem
However when i type fastboot boot twrp.img i get the error:
FAILED (remote dtb not found)
typing fastboot flash twrp.img is down as successful but when i try to boot recovery it just takes me to the stock recovery reset.
All fastboot and lg drivers installed.

Spaceboy60 said:
Ok read through it, inc a couple of guides mentioned in that thread. Rebooted to bootloader no problem
However when i type fastboot boot twrp.img i get the error:
FAILED (remote dtb not found)
typing fastboot flash twrp.img is down as successful but when i try to boot recovery it just takes me to the stock recovery reset.
All fastboot and lg drivers installed.
Click to expand...
Click to collapse
No there is only one official twrp thread (see my signature) and there is only one guide to flash.
Try fastboot boot but with version 3.0.2.0 instead
#
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Yea just read the main XDA twrp thread carefully! You did it wrong and its all there.
And fastboot is not adb! In fastboot mode you can't use adb
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
steadfasterX said:
No there is only one official twrp thread (see my signature) and there is only one guide to flash.
Try fastboot boot but with version 3.0.2.0 instead
#
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Same error:
FAILED (remote dtb not found)

Spaceboy60 said:
Same error:
FAILED (remote dtb not found)
Click to expand...
Click to collapse
http://www.androidrootguide.com/2015/06/how-to-install-twrp-recovery-and-root-lg-g4-h815.html

gentr said:
http://www.androidrootguide.com/2015/06/how-to-install-twrp-recovery-and-root-lg-g4-h815.html
Click to expand...
Click to collapse
That's the guide i was following. Still get same error when issuing command. Think it's to do with the drivers in win 10 under fastboot mode.
Had an explanation mark against android. I selected update driver and then adb bootloader interface from the list.

Spaceboy60 said:
That's the guide i was following. Still get same error when issuing command. Think it's to do with the drivers in win 10 under fastboot mode.
Had an explanation mark against android. I selected update driver and then adb bootloader interface from the list.
Click to expand...
Click to collapse
maybe problem is not on the driver but haw to write comand, use this ( flash recovery twrp-2.8.x.x-xxx.img ) or ( fastboot flash recovery twrp-2.8.x.x-xxx.img ). use and this twrp 2.8.... if the problem is on the driver's use this link http://www.guideitech.com/mobile/android/risolvere-errore-waiting-for-device-android-adb-fastboot/ this section adb kill-server adb start-server
Sent from my LG-H815 using Tapatalk

Spaceboy60 said:
That's the guide i was following. Still get same error when issuing command. Think it's to do with the drivers in win 10 under fastboot mode.
Had an explanation mark against android. I selected update driver and then adb bootloader interface from the list.
Click to expand...
Click to collapse
if you wanna be sure that this is not a driver issue just try FWUL
but back to your problem. This error can happen when u have a older/newer bootloader flashed which works in another way as it should.
What is your current ROM version?

gentr said:
http://www.androidrootguide.com/2015/06/how-to-install-twrp-recovery-and-root-lg-g4-h815.html
Click to expand...
Click to collapse
gentr said:
maybe problem is not on the driver but haw to write comand, use this ( flash recovery twrp-2.8.x.x-xxx.img ) or ( fastboot flash recovery twrp-2.8.x.x-xxx.img ). use and this twrp 2.8.... if the problem is on the driver's use this link http://www.guideitech.com/mobile/android/risolvere-errore-waiting-for-device-android-adb-fastboot/ this section adb kill-server adb start-server
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
steadfasterX said:
if you wanna be sure that this is not a driver issue just try FWUL
but back to your problem. This error can happen when u have a older/newer bootloader flashed which works in another way as it should.
What is your current ROM version?
Click to expand...
Click to collapse
Stock ROM. Was running MM at one point but downgraded to lollipop with lgup as i was having issues. Software info screenshot:

Spaceboy60 said:
Stock ROM. Software info screenshot:
Click to expand...
Click to collapse
most ppl are on MM or N these days which has a newer bootloader.
This should solve your problem.
otherwise just try all TWRP versions you find - from high to lowest version. hope u will find a working one for LL.

steadfasterX said:
most ppl are on MM or N these days which has a newer bootloader.
This should solve your problem.
otherwise just try all TWRP versions you find - from high to lowest version. hope u will find a working one for LL.
Click to expand...
Click to collapse
Ok tried FWUL. although my phone shows up on the desktop adb and fastboot don't see it.

steadfasterX said:
most ppl are on MM or N these days which has a newer bootloader.
This should solve your problem.
otherwise just try all TWRP versions you find - from high to lowest version. hope u will find a working one for LL.
Click to expand...
Click to collapse
Spaceboy60 said:
Ok tried FWUL. although my phone shows up on the desktop adb and fastboot don't see it.
Click to expand...
Click to collapse
Edit: upgraded to MM. Still get errors when i try to boot or flash twrp. Beginning to think there's something wrong with my phone.

Ok, I can boot TWRP using fastboot boot twrp-3.0.2-1-h815.img. However when I try to flash it I get the following error:
fastboot flash recovey twrp-3.0.2-1-h815.img
target reported max download size of 536870912 bytes
sending 'recovey' (16860 KB)...
OKAY [ 0.499s]
writing 'recovey'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.523s
Any ideas?
Thanks

Spaceboy60 said:
Ok, I can boot TWRP using fastboot boot twrp-3.0.2-1-h815.img. However when I try to flash it I get the following error:
fastboot flash recovey twrp-3.0.2-1-h815.img
target reported max download size of 536870912 bytes
sending 'recovey' (16860 KB)...
OKAY [ 0.499s]
writing 'recovey'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.523s
Any ideas?
Thanks
Click to expand...
Click to collapse
Good so it is actually a bootloader thing. Please read the official twrp thread (see my signature) and find the installation guide. The behavior above is expected and there is a way to solve. Just read carefully.
#
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Good so it is actually a bootloader thing. Please read the official twrp thread (see my signature) and find the installation guide. The behavior above is expected and there is a way to solve. Just read carefully.
#
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok, so followed the guide from https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 (which was in your signature)
Installation
General Howto Guide
The general guide seems to do not work properly when it comes to flashing so here is an additional howto which seems to work 100%:
I said you need an unlocked device. So ensure you have it unlocked and OEM unlocking option is enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC:
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
Then copy the twrp.img to your device while still in twrp (e.g. with a file explorer or by typing adb push twrp.img /sdcard)
Flash the twrp.img with twrp GUI to the recovery partition (choose the button at the bottom named image to show the copied image)
done.
You can now reboot into recovery again to check it has worked.
However, despite booting into twrp ok and flashing the recovery ok (according to twrp), when i restart the phone and go to recovery it's the stock recovery, not twrp.

Spaceboy60 said:
Ok, so followed the guide from https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 (which was in your signature)
Installation
General Howto Guide
The general guide seems to do not work properly when it comes to flashing so here is an additional howto which seems to work 100%:
I said you need an unlocked device. So ensure you have it unlocked and OEM unlocking option is enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC:
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
Then copy the twrp.img to your device while still in twrp (e.g. with a file explorer or by typing adb push twrp.img /sdcard)
Flash the twrp.img with twrp GUI to the recovery partition (choose the button at the bottom named image to show the copied image)
done.
You can now reboot into recovery again to check it has worked.
However, despite booting into twrp ok and flashing the recovery ok (according to twrp), when i restart the phone and go to recovery it's the stock recovery, not twrp.
Click to expand...
Click to collapse
ok. do the same again but when you have flashed twrp from within TWRP grab the recovery log (like described in FAQ #4-A)
hope we get some meaningful information.. because this really should work.
EDIT:
oh and please try the latest BETA here: https://forum.xda-developers.com/devdb/project/dl/?id=22169 !
.

https://paste.omnirom.org/view/3f6a4e1e
https://paste.omnirom.org/view/72c6b7a1
Reboot to recovery worked within the booted twrp, just not when I turn the device off and try to enter recovery from the hardware keys. Using hardware keys and selecting Yes twice just took me to stock recovery which does a factory reset and wipes device.
Didn't try adb reboot recovery.

Spaceboy60 said:
https://paste.omnirom.org/view/3f6a4e1e
https://paste.omnirom.org/view/72c6b7a1
Reboot to recovery worked within the booted twrp, just not when I turn the device off and try to enter recovery from the hardware keys. Using hardware keys and selecting Yes twice just took me to stock recovery which does a factory reset and wipes device.
Didn't try adb reboot recovery.
Click to expand...
Click to collapse
ok thx will look into this soon.
In the meanwhile and because you mentioned it one more question: which hardware key combo do you try exactly?
#

steadfasterX said:
ok thx will look into this soon.
In the meanwhile and because you mentioned it one more question: which hardware key combo do you try exactly?
#
Click to expand...
Click to collapse
Volume down and power button together. Release power button for a second when LG logo appears and then press and hold it again until reset screen appears. Usually from there i select yes and yes again and twrp would appear (when it was working)

my zen faild google verification to boot up

hey
when my phone boots shows that my device is not verified by google , what to do?

Jwtiyar said:
hey
when my phone boots shows that my device is not verified by google , what to do?
Click to expand...
Click to collapse
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around

sukhwant717 said:
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
Click to expand...
Click to collapse
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related

Jwtiyar said:
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Click to expand...
Click to collapse
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.

sukhwant717 said:
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
Click to expand...
Click to collapse
You made it really complex bro i dont understand what to do.

Jwtiyar said:
You made it really complex bro i dont understand what to do.
Click to expand...
Click to collapse
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.

sukhwant717 said:
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
Click to expand...
Click to collapse
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?

Jwtiyar said:
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Click to expand...
Click to collapse
device model ze551ml oe ze550ml?

sukhwant717 said:
device model ze551ml oe ze550ml?
Click to expand...
Click to collapse
ze551

Jwtiyar said:
ze551
Click to expand...
Click to collapse
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error

sukhwant717 said:
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
Click to expand...
Click to collapse
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .

Jwtiyar said:
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Click to expand...
Click to collapse
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk

sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
I installed RBR ROM which based on MM , now the error gone after flashing boot.img but the will boot to asus logo and will reboot again it seems its bootloop .

sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/

Jwtiyar said:
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Click to expand...
Click to collapse
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?

sukhwant717 said:
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
Click to expand...
Click to collapse
custom MM

Jwtiyar said:
custom MM
Click to expand...
Click to collapse
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question

sukhwant717 said:
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
Click to expand...
Click to collapse
thank you very much now its booted successfully

Jwtiyar said:
thank you very much now its booted successfully
Click to expand...
Click to collapse
great good to know your device is alive again

sukhwant717 said:
great good to know your device is alive again
Click to expand...
Click to collapse
Thank you bro