Going into Fastboot just reboots? - ZTE Axon 7 Questions & Answers

I just killed my TWRP by flashing the recommended one for Lineage 15.1 and need to reflash it. Unfortunately,
Code:
adb reboot bootloader
or the fastboot option in the bootloader or holding down volume down and plugging in the cable just reboot into LineageOS. How do I get into fastboot? I am unfortunately not rooted so I am in an uncomfortable position where I have no other options, I guess?

Fastboot mode was removed by ZTE.
So simply use the axon7toolkit to apply what you want
Gesendet von meinem SM-G965F mit Tapatalk

marcus.linkenbach said:
Fastboot mode was removed by ZTE.
So simply use the axon7toolkit to apply what you want
Gesendet von meinem SM-G965F mit Tapatalk
Click to expand...
Click to collapse
Thanks for your help. Would not have remembered this tool since I have not used it since unlocking my bootloader.
Just a sidenote: If I remember correctly, fastboot was used to unlock the bootloader? And since then I've not used ZTE's ROMs. So how can they have removed it on my device?

TheGreatB said:
Thanks for your help. Would not have remembered this tool since I have not used it since unlocking my bootloader.
Just a sidenote: If I remember correctly, fastboot was used to unlock the bootloader? And since then I've not used ZTE's ROMs. So how can they have removed it on my device?
Click to expand...
Click to collapse
They removed it with any marshmellow Update

marcus.linkenbach said:
Fastboot mode was removed by ZTE.
So simply use the axon7toolkit to apply what you want
Gesendet von meinem SM-G965F mit Tapatalk
Click to expand...
Click to collapse
Doesn't the toolkit use fastboot? When I select Install TWRP option, it wants to reboot to bootloader, the device proceeds to boot into the ROM and the toolkit says "fastboot not installed" or something like that.

Yes it does but before it installs fastboot. Do it with miflash. I am not at home and cannot help at this moment. Sorry
Gesendet von meinem SM-G965F mit Tapatalk

marcus.linkenbach said:
Yes it does but before it installs fastboot. Do it with miflash. I am not at home and cannot help at this moment. Sorry
Gesendet von meinem SM-G965F mit Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help as best as you currently can
I read MiFlash is somehow included in the toolkit. Information about how to use MiFlash to install fastboot isn't easy to find. And some guides say having the 2017or 2017U version is required (I have 2017G). I would be very grateful if you could provide instructions on how to do this when you are back at home

Yes I will. I have the G Version as weil.
Gesendet von meinem SM-G965F mit Tapatalk

I think I found another way, can I just use the axon7tool (not toolkit) to flash TWRP in EDL mode and thereby skip the hassle with fastboot?

You can but with miflash it is much easier.
Open miflash and select
Axon7Development\Axon7toolkit\miflash\unlock\ and then MM or N
Start flashing...that's it
Gesendet von meinem SM-G965F mit Tapatalk

I used the axon7tool, worked like a charm Seemed less scary to me. Thanks for your help, I'm sure your way would have worked as well

TheGreatB said:
I used the axon7tool, worked like a charm Seemed less scary to me. Thanks for your help, I'm sure your way would have worked as well
Click to expand...
Click to collapse
The easiest one by far is EDL Tool by djkuz, since it has a mode for doing this and it's not nearly as finicky as axon7tool (and much more reliable than axon7toolkit), while the miflash method seems too hacky.
Now that you used axon7tool you won't be able to use EDL things like EDL tool or miflash because you have the Zadig driver installed; if you ever need to use EDL just uninstall the driver and let Windows get the normal EDL one

Related

Unknown partition while trying to flash via fastboot

Hi!
So everything crashed after i tried this Ubuntu Touch, I go back to PA and I don't have radio and imei in Settings now (it's showing .84 in fastboot mode). No signal at all. So i tried to flash stock via fastboot, but it says that something about 'unknown partition'.
'adb devices
fastboot reboot-bootloader
flash radio-mako-m9615a-cefwmazm-2.0.1700.84.img'
and there is this error about uknown partition 'cannot determine image file'. I don't know what to do, cause I really need my phone's signal ...
Thanks for any help, and don't flash this Ubuntu Touch ...
I'm trying to flash stock rom via recovery, will see what happen.
jahlovePL said:
Hi!
So everything crashed after i tried this Ubuntu Touch, I go back to PA and I don't have radio and imei in Settings now (it's showing .84 in fastboot mode). No signal at all. So i tried to flash stock via fastboot, but it says that something about 'unknown partition'.
'adb devices
fastboot reboot-bootloader
flash radio-mako-m9615a-cefwmazm-2.0.1700.84.img'
and there is this error about uknown partition 'cannot determine image file'. I don't know what to do, cause I really need my phone's signal ...
Thanks for any help, and don't flash this Ubuntu Touch ...
I'm trying to flash stock rom via recovery, will see what happen.
Click to expand...
Click to collapse
I can't copy the zip of stock rom to the sd card. So yeah, partitions are ****ed up.
Flash a factory image, that should help.
Gesendet von meinem Nexus 4 mit Tapatalk
jadephyre said:
Flash a factory image, that should help.
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
Didn't you read what i wrote here? I can't flash anything cause there's this unknown partition error.
you forgot the partition in the Flash Command u Should use this "fastboot flash radio nameofradioimg.img

[CLOSED]Yoga Tab 2 - what the bri(**ck) is going on?

@MikeChannon removed OP. please close
what? lol
Hey thanks for this explanation! I have a question: Ist it possible to flash a BIOS through dnx? Because i have a different device Intel z3575 SoC, with AMI BIOS and working dnx mode but no booting. I just get bootloops after the manufacturers Logo also I noticed that in BIOS Menu I can't choose any devices to Boot from. Booting into EFI shell or bootable USB stick doesnt work either.. I accidentally flashed a dual Boot BIOS for win/Android to an Android only device. Maybe the partition table is wrecked. I need to find a way to flash the original BIOS, which I have, back on to the device with dnx and mft tool. Any suggestions?
Gesendet von meinem SM-G920F mit Tapatalk
mirco446 said:
Hey thanks for this explanation! I have a question: Ist it possible to flash a BIOS through dnx? Because i have a different device Intel z3575 SoC, with AMI BIOS and working dnx mode but no booting. I just get bootloops after the manufacturers Logo also I noticed that in BIOS Menu I can't choose any devices to Boot from. Booting into EFI shell or bootable USB stick doesnt work either.. I accidentally flashed a dual Boot BIOS for win/Android to an Android only device. Maybe the partition table is wrecked. I need to find a way to flash the original BIOS, which I have, back on to the device with dnx and mft tool. Any suggestions?
Gesendet von meinem SM-G920F mit Tapatalk
Click to expand...
Click to collapse
you need to give more details... what is your tab model? also give me a link to a (known by you) stock rom for your device
First of all thanks for the quick answer.
The Device is Teclast X98 Air iii (3) 32 GB wifi rev. M5C5 I accidentally flashed the BIOS for the x98 air 3g (c5j6) because in tecknights tutorial it was unclear that it was not supported by my device.
The link to the ROMs :
http://forum.xda-developers.com/x98-air/development/mirek190romv5-0-android-lollipop-t3206772
The Rom itself worked at first when I only flashed the Rom and not the BIOS. Then I tried to flash the dual Boot BIOS from Here:
http://forum.xda-developers.com/showpost.php?p=62823494&postcount=3
Because it said compatible with virtually all air devices. I know at least 5 other people who now have the same problem with broken bios and bootloops.
I have the original BIOS file from Teclast site but I cant find the link right now.
If you need the original file I would upload it and provide it but I'm not at my desktop ATM.
Gesendet von meinem SM-G920F mit Tapatalk
mirco446 said:
The Device is Teclast X98 Air iii (3) 32 GB wifi rev. M5C5 I accidentally flashed the BIOS for the x98 air 3g (c5j6) because in tecknights tutorial it was unclear that it was not supported by my device.
Click to expand...
Click to collapse
downlad and extract the attached zip
place your tab in DnX mode (Fastboot Starting...) and input:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
tell me if it boots to the droidboot menu
It does Boot to droidboot
Gesendet von meinem SM-G920F mit Tapatalk
mirco446 said:
It does Boot to droidboot
Gesendet von meinem SM-G920F mit Tapatalk
Click to expand...
Click to collapse
have you used the zip file i provided?
there is no zip file attached :/
mirco446 said:
there is no zip file attached :/
Click to expand...
Click to collapse
fixed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thats what it boots to. Before it Booted it said couldn't find device handle but it was too fast for me to take a pic
Gesendet von meinem SM-G920F mit Tapatalk
---------- Post added at 01:54 PM ---------- Previous post was at 01:46 PM ----------
You think it would be possible to flash a recovery image that supports adb? Because I have a flashing routine that can flash bios through adb but i dont have adb in this recovery
mirco446 said:
thats what it boots to. Before it Booted it said couldn't find device handle but it was too fast for me to take a pic
Gesendet von meinem SM-G920F mit Tapatalk
---------- Post added at 01:54 PM ---------- Previous post was at 01:46 PM ----------
You think it would be possible to flash a recovery image that supports adb? Because I have a flashing routine that can flash bios through adb but i dont have adb in this recovery
Click to expand...
Click to collapse
i am making now a bios flashing tool from the droidboot image (that is why i needed confirmation that it boots to the droidboot menu)
i will send in in a few minutes a test one (will not change anything, it will just run and reboot at the end, will be used only for testing and after you send me the bios file i will include it and make the final version)
My friend! You got a Donation Account? Would donate you some beer!
Theres the link for the original firmware:
https://drive.google.com/file/d/0B-DELdERnCp-TGp3dDJSeVpUVzA/view?usp=sharing
mirco446 said:
My friend! You got a Donation Account? Would donate you some beer!
Theres the link for the original firmware:
https://drive.google.com/file/d/0B-DELdERnCp-TGp3dDJSeVpUVzA/view?usp=sharing
Click to expand...
Click to collapse
download, extract and input (tab in DnX mode):
fastboot flash osloader efilinux.efi
fastboot boot testboot.img
if ok it will say so on your tab and reboot after the counter
will not change nothing, just test
Okay so it did this again and then after a few seconds it rebooted. Did not See a counter ( was i supposed to?)
Gesendet von meinem SM-G920F mit Tapatalk
Okay, for the readers, ionioni is the man! He managed to create a flashable .img that we can use to restore the original BIOS on m5c5 (and probably other devices) through fastboot/dnx!
I will set up a thread at X98 Air Forums with the details!
Guy doesn't even want me to buy him a beer! Oh and by the way, he did this without having any knowledge about the device at hand true master.
-solved

Bricked Jiayu s3, help please

Hello, I tried an upgrade to android 7.1 but my device is bricked now. It is in a loop and only the Jiayu logo shows up and it shuts off again. Not possible to get it into the (Chinese) recovery mode. It is possible to get it in the fastboot mode though, but when i connect the device to my laptop and run "adb devices" in windows command screen the phone is not found. So i tried to install the right drivers, but without succes. I don not know what to do anymore.
Can anybody help me?
Thanks
don't panic. I am sure you will be NOT the first one that can brick our phone. Let's take it step by step. First of all check with version of S3 you got, and if you installed the correct rom version. Then download (again) the correct one.
You don't have to enter Chinese Recovery. When you power on the phone hold the volume + until after the short vibration and check if you enter the TWRP Recovery. Then report here or install the rom again.
sent from my JiaYu S3 through TapaTalk
gorillaz_gr said:
don't panic. I am sure you will be NOT the first one that can brick our phone. Let's take it step by step. First of all check with version of S3 you got, and if you installed the correct rom version. Then download (again) the correct one.
You don't have to enter Chinese Recovery. When you power on the phone hold the volume + until after the short vibration and check if you enter the TWRP Recovery. Then report here or install the rom again.
sent from my JiaYu S3 through TapaTalk
Click to expand...
Click to collapse
It's a S3 advanced with mt6752, i used the right rom, but i f..ked it up. Sorry.
Press power + volume up gives fastboot mode. That's the only thing that stille opens in the phone.
No recovery, nothing happens. Not starting up, in a loop. Battery is almost empty and won't charge anymore.
So, in my opinion my only chance is fix it with fastboot mode, but my pc cannot find the device.
So, i think that's because of the drivers, but i installed them.
So, i know i can open up the pc for usb connection with windows command, but i don't know the command.
Step by step > which step to do now?
Thanks
Device not found
I don't understand. I installed the drivers and put my laptop in test mode. Still device not found in fastboot. There's nothing i can do anymore. When i can connect the s3 with laptop in fastboot then i can fix this i think. But i am stuck. Any advise?
why don't you use SP Flash Tools to install an older rom? perhaps Rc4? check it out on needrom.
sent from my JiaYu S3 through TapaTalk
Can i flash a rom in this situation? I mean, the phone doesn't do anything, will it be flashed then?
I tried before, but i cannot found scatter file. Where can i find this? I can try flashtool.
On the other hand, why does fastboot not work? Do you understand that?
For flashing I always used this tutorial, it's German but it should be understandable with Google translator: http://mastazone.de/jiayu-flash-anleitung/
Could you exactly tell us what you have done. For example which file did you try to install...
If you have any questions regarding the German site ask me (German native here)
Gesendet von meinem S3 mit Tapatalk
supermar10 said:
For flashing I always used this tutorial, it's German but it should be understandable with Google translator: http://mastazone.de/jiayu-flash-anleitung/
Could you exactly tell us what you have done. For example which file did you try to install...
If you have any questions regarding the German site ask me (German native here)
Gesendet von meinem S3 mit Tapatalk
Click to expand...
Click to collapse
Hello, I tried to put the 7.1 on the s3 but i did it the wrong way obviously. Now the s3 is bricked.
I want to flash, but i need to find an scatter.txt file and it's just not there.
Also my pc cannot find the s3 in fastboot mode.
I hope (and think) there's still a solution, but i am a layman and not that technical. I flashed and fastboot before, but now i cannot succeed somehow.
Can you help me step by step?
I went to the German site and downloaded the SP Flash Tool and the ROM.
Now what to do?
try Google and search for a mtp mega drive pack to install again in your pc...
sent from my JiaYu S3 through TapaTalk
1. Download the file Jiayu RC5
2. Download the MTK VCOM USB[16KB]
3. Download the SP Flashtool V5.1548.00.0000
Extract all files. All downloads from the site linked above
4. Shut down your phone(battery out)
5. Open device manager
6. Connect it by USB to your computer
7. Right mouse click on the entry Mt65xx Preloader
8. Click on update driver
9. Click on search on the computer for drivers(or a similar text)
10. Navigate to the folder you extracted the Mtk vcom USB to
11. Check the box also search sub folders
12. Wait until its finished
13. Open the flashtools software as admin(right mouseclick open as administrator)
14. Click on download(next to Format and Readback)
15. Click on scatterloading file. It is in the folder where you extracted the rc5 file
16. In the drop down box click firmware upgrade
17. First click the green download button and then connect your device. The lower bar should be red at first. It is ready when the green hick shows up
Questions left?
Gesendet von meinem S3 mit Tapatalk
---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------
This is how the flash tool should look before hitting the download button:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem S3 mit Tapatalk
Hallo Mario, yes I have this screen (finally), but it says "PMT changed for the ROM, it must be downloaded" The line was red and 100%, but there it stuck.
Cannot find MT67xx preloader in Device Manager.
Is there any juice left in your battery? Is it still showing the green logo?
Is it charging? If not try removing the battery for a few seconds put it back in and then hook it up to a charger
If the mt65xx does not show up, flashtools won't work.
What operating system do you have? Are the drivers installed correct?
Did the flash tool showed some reaction she plugged the phone in? Like a box with chip info as title? If so the drivers seem to be installed correct.
Are you sure you selected firmware upgrade?
Gesendet von meinem S3 mit Tapatalk
Mario!
The flashing went well, yes! Empty battery, but it worked. I forgot to choose upgrade, thanks my friend.
So, now the s3 is on 5.1
What I want to do is:
Install TWRP on the s3 and then install 7.1
Can I flash TWRP the same way as the firmware?
Glad it worked
TWRP should have been installed automatically at least for me it was. So try to boot to twrp
Gesendet von meinem S3 mit Tapatalk
Yes, you're right. Boot to twrp (2.8.7.0)
Can i install the android 7.1 rom with this twrp or
should i install twrp 3.02 first for installing the upgrade to 7.1?
Can i put twrp 3.0.2 on the phone with fastboot?
Or just copy the software to the internal storage and install with twrp?
Or with flash tool again?
I used to install twrp with fastboot.
Almost there...
I would recommend updating twrp first. Just boot into twrp and flash it
Gesendet von meinem S3 mit Tapatalk
How exactly? Just put the twrp 3.0.2 in the phone (internal storage) and open the phone in twrp recovery and then choose twrp 3.0.2 and install it?
Yeah
At least I did so. I think you could do it with fastboot but I'm not sure
Gesendet von meinem S3 mit Tapatalk
supermar10 said:
Yeah
At least I did so. I think you could do it with fastboot but I'm not sure
Gesendet von meinem S3 mit Tapatalk
Click to expand...
Click to collapse
PC doesn't recognize S3 anymore. Very strange, it did before. So now i cannot drag twrp (new version) to internal storage.
Any suggestions?

After Unlock and CM13 no TWRP

Hello everybody,
My english is very bad please excuse me. I hope I am right here.
I have my mobile phone gerootet and wanted to install CM13 ..
After restarting, CM wants a password. In the guide, which you should not change / must / need. Unfortunately, it is not progressing. Then I wanted to flash the stock ROM again. Unfortunately, this is no longer the case. I can only get into the Fastboot & Rescue MODE. There stands PHONE Unlocked FRP Unloock. By "platform tools" I can reach fastboot devices. ADB does not work. When I type fastboot flash twrp.img, it copies it. After a reboot I only enter the EMUI recovery ..
The data were already already deleted by TWRP all.
How can I save my phone?
Update
It does not even start the system (CM).
If you want to delete "fastboot erase xx", "Failed (remote: Command not allows)" appears
Is there still any help?
Here is a small video to the problem.
youtube.com/watch?v=PhgONyr5YMY
go back to the official firmware and start over again
I can The official Firmware flash with a zip over fastboot?
directupload.net/file/d/4588/daa7qcoq_png.htm
Gesendet von iPhone mit Tapatalk
thilak devraj said:
go back to the official firmware and start over again
Click to expand...
Click to collapse
THANK YOU :good::fingers-crossed:
I have found it. I must the Update.app extract...
bambino24 said:
THANK YOU :good::fingers-crossed:
I have found it. I must the Update.app extract...
Click to expand...
Click to collapse
Did you fix your problem, i am having the same problem
You must Download the original Firmware.
Extrakt this Firmware.
In the folder is a Update.app File.
With the Huawei Extraktor Software must you Extrakt the Update.app File.
In the Extrakt Software is the System.img, Boot.img and all other .Img Files.
Over the fastboot (cmd) can you Flash your devices.
forum.xda-developers.com/showthread.php?t=2433454
Ich hope you understand me with my very Bad Englisch
Gesendet von meinem FRD-L09 mit Tapatalk

Help needed: I think I hosed my OP5 trying to flash a ROM

I've been installing ROMs for a couple years, back to my LG G3 but this is the first major hiccup I've run into.
So I was trying to install This ROM. For some reason it never got through the initial boot sequence and then wouldn't boot past TWRP.
Now I had taken a backup before doing the wipe/flash but even that won't boot. Sometimes TWRP will read "no OS installed" or it will get to the boot screen for OOS (The red circle with the white dots going around it)
I'm kind of at a loss here because my backups won't boot and neither will the ROM I have downloaded. They all will just get to the boot screen.
Any help is much appreciated. Also going to post on XDA.
EDIT: Now it's when trying to boot to recovery it is booting into a ONEPLUS screen which I have not seen before. It isn't going to TWRP any longer. It has the oneplus logo and what looks like stars near the top.
Here are my options from there:
Install from internal storage
Install from ADB
Wipe data and cache
Advanced
Exit
Anybody know what screen this is?
sippinhenn said:
Anybody know what screen this is?
Click to expand...
Click to collapse
Stock Recovery Screen. Put your phone in fastboot mode, download latest bluspark twrp and flash it with fastboot flash recovery filename. After that you can boot to twrp again. Download the last official release and put the ROM on your phone and then install it.
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
addicted1900 said:
Stock Recovery Screen. Put your phone in fastboot mode, download latest bluspark twrp and flash it with fastboot flash recovery filename. After that you can boot to twrp again. Download the last official release and put the ROM on your phone and then install it.
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
Click to expand...
Click to collapse
Thanks. I actually tried doing this but for some reason when I try to flash blu spark via fastboot it's not seeming to like it. I can do the regular twrp but not blu spark. Is this the right file location?
I tried flashing twrp and sideloading a couple different ROMS but they all get stuck in the boot animation, strange huh?
I did notice that when I am in fastboot name it says the following:
PRODUCT_NAME - QC_REFERENCE_PHONE
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION
SERIAL NUMBER - (MY SERIAL)
SECURE BOOT - yes
DEVICE STATE - unlocked
Should the bootloader version and baseband version be empty like that? I'm at a loss right now and don't know what to do at this point.
Edit: Found this link where someone has the same deal, empty bootloader so that's reassuring
https://forums.oneplus.net/threads/bummer-my-op3-is-now-a-paperweight.452125/#post-14999707
Rename recovery, like 3.2.1.8.61. The name it's too long.
In FastBoot mode type, or copy/paste:
fastboot flash recovery 3.2.1.8.61.img
Why such a complicated name? Just name it recovery.img
Is your phone encrypted or decrypted?
ROMs only work on one or the other and will result in a bootloop if flashed on the wrong encryption status.
Man started supporting encrypted devices, though I don't know if the one you mentioned, or the ones you've tried, do support that.

Categories

Resources