Database Users

Stuck on TWRP without a system to boot to.

Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!

PriStol said:
Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!
Click to expand...
Click to collapse
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)

thecadman99 said:
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)
Click to expand...
Click to collapse
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.

PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.

d00lz said:
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.
Click to expand...
Click to collapse
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.

PriStol said:
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.
Click to expand...
Click to collapse
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Edit: Upon reflection, this is most likely because I have created an RSA key between the PC and my phone.

d00lz said:
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Click to expand...
Click to collapse
It just says error: device not found whenever I do a command.

Please help, I really dont know what to do.

PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?

yanis15 said:
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?
Click to expand...
Click to collapse
I tried to wipe but it just wrote "wipe failed". I do have a back up on my computer but for some reason when I try to connect my phone to my computer through an OTG cable, it doesn't find the backup. And my pc doesn't show anything when I connect my phone.

And now what i do with my Axon 7?

Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...

Let me link you my ingenious, allmighty Axon 7 Companion Thread.

Try to install twrp with MiFlash if you can enter edl mode

macerf said:
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Click to expand...
Click to collapse
Your phone works normally
You don't have fastboot
You have stock recovery
If this is the case then most surely you have EDL working...
Install TWRP from EDL mode:
This is taken from Controllerboy's guide
BE SURE THAT WINDOWS SHOWS FILE NAME EXTENSIONS!
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.

Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.

macerf said:
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
Click to expand...
Click to collapse
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again

Choose an username... said:
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Click to expand...
Click to collapse
Hello and thanks for the advice. Unfortunately it does not change anything.. I have done exactly as you say but the result does not change anything...io have connected the device, Open command window, type "adb devices ", is viewed as "Cd07b2e9 device ", I type "adb reboot EDL ", it restarts in EDL, then go to management Devices and is viewed as "QUSB_BULK ", Run command "Axon7tool-r GPT boot recovery " but it says "Failed to connect ", then I'll return to Device Manager, hold volume up & Down & Power, Icon disappears and returns after a few seconds, close window and launch command "Axon7tool-r GPT boot recovery " but still give "failed to connect "...
So, recapping: I have bootloader unlocked, I can get into EDL but PC does not see device although on Device Manager it exists...
I now launch device into the wall... problem solved.

if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.

kitcostantino said:
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
Click to expand...
Click to collapse
Of course I'm kidding... have just purchased this device, have a great hardware but the software does not go well for nothing. I have had a dozen phones, I changed about 60 ROMs, so for me it is not difficult to change the software...ma in this case have problems. Is it possible that I fail to solve this problem? Be a way to reset everything and start from scratch? Okay, the bootloader be unlocked but not be any other way to go back? I have seen many guides but not able to solve the problem. I fail to make flash of TWRP, fail to do downgrade to MM....io hope someone help me... thanks.

are you using a USB 2.0 or 3.0 port? it may not apply to this scenario, but with Motorola and RSD Lite, I always had to use usb 2.0 ports or it wouldnt see my device when flashing.
also, the steps @choose an username listed out are the best way to start from scratch, but obviously you have to be able to have your computer see the phone in the desired mode.
@DrakenFX has several guides in the axon 7 forums that should help once the computer sees the phone as well.

I use USB 3.0 with original cable ... but if you now tell me that maybe this is my problem, then I use USB 2.0. Thank you...

Good morning...
Nothing to do... I put the original cable on USB Port 2.0, have redone procedure from window PowerShell, on command "adb devices " Everything OK, on command "adb reboot EDL " It enters EDL mode, but then all the procedures are failed... if command "Axon7tool-R recovery GPT boot "I always get out of the inscription " Failed to connect ", it remains in EDL and I just have to reboot... I replaced the drivers with Zadig 2.3 but did not change anything... are there any other moors to make flash of TWRP? exist lthough an app that do this? I remember that for LG G3 I'll fix everything with an app...

Unable to enter fastboot mode after flashing

I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.

pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".

DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).

pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?

DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.

pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?

DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"

pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.

Can only boot into Andoid Recover/ZTE/P996A01 ...

Current scenario: I can only boot into Android Recovery.
Options on screen:
.Reboot system rom
.Reboot to bootloader
.Apply update from ADB
.Apply update from SD card
.Wipe data/factory reset
.Wipe cache partition
.View recovery logs
.Power Off
Select "apply udate from ADB" only allows me ADB sideload. Not sure how to sideload TWRP. Selecting any rom gives me signature issue.
When I select "apply update from ADB", Windows 10 devmgmt.msc shows "Universal Serial Bus devices: ZTE A2017U".
I cannot boot to get any serial port connection.
Your assistance is appreciated!

itsmeinarizona said:
Current scenario: I can only boot into Android Recovery.
Options on screen:
.Reboot system rom
.Reboot to bootloader
.Apply update from ADB
.Apply update from SD card
.Wipe data/factory reset
.Wipe cache partition
.View recovery logs
.Power Off
Select "apply udate from ADB" only allows me ADB sideload. Not sure how to sideload TWRP. Selecting any rom gives me signature issue.
When I select "apply update from ADB", Windows 10 devmgmt.msc shows "Universal Serial Bus devices: ZTE A2017U".
I cannot boot to get any serial port connection.
Your assistance is appreciated!
Click to expand...
Click to collapse
Of course you can't sideload TWRP... Things would be much easier
You left out a rather important piece of info. Is your phone unlocked? Do you have OEM unlocking or usb debugging enabled?
Also, the current scenario is nice to know, but how did you get there?? ?
From the MiFavor recovery you can only install MiFavor ROMs that have been signed by ZTE, so no luck there. You have 3 things to try:
-Factory reset and see if it works. Honestly not knowing what the heck you did doesn't help, but if it suddenly entered the recovery without you touching anything, then you will probably recover the phone by formatting your data.
-Turn it off, then hold Vol+ and Vol- together and connect the USB cable (should be connected to your PC on the other end). The phone will either flash a red light and stay black or keep the red light on. If the red light stays on, get the MultiDL tool from raystef and use it to enter EDL, if the red light went off it already was in EDL. Then use EDL Tool by djkuz with a package corresponding to your phone model to rewrite the system
-Tinker with the official update.zip files and an SD card (or adb sideload). The sd card method is much more reliable than adb sideload, so get one if you will try the official update method

Choose an username... said:
You left out a rather important piece of info. Is your phone unlocked? Do you have OEM unlocking or usb debugging enabled?
Also, the current scenario is nice to know, but how did you get there??
Click to expand...
Click to collapse
Thanks! I'll try your suggestions and report back.
As for how I got here, I previously only had issues and ran MiFlash to get TWRP and access to the SD-Card. I then installed A2017Uv1.1.0B35_Bootstack_by_DrakenFX.zip and then A2017Uv1.1.0B35_StockRecovery_by_DrakenFX.zip.
Not sure what I did incorrect.
I'll spend a few days trying your suggestions. Again .. Thanks for your suggestions.

itsmeinarizona said:
Thanks! I'll try your suggestions and report back.
As for how I got here, I previously only had issues and ran MiFlash to get TWRP and access to the SD-Card. I then installed A2017Uv1.1.0B35_Bootstack_by_DrakenFX.zip and then A2017Uv1.1.0B35_StockRecovery_by_DrakenFX.zip.
Not sure what I did incorrect.
I'll spend a few days trying your suggestions. Again .. Thanks for your suggestions.
Click to expand...
Click to collapse
What were you trying to accomplish by flashing those two files? The bootstack is part of the official update files, you shouldn't have to use them at all unless you are using custom ROMs.
You can use EDL Tool to get TWRP back, instead of reflashing stock which is usually a huge file. But download a full EDL file anyways, it might save your arse someday

Soft Bricked without TWRP - ADB can only sideload

Hi all, so I tried to flash a custom rom for the first time and was stupid enough to try to flash stock firmware (from here https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538) without first flashing TWRP.
Now when I boot into android recovery reboot and reboot to bootloader doesn't work and gives me a strange heart beat sound, also when powering off and plugging in the charger. Now I can only 'Apply update from ADB' and when using the adb tool I cannot do 'adb reboot edl' and can only sideload or get info.
When sideloading every file I tried gives an error when verifying, either 'footer is wrong' with 'error: 21' or that the whole-file signature failed.
I tried sideloading my read boot and recovery files, stock firmware bootstack & system and boot, twrp image, 7.1.1 b12 & b13 noverity images, and the eu v1.2.0 b13 update.
I have an EU version 7.1.1/NMF26V/20170909.121037 which is probably b13 which I last updated before trying to flash a custom ROM.
adb devices -l gives: 6064a8eb sideload product852A11 model:ZTE_B2017G device:tulip transport_id:2
Probably what needs to happen is for the phone to get into EDL mode, but I have no idea how.
The US version trick with both volumes buttons + power just gets me into Android Recovery, should I get an EDL cable?
Can anyone help me with this?
Thanks!

kerstmus said:
Hi all, so I tried to flash a custom rom for the first time and was stupid enough to try to flash stock firmware (from here https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538) without first flashing TWRP.
Now when I boot into android recovery reboot and reboot to bootloader doesn't work.
Click to expand...
Click to collapse
Hi! Try to check if the "Apply update from a SD card" option is active in the menu. It well may be.
The same problem happenned to my phone a couple of days ago after I deleted a custom rom, and the "apply update from the ADB sideload" menu option didn't work properly. However, I managed to install B16 firmware from my SD card via the "update from the SD card" menu line.
I have the EU Axon 7 mini version. The B16 firmware that successfully restored my phone is here: https://forum.xda-developers.com/showpost.php?p=79336783&postcount=91
As for the ways to get your phone into the EDL mode, you can try to push and hold "Volume -" and "Power" buttons simultaneously. This should bring your EU version phone into the FTM mode. Then you can check if the phone is seen via ADB ("adb devices" command). If yes, then just type "adb reboot edl". (However, in my case the buttons didn't work. )

nikaiako said:
Hi! Try to check if the "Apply update from a SD card" option is active in the menu. It well may be.
The same problem happenned to my phone a couple of days ago after I deleted a custom rom, and the "apply update from the ADB sideload" menu option didn't work properly. However, I managed to install B16 firmware from my SD card via the "update from the SD card" menu line.
I have the EU Axon 7 mini version. The B16 firmware that successfully restored my phone is here: https://forum.xda-developers.com/showpost.php?p=79336783&postcount=91
As for the ways to get your phone into the EDL mode, you can try to push and hold "Volume -" and "Power" buttons simultaneously. This should bring your EU version phone into the FTM mode. Then you can check if the phone is seen via ADB ("adb devices" command). If yes, then just type "adb reboot edl". (However, in my case the buttons didn't work. )
Click to expand...
Click to collapse
Yes, that worked. Thank you so much!