fastboot failed (remote, unknown command) - ZTE Axon 7 Questions & Answers

So i tried restoring my axon 7 back to stock and did using edl flash tool. However i am unable to lock the bootloader. I always get the same error command (remote, unknown command) and now i decided to stay with lineage 16 and a schwifty kernal i cannot go back as i now cannot install twrp. Same error commands in fastboot.
The phone is currently on a marshmallow build i think b29. Its a 2017u model..
It says secure boot enabled on fastboot. Is this the route of my problems with trying to lock the bootloader and now flashing twrp???
I bought the phone used last year in Toronto with Nfounds twrp already installed so i just moved things along using the twrp img installer and ran lineage 16.0.
Any help appreciated either locking this bootloader or tbh now getting twrp 3.2.3-0 back on it so i can for the time run LOS16 and schwifty.
cheers

Jcth1 said:
So i tried restoring my axon 7 back to stock and did using edl flash tool. However i am unable to lock the bootloader. I always get the same error command (remote, unknown command) and now i decided to stay with lineage 16 and a schwifty kernal i cannot go back as i now cannot install twrp. Same error commands in fastboot.
The phone is currently on a marshmallow build i think b29. Its a 2017u model..
It says secure boot enabled on fastboot. Is this the route of my problems with trying to lock the bootloader and now flashing twrp???
I bought the phone used last year in Toronto with Nfounds twrp already installed so i just moved things along using the twrp img installer and ran lineage 16.0.
Any help appreciated either locking this bootloader or tbh now getting twrp 3.2.3-0 back on it so i can for the time run LOS16 and schwifty.
cheers
Click to expand...
Click to collapse
If you lock the bootloader while running anything other than stock ROM and recovery you'll brick the phone. Try using a B19 EDL package to return to stock B19, where there's fastboot. Then enter fastboot, and use the command
fastboot oem lock
and it should lock.

I did run the fastboot command and it was always coming up with the remote, unknown command error.
Doesn't matter now as I decided I'll keep the phone so used one of the toolkits to unlock the bootloader and fastbooted twrp 3.2.3-0 to it and reverted back to Los 16.
My issues mainly was when I put it back to stock I still had the device not encrypting screen upon reboot whereby I could choose to not let it boot within 5 seconds and scroll into recovery or bootloader.

Related

Can anyone help me fix my Axon 7.

I tried to unlock my phone (A2017G) and flash lineage OS today following Controllerboys guide, but must have done something wrong, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore just the stock recovery.
Is there a way that I can just flash stock OS and be able to use my phone?
King Norman said:
I tried to unlock my phone (A2017G) and flash lineage OS today following Controllerboys guide, but must have done something wrong, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore just the stock recovery.
Is there a way that I can just flash stock OS and be able to use my phone?
Click to expand...
Click to collapse
That's not an error message, it's the unlocked bootlaoder screen. get used to it, you're gonna see it every time you reboot
You probably didn't flash the Universal Bootloader. You didn't even read. You should install TWRP again with axon7tool, then get there and flash the Universal Bootloader, then the A2017G modem, the the ROM. If that doesn't work just download MiFlash and the latest G package and flash it

Corrupted recovery, no o/s, what to do now?

I have a Axon 7 A2017U, bootloader unlocked. My recovery is corrupted after attempting to flash a older version of TWRP in recovery. I can no longer reboot into TWRP via recovery, it hangs at the ZTE powered by screen. I can't boot into the o/s, it too was corrupted while attempting to restore to stock using the DrakenFX's guide.
Booting into fastboot is a no go either, it just hangs at bootloader screen.
Any suggestions on where to go from here or how to fix the corrupted recovery?
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Teet1 said:
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Click to expand...
Click to collapse
Thanks, I flashed it with A2017U_B19-NOUGAT_FULL_EDL and was able to flashed twrp recovery. I was hoping the o/s would be fixed too but I get this error message as soon as o/s load "settings keeps stopping, close app". It appears it's a bad or incorrect stock file. I had to format data in TWRP recovery as the drive was encrypted. So now i'm back at square one.
Bad o/s but working recovery, so I attempted to flash these files to get back to stock but was unsuccessful. It would flash halfway and then just restarts and hung at the bootloader unlock screen.
A2017UV1.0.0B29_RollBackModded.zip
A2017UV1.1.0B32_bootstack_by_DrakenFX.zip
A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip
Am I on the right track? Or should I be flashing with a different os variant?
freeb0rn said:
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Click to expand...
Click to collapse
So you didn't read all of the hurdles and warnings about locking the bootloader with non-stock firmware?
Plus you also didn't find out about the Universal Bootloader? Did you even read the installation steps???
You had an error 7, which is that you forgot to install the Universal Bootloader. Do so this time.
EDL has nothing to do with ADB. You can access it with the phone completely off... (volume up and down, and insert usb)

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

ZTE Axon 7 A2017G Bootloader not booting

I was going through the usual steps of flashing lineage 14.1 to my Axon 7.
In one of the guides i was following it recommended downgrading to android marshmallow before flashing lineage, which i did.
I had TWRP installed however this got removed when i flashed the stock marshmallow file which included stock recovery.
However, i cant get it to boot into fastboot, i tried, "adb reboot fastboot", and tried the manual method by holding down the power and + vol.
When it reboot it just skips fastboot and just boots normally
I'm not sure what is wrong, whether the bootloader is corrupt or it is completely missing.
I'm not sure how i can flash a new bootloader if i can't use fastboot. If there is a piece of software out there that can flash without fastboot i would be thankful for a pointer.
GeorgeJohnson5610 said:
I was going through the usual steps of flashing lineage 14.1 to my Axon 7.
In one of the guides i was following it recommended downgrading to android marshmallow before flashing lineage, which i did.
I had TWRP installed however this got removed when i flashed the stock marshmallow file which included stock recovery.
However, i cant get it to boot into fastboot, i tried, "adb reboot fastboot", and tried the manual method by holding down the power and + vol.
When it reboot it just skips fastboot and just boots normally
I'm not sure what is wrong, whether the bootloader is corrupt or it is completely missing.
I'm not sure how i can flash a new bootloader if i can't use fastboot. If there is a piece of software out there that can flash without fastboot i would be thankful for a pointer.
Click to expand...
Click to collapse
You got stuff wrong. I don't know if 'reboot fastboot' works, but it's actually "reboot bootloader". Plus they got rid of it since Marshmallow, and you have to install it if you want it.
Use EDL and install TWRP with it (EDL Tool by djkuz , or axon7tool by tennear). Don't even reflash the bootloader
Choose an username... said:
You got stuff wrong. I don't know if 'reboot fastboot' works, but it's actually "reboot bootloader". Plus they got rid of it since Marshmallow, and you have to install it if you want it.
Use EDL and install TWRP with it (EDL Tool by djkuz , or axon7tool by tennear). Don't even reflash the bootloader
Click to expand...
Click to collapse
Thank you, all fixed now and Lineage installed

Failed Update from 10.3.12 to 11 - Assistance Appreciated

Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
SMcC2 said:
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
Click to expand...
Click to collapse
An attempt to flash TWRP and reflashing should go.
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
I did not have time to wait so before bed I just reset everything.
I ended up using the MSM tool located here:
The Complete Guide to Unbrick OnePlus 6/6T from a Hard-Brick using MSMDownload Tool
Unlocked bootloader, installed TWRP & Magisk, installed A11 zip, everything is working again now.
Good luck!
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Artificial_Intelligence said:
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Click to expand...
Click to collapse
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
s.seila said:
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
Click to expand...
Click to collapse
Hm but how would I install lineage recovery? Flashing recovery through fastboot doesn't work on the new devices anymore right?
I also tried booting lineage recovery without flashing but that also didn't work (although it didn't get stuck on crashdump but booted into the regular OS instead).
I did notice that it seems to be related to OOS 11 firmware. On 10 booting into TWRP works just fine and as soon as I upgrade to 11 it stops working (maybe this means it's fixable?). What I used as a workaround for now is to have 10 firmware in one slot, upgrade other slot to 11 and flash TWRP to both slots from the 10 slot. Seems to work so far but is not ideal IMO. I'm not a developer sadly but maybe someone smarter than me will come up with a solution.
What do you mean by "new device"?? New OOS version right??
I use this method all the time with oos 11.x.x.x.x to install TWRP so i can install Custom ROM later.
no need to go to oos 10 you can flash it from newest oos11.
---------------------------------------------------------------------------------------------------------------
First boot into fastboot mode.
to install lineage recovery
fastboot flash boot <lineage recovery image>.img
download from here https://download.lineageos.org/fajita
menualy select and boot to recovery. It will boot to lineage recovery.
lmao it appear in two posts. deleted 1.

Categories

Resources