fastboot flashable boot.img - ZTE Axon 7 Questions & Answers

Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.

Exnocte said:
Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.
Click to expand...
Click to collapse
can't you flash recovery? I think someone made a flashable TWRP somewhere

Choose an username... said:
can't you flash recovery? I think someone made a flashable TWRP somewhere
Click to expand...
Click to collapse
I've tried to flash TWRP several time, but it won't boot...

Exnocte said:
I've tried to flash TWRP several time, but it won't boot...
Click to expand...
Click to collapse
you can try getting into EDL and using MiFlash to flash one of the zips on the Russian page 4pda. Go to the debrick page (the one with the phone carnage pictures inside), find the links for the chinese full recovery package. it will get you to the 4pda page. from there find a package that suits your needs (there is one with aboot and fbop) and flaah with MiFlash
Otherwise download the full B10 recovery package and flash it with MiFlash. you won't lose data but it might conflict if you were on Nougat

I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
 @op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck

Sn8K said:
I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
@op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck
Click to expand...
Click to collapse
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.

tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Humm ... Early morning for me ... i meant DFU. Vol+ & - while powering the phone Result on a black screen, and driver is recognized as Handset Diagnostic Driver (DFU COm port x)
Ind in that kind of brick, FTM is not accessible either.

tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Yeah that pretty much sums it up. If you get ZTE handset diagnostic driver on Ports COM&LPT you'll have to take your device apart and use the test point. If it is recognized as Qualcomm HS-USB QDLoader 9008 it means that you're on EDL. I'd reccomend trying to use miflash like i described, if it doesn't work return it or take it apart

Maybe a bit late for a reply, but I was able to get out of a similar situation (from DFU) by holding power and volume down for a long time. That got me to FTM and then I could reboot into edl via "adb reboot edl". Then I used the Axon7toolkit to flash fastboot and from there I could get to twrp and back in business. Any questions, let me know.

@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.

Sn8K said:
@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.
Click to expand...
Click to collapse
From what I read you have to let the device discharge totally, then you can get ftm. I had my battery fully charged when i bricked so i just did the 4th categ unbricking process

Related

Axon 7 A2017 problem

Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode
AmilDK said:
Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode
Click to expand...
Click to collapse
Flash universal bootloader and the modem for A2017 from the lineage os thread. Then you should get radio signal again.
I don't know how to do It Can you give me more information please?
AmilDK said:
I don't know how to do It Can you give me more information please?
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP
Choose an username... said:
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP
Click to expand...
Click to collapse
Thx for the help, i do not have bootloader unlocked and not have TWRP.
I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen
AmilDK said:
I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen
Click to expand...
Click to collapse
What version did you install? 3.1.1-0?
Followed a guide and with minimal fastboot and adb tool put in the phone the 3.0.4-0-ailsa_ii.img successful After that can't go on with steps and if try to open recovery nothing happen
Install Stock ROM from EDL with MiFlash.
WesTD said:
Install Stock ROM from EDL with MiFlash.
Click to expand...
Click to collapse
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl
AmilDK said:
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl
Click to expand...
Click to collapse
Is your phone on edl mode?
Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device
AmilDK said:
Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device
Click to expand...
Click to collapse
Try 'adb reboot recovery' from cmd
I don't know where i miss, i tried with adb and axon 7 tool, adb edl reboot, axon7tool axon7tool -r gpt boot recovery*, then axon7tool -w recovery, with twrp-3.1.1-0-ailsa_ii.img renamed in recovery bin, but from here nothing happen, i can't go in recovery if i try nothing happen black screen if i put the old recovery.bin can reboot in recovery but can't flash modem file or unlock bootloader. Tried with miflash but nothing happen give me error "cannot receave the hello packet"
PS my buil now is ZTE A2017GV1.2.0B04, the original one was ZTE_A2017V1.0.0B15
Choose an username... said:
What version did you install? 3.1.1-0?
Click to expand...
Click to collapse
i found a post with exactly my situation
https://forum.xda-developers.com/axon-7/help/sim-airplane-offbut-turnd-t3698325
perchance have you the file you talk in this post https://forum.xda-developers.com/showpost.php?p=74386034&postcount=24
i don't know how, but i did it.. with axon7toolkit, restored original rom, then updated to V.2.0.0B13, now works good

QFIL to Leeco le pro 3 (Lex722)

Hello everyone!
my problem is the next: I tried install a rom of MIUI but fail in my device, after, I tried to install differents roms but nothing work, just showed me the logo Leeco and no more, no avance from the logo.
But I still had recovery with TWRP and I thinked I can install official rom 26s, It was my error.
Now follow with the same problem but now I not have recovery mode (show me recovery with logo Leeco but it instantly turns off ) and bootloader is block.
My only hope, is QFIL to recover recovery mode o any rom, Does anyone have it or tell me how to create one?..
Please anybody will can help me, I have this problem 3 days ago.
Sorry for my bad english, I am learning.
PS. I tried with post of tora33 but no work
FlashOne2.0\le_zl1_qfil_ufs\prog_ufs_firehose_8996_ddr.elf"
22:00:34: ERROR: function: rx_data:247 Error occurred while reading from COM port
22:00:34: ERROR: function: sahara_main:854 Sahara protocol error
22:00:34: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.
Does your fastboot work volume and power down same time??
Sent from my LEX727 using xda premium
---------- Post added at 11:09 AM ---------- Previous post was at 10:53 AM ----------
worked on the phone i got off amazon. thanks!
[quote name="wpbear" post=71566961]This works on lastest USA update Stock (21s).
Have ADB/Fasboot tools on your computer
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device
Put emmc_appsboot.mbn from this zip (Download: x727-5.8.019s_bootloader-unlock.zip) in your adb directory on your PC
Put twrp.img from this zip (Download: TWRP) in your adb directory on your PC
On PC open admin CMD prompt
go into fastboot mode on phone (hold power and VOL -)
on PC type:
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
after flash force reboot using Power button. It will ask for a password, just ignore it and reboot back to fastboot by forcing power down then reboot to fastboot (hold power and VOL -)
on PC type:
fastboot devices
fastboot oem unlock-go
fastboot flash recovery twrp.img
boot into twrp (force power down, then hold POWER and VOL +)
TWRP will boot, choose modify system. Choose wipe - then swipe to factory reset, when that is done - then advacned then format data
In TWRP ensure MTP is enabled. In Windows File Explorer the phone should be visibile. Drag and Drop your new ROM.zip, gapps.zip, SU.zip etc...
In TWRP INSTALL new ROM and other zips; choose wipe/dalvik/cache
If you unlock bootloader push power off until it goes off then put it back into fastboot flash twrp .img them power off again power on when phone vibrate volume down you see stock recovery then twrp.
Reboot System.
DONE![/QUOTE]
Sent from my LEX727 using xda premium
voron00 said:
Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.
Click to expand...
Click to collapse
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.
zeckAlexs said:
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.
Click to expand...
Click to collapse
Every so often the same questions and the same answers.
You should read more. The X722 subforum is for something.
There is no qfil for X722, and there are no magic solutions of X720 / X727. This is an X722, it is locked and NOTHING of X720 / X727 is going to fix it.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Greetings.
How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked when you try to flash TWRP. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.
sk8223 said:
How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.
Click to expand...
Click to collapse
You know I don't really know how they keep doing it but I seen a lot new ones getting this phone and not really studying how to do this stuff and their not paying attention to what model this have this a solid phone.
Sent from my LEX720 using xda premium
This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip
paiktaras said:
This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip
Click to expand...
Click to collapse
ZL1 its x720/x727 not x722, it's a fix for ppl thata not work the normal qfil rom.

H918 stuck on fastboot.

One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
sing2x said:
One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
Click to expand...
Click to collapse
What does using the "fastboot reboot" cmd do ?
Ak7J4 said:
What does using the "fastboot reboot" cmd do ?
Click to expand...
Click to collapse
It goes back straight to fastboot after LG logo
If you can get into download mode try the 'upgrade' option in lgup
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
runningnak3d said:
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
Click to expand...
Click to collapse
I think that's what happen, and I don't have any choice except to wait . Returning to LG is not an option.
Thank you very much sir.
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
thee011 said:
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
Click to expand...
Click to collapse
If you cant get into download mode by powering off, holding vol up and then plugging into a pc (no power button needed) then you dont have a phone anymore. Unless rooted via dirtysanta which replaces aboot (which provides fastboot), the stock fastboot mode of the h918 can't actually flash anything to the phone which means no unbricking with it; TWRP and download mode are only ways to restore firmware.
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
wolf45801 said:
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
Click to expand...
Click to collapse
This is a Magisk 20.2 issue there's at two threads in the LGV20 forum on how to recover
Sent from my LG-H910 using XDA Labs

[SOLVED!][BRICKED!] Stuck in Fastboot mode and I can't boot into TWRP!

Hi I bricked my 6T. I tried to flash HavocOS ROM. But it wasn't installed properly where the systemUI wasn't working properly and I should've wiped my phone beforehand. I rebooted back into recovery and the internal storage was corrupted. I wipe data, but that didn't work and I wiped the system to get into a mode where the MSMDownload Tool can access it. But instead I'm stuck in Fastboot mode, but I could boot into TWRP.
But I followed this thread to recover my 6T through Fastboot, most of the commands worked not the system 'fastboot flash system_a system.img' this was the same for '_b' as well. It kept on saying 'error: cannot load 'system.img'' and now I can't boot into TWRP. Every option in fastboot mode just reboots to fastboot. I tried to get my situation across in each thread (Havocos and Fastboot rom thread) But no reply, I am running out of options and losing hope
If fastboot commands work, type in " fastboot reboot EDL "
then run the msm tool
kdog12 said:
If fastboot commands work, type in " fastboot reboot EDL "
then run the msm tool
Click to expand...
Click to collapse
It didn't work
You found the fastboot ROM thread, did you try flashing everything again from fast boot? Don't just flash what you think you need, reflash all of them. I got stuck in this loop recently and after flashing everything my phone booted as normal, and then I just started over, installing TWRP and rooting etc. Reloading AOSP.
Kept me from having to use the MSM Tool.
Extreme_Ninja2099 said:
It didn't work
Click to expand...
Click to collapse
What didn't work. How didn't it work. Didn't go to EDL mode? Or msm tool didn't work
kdog12 said:
What didn't work. How didn't it work. Didn't go to EDL mode? Or msm tool didn't work
Click to expand...
Click to collapse
The command didn't work
Extreme_Ninja2099 said:
The command didn't work
Click to expand...
Click to collapse
Is very simple to fix this....
Unplug... Hold power plus volume up till the device shuts off
Now with the device turned off and unplugged still.....
Hold both volume buttons for about five seconds and while continuing to hold plug in the USB..... Screen will stay black that's normal cause because the device is now in edl and the msmtool should be detecting it.......
Deleted

fastboot boot twrp.img [but stuck on splash screen]

Hey guys!
It's been a while since I've used my Mi A1. I turned it back on after a very long time and it was stuck on the android screen as if there was nothing to boot into so I tried booting into my recovery but there was nothing there either. I figured I probably formatted some stuff a while ago but I don't really remember what happened. Anyways, here's what I did next:
I could only boot into fastboot so I ran the command
Code:
fastboot boot path/to/tissot/twrp.img
but that didn't work.
So I flash the img to boot and tried rebooting to recovery but I was stuck on the android logo and again. I then again had to wait for my battery to run out before I could do anything else (I couldn't enter fastboot again. Only works when the phone is off for some reason)
I then erased the system partition using fastboot and tried booting into the recovery again but no luck. Can someone help me?
I know I messed up... big time. Someone save me
EDIT: Some more details
I tried two recoveries. The Pitch Black on XDA and also the standard "twrp-3.3.1-0-tissot.img" but had the same issue of getting stuck at the splash screen for both.
Also, I remember using Android 10 before all this happened.
EDIT 2: I ran the following commands:
Code:
fastboot set_active a
Code:
fastboot flash boot path/to/tissot/twrp.img
And I can now use the button combination to boot into recovery but I still get stuck on the splash screen
Hi,
have you fixed it? I face the same/similar issue, that I stuck at twrp splash screen after booting in twrp with fastboot
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I have erased/formatted everything (userdata, cache, boot) and also tried to reflash the original rom with mi flash tool, but without success.
Any ideas?
MBR might be creating problem , try clean install with mi flash tool with official ROM .
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
xiaomiA1 said:
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
Click to expand...
Click to collapse
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
MIN313 said:
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
Click to expand...
Click to collapse
If Phone Showing Charging Only and Can't Even Transfer Data , Not Detected on Pc then will have to do EDL flash
My phone is recognized by MiFlash when I enter the fastboot mode
It is also shown with
Code:
fastboot devices
and I can boot into TWRP, but it stucks in splash screen of twrp.
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I also tried older versions of twrp for tissot.
smilar issue, following attempts:
flashed with MiFlash, with or without EDL
flashed installing image with twrp
flashing after wiping dalwik, data, system and so on
flashed several type of ROM: official from xiaomi, crdroid, pixel, lineage
phone only booting with twrp (if installed) or stuck on mi logo

Categories

Resources