Database Users

[Q] Need to unbrick Defy+ - Strange problems

Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis

If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2

Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.

Downgrade to Marshmallow

Hello Friends, I just upgraded my Zenfone 3 ze520kl to Nougat, but i prefer Marshmallow i try from recovery mode to flash Marshmallow, it shows error and the installation aborted. Can any one help . Thanks.

What error does it show?

Error with some numbers follows by 'install aborted'. I unable remember the error numbers. I did three times all the time with same remark.Thanks.

That's not very helpful. Can you try it again and tell us exactly what it says?

Hi,
I downgraded a few days ago, here's an overview of the steps.
WARNING, this requires a factory reset so you will lose the data on the phone, so make sure you have backups before you proceed. You do this at your own risk and I am not responsible for any damages.
I assume you have adb / drivers all configured and know to how use them.
1) download firmware file http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip and save to SD card / insert card in phone.
2) download recovery and boot img files for Z017D_WW_13.20.10.152
- https://mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
- under the folder Z017D_WW_13.20.10.152
3) Go to fastboot mode (power + vol up)
- flash recovery.img (command: fastboot flash recovery recovery.img)
- flash boot.img (command: fastboot flash boot boot.img)
4) reboot to recovery (power + vol down)
5) install update form micro sd card.
set the file UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip that you saved earlier
6) wipe cache
7) factory reset
If you don't do a factory reset and reboot, Android pretty much crashes on multiple processes on start up, it is unusable.
Regards,
TK

Credit goes to https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524 for laying the foundation.

Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.

Same thing happened to me as well. I just went ahead to flash the RAW file (http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html) and updated the software to the latest marshmallow update, followed by a factory reset.

If we Downgrade
Then we get update in future yes or no??
Sorry for bad English??

Yes.

Hi, thanks for the help. Please answer this:
Do I need to use Recovery and Boot.img the same version of ROM? Why?
Why do I need to install Boot.img?

Hardest Bricked my P10 Plus. Can't even turn my phone off.

However, if you are watching this, it means ur phone is bricked with huawei p10 lite/p10/p10 plus
Read the replies and follow the instruction noted by @Blackball and his links.
Then you will find you self a way to restore the phone.
Thanks again to @Blackball and rest of you guys, much appreciated for your help.

What on earth is Yoroot?

So, You can't enter fastboot mode am i right ?
Do you connect usb cable to your devices before press Vol- and Power button ?

Current Situation
After the battery was dead, i actually can enter the fastboot and i used TWRP 3.1.1 for huawei P10 Plus from github. double wiped my device and by far i have entered the system normally.
However, the ROM wasn't official and i lost my warranty for unlock my huawei phone. And the custom service from Huawei said that they don't provide any official ROM Since it's Android 7.0 .
This ROM is really crappy that i can't delete/uninstall any Application i installed.(It gets reboot everytime i try to and the Application is still there even i just tried to Delete/Uninstall).
Worst of all, some options does not work properly in "Option" menu . (For example i can't access to "Developer mode" that everytime i press it it tabbed back to the former menu.)
I really hate this crappy menu so i tried to search on the internet for P10 Plus ROM so far i get B133 update ROM i can find and i tried to install it from SDcard by pressing VOL - and VOL + and Power buttom.
It says failed to update system at 5% while updating/recoverying the system.
and the ROM which i'm using was found in HUAWEI's official fan forum from Club.Huawei.com a forum belongs in china.(Rooted rom B140).
Right now seems the only option for me is to find a better ROM than this .(At least won't get me so many bugs like this one .:crying: )
and Thanks for your comment "Bigbearxl" it worked as normally it should after the battery was dead then i recharged it.
Yet Right now the PC doesn't recognize the device though Via-Usb because it's not Huawei official ROM and Hisuite helper only recognize their own ROM and the rest Phone helper or ADB can't recognize the device while The Phone is Booting normal .
And Reply to "Craphead" Yoroot is a special Root tool for Huawei P10/P10 plus made by chinese from Huawei Fan Club forum.

New Update
After rewrited boot.img though fastboot mode from https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946 thanks to "yury_z, " i can start to delete files with current system, but it's still crappy that it doesn't even have camera
So i think i will try dload method to recovery my phone with firware that i found in forum.

Failed
Looks like i have to stock with that bit longer
dload with update.app method failed. and recovery TWRP install missing md5.
Unless i get System.img or i guess i can't get another system.:crying:

This work for P10plus too
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

WackyJoker said:
Looks like i have to stock with that bit longer
dload with update.app method failed. and recovery TWRP install missing md5.
Unless i get System.img or i guess i can't get another system.:crying:
Click to expand...
Click to collapse
Maybe you could also try installing stock firmware with funkyhuawei, it's not for free though. But dload method never works on P10/plus unfortunately.

thanks @Blackball and @Craphead. i checked both of your method but didn't work and this new twrp 3.1.0 i downloaded displayed sd card 0mb. and i followed poster's step and missing one file.
However i might found a useful Thead that might work and i'm gonna try tonight.
http://www.stechguide.com/huawei-p10-plus-b133-nougat-update/

That is what I wrote.
It seems that firmware finder work for P10/plus now.
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder

@Blackball not sure you what you mean by that, do you mean that you can actually use it to install firmware on p10/p10 plus now? If so how did they manage to get around the authentication issue?

I debranded my phone from L09 to L29 DualSim with this guide. It work with moded stock recoverys.

Blackball said:
That is what I wrote.
It seems that firmware finder work for P10/plus now.
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Click to expand...
Click to collapse
well i tried your method but there were some file that can't be downloaded from that post so i used another and,eventhough with complete files, the method i posted and i was going to use it tonight. Failed.
did all the steps from update.bat indicated and all worked fine till the last step that it says " automaticly install system" and the phone shows error at recovery.(similar to dload method because it automaticly create dload and exact those ROM files)
it indicates a big red " ! " sign and stopped. basicly i'm back to "No System Status"
The only method wowrks for my "P10 Plus" is " flash system system.img " method.
yet i don't know how to exact system.img boot.img recovery.img etc from those stock firmware like those chinese.
i have some of their rewrote roms (it's crappy because i has no default camera and it's for chinese P10 Plus A.K.A VKY_L29) .
Yet i can't find any System.img on google by far.

Blackball said:
I debranded my phone from L09 to L29 DualSim with this guide. It work with moded stock recoverys.
Click to expand...
Click to collapse
I haven't tried your Firmware Finder method , i think i can install crappy system.img then try your Firmware Finder method.
Because right now i wiped my system and i'm without system :crying:

Guys This Thead https://forum.xda-developers.com/showthread.php?t=2315547
tells you how extract flashable rom files from firmware update.app.
It should work but i only made to Unknownfile XX .img and i can't download his script "HuaweiFinder" from his google drive.

Holy Crap it worked, i Extracted system.img and other img from update.app by some Chinese scripted unpack script. and I'm trying to restore my device though fastboot mode with adb.

Blackball said:
That is what I wrote.
It seems that firmware finder work for P10/plus now.
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Click to expand...
Click to collapse
well just tried your method and at last step it says installing failed. then i reboot entered rec mode choose wipe/factory reset
wiped till 50% and stopped, it can't factory reset.
Before this method fastboot mode was " Phone unlock " " Bootloader unlock."
Now it's just "Phone unlock"

now i'm stuck at boot loop "your device is booting now" then it rebooted and back to "your device is booting now" again then automaticly goes to Erecovery mode. I have to shutdown device for now and hope i can find some solution tomorrow :S

When you try this :
https://forum.xda-developers.com/showthread.php?t=3593108
It's important that you have the 3 zip files from your wanted firmware and rename them correctly. Don't mix with another firmwares.

Blackball said:
When you try this :
https://forum.xda-developers.com/showthread.php?t=3593108
It's important that you have the 3 zip files from your wanted firmware and rename them correctly. Don't mix with another firmwares.
Click to expand...
Click to collapse
i did this method yesterday and, well, i can't get update_full_VKY-L09_hw_eu.zip from the link : http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v85029/f1/full/filelist.xml . only Update.zip and Update_full_data.zip . the other one "update_full_VKY-L09_hw_eu.zip" i had to get it from another webside (it's also b133)
it shows a big "!" sign at the last step . i did everything it tells and tried both sdcard&script way to flash twice both rebrand&same brand update.
after the failure i can't enter "Vol +" and "Vol -" and "Power button" to do dload method . When i try to do that it just goes in Recovery mode.
In recovery mode i tried to wipe data/factory reset. It stopps at 50% which is after wipe and starting to factory reset at 50% it failed.
i try to flash in system.img and boot.img yet i still can not enter the system and stuck at bootloop.

Asus zenfone selfie ZD551KL Bricked, bootloop asdf/recovery/last_log

Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)

Kamen911 said:
Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)
Click to expand...
Click to collapse
same problem. stuck on bootloop on stock recovery

https://www.youtube.com/watch?v=cDRsEsI0qBY
Have you guys tried this method, yet?

HELP please... how to stop boot loop

Thank you in advance for any help you can provide.
I successfully rooted my Zenfone 3 Max (ZC520TL) using Magisk, but wanted to restore the phone back to its factory firmware. I used the uninstall option in Magisk but this reported that it could not find the backup boot image. Unfortunately I then made the mistake of following unroot steps on other sites rather than this excellent resource. Long story short I somehow managed to lock the bootloader again so when I try to use fastboot to flash any image I get the error "FAILED (remote: not allowed in locked state)".
When I turn on the phone, on the ASUS splash screen it says...
Red State
Your device has failed verification and may not work properly
Your device will boot in 5 seconds
… ie boot loop.
Q) What can I do to get my phone usable again? I searched this site and found lots of info on how to unlock the bootloader and how to root, but nothing about how to stop the boot loop.
I do have access to the Recovery mode and see options such as "Apply update from ADB" and "Apply update from SD card" but I am unsure if these will help?
Thanks again for any help and/or links to solutions on this site that I missed.

I was caught in similar situation, due to unsuccessful flashing using asus flashtool, I ended up flashing stock firmware (not the raw firmware) via recovery and everything was back to normal.

Thank you... but...
sanctitude888 said:
I was caught in similar situation, due to unsuccessful flashing using asus flashtool, I ended up flashing stock firmware (not the raw firmware) via recovery and everything was back to normal.
Click to expand...
Click to collapse
Thank you @sanctitude888 so much for your help. I'm new to rooting but keen to learn. What's the difference between "stock" firmware and "raw" firmware? For example I can download the device firmware from ASUS and extract the boot.img file (ASUS no longer provides the recovery.img file) but is this considered "stock" firmware or "raw" firmware?
You also mentioned you flashed via recovery. In Recovery mode I see multiple options such as "Apply update from ADB", "Apply update from SD card", "Mount /system", etc. Could you please be more specific on how you did the recovery please?
Thank you for your help.
Kind Regards

Sorry for very late reply. Despite useful guides are there, they are pretty much scattered. Few posts or threads I could suggest as follows :
1. https://forum.xda-developers.com/zenfone-3/how-to/updated-unlock-relock-bootloader-t3749456
2. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-ze520kl-ze552kl-unofficial-t3738811
3. https://forum.xda-developers.com/zenfone-3/help/help-ze552kl-bootloop-flashing-t3820371
4. https://forum.xda-developers.com/zenfone-3/how-to/guide-how-to-root-zenfone-3-official-t3745650