Database Users

No device found ONLY during fastboot - help needed please

I've been reading up about what to do after I tried to "factory reset" my phone and then was stuck at the htc start up soon, which kept looping.
I've been trying to load recovery.img during fastboot (back+power) and then to apply update.zip during recovery (home+power).
However, the problem is that during fastboot, the device isn't recognized (when I go to adb devices on command prompt, no device is listed). I know that my drivers are good bc the device is found when I start up in the recovery mode. I tried to skip the part where I load recovery.img (since when I try to do that, it tells me that it can't be loaded), and to go straight to apply update.zip, but then the phone tells me that update.zip is either bad or can't be mounted.
I have a Rogers Magic (32A). I am a complete newbie, so any help would be greatly appreciated. I should also say that before I tried to do the factor reset, the phone was on the hero rom loaded by a previous user.

try this:
boot in recovery:
fastboot boot recovery.img
then, push update.zip on your sd card ( need a good rom in the tools folder on your computer)
adb shell mount /sdcard
adb push update.zip /sdcard
and apply update.zip with the recovery menu.

thanks for your reply, but it didn't work:
first, it said "cannot load recovery.img"
and then when I tried to mount, it said "mount: mounting dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy"

replace recovery to correct path to your recovery image. (your phone mut be in fastboot mode power with back button pressed)
ex:
fastboot boot c:\sdk\tools\recovery-RAv1.2.1G.img
then your phone must boot on recovery and you could push update.zip

thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.

pato17 said:
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
Click to expand...
Click to collapse
i am having the same issues.
any help?

beastmods said:
i am having the same issues.
any help?
Click to expand...
Click to collapse
What exactly have you tried to do?
Sent from my HTC Magic using XDA App

Hi. My magic is having the same issues. Although I believe it is my own doing. I was going to create a gold card and I flashed the sappimg.zip, I can boot the phone into fastboot but it us not seen, when I run the fast boot command it just says waiting on device..
I can boot the phone up normally but it does not want to connect to the market our link my gmail account to it..
All to jailbreak... Any ideas?
Edit....
I must have had a poor internet connection last night. I have got the market working.
Sent from my GT-I9000 using Tapatalk

I am having the same problem.
I have a 32b on vodafone uk.
all the device adb drivers have installed fine. I have tried this on both my laptop and desktop (win 7) and when the phone is turned on - it shows fine under adb devices.
When i boot to fastboot, the phone doesnt show, and therefore i cannot load a custom rom.
Trying to root the phone I have so far used the goldcard method to downgrade to get back to 1.5, if i try to flash the recovery img from the phone (using flash rec) then when i boot to recovery (home+power) it hangs on the vodafone screen - this is why i wont to flash from fastboot.
any ideas?
Thanks

phone rooted?
FlashRec is out of date, I'm pretty sure. Is your phone rooted already, or are you at stock?

Recovery problems with 1.33.0004 (Blank screen - black screen)

Hello and sorry for my bad english.
I was using an HTC magic 32B before getting my nexus one.
Recently I decided to give the magic to my girlfriend to remplace her old nokia.
My magic was on custom rom (Super D 1.8) but, when I want to do a hard reset, the phone just reboot.
So I tried to go to the recovery (amon ra custom recovery) to wipe or change the rom to a most recent.
And, instead of having the recovery i have a black screen, juste have to reboot the by pulling out the battery.
Also, when the phone boot i've first the "SFR" logo and then, instead of the bootimage i've only an black screen, juste the time of the bootimage, after that, i juste have to presse the menu button to wake up the device.
I don't understand what it happens bescause before getting my N1 it was working fine...
Juste see on a video i've done, a part of second before pin code asking, there is the "android" displaying...
I can't post the video cause i'm new membre
I hope someone here avec an answer !
Thanks to all the XDA comunity

gniouki said:
Hello and sorry for my bad english.
I was using an HTC magic 32B before getting my nexus one.
Recently I decided to give the magic to my girlfriend to remplace her old nokia.
My magic was on custom rom (Super D 1.8) but, when I want to do a hard reset, the phone just reboot.
So I tried to go to the recovery (amon ra custom recovery) to wipe or change the rom to a most recent.
And, instead of having the recovery i have a black screen, juste have to reboot the by pulling out the battery.
Also, when the phone boot i've first the "SFR" logo and then, instead of the bootimage i've only an black screen, juste the time of the bootimage, after that, i juste have to presse the menu button to wake up the device.
I don't understand what it happens bescause before getting my N1 it was working fine...
I hope someone here avec an answer !
Thanks to all the XDA comunity
Click to expand...
Click to collapse
Kind of a strange problem.
Does the phone boot up still?
Did you try reflashing your recovery image? (flash_image recovery recovery.img)
if not
can you get into fastboot?
if so then fastboot flash recovery recovery.img from the command prompt of your pc.
Good luck.

Hello,
thanks for you answer.
I've tried to flash the recovery but didn't works.
I don't try the fastboot mod but I don't have the phone with me for the moment.
I'll try ASAP.
video : youtube.com/watch?v=RJmXjV8E4jw
edit : ok I asked to my girlfriend to try, fastboot works.

gniouki said:
Hello,
thanks for you answer.
I've tried to flash the recovery but didn't works.
I don't try the fastboot mod but I don't have the phone with me for the moment.
I'll try ASAP.
video : youtube.com/watch?v=RJmXjV8E4jw
edit : ok I asked to my girlfriend to try, fastboot works.
Click to expand...
Click to collapse
Then we have a shot.
Procedure
1.Turn your phone off. Turn it on by holding Back and Power, or Vol. down and Power. Either way, boot into the bootloader.
You should see the three Androids on skateboards, and the menu title should say "Fastboot".
2.Connect your device to the computer. The display on your phone should now say "Fastboot USB".
3.Open up the shell/terminal on your computer, and type
fastboot devices [enter]Your device should be listed with it's serial number, and should say "fastboot".
4.Change directory to where you have saved your recovery image. I.e. type "cd /path/to/recovery.img in windows prompt, press enter.
5.You may issue a "dir" command (Windows) or "ls" (Unix/Linux) to make sure you are at the right directory, or just skip this step.
6.Type
fastboot flash recovery recovery.img [enter]
Check your phone's display, as recovery is being sent and flashed to your device.
Check your command prompt/shell to make sure the process is over.
Click to expand...
Click to collapse

Thanks a lot.
I try it as soon as possible and will post here to say if has work.
Thanks again, I love XDA community

Hello again,
when i try to flash recovery via fastboot i've got this message :
remote: signature verify fail.
I've the 1.7.0G amon ra recovery and a 32B magic with Hboot 1.33.0004
When i try to run the recovery with : fastboot boot recovery.img i've got a reboot, SFR logo and black screen.
Could you help me with these information ?
Thanks

gniouki said:
Hello again,
when i try to flash recovery via fastboot i've got this message :
remote: signature verify fail.
I've the 1.7.0G amon ra recovery and a 32B magic with Hboot 1.33.0004
When i try to run the recovery with : fastboot boot recovery.img i've got a reboot, SFR logo and black screen.
Could you help me with these information ?
Thanks
Click to expand...
Click to collapse
Okay... I think that you need the Engineering SPL because right now you should see SHIP S-ON G on your screen. That means it's the standard SPL. To modify anything you need the Engineering SPL. In this case I think you need 2004 from this thread: http://forum.xda-developers.com/showthread.php?t=529019 but to do that you may need to create a goldcard.
So just to verify with you, you cannot boot up your phone at all and you cannot access recovery? What do you get when you connect it to your computer, boot it up and type adb devices in the command prompt?
Also try starting the phone while holding MENU. This sometimes helps.

Thanks for your answer, i don't have the phone in my hands now, i'll ask to my girlfriend to boot it with home.
Adb devices didn't recognize my device.
edit : booting with home holding down bring me à black screen, certainly the "invisible" recovery.

gniouki said:
Thanks for your answer, i don't have the phone in my hands now, i'll ask to my girlfriend to boot it with home.
Adb devices didn't recognize my device.
edit : booting with home holding down bring me à black screen, certainly the "invisible" recovery.
Click to expand...
Click to collapse
There is no such thing as an invisible recovery.
It is possible that your recovery was deleted or corrupted.
If you did have a recovery you would still be able to access the device through adb. All you would need to do is place Amon_Ra recovery.img (G) onto your sdcard with another phone or adapter, place it into your damaged device and boot it into your "invisible recovery" and use adb shell devices in command prompt. If you do have a recovery image installed (but no text) you should see your device. If not then you will probably have to start over with the goldcard. If it does detect your device then all you need to do is mount /sdcardflash_image recovery /sdcard/recovery.img (or whatever it's called)

Okay thanks, I'll try this ASAP.
I could put the recovery on the SD directly from the phone, right ?
Cause the phone could boot, just that I can't see recovery, do an hard reset and see the bootimage.

gniouki said:
Okay thanks, I'll try this ASAP.
I could put the recovery on the SD directly from the phone, right ?
Cause the phone could boot, just that I can't see recovery, do an hard reset and see the bootimage.
Click to expand...
Click to collapse
Wait! What? If the phone boots then simply put the recovery file on your sdcard and run flash_image recovery /sdcard/recovery.img from adb shell
-or-
from terminal on your phone
flash_image recovery /sdcard/recovery.img

I'll try it,
how can i acces to the terminal of the phone ?
Thanks

gniouki said:
I'll try it,
how can i acces to the terminal of the phone ?
Thanks
Click to expand...
Click to collapse
Through teminal emulator?

Ok, done it from the terminal emulator on the phone, seems working but still booting on a black screen

gniouki said:
Ok, done it from the terminal emulator on the phone, seems working but still booting on a black screen
Click to expand...
Click to collapse
So you boot up your phone while holding the Home button and it gives you a plane black screen with absolutely NOTHING on it at all?
Hmmm... I would have to say that the next step is either:
Try a different recovery such as Clockwork
Start completely over with the Goldcard
Other than that... I really don't know.

This is exactly that, pressing home while phone is starting gives me a black screen with nothing on it.
I'll try another recovery and will see later for the goldcard.
thanks

gniouki said:
This is exactly that, pressing home while phone is starting gives me a black screen with nothing on it.
I'll try another recovery and will see later for the goldcard.
thanks
Click to expand...
Click to collapse
Sounds good. Good luck.

Flashed the clockwork recovery and when trying to launch recovery it stuck on the SFR logo but normal boot still working
Edit : Using ROM Manager app it says that the clockwork recovery is installed...

Bump. I have no clue then man. I can't understand why all of a sudden you have nothing more than a blank (black) screen for recovery. The only thing left for you to try is the goldcard method. It will put your phone right back to the way that it was out of the box. Unrooted and everything. It'll be starting over from square one.
In fact, I rooted a friend Fender last night and I forgot how easy it was once you already had the goldcard. Simply:
place the card into the card slot,
reboot into bootloader,
press the back button and let it do it's thing.
Afterwards reboot the phone to bootloader again
go to fastboot mode and
fastboot flash radio radio.img,
fastboot flash hboot hboot.nb0,
fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img.
Then power off the device.
Hold Home and power the device back on and Voila! You should have a recovery screen.
If that doesn't work... well... I would have to see it to believe it.
For details and links to create a goldcard just Google it. Easy to find.

Something I don't understand is that ROM Manager recognize my recovery ... so I've a recovery and it's realy invisible cause i've got this black screen ...

[Q] No recovery

Hello every body and sorry for my poor English !
I have root my phone some month ago by changing my recovery with flashrec 1.0
all work done, I can be root on my phone by press "su".
But there is an update now and I want my old recovery partition.
So I use flashrec and type "restore backup" but it tell me failed !
I restart the phone and try it again : and in 0,01 second flashrec tell me success and when I restart my phone in recovery mode I have a block screen with triangle next to phone icon and I can't do nothing else than remove the battery !
So I try to do :
Code:
adb shell reboot bootloader
fastboot boot recovery-backup-htc-hero.img
But it answered : "FAILED (remote: not allow)"
I try :
Code:
adb shell flash_image recovery /sdcard/recovery-backup-htc-hero.img
But it answered : "mtd: read error at 0x00000000 (Out of memory)"
or nothing happens.
I have try :
Code:
fastboot erase recovery
But it answered : "FAILED (remote: not allow)"
Any idea for recover my recovery ?
Thanks or your answers.

i guess you are using unlocked SPL It might be causing problems

Greetings,
See the following :
http://forum.xda-developers.com/showpost.php?p=9143548&postcount=7
This is another way to root the phone and get amon ra on.

maheshpatel said:
i guess you are using unlocked SPL It might be causing problems
Click to expand...
Click to collapse
I'm not sure I have understand :
Code:
unlocked SPL
What I must do ?

Steven_belfast said:
Greetings,
See the following :
http://forum.xda-developers.com/showpost.php?p=9143548&postcount=7
This is another way to root the phone and get amon ra on.
Click to expand...
Click to collapse
The link is for root a phone ?!? no?
I just want to recover my recovery !
For flash my old recovery I do all it say in your URL apart the format of SD card, do you think it is important?
Moreover memory on my phone is 56m do you think it can be the problem ?
Can I saw my recovery partition on the file system?
Thanks at both of you for your rapid answered, I hope you will answered me again !

Is your phone is rooted ?
Code:
"mtd: read error at 0x00000000 (Out of memory)"
It needs rooted phone to run it ..
i 'd suggest root your phone -)
&
try this :-
Power on your hero while holding down the volume down button.
then:
Code:
fastboot erase recovery
fastboot flash recovery - & filename of recovery in the pc
try flashing old Recovery of Amon_ra first . if it works than try latest one ..
If nothing comes on your way. than i would suggest use stock RUU & than try flashing Amon_Ra & See you can flash it from boot loader or not ?

maheshpatel said:
Is your phone is rooted ?
Code:
"mtd: read error at 0x00000000 (Out of memory)"
It needs rooted phone to run it ..
i 'd suggest root your phone -)
&
try this :-
Power on your hero while holding down the volume down button.
then:
Code:
fastboot erase recovery
fastboot flash recovery - & filename of recovery in the pc
try flashing old Recovery of Amon_ra first . if it works than try latest one ..
If nothing comes on your way. than i would suggest use stock RUU & than try flashing Amon_Ra & See you can flash it from boot loader or not ?
Click to expand...
Click to collapse
Yes my phone is rooted : When the phone is on, I can become root by typing "su" and then an application ask me if I allow to become root.
So I have "Power on my hero while holding down the volume down button" and I see a green check list during a second and after I see in blue HBOOT.
So I have try to do on my computer "fastboot erase recovery" but my prompt say me
Code:
C:\Windows\System32>fastboot erase recovery
erasing 'recovery'...
and it never do anythinks !
So if I press back on the Hero I can see :
Code:
C:\Windows\System32>fastboot erase recovery
erasing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 78.280s
An idea?

I'm totally out of ideas...
you are not using the standard data cable that comes with the htc hero? status read failed (Too many links)) error comes when you are not using standard data cable that comes with the htc hero..
Make sure your adb tools working correctly..

maheshpatel said:
I'm totally out of ideas...
you are not using the standard data cable that comes with the htc hero? status read failed (Too many links)) error comes when you are not using standard data cable that comes with the htc hero..
Make sure your adb tools working correctly..
Click to expand...
Click to collapse
This is the standard cable but a little broken.
I will search a bit more.
If you or someone find an other idea !
Thanks !

your cable is causing problem . find a good cable and do it

I had problems with the original cable. So what's happening when you shutdown and press menu/power. Blocked triangle?
And it was all yellow...

spikey68 said:
I had problems with the original cable. So what's happening when you shutdown and press menu/power. Blocked triangle?
And it was all yellow...
Click to expand...
Click to collapse
Yes this is my problem a yellow blocked triangle when boot on recovery mode...
Do You have a solution?

stuck at htc screen - what to do?

ok, it is just a idea
it looks like many people do have the problem that for some reason their phone stops booting at htc screen...
i´m thinking about writing something like a guide (wip) what are the things you could try to get the phone working again (only basic stuff and links, i´m not a dev) - so if anybody got an idea what i should add pls post it
how to check your emmc chip:
http://forum.xda-developers.com/showpost.php?p=13895268&;postcount=48
if one step works stop and don´t go further...
1. post: stock phone (no root)
2. post: rooted phone
3. post: rooted phone & eng hboot
STOCK PHONE - NO ROOT (bootloader shows: hboot: ??? & S-ON):
1. pull the battery and try it again
2. turn your phone in usb fastboot mode (power & tp) connect it to pc; on pc go to platform tools and type fastboot devices (your device should show up) then type fastboot oem boot
3. wipe cache or do a factory reset (= push power & volume down to enter bootloader; select recovery = a red triangle will appear then push power & volume up to enter recovery menu)
3.a. wipe cache = none of your apps are lost
3.b. factory reset = you will loose your apps & sms & so on... but you won´t loose your sdcard content
reboot
4. use a ruu (it´s .exe to start from windows pc) and try to update (install htc sync):
http://shipped-roms.com/index.php?category=android&model=Vision ...for example
5. if point 3 didn´t work, extract the PC10IMG.zip put it on your sdcard (not in a folder) enter bootloader and start the update (more details will follow)
6. hope for warranty

PHONE ROOTED (bootloader shows: hboot ??? & S-OFF):
1. if you enabled usb debugging before, start adb and type adb devices, if your device shows up type adb reboot bootloader (if it worked next step = 4)
2. pull the battery and try it again
3. turn your phone in usb fastboot mode (power & tp) connect it to pc; on pc go to platform tools and type fastboot devices (your device should show up) then type fastboot oem boot
4. wipe cache or do a factory reset (power & volume down to enter bootloader then select recovery) - reboot
5. wipe again (this time use superwipe: http://forum.xda-developers.com/showthread.php?t=1044992) & wipe through recovery then flash a different rom
6. any suggestions?

PHONE ROOTED & ENG HBOOT (bootloader shows: hboot 0.76.2000 |g2| or 0.84.2000 |desire z| & S-OFF):
1. if you enabled usb debugging before, start adb and type adb devices, if your device shows up type adb reboot bootloader (if it worked next step = 4)
2. pull the battery and try it again
3. turn your phone in usb fastboot mode (power & tp) connect it to pc; on pc go to platform tools and type fastboot devices (your device should show up) then type fastboot oem boot
4. wipe cache or do a factory reset (power & volume down to enter bootloader then select recovery) - reboot
4. wipe again (this time use superwipe: http://forum.xda-developers.com/show....php?t=1044992) & wipe through recovery then flash a different rom
5. if you can´t enter recovery for some reason turn your phone in usb fastboot mode and connect to pc:
5.a. wipe cache & data through fastboot (go to platform tools and type fastboot erase cache and fastboot erase userdata) - reboot
5.b. flash a recovery.img through fastboot (download the image and put it in your platform tools folder; go to platform tools and type fastboot flash recovery recovery.img) then enter recovery and flash whatever you want to...
6. any suggestion?

My DZ is with new mainboard now - there was no other way... I tried all steps for "STOCK PHONE - NO ROOT" without success.

chyles said:
My DZ is with new mainboard now - there was no other way... I tried all steps for "STOCK PHONE - NO ROOT" without success.
Click to expand...
Click to collapse
sure if it is a hw defect nothing will work... i planned to add a way to confirm if it´s a broken emmc chip, but if there is no interest in a thread like this i will stop...

there is really not too much to worry about, if you private message me, I can give you Josh's information here on XDA - he can unbrick pretty much any G2/Desire-Z for $40 and has done 100's of them - he has like almost 500 Thanks on here -
the only thing he can't fix is a fried emmc chip, but thankfully those are relatively rare!
(and if the emmc chip is fried, then HTC will fix it, because that truly is their fault, so no worries!)
(HTC knows of the emmc chip failures, and that is why in this case they are not going to give you a hassle about the warranty, sort of like when an auto company has done a silent recall, so to speak)

ADB
Well when i first rooted and installed cyanogen..it got stuck oon the htc screen..pulled the battery(not safe)... so the next time i flashed a rom and this happened i just connected the phone to pc and used adb to reboot into the bootloader....
Confused with all the links to various places for rooting your Desire Z/ G2 ???? Maybe you could find it a little easier on my blog www.desirez.strawmetal.com ... Hope it helps you..

strawmetal said:
Well when i first rooted and installed cyanogen..it got stuck oon the htc screen..pulled the battery(not safe)... so the next time i flashed a rom and this happened i just connected the phone to pc and used adb to reboot into the bootloader....
Click to expand...
Click to collapse
thx, i´ve changed the op

any feedback on this thread? i don´t know the hboot numbers (normal hboot, not eng hboot) for g2 or dz - does anybody know?

And now what i do with my Axon 7?

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

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

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

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

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

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

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

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

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

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

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

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