I need to return a "Used - Like New" condition phone to Amazon that I recently purchased since I noticed it has severe red tint in one corner of the screen. Problem is, I was in the process of rooting the phone when I noticed.
Current status of the phone:
Unlocked bootloader
Flashed TWRP
Flashed stock B32
Phone has not actually been rooted
I've been trying to get the phone back to completely stock before I send it back, but I'm running into issues. I've tried using the Axon7Toolkit and when I select option 11, "Restore to Stock (EDL)" and go to flash B19 in MiFlash, I've gotten either the error "Cannot find programmer file" or "Cannot receive hello packet".
I've also tried flashing the stock recovery back using the ADB commands, "adb reboot-bootloader" then "fastboot flash recovery recovery.img" with the recovery I grabbed from the stock B32 zip. With that, it just says waiting for device and nothing happens.
Any thoughts? Really not sure what else to try other than just sending it back as is.
newbrightwhites said:
I need to return a "Used - Like New" condition phone to Amazon that I recently purchased since I noticed it has severe red tint in one corner of the screen. Problem is, I was in the process of rooting the phone when I noticed.
Current status of the phone:
Unlocked bootloader
Flashed TWRP
Flashed stock B32
Phone has not actually been rooted
I've been trying to get the phone back to completely stock before I send it back, but I'm running into issues. I've tried using the Axon7Toolkit and when I select option 11, "Restore to Stock (EDL)" and go to flash B19 in MiFlash, I've gotten either the error "Cannot find programmer file" or "Cannot receive hello packet".
I've also tried flashing the stock recovery back using the ADB commands, "adb reboot-bootloader" then "fastboot flash recovery recovery.img" with the recovery I grabbed from the stock B32 zip. With that, it just says waiting for device and nothing happens.
Any thoughts? Really not sure what else to try other than just sending it back as is.
Click to expand...
Click to collapse
Well you should just download an EDL package and flash it via MiFlash. you need a Windows PC with 64 bit support. There are plenty of guides but basically you have to get an A2017U_FULL_EDL package (just be sure that it's for the A2017U!) then download MiFlash, then get ADB while the phone's on and issue 'adb reboot edl'. The phone will seem off but it is not, it is in EDL (no indication, just trust me). If you open Device Manager the phone should appear as Qualcomm HS-USB QDLoader 9008 under the Ports (Com & LPT) tab. Simply unpack the FULL_EDL file, point MiFlash to it, and flash away.
After that read a guide for the U on how to relock. It is VERY dangerous, so read carefully!
Solved. Followed the advice I received on another forum:
This what I do exactly, "adb reboot edl" on my computer. Open MiFlash, refresh, and flash this package "A2017U_B15-NEW_FULL_EDL.zip" [cannot post link] Takes awhile, then once I verify it's B15, and stock recovery. Then "ADB reboot bootloader" And "fastboot oem lock." I've done this exact procedure at least 6 times, never failed me once.
Click to expand...
Click to collapse
newbrightwhites said:
Solved. Followed the advice I received on another forum:
Click to expand...
Click to collapse
Hey that's mine from Reddit lol You're welcome
chrisrodsa210 said:
Hey that's mine from Reddit lol You're welcome
Click to expand...
Click to collapse
Looks like you check Reddit more often than here haha! Thanks again for the help, I was getting a little frustrated.
Related
Hey,
I had problems with the phone and support told me I should flash it. So when I wanted to "flash system.img"
it showed me: Data Transfer Failure (after 48secs)
and when I type in "fastboot devices" now, the name of device now only shows questionmarks: "?????????? fastboot"
And nothing is working now
So when i try to flash system again, windows says "fastboot.exe stopped working"
I am devastated. How can this happen? and what can I do? Please help me
OlivBlum said:
Hey,
I had problems with the phone and support told me I should flash it. So when I wanted to "flash system.img"
it showed me: Data Transfer Failure (after 48secs)
and when I type in "fastboot devices" now, the name of device now only shows questionmarks: "?????????? fastboot"
And nothing is working now
So when i try to flash system again, windows says "fastboot.exe stopped working"
I am devastated. How can this happen? and what can I do? Please help me
Click to expand...
Click to collapse
So you were on cos12.1 and you tried to flash stock images using fastboot? Explain a bit what happened so that i can guide you more accurately..
Anyhow you can always go here http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
And use qfil tool to flash to stock .. read a few posts below to figure out how you should do this and u will end up with zui 1.5 then you can convert to cm or any other rom
Hey thanks for the answer
So I was on COS 12.1 all normal, no root, no unlocked bootloader.
And I wanted to flash COS 12.1 again. So I downloaded the official fastboot image from cyngn . com/support and unzipped it. In there was a system.img file that I tried to flash via "fastboot flash system system.img" Thats when the error occured.
Before that I unlocked the bootloader, started the device, then I flashed the recovery and afterwards the system.
I will now look into the link and see if it helps and report back. Thanks already
OlivBlum said:
Hey thanks for the answer
So I was on COS 12.1 all normal, no root, no unlocked bootloader.
And I wanted to flash COS 12.1 again. So I downloaded the official fastboot image from cyngn . com/support and unzipped it. In there was a system.img file that I tried to flash via "fastboot flash system system.img" Thats when the error occured.
Before that I unlocked the bootloader, started the device, then I flashed the recovery and afterwards the system.
I will now look into the link and see if it helps and report back. Thanks already
Click to expand...
Click to collapse
Before you go to what i suggested
Can you boot into fastboot or recovery ?
If you have whatsapp add me then we can talk it through would be easier than me checking the forum everynow and then ..u'll find my number in private
I was previously on CM13 rooted and unlocked. Decided to upgrade to B15 today. Everything went great and installed Beast mode rom with Magisk (hopefully to allow DTVnow app to work). Magisk showed my safetynet was still tripped so I figured I would need to lock the bootloader. Used adb to fastboot oem lock and immediately the phone rebooted. It will now flash the ZTE logo and then the red led flashes twice and it turns off.
I can get into EDL mode. I can successfully send a recovery using tenfar's tool, but I have not been able to get into any of the recoveries I have tried so far. I tried Mi Flash, but I get an error from that as well. Any ideas what I should do next? I think I need to find a stock A2017u B15 recovery, but I have not been able to find that yet.
Code:
[0.00 COM4]:[COM4]:start flash.
[2.05 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[4.61 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.17 COM4]:try to reset status.
[7.17 COM4]:Switch mode back
[7.17 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.19 COM4]:eek:bject reference not set to an instance of an object.
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
wolly6973 said:
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
Click to expand...
Click to collapse
Gotta keep that bootloader unlocked on any kind of custom software, man. Lol. Did you enable Magisk Hide in the Magisk Manager before you checked SafetyNet? That's the only reason I can think of that it wouldn't have passed, but hey, at least you were able to get everything working again.
wolly6973 said:
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
Click to expand...
Click to collapse
What is the file you were able to flash with the tenfar tool? I am stuck!
I'm completely bricked. I've even contacted ZTE support via chat.
2017U on stock B15 w/ TWRP 3.1 & SuperSU 2.69; I then flashed the stock recovery and attempted to updated to the latest 7.1.1 (I forgot to unroot). It said it was successful, however when it rebooted, the phone set up like a brand new phone (still on B15 though :/). Shortly after finishing the initial set up, I received the same OTA notification for 7.1.1. It tried to install, and never booted back up. Refuses to go to recovery or fastboot, and PC does not recognize ADB or EDL - is says it's in DFU (which ZTE support said was "Device Firmware Upgrade" mode). It just sits on a black screen with a constant red LED.
Any help at all is appreciated. I'm pretty much left with a $400 paper weight.
t2jbird said:
I'm completely bricked. I've even contacted ZTE support via chat.
2017U on stock B15 w/ TWRP 3.1 & SuperSU 2.69; I then flashed the stock recovery and attempted to updated to the latest 7.1.1 (I forgot to unroot). It said it was successful, however when it rebooted, the phone set up like a brand new phone (still on B15 though :/). Shortly after finishing the initial set up, I received the same OTA notification for 7.1.1. It tried to install, and never booted back up. Refuses to go to recovery or fastboot, and PC does not recognize ADB or EDL - is says it's in DFU (which ZTE support said was "Device Firmware Upgrade" mode). It just sits on a black screen with a constant red LED.
Any help at all is appreciated. I'm pretty much left with a $400 paper weight.
Click to expand...
Click to collapse
Have you try this:
Option 1: Zadig driver not going to work if you want to use MiFlash. Try to use in this post https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Option 2: if 1 not work, i found this http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
You can do similar using full firmware B29/B15
Tell me if it works
tamahouse02 said:
Have you try this:
Option 1: Zadig driver not going to work if you want to use MiFlash. Try to use in this post https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Option 2: if 1 not work, i found this http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
You can do similar using full firmware B29/B15
Tell me if it works
Click to expand...
Click to collapse
Option 1 does not work and in the instructions for option 2, the links to the necessary files just take me to this wheretowatch website.. so i don't know if that would work or not.
jwilensky said:
What is the file you were able to flash with the tenfar tool? I am stuck!
Click to expand...
Click to collapse
Tenfar allows you to flash a recovery. I used the stock recovery.img file from miflash. You will want to try using a recovery from whatever version you have installed.
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Americ said:
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Click to expand...
Click to collapse
Ouch, DFU brick. I don't know if you can really do anything from fastboot, maybe unlock the bootloader again? fastboot oem unlock?
I'm wondering how you managed to lock the bootloader without having been warned tgat your phone would become a brick if ANYTHING was out of place (for example a custom recovery, or root) Every guide to relock has a big flashy warning. Did you use the toolkit to relock? If that's the case I'd say @bkores needs to add a warning to the option, maybe something like the "Type yes to continue" kind.
Okay, on to the other stuff. There are two ways to fix a DFU brick: send to ZTE, say it broke itself (Or be honest and pay $80, your choice) or take apart your device (I did this on my A2017G, with a lot of care and patience it works). There might be a solution that uses fastboot, but I'm unsure about flashing a system with fastboot, maybe it is possible though. You want EDL mode to use MiFlash and reinstall a working system on the phone. You are on DFU mode instead of EDL. google "4th category brick repair guide" for the actual guide that you need to use (it's here in XDA but it's faster to find via google). Just a small comment:
To download the stuff easily without having to translate the whole 4PDA page (the guys who made the method are Russians from 4pda), find the "MiFlash and Drivers" link. Open it, you'll find a bunch of spoilers. If you open them all you'll see that the actual files that you need to use have non-cyrillic titles, so download the A2017U_FULL_EDL (like 3 GB), and the MiFlash and drivers. Once you have everything you can simply follow the XDA guide and get it up and running again. Remember to keep the battery plugged to the motherboard though, it won't work otherwise
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers