Database Users

Help twrp

I have a Huawei P9 Lite and i have installed twrp and android 7.0 on it. Now I want to install Google assistant, but when i try to boot in twrp recovery (volume down + power b) it shows me the screen where it says ''Installing update'' and then freezes at 5 % so i have to hold my power button to power off the phone.
If I dont try to run in the twrp, phone works just fine.
I apologize for my bad english.

Hi there,
I will move your thread in the correct forum dedicated to Huawei P9 Lite for more relevant answers.
Good luck

Bump..
Just to state that I am in the same boat here; as I am facing the same issue. Here's what happened in my case (using a guide found here at XDA-Developers):
-- unlocked the bootloader
-- booted to bootloader and flashed twrp
-- used adb to reboot to recovery (adb reboot recovery)
-- used twrp recovery to flash nougat update (two zip files, one ~1300mb and second ~680mb)
-- had some errors that were expected, the guide said ignore them and reboot after both zips have been flashed.
-- the flash overall was successful as the phone booted in emui 5 with android nougat. However, there was no virtual keyboard; so decided to do a factory reset
-- rebooted to recovery, but this time, the phone booted to huawei erecovery
-- did a factory reset, but to no avail
-- now, i can't boot into twrp to flash anything else. booting into bootloader and using fastload to flash recovery image is successful, but the phone does not boot to twrp recovery; remain stuck on "your phone is booting up" (or something similar).
My phone is not bricked, as basic telephony, wifi and built-in apps are working fine. But, without a keyboard, its pretty useless for everyday use. Any help in this matter will be appreciated.

KashifSMalik said:
Just to state that I am in the same boat here; as I am facing the same issue. Here's what happened in my case (using a guide found here at XDA-Developers):
-- unlocked the bootloader
-- booted to bootloader and flashed twrp
-- used adb to reboot to recovery (adb reboot recovery)
-- used twrp recovery to flash nougat update (two zip files, one ~1300mb and second ~680mb)
-- had some errors that were expected, the guide said ignore them and reboot after both zips have been flashed.
-- the flash overall was successful as the phone booted in emui 5 with android nougat. However, there was no virtual keyboard; so decided to do a factory reset
-- rebooted to recovery, but this time, the phone booted to huawei erecovery
-- did a factory reset, but to no avail
-- now, i can't boot into twrp to flash anything else. booting into bootloader and using fastload to flash recovery image is successful, but the phone does not boot to twrp recovery; remain stuck on "your phone is booting up" (or something similar).
My phone is not bricked, as basic telephony, wifi and built-in apps are working fine. But, without a keyboard, its pretty useless for everyday use. Any help in this matter will be appreciated.
Click to expand...
Click to collapse
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!

Claleale said:
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Click to expand...
Click to collapse
Did that and it worked thanks!

Claleale said:
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Click to expand...
Click to collapse
This seems helpful; but how can I flash recovery if I can't boot to fastboot?
[Update] Oh, got to fastboot, trying the suggested recovery now.

Fixed
Fixed using the suggestion above. Thanks.

[Solved] No way to unbrick my A2017G ?

I have no idea how I managed to get into this situation.
My A2017G was on Oreo 8.1 RR with a treble partition. Since I wasn't happy with that I want to go back to the newest stock rom.
So i followed this Guide [GUIDE] [A2017G] Return to Stock from Custom ROM - Updated.
I flashed the bootstack, then I flashed the stock system and the result was a dfu brick. Meanwhile i have an Axon 7 teared down into pieces, so I'm able to flash with MiFlash.
I tried to flash these roms until now:
ZTE_A2017GV1.2.0B06_FULL_EDL_PACKAGE_BY_TURKDEVS
A2017G_B09_NOUGAT_FULL_EDL
A2017G_B10_NOUGAT_FULL_EDL
ZTE_A2017GV1.2.0B10_Stock_System_by_raystef66 (+ ZTE_A2017GV1.2.0B10_BootStack_by_raystef66)
(I also tried to flash the "Remove Bootloader Unlock Warning" zip afterwards...)
My only chance to get into the TWERP Recovery is to replace an original recovery.img with the twerp one and flashing with the test point method.
All of them result in a dfu brick or stuck in the Axon7 logo screen after the animation (if i force a shutdown, it will result in a dfu brick too).
I'm out of any ideas since every single try result in a broken device. Does anyone has a suggestion what to do now?

No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.

I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default

tdm said:
No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.
Click to expand...
Click to collapse
keep this in mind, not all G users can do the cable procedure. He's just one more on a pretty big list. It's okay to suggest that unbricking without disassembly is possible but it's nowhere near 100% (or even 50% i'd say) effectivity. Same with FTM mode, people reported that they could get there after draining the battery, well it didn't work for everyone
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
Warcon said:
I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default
Click to expand...
Click to collapse
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done

Choose an username... said:
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done
Click to expand...
Click to collapse
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?

Warcon said:
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?
Click to expand...
Click to collapse
You have no fastboot, because N builds don't have it by default. If you select fastboot it simply boots into system. (in your case it attempts to, so it ends up in the same situation).
Try to install LOS14.1 maybe, since it's just modem, bootstack and ROM. I have zero hope that it'll work but it may as well do the trick. I have no idea why this is happening to you but it's just plain weird, I mean EDL should reflash most partitions

flashed TWRP 3.2.3
made a full edl backup
whiped data, system, cache, dalvik
flashed bootstack_O_b12
flashed oreo modem
flashed lineage-15.1-20180810
flashed pico gapps
it works now

A2017G only EDL mode available, need help with brick

Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks

Drunkenmazter said:
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Click to expand...
Click to collapse
Use one of the less archaic methods:
Download "EDL Tool" from the ROMs, kernels, development section, along with an EDL package that goes with your phone model. Put your phone in EDL and just flash it with that tool. after that, if it still doesn't boot you have to format data, because you might have conflicting data. If you can't do it from EDL Tool (i think you can, don't remember) just enter the recovery with Vol+ and Power and make a factory reset

My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?

From some other threads, I believe you could try to EDL flash Nougat instead of Oreo, it would work better.
https://forum.xda-developers.com/axon-7/help/help-edl-factory-restore-stuck-device-t4031619

I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.

xperiaatic said:
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
Click to expand...
Click to collapse
According to other threads, the problem could be due to "sparse" structure while flashing.
I suggest the following:
- Use Axon 7 EDL toolkit to flash latest official TWRP recovery (for Oreo a specific TWRP would be requied).
- Inside TWRP then wipe data/factory reset and at the utmost Format data. Then retry to boot.
- If not OK, reflash with EDL full ROM and try again.

Already done that for several times with O ja N EDL rom's but no luck. Can't get to recovery nor make system to boot.

Did you successful unlocked bootloader?
If not, I would recommended Axon 7 EDL Tool by djkuz, flashing nougat edl package and unlock it through the options.
Can you get into stock recovery after flashing EDL package? It supposed to have a format option for userdata and cache.
Did you try to get into fastboot mode? Power + Vol up buttons if i'm not wrong.
If so, you could try to format these partitions.
fastboot erase /cache
fastboot erase /data

I have experienced the same problem but I have resolved flashing, with Xiaomi MiFlash (sometimes I use this program because occasionally flashing EDL packages with AxonEDLTool, it gives me problems like this) this package Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL.
With this EDL, if the flash is successful, you will find NFound recovery 3.2.1-7 installed with which you can make a complete wipe and / or format them with the file system you prefer.
Afterwards, using MiFlash or EDLTool at your discretion, you can flash the EDL of the original system if you prefer.
I'm not an expert but this has solved my problem.
To unlock the bootloader, if the unlocking with EDLTool does not go well (it happened to me just yesterday while I was installing a Rom on another Axon 7), you can use Axon7ToolKit 1.2.1, it always worked well for me.
I hope it can help :fingers-crossed:.

xperiaatic said:
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
Click to expand...
Click to collapse
Hi, just want to let here my solution for the same problem, it may help others.
I tried to flash A2017G_B10_NOUGAT_FULL_EDL and A2017G_B02_OREO_FULL_EDL but always getting the Can't mount /cache/recovery/last_locale error, phone completely bricked.
So I flashed A2017_B13_FULL_EDL_UNBRICK_DFU using MiFlash through EDL, you can find this here: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 (if your EDL mode works fine there is no need to disassemble the phone as shown in that tutorial)
Now the phone is completely working, recovery and system, but everything in chinese.
Then I flashed A2017G_B02_OREO_FULL_EDL using MiFlash through EDL, and now everything is working and in english

Thanks a lot for the tip! A2017_B13_FULL_EDL_UNBRICK_DFU did the trick and unbrick the phone.
What i did:
1. used MiFlash to flash A2017_B13_FULL_EDL_UNBRICK_DFU
2. after that A2017G_B03_OREO_FULL_EDL
3. reboot to recovery and performed factory reset
First time I did not perform the factory reset and got stuck on the boot picture without the reset function (power button did not work). Drained the battery and performed factory reset and got the phone working again.
update:
Phone is not stable on B03, some apps crashing from time to time for no apparent reason and also soft reboots happening randomly.
Now I got stuck on the Axon boot screen again after rebooting the phone manually and waiting for the battery to drain ...
i did not install or perform any custom action to the system, just regular use and apps, but it is still acting up badly.
I was planning to use this phone as a secondary handset because it is actually a very nice piece of hardware but now i am starting to have second thoughts about that.

A2017G Bricked Oreo

Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3).
How i got here.
used a update.zip to go to oreo b3
using the EDL tool i backed up the OREO (A2017B03) recovery
using the EDL tool i flashed oki's trwp and rebooted
nothing...
Tried flashing EDL packages with the EDL tool and MIFlash.
> EDL tool hangs on `loading the programmer`
> MiFlash "cannot retrieve hello packet" , "try to reset status" ,"write time out maybe device was disconnected"
Tried other USB2 and USB3 slots
Tried other USBC cables
prediction, it seems i have broken EDL mode as the device is in the state but does not do anything after that.
device does not boot or reboot into edl. stuck in this state

dalebaxter01 said:
Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3).
How i got here.
used a update.zip to go to oreo b3
using the EDL tool i backed up the OREO (A2017B03) recovery
using the EDL tool i flashed oki's trwp and rebooted
nothing...
Tried flashing EDL packages with the EDL tool and MIFlash.
> EDL tool hangs on `loading the programmer`
> MiFlash "cannot retrieve hello packet" , "try to reset status" ,"write time out maybe device was disconnected"
Tried other USB2 and USB3 slots
Tried other USBC cables
prediction, it seems i have broken EDL mode as the device is in the state but does not do anything after that.
device does not boot or reboot into edl. stuck in this state
Click to expand...
Click to collapse
Why do you backup the recovery? its already included in the zip file,just grab it.And OKIs twrp does not support stock oreo.
If you can boot in twrp,do it and flash a twrp for oreo from nfound and wipe everything

Predatorhaze said:
Why do you backup the recovery? its already included in the zip file,just grab it.And OKIs twrp does not support stock oreo.
If you can boot in twrp,do it and flash a twrp for oreo from nfound and wipe everything
Click to expand...
Click to collapse
i backed up the stock recovery just incase i was going to go back to it, but seeing what has happened it seems like even tho i flashed a custom recovery and didn't boot into it i am just plain stuck in a EDL state. i can't boot into recovery or fastboot as i'm seemingly stuck in EDL

dalebaxter01 said:
i backed up the stock recovery just incase i was going to go back to it, but seeing what has happened it seems like even tho i flashed a custom recovery and didn't boot into it i am just plain stuck in a EDL state. i can't boot into recovery or fastboot as i'm seemingly stuck in EDL
Click to expand...
Click to collapse
i was stuck in edl sometime ago too because i was flashing edl firmware and my laptop shutdown because empty battery.Can you enter FTM mode? hold vol down + power button.
If yes do it.Now close axon7toolkit EDL TOOL.After that open axon7toolkit and follow instructions.It will boot in edl again and try to flash firmware

Predatorhaze said:
i was stuck in edl sometime ago too because i was flashing edl firmware and my laptop shutdown because empty battery.Can you enter FTM mode? hold vol down + power button.
If yes do it.Now close axon7toolkit EDL TOOL.After that open axon7toolkit and follow instructions.It will boot in edl again and try to flash firmware
Click to expand...
Click to collapse
holding for 2 min unplugged and another 2 min plugged and nothing

FIXED
- Waited for battery to drop to 0% and the EDL loop was ended
- plugged into PC and used the buttom combo
- EDL'd ZTE Oreo Rom

dalebaxter01 said:
FIXED
- Waited for battery to drop to 0% and the EDL loop was ended
- plugged into PC and used the buttom combo
- EDL'd ZTE Oreo Rom
Click to expand...
Click to collapse
Refreshing subject because same **** happened to me
My question is how long did you wait to empty the battery? I was about 57% when phone stucked in EDL... does it drains battery when being dead-like?

yarecco said:
Refreshing subject because same **** happened to me
My question is how long did you wait to empty the battery? I was about 57% when phone stucked in EDL... does it drains battery when being dead-like?
Click to expand...
Click to collapse
I don't have my Axon 7 on me, but I would give it about a day or 2 for it to die out on its own because its standby time can be insane if you have a custom kernel.

Stuck at 'bootloader unlocked' screen

My A2017G did an OTA update on its own yesterday and after that it would only display the 'bootloader unlocked' warning and go straight to DFU mode. I managed to get into EDL mode and Windows also now recognises the phone as 9008. Is there any way that I could backup data before reflashing? The key combinations work normally and I can reboot into any mode

blendomatik said:
My A2017G did an OTA update on its own yesterday and after that it would only display the 'bootloader unlocked' warning and go straight to DFU mode. I managed to get into EDL mode and Windows also now recognises the phone as 9008. Is there any way that I could backup data before reflashing? The key combinations work normally and I can reboot into any mode
Click to expand...
Click to collapse
Did you have TWRP or anything else installed?
If you don't have TWRP, install it via EDL with EDL Tool, then enter it and get stuff out via usb. You were most probably encrypted, in that case I honestly don't recall which TWRP handled stock encryption, but I guess the official one on twrp.me (axon7) does.
any reason you're still on stock, though? Friendly advice, take a hard look at the new Pie device-specific ROMs

Choose an username... said:
Did you have TWRP or anything else installed?
If you don't have TWRP, install it via EDL with EDL Tool, then enter it and get stuff out via usb. You were most probably encrypted, in that case I honestly don't recall which TWRP handled stock encryption, but I guess the official one on twrp.me (axon7) does.
any reason you're still on stock, though? Friendly advice, take a hard look at the new Pie device-specific ROMs
Click to expand...
Click to collapse
I tried flashing various versions of TWRP using the EDL tool and it always showed a success message at the end, but when I booted to recovery via the bootloader menu, it just went to DFU mode instead.
Also, i tried custom roms before but i switched back to stock for the camera quality.