Database Users

[HOW TO] Rooting on the Mac with Heimdall

After getting my GS3/i9300 I realized that I didn't have a Windows computer anymore to root it. So I was stuck finding an alternative to Odin. I had trouble finding one aggregated source of Mac info that was relatively recent (last post I see is from Feb 2012) and all in one place.
I'm on MacOS X 10.7.5 (Lion) which isn't the most current version. I'm also a noob so maybe I got lucky as I've seen many comments within the various threads where my steps didn't work for other people.
When you download Chainfire's Auto-Root zip file, you'll need to do things a bit differently than with Odin. After unzipping, you'll need to untar the .tar file as well. You'll want the recovery.img and cache.img files in a folder on your PC. You'll need to know the path to that directory.
Instead of using the Heimdall GUI (which I found confusing), I ended up finding Chainfire's comments about using the Linux/Terminal commands in one of his old posts. He said it was "hearsay" but I can confirm that it worked on my GS3. Credit goes to jzuijlek for posting it (his post).
You'll want to install Heimdall from here
Currently they're saying to install version 1.3.1 instead of 1.3.2.
After Heimdall installs, I suggest rebooting your Mac.
Now to the good stuff...
Boot your phone into download mode:
1) Unplug your phone from the computer.
2) Turn your phone off
3) Hold both the volume down + home button. Then press and hold power until download mode comes up. Then press the volume up key to continue.
3) Plug in your phone
4) Open up Terminal and then cd to your recovery/cache.img files directory
5) Then type in this command:
sudo heimdall flash --recovery recovery.img --cache cache.img
If all goes well then you'll see stuff being installed and your phone will reboot and you'll be DONE!
However, if you're like me, you got an error. The response from Heimdall said, "Claiming interface failed". It turns out that there may be conflicts with Kies kexts if you have it installed. If you don't have it installed and you're seeing this error, I'm not sure if I can help. I suggest uninstalling Kies as you won't need it after you root. I searched Google with my error and finally found this gem from March 2012!
http://blog.scott.wallace.sh/2012/03/getting-heimdall-to-work-on-your-mac.html
As such, if you've installed Kies on your Mac and you're having this error, I suggest using the following commands. It seems some kernel extensions that Kies installs conflict with Heimdall.
sudo kextunload -b com.devguru.driver.SamsungComposite
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
After this, I tried to flash again and it worked like a charm!
Now you're rooted.
However, Chainfire doesn't support CWM in his CF-Autoroot anymore so you'll need to get CWM or some other recovery image (Philz, TWRP, etc.). You can search these forums but these links should be mostly correct
CWM (find the Samsung Galaxy S3 i9300 in the list: http://www.clockworkmod.com/rommanager
Philz (built on CWM): http://forum.xda-developers.com/showthread.php?t=2002953
TWRP: http://forum.xda-developers.com/showthread.php?t=1943592
You'll flash the same way as above with just the .img file
Boot into download mode using sequence above.
(Example with CWM)
Open up Terminal and cd to the directory with your .img file.
Then type:
sudo heimdall flash --recovery recovery-clockwork-6.0.2.7-i9300.img
For reference...to boot into recovery:
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
I hope this helps! Let me know if you think I got anything wrong!

Is this still theway to root on mac?
I have s3 uk 3 network. 4.1.2 xxella.
I blieve my phone was open to sds attack before the xxella update. can i keep this recovery?

I would strongly advise against using Heimdall. Nothing against the authors, but I tried it and would recommend avoiding it. Simpler approach is to setup Windows (In my case Windows 7) in a VM environment (I bought VMware Fusion) and just use the normal Odin. You'll get far more support from people here, and less headaches.

While i agree that Odin is easier and gives you more help from the community, i used Heimdall anyway due to not having any wish at installing windows on my mac.
This method does work (as of may 2013), however:
-Uncheck the "reboot after flashing" option in Heimdall. When Heimdall has done its job, manually boot into recovery. This way your custom recovery wont be overwritten by stock recovery.
Happy flashing!

Real fix for thinkpad tablet boot loop!

Introduction
OK. the story is I was on Thinkpad Tablet A 400-03-0070-0132-ROW, I decided to taste CM10 by Koshu, Thank you Koshu!), I accessed Root by RootDebugfs script! (Folow this instruction: http://forum.xda-developers.com/showthread.php?t=1706588)
Then I installed CWM and backup my tablet, then after install CM10. (Folow this instruction: http://forum.xda-developers.com/showthread.php?t=1846044 , Thanks Koshu again)
Everything was fine. thanks Koshu again !
Then I decided to back to my stock ROM, My backup was corrupted!!!!!! YES! and Thinkpad tablet went to BOOT LOOP.
Finally I solve it after 3 day's experiments! I repeated my experiment and I was successful as many times as I repeated. Then I decide to share my solution to anyone.
It works for any Thnkpad Tablet (US,ROW,WE,...) but at the end you will have A 400-03-0070-0132-ROW, but you can repeat to ROOT, CWM and CM10 again
Before Start
1) your tablet is Thinkpad Tablet and stocked in the boot loop.
2) your tablet partition 4EBT is not lock by factory (you will learn if it is!)
3) after this instruction your tablet cure completely and you will have A 400-03-0070-0132-ROW version, not Rooted but you can access root later (RootDebugfs) and also you can do anything, also you can brick it again and this will solve it again !!!!
4) at each step, if you don't know the meanings, just search this forum.
Instruction:
1) download nvFlash + driver + CMW files + my script (included at the end).
2) put your tablet in the APX mode:
yes, you are at boot loop, but you can push the power button for 10sec. you will be off for a while, instantly push rotation lock key then add power button, wait for 2 second and release both buttons, you are at APX mode now, at the device manager of your control panel you can see APX installed.
3) install APX drivers:
if device start to loop before installing driver go to 2.
install driver from downloded files, drivers folder. windows say something! ignore it! and install driver
4)now we start to put recovery image to your SOS partition, it can help the device come back from loop!
(learn how to go into APX mode)
run my scrip from downloded files (alikghp.bat)
choose install CWM5.0,
go to APX mode and wait.
you will see big PASS on your device.
5) copy
a. clockworkmod folder and it's content
b. ThinkPadTablet_A310_02_0039_0089_ROW.zip
c. ThinkPadTablet_A310_03_0069_0121_ROW.zip
d. ThinkPadTablet_A400_03_0070_0132_ROW.zip
from downloaded files to a SDcard and insert SDcard to your tablet.
6) turn off your device, go to recovery mode (power (after vibration release power, push Vol.up 2 or 3 times), you will see the CWM recovery.
YES you break the DEVIL's LOOP!
7) use Vol.up, Vil.down and power to choose -backup and restore, then
-restore from external sdcard.
the -yes.
be patient and wait until to end.
8) at CWM's main menu choose -install zip from sdcard. then
-choose zip from external sdcard.
-choose ThinkPadTablet_A310_02_0039_0089_ROW.zip
9) again run alikghp.bat but this time
choose install OriginalRecovey
after see the big PASS...
10) turn off, and turn on to recovery mode again.
choose wipe data/factory reset. wait until finish.
choose reboot system now.
11) your tablet back to life. with A310_02_0039_0089_ROW !!! wait until it it's jobs done!
12) turn off and turn on to recovery mode again. choose apply update from external storage.
choose ThinkPadTablet_A310_03_0069_0121_ROW. after finishing reboot and wait wait until it it's jobs done!
repeate this step and
choose ThinkPadTablet_A400_03_0070_0132_ROW after finishing reboot and wait wait until it it's jobs done!
it's done.
now you can root and install CM10 again, (refer to Introduction above) BUT this time make sure your Nandroid backup is healthy and pull it on your hard disk to safety.
==============================================================================
Download files here:
https://drive.google.com/file/d/0B5cPsgBIMN0JLWdlM00wLUlYZEE/edit?usp=sharing
==============================================================================
ENJOY!!! By:Ali Ghodratipour

when using nvflash and type "sync" i got this
error: rcm version 0X4 Command send failed (usb write failed)
is this mean that my tablet partition 4EBT is lock by factory and i can't use this method

m7mdrda said:
when using nvflash and type "sync" i got this
error: rcm version 0X4 Command send failed (usb write failed)
is this mean that my tablet partition 4EBT is lock by factory and i can't use this method
Click to expand...
Click to collapse
I guess this problem may come from 2 area.
1) are you sure that you have installed nvflash drivers properly?
2) do you install Bootloader on your 4EBT partition, because you have to do it before any command sending?
check the following post (thanks suntechnic!) to learn more about nvflashing.
http://forum.xda-developers.com/showthread.php?t=1745450

Thank you ali
i did every thing you said in your post .... i have a bricked thikpad tablet stay in logo when start and have a bricked recovery mode but when i used your methode my tablet don't wont to enter in recovery mode again when i hold start button and push the vol up twice i see on top booting recovery kernal image and my tablet restart after that
i think my bootloader is unlocked but i dont know how to use nvfash so please help me i don't know what i will do please is there a solution
if you have solution i can give you permission to enter to my pc and do what ever you want to do just please help me

same as gharib madrid; but my thinkpad boots directly into "booting recovery kernal image" screen, then it hangs for few seconds then it powers down or restarts into bootloops,
my bootloader is unlocked.
after trying this method in the original post TENS of times, with bootload inetialize failuer, I got this
Code:
Nvflash started
[resume mode]
sending file: recCWM5.img
/ 4452352/4452352 bytes sent
recCWM5.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
anyone can help me in this?

7) use Vol.up, Vil.down and power to choose -backup and restore, then
-restore from external sdcard.
the -yes.
be patient and wait until to end.
How long this step may take?
after
"Cheking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...?
it looks like the process hanged here, now 25 minutes passed and still waiting some cool to happen
anyone who tried this method, please reply

ana_mawjoud said:
same as gharib madrid; but my thinkpad boots directly into "booting recovery kernal image" screen, then it hangs for few seconds then it powers down or restarts into bootloops,
my bootloader is unlocked.
after trying this method in the original post TENS of times, with bootload inetialize failuer, I got this
Code:
Nvflash started
[resume mode]
sending file: recCWM5.img
/ 4452352/4452352 bytes sent
recCWM5.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
anyone can help me in this?
Click to expand...
Click to collapse
My thinkpad tablet suddenly die..and i am suck in the same place as you... it shows "booting recovery kernal image" screen, then it hangs for few seconds then it powers down or restarts into bootloops,
WIll my thinkpad 32G be an issue?

Hi.
I had the same problem. Follows the isntructions an after that "booting recovery kernal image" plus lenovo loop.
My solution was: I had changed the line 30 in "alikghp.bat" by:
nvflash -r --download 6 clockworkmod\backup\ThinkPadTablet_0089_ROW_Root_CWM\recovery.img
that is: I had used the recovery partition from "clockworkmod\backup\ThinkPadTablet_0089_ROW_Root_CWM".
After that, the steps 6 and 7 of post#1 work!!
reaperhk said:
My thinkpad tablet suddenly die..and i am suck in the same place as you... it shows "booting recovery kernal image" screen, then it hangs for few seconds then it powers down or restarts into bootloops,
WIll my thinkpad 32G be an issue?
Click to expand...
Click to collapse

The files?
Thank You for all this help, Ali. I'm trying to follow these instructions today with a Thinkpad 1838 tablet to that's stuck in the animation loop.............but the link to your files is broken.
Can you (or anyone reading) help me?
Thanks again; this is a great tablet, and I wish to resurrect it for my daughter for her birthday.
***************************************************
aliakg56 said:
Introduction
OK. the story is I was on Thinkpad Tablet A 400-03-0070-0132-ROW, I decided to taste CM10 by Koshu, Thank you Koshu!), I accessed Root by RootDebugfs script! (Folow this instruction: http://forum.xda-developers.com/showthread.php?t=1706588)
Then I installed CWM and backup my tablet, then after install CM10. (Folow this instruction: http://forum.xda-developers.com/showthread.php?t=1846044 , Thanks Koshu again)
Everything was fine. thanks Koshu again !
Then I decided to back to my stock ROM, My backup was corrupted!!!!!! YES! and Thinkpad tablet went to BOOT LOOP.
Finally I solve it after 3 day's experiments! I repeated my experiment and I was successful as many times as I repeated. Then I decide to share my solution to anyone.
It works for any Thnkpad Tablet (US,ROW,WE,...) but at the end you will have A 400-03-0070-0132-ROW, but you can repeat to ROOT, CWM and CM10 again
Before Start
1) your tablet is Thinkpad Tablet and stocked in the boot loop.
2) your tablet partition 4EBT is not lock by factory (you will learn if it is!)
3) after this instruction your tablet cure completely and you will have A 400-03-0070-0132-ROW version, not Rooted but you can access root later (RootDebugfs) and also you can do anything, also you can brick it again and this will solve it again !!!!
4) at each step, if you don't know the meanings, just search this forum.
Instruction:
1) download nvFlash + driver + CMW files + my script (included at the end).
2) put your tablet in the APX mode:
yes, you are at boot loop, but you can push the power button for 10sec. you will be off for a while, instantly push rotation lock key then add power button, wait for 2 second and release both buttons, you are at APX mode now, at the device manager of your control panel you can see APX installed.
3) install APX drivers:
if device start to loop before installing driver go to 2.
install driver from downloded files, drivers folder. windows say something! ignore it! and install driver
4)now we start to put recovery image to your SOS partition, it can help the device come back from loop!
(learn how to go into APX mode)
run my scrip from downloded files (alikghp.bat)
choose install CWM5.0,
go to APX mode and wait.
you will see big PASS on your device.
5) copy
a. clockworkmod folder and it's content
b. ThinkPadTablet_A310_02_0039_0089_ROW.zip
c. ThinkPadTablet_A310_03_0069_0121_ROW.zip
d. ThinkPadTablet_A400_03_0070_0132_ROW.zip
from downloaded files to a SDcard and insert SDcard to your tablet.
6) turn off your device, go to recovery mode (power (after vibration release power, push Vol.up 2 or 3 times), you will see the CWM recovery.
YES you break the DEVIL's LOOP!
7) use Vol.up, Vil.down and power to choose -backup and restore, then
-restore from external sdcard.
the -yes.
be patient and wait until to end.
8) at CWM's main menu choose -install zip from sdcard. then
-choose zip from external sdcard.
-choose ThinkPadTablet_A310_02_0039_0089_ROW.zip
9) again run alikghp.bat but this time
choose install OriginalRecovey
after see the big PASS...
10) turn off, and turn on to recovery mode again.
choose wipe data/factory reset. wait until finish.
choose reboot system now.
11) your tablet back to life. with A310_02_0039_0089_ROW !!! wait until it it's jobs done!
12) turn off and turn on to recovery mode again. choose apply update from external storage.
choose ThinkPadTablet_A310_03_0069_0121_ROW. after finishing reboot and wait wait until it it's jobs done!
repeate this step and
choose ThinkPadTablet_A400_03_0070_0132_ROW after finishing reboot and wait wait until it it's jobs done!
it's done.
now you can root and install CM10 again, (refer to Introduction above) BUT this time make sure your Nandroid backup is healthy and pull it on your hard disk to safety.
==============================================================================
Download files here:
https://drive.google.com/file/d/0B5cPsgBIMN0JLWdlM00wLUlYZEE/edit?usp=sharing
==============================================================================
ENJOY!!! By:Ali Ghodratipour
Click to expand...
Click to collapse

Ive upload files again
Dear friend, I tried to upload my script, however the post is so old and I don't have all the files. But you can find all of them in this forum and in the internet. just google the file's names. I wish you luck!
Here you can download stock ROMs:
http://download.lenovo.com/slates/think/tablet1
for NVFlash this link can help you:
http://forum.xda-developers.com/showthread.php?t=1745450
I am not Chinese but this website + google chrome translator is something
http://cnzhx.net/blog/apx-root-thinkpad-tablet/

Recovery lost

I need help guys because i lost my twrp recovery while flashing the xenon rom. The problem is now my phone is also not detected in adb devices in my laptop. I am running windows 10 i had installed twrp from this laptop. When ever i connect and give command ADB DEVICES the it doesn't show any devices found. I had installed all the drivers. My phone is running in the xenonhd rom. Pls help me how i can install twrp and how to correct adb.
Sent from my Lenovo A6000 using XDA-Developers mobile app

Lenevo A6000 Unbrick/Fix For Any Problem
It's common since, when modified, the A6000 doesn't have a way to directly boot into recovery without a System or ADB command (Power Hold > Reboot > Recovery and "adb reboot recovery" respectively). However you can always boot into Download mode which acts as an emergency subsystem at any time. Have a quick guide on how to do that and you'll be flashing away custom ROMs again in no time.
(Optional but recommended steps will be market with an asterisk (*))
Disclaimer: You are doing everything out of your own free will and volition. I am in no way responsible to any potential damage you might cause to your device. This can occur in cases of not following the guide properly.
Below is the fix for problems when the phone has no OS to reboot from. In case of Xenon which is rooted, follow this:
Easy Guide
(This is for when a phone already has an OS to boot from)
1. Open Terminal Emulator
2. Write
Code:
su
reboot recovery
(On any Superuser permissions pop-ups press Grant.)
3. Follow Steps 4 and 5 from the guide bellow.
Downloads
If you are on Kitkat (4.4.X), Download This (Mirror)
If you are on Lolipop (5.X.X), Download This (Mirror)
If you are not sure, download both and try both, no damage should be done.
[Source]
Instructions
1. Download all the prerequisite files.
2. Power Off Your Phone by removing the battery.* (See Note 1)
3. Hold the Volume Down and Power keys until the phone vibrates once and the Lenovo screen appears. At the bottom it should say "Powered by Android" and under it some small Chinese letters and "Power key long press can reboot phone". (See Note 2)
4. Extract the downloaded ZIP files anywhere you want. You should end up with a "TWRP" folder.
5. Open that TWRP folder and run "Boot-TWRP_A6000.bat"
6. If everything went well, you should be in TWRP recovery. Flash your desired ROM following the instructions from their thread, and everything should now be fine. (See Note 3)
Notes
1. I have noticed that sometimes my phone will not recognize that it's in Bootloader mode and will try to boot normally after a few seconds along with the fastboot not recognizing it. Theory: it doesn't shut down completely when rebooted via Holding the Power button, and tries to boot like nothing is wrong. I don't have a concrete fix, the best i can offer is to try different button combinations. (Vol. Down+Power / Vol. Up+Power / Vol. Up+Vol. Down+Power)
2. If you get the problem described in Note 1 do steps 4 and 5 before step 3. The .bat script will wait for the phone, as soon as it detects the Bootloader it will do it's job.
3. If something went wrong, leave a reply, I'll see if i can guide you through it. Remember to follow instructions carefully!

i had a simple sol....
Just boot into bootloader by Press n hold vol - an power ... den do wht u r doing .. Connect cable .. to pc.. n do the command in cmd.. That it

I have simple method
1. First root with kingoroot it is on click root method.
2.then install rashr
3.then flast twrp recovery img
4.then reboot to recovery.
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
It is link for kingoroot
https://root-apk.kingoapp.com/kingoroot-download.htm
Download rashr via play store

I was totally in awe when my phone won't reboot to to recovery and download mode even tho i can reboot system normally and after I flash some recoveries all of them bootlooped my phone but that fix by AXAzor completely worked. Very huge thanks to @AXAz0r

blaspheme000 said:
I was totally in awe when my phone won't reboot to to recovery and download mode even tho i can reboot system normally and after I flash some recoveries all of them bootlooped my phone but that fix by AXAzor completely worked. Very huge thanks to @AXAz0r
Click to expand...
Click to collapse
Glad to hear that, cheers

flash twrp using flashify,rashr

SOLVED - Fastboot with no adb - any help?

Hi,
rooted 2017 16GB ShieldTV.
Unlocked bootloader.
TWRP was not installed just used to boot once and installed SuperSU (I feel like an idiot learning this only after)
Played with it - removed some critical system apps, and also managed to disable USB debugging (this only as I thought that TWRP was installed - and felt safe to do ANYTHING)
Now - boot to fastboot happens, but there is no adb.
Any saving method?
Original recovery gives options to ADB sideload and USB update.
Tried to use this by putting official Nvidia stock image on USB and but it reports signature failed, and refuses to flash.
Any help?
Thanks guys

SOLVED
Writting this as soon as I could cool down.
Situation:
- Shield ATV 16GB 2017. SW Nougat 5.2
- Unlocked bootloader (every boot gives that safety warning)
- System bootloop on Android circles animation (managed to root it previously and removed some critical apps by mistake)
- NO USB debugging
- NO custom recovery (as process for rooting only used TWRP to flash SuperSU, nothing else)
- Entering fastboot possible only by hardware method (controller connected by USB, hold A+B buttons while Shield is plugged off 10sec, then plug Shield in. Two short vibrations of controller and fastboot screen appears.)
However - NO adb in fastboot. (pinging with adb devices gives NO response). Only option that works is entering official recovery which gives options for adb sideload or update from USB. However - no zip file is accepted due signature check (and I tried tons of them)
Tools
1. Windroid
https://forum.xda-developers.com/showthread.php?t=2499926
2. Proper TWRP build
http://nvidiashieldzone.com/download/twrp-3-1-1-1-shield-tv/
3. Custom flashable rom (I used Lineage OS for Shield - lite and without Gapps - to speed up booting into environment that works). Put it onto USB drive
4. Oficial Nvidia recovery image (https://developer.nvidia.com/shield-open-source)
5. Minimal ADB and Fastboot (http://nvidiashieldzone.com/download/minimal-adb-and-fastboot/)
6. Nvidia controller plugged into USB port next to HDMI
7. Male-to-male USB cable (for ADB)
8. USB mouse
Process
1. Start Windroid and choose device (Nvidia, Shield TV)
Windroid will automatically download resources in Data folder (incl. TWRP that did not work for me), so dont block it with firewall.
2. Download proper TWRP from link above, and replace the one in Windroid Data/Recoveries folder using same name (Recovery1.img). You will notice difference in sizes. One that Windroid downloads is 25mb, while the one from link is ~ 16mb.
3. Enter fastboot on ShieldTV using hardware method (above mentioned with A+B buttons)
4. Now quickly In Windroid click button Refresh - and status will be updated to Fastboot
5. Then again in Windroid - click Flash TWRP and accept safety questions.
6. After successful flash - reboot into TWRP (here you need USB mouse - so you can unplug Nvidia controller, and plug mouse)
7. In TWRP - Choose Install - navigate to external USB and select flashable zip (Lineage ROM as above)
8. Once booted - enable USB debugging again. (you could be prompted on the Shield TV to allow your PC as debugging device, if so, say yes)
Getting back to full stock ROM with TWRP and unlocked bootloader
1. Install Minimal ADB and Fastboot you downloaded
2. Extract boot.img, system.img and vendor.img from Nvidia stock recovery image (leave other files out), and place these files into Minimal ADB and Fastboot folder (it is in Program Files x86)
3. While on (in LineageOS) connect Shield TV with PC using male-to-male USB cable
4. Start Minimal ADB from destkop icon and run following commands (commands are only in italic)
adb devices (checks if device is online. Its a must to proceed)
adb reboot bootloader (reboots to fastboot)
fastboot flash boot boot.img
fastboot flash system system.img (will take longer as its a big file)
fastboot flash vendor vendor.img
Once finished - reboot to TWRP, plug in USB mouse (instead of controller) to navigate, and perform Factory Reset.
If you wish to root you can do it via TWRP (which is what I did, flashing SuperSU previosly downloaded to USB)
Thats it - you are back from the dead!

Post updated - with process how to go back to stock

Thanks for this guide. It saved my ass!

Hi phnikola
thank you very much for your super instructions.
With this tool I could bring my TV Shield 2017 back to life, which got stuck in the Boot Animation.
I thought it was a trash can case, also contacted NVIDIA support to see what they were saying.
So I can also send the possible to me for the purpose of repair saved, thanks to you!!!!!!!!!!!!!!!!!!
Greetings Akki

Bricked phone doing factory upgrade to B04. Stuck in EDL mode, but wont connect :(

Bricked phone doing factory upgrade to B04. Stuck in EDL mode, but wont connect
Device manager shows QUSB_BULK but no tool will see the phone. Any ideas guys.
I have installed quailcom drivers etc , no difference

You can try this tool:
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

Hi , I did try that. The port manager in the app does not show anything. It as if the phone is not connected. Even though it is listed in windows device manager as QUSB_BULK

Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash

the_hoho said:
Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash
Click to expand...
Click to collapse
Hi,
I waited till the battery discharged. Went into EDL mode. They only success I had is with axon7tool.exe
Miflash will not detect the phone. As seen believe I can read and write with axon7tool.exe
Is there any recovery I can put back on the phone that will run? The bootloader is unlocked. Thanks
H:\TRWP AXON 7>axon7tool -r recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Reading recovery ...
Success!
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...

> H:\TRWP AXON 7>axon7tool -r recovery
Your command with option "-r" (for read) only backuped the existing recovery to your PC.
There was no effect on the phone. It read your phone recovery and downloaded (=backuped) to your PC (probably with name recovery-backup.bin).
Since your booloader is unlocked, you can write official but unsigned TWRP recovery to the phone. This official but unsigned TWRP recovery
will run correctly (since bootloader is unlocked). So you need to 1) download latest official TWRP recovery, then 2) write it to the phone.
1)
On your PC:
Go to https://eu.dl.twrp.me/ailsa_ii/
Download the recovery twrp-3.3.1-0-ailsa_ii.img (14 897 152 bytes, md5 0d57b791c6b7c7d979ea70b0951c519d) with the link:
https://eu.dl.twrp.me/ailsa_ii/twrp-3.3.1-0-ailsa_ii.img.html
Copy the file to the directory containing your axon7tool.exe ("H:\TRWP AXON 7").
Then copy twrp-3.3.1-0-ailsa_ii.img to recovery.bin (command: "copy twrp-3.3.1-0-ailsa_ii.img recovery.bin")
(this means you have a new recovery.bin file which is exactly the same as twrp-3.3.1-0-ailsa_ii.img file).
Explanation: this to prepare to write TWRP recovery to the phone, the axon7tool.exe syntax "-w recovery" requires a file named recovery.bin
which has the content of the recovery you want to put (in your case, latest official TWRP recovery twrp-3.3.1-0-ailsa_ii.img).
On your PC, go to H:\TRWP AXON 7 directory:
H:\TRWP AXON 7>
type "dir" command, you should have files: axon7tool.exe, recovery.bin (identical to twrp-3.3.1-0-ailsa_ii.img), twrp-3.3.1-0-ailsa_ii.img and other files.
2)
Put you phone in EDL mode as you did before.
On your PC, type the following command to write TWRP recovery to the phone:
axon7tool -w recovery
(Explanation: the above command will write (-w) the recovery to the phone using the file named recovery.bin (= twrp_rec_tenfar.img) found in your PC.
You can then boot to recovery, using menu in bootloader at start (use Vol-Up, Vol-Down for selection, Power to Confirm selection).
Other way: if phone is power off: Vol-Up + Power to get into TWRP recovery.
Afterwards, with TWRP you have total control on the phone, custom ROM etc...