Develop Bugs

[Q] completely unrootable

i tried to root my phone (unsuccessfully) and now i cant even factory reset it. if i try it loads onto the recovery screen where the touch screen is unresponsive (my reason for not completing the root, as well as not detecting my phone for twrp flashing). is my phone now "bricked" on stock? UNROOTABLE

I presume your bootloader is unlocked? Are you able to boot into your ROM or not?
If you want to just bring your phone back up and running, you will need to run a RUU or restore a nandroid backup:
So post the result of the following:
Code:
fastboot getvar version-main

vin4yak said:
I presume your bootloader is unlocked? Are you able to boot into your ROM or not?
If you want to just bring your phone back up and running, you will need to run a RUU or restore a nandroid backup:
So post the result of the following:
Code:
fastboot getvar version-main
Click to expand...
Click to collapse
thanks again vin4yak..my phone works perfectly as htc wants it to .. ive unlocked bootloader.. pushed super su.zip.. reboot into bootloader.
cannot push twrp as it says device not found. if i go into recovery the touch screen is unresponsive.. could this be due to missing this step or should it be working?

startfromscratch said:
thanks again vin4yak..my phone works perfectly as htc wants it to .. ive unlocked bootloader.. pushed super su.zip.. reboot into bootloader.
cannot push twrp as it says device not found. if i go into recovery the touch screen is unresponsive.. could this be due to missing this step or should it be working?
Click to expand...
Click to collapse
The latest TWRP doesn't work on bases greater than 3.14... So I recommend flashing CWM and then proceeding with the rooting process!

vin4yak said:
The latest TWRP doesn't work on bases greater than 3.14... So I recommend flashing CWM and then proceeding with the rooting process!
Click to expand...
Click to collapse
Note, you will find a .img file that ends in -JB.img. Only install this version if touch is not working for you in the regular version.
Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
sorry to sound pc illiterate but whats the start of that string in cmd bcos it cantbe c:ect can it lol
I DIIID ITTTT!!! YEEESSS... GET IN U LEGEND!!!! THNX MAN..

startfromscratch said:
Note, you will find a .img file that ends in -JB.img. Only install this version if touch is not working for you in the regular version.
Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
sorry to sound pc illiterate but whats the start of that string in cmd bcos it cantbe c:ect can it lol
Click to expand...
Click to collapse
Didn't get you??! What are you trying to say?
To flash a new recovery you have to put the recovery img file in your fastboot folder and then flash it via opening cmd in fastboot folder and phone in fastboot mode... and then :
Code:
fastboot flash recovery recovery.img
fastboot erase cache

vin4yak said:
Didn't get you??! What are you trying to say?
To flash a new recovery you have to put the recovery img file in your fastboot folder and then flash it via opening cmd in fastboot folder and phone in fastboot mode... and then :
Code:
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
LOL MY ISSUE WAS JUST PUTTING CD \ANDROID 1ST.. sorry bout shouting im too happy lol all done.. thnx matey

Greaatt!!! :good:

Phone completely bricked

Hi everyone !
Yesterday, I wanted to wipe cache for some reasons, and I stupidly restarted the phone while formatting cache.
Result :
-A bootloop at the firt restart, then a "Error !"
-Can't acces Recovery mode, "Error !". I tried power button+volum up, don't work.
-ADB don't work anymore, I can't see the phone via adb devices
The only thing I can do is execute fastboot commands in Windows. I successfully made a tethered TWRP recovery, but I seriously don't know what to do from here. I tried flahsing a ROM, but it didn't worked (still have Error !).
I tried install permanent TWRP (unofficial), but I can't acces it. Probably because my bootloader is locked.
So... what should I do ?

Fastboot format cache should do the trick.

KillerNo2 said:
Fastboot format cache should do the trick.
Click to expand...
Click to collapse
I tried it.
Still don't start correctly, don't forget that I did some **** to try to fix it :s
The ROM is probably also damaged...
EDIT : Now it don't show the Error ! anymore, it always return to fastboot mode...

Baldriksen said:
I tried it.
Still don't start correctly, don't forget that I did some **** to try to fix it :s
The ROM is probably also damaged...
EDIT : Now it don't show the Error ! anymore, it always return to fastboot mode...
Click to expand...
Click to collapse
After formating cache you should've been able to get into recovery mode, if not, download recovery image from here then:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
You can always sideload stock roms from there.

KillerNo2 said:
After formating cache you should've been able to get into recovery mode, if not, download recovery image from here then:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
You can always sideload stock roms from there.
Click to expand...
Click to collapse
I get this :
">fastboot flash F:\recovery.img
unknown partition 'F:\recovery.img'
error: cannot determine image filename for 'F:\recovery.img'"
EDIT : oh **** sorry i misswrited the command é_è
EDIT 2 : THANKS ! I have acces to normal recovery. Can you tell me what should I do now ? (seriously don't want to make everything goes brick again ^^')

Baldriksen said:
I get this :
">fastboot flash F:\recovery.img
unknown partition 'F:\recovery.img'
error: cannot determine image filename for 'F:\recovery.img'"
Click to expand...
Click to collapse
Put all image files into the adb folder.

KillerNo2 said:
Put all image files into the adb folder.
Click to expand...
Click to collapse
Sorry, I edited my message, the error was from me.
So now I am on recovery... what should I do ?

Baldriksen said:
Sorry, I edited my message, the error was from me.
So now I am on recovery... what should I do ?
Click to expand...
Click to collapse
Download stock ROM from Asus site, and then sideload the ROM in recovery mode. Follow 3.2) Flashing Zenfone 2 via ADB in this thread.

KillerNo2 said:
Download stock ROM from Asus site, and then sideload the ROM in recovery mode.
Click to expand...
Click to collapse
Sideload with "Apply update from ADB" ?
The stock ROM is a zip of about 1.1GB ? I heard that their were update only package and full firmware ?

Baldriksen said:
Sideload with "Apply update from ADB" ?
The stock ROM is a zip of about 1.1GB ? I heard that their were update only package and full firmware ?
Click to expand...
Click to collapse
That zip file is a full firmware.

Thanks !
I did it and I have now the stock firmware installed correctly !

I have the same problem... But there is no option to fastboot format cache... only normal boot, power off, recovery mode... can't enter recovery mode either...

ndruqltn said:
I have the same problem... But there is no option to fastboot format cache... only normal boot, power off, recovery mode... can't enter recovery mode either...
Click to expand...
Click to collapse
You need to follow the steps in this thread to install drivers and adb package first. Fast boot firmat cache is the command that you should type in on your PC.

Just a thought but instead of trying to install anything through adb why not instal a pre-rooted rom img through fastboot too. You can always wipe out root with the next OTA...

I have already wipe cache and now boots up properly but the problem is that touch screen doesn't seem to work...

Can't connect my Zenfone 2 to my pc even though I have installed drivers and adb...

[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.

Help needed to Unbrick

Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.

mumith3 said:
Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.
Click to expand...
Click to collapse
Re failing at 5% suggests to me that one of the three file was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is you bootloader unlocked. Still?

mrmazak said:
Re failing at 5% suggests to me that one of the three files was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is your bootloader unlocked? Still?
Click to expand...
Click to collapse
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?

mumith3 said:
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?
Click to expand...
Click to collapse
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img

mrmazak said:
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img
Click to expand...
Click to collapse
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?

mumith3 said:
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?
Click to expand...
Click to collapse
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash

mrmazak said:
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash
Click to expand...
Click to collapse
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable

mumith3 said:
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable
Click to expand...
Click to collapse
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)

mrmazak said:
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)
Click to expand...
Click to collapse
Thanks for all the help Sir ?
P.S. Oreo stable is pretty damn good so far.