Database Users

[Help] I bricked my Axon. Need help.

So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.

You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?

senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?

nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.

raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.

senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...

Try the Marshall London Bootloader Interface driver maybe?

nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?

senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.

Bricked - please help !

I accidently formated everything in twrp and ended without OS and was stuck in custom twrp. I tried to flash stock recovery and that went ok. Now whatever i do i cant sideload stock zip file using adb. Fastboot is recognized but adb is not. When connected to pc shows error. I have tried to install, reinstall all sorts of drivers but all the same. Is there a way to get back to stock using fastboot commands manualy? Please help !!

Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.

himanshuladia said:
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
Click to expand...
Click to collapse
You mean stock twrp or custom because i have stock but when connected i cant copy files on device because it is not recognized by PC

Del.

TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.

himanshuladia said:
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
Click to expand...
Click to collapse
Ok will try !

Del.

Finaly i did it after a few hours of trying to find a solution and figuring out why my PC doesn't recognize phone in adb I tried on an old PC with win7 installed and sideload went smooth like butter on first attempt. I have tried on two computers with win10 installed, tried with all sorts of USB cables, usb on computer 3.0 , 2.0, tried all sorts of drivers and nothing helped. I hope that someone else will have a benefit of this post and sort of a solution if he will have the same issue. Thanks to everyone that tried to help out!

drivers to MTP while recovery mode

Hi
i remember i had option to mount the n6p throgh the twrp, now when i connect my device through the twrp (recovery) i can't see the the device as MTP, i tried to install google drivers and still nothing, what to do more?
thanks

I7210I said:
Hi
i remember i had option to mount the n6p throgh the twrp, now when i connect my device through the twrp (recovery) i can't see the the device as MTP, i tried to install google drivers and still nothing, what to do more?thanks
Click to expand...
Click to collapse
It's built into TWRP and just works. Try a different cable/port.

v12xke said:
It's built into TWRP and just works. Try a different cable/port.
Click to expand...
Click to collapse
it's not driver thing? i tried in few ports and i got all the time same results

I7210I said:
it's not driver thing? i tried in few ports and i got all the time same results
Click to expand...
Click to collapse
Does it work when android is up and running?

yes, there i have the right drivers, also when i type adb devices when i'm in recovery mode or fastboot devices in fastboot, the device is recognized, the only thing is with the twrp mount
Sent from my Nexus 6P using Tapatalk

MI A1 not detecting in fastboot mode need some help

Help me ......I am trying to install gcam by no root method
I've installed adb and fastboot drivers on my pc but only adb is detecting my device but
In fastboot mode
Command > fastboot devices
Shows waiting for device
So can anyone plz help me finding proper fastboot drivers?
And if possible also share the process of installing them
Ps- I'm on Windows 10
Regards

You could try using " Mi A1 Tool" https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
Try power off and back on again a few times and then try using the tool to reboot in Twrp or fastboot. If that works your adb connection is OK.
Good Luck

RikLIjkendijk said:
You could try using " Mi A1 Tool" https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
Try power off and back on again a few times and then try using the tool to reboot in Twrp or fastboot. If that works your adb connection is OK.
Good Luck
Click to expand...
Click to collapse
I tried it but still my problem isnt solved by this one..
i cant even turn off my phone

Unable to flash TWRP - ADB is (Waiting for devices)

Nevermind I think it was my USB cable. Changed cable and everything works fine.
Until today I had an older version of TWRP installed no problem but I have reset my phone so I could update TWRP and install a fresh ROM but for the life of me I can not get fastboot to detect my phone or install a new TWRP
ADB commands work fine but when I boot or command into fastboot it just doesn't detect my phone any more. I've tried a few different drivers for my phone and USB etc but still nothing.
Have any of you had this problem? I'm hoping I may be overlooking something.
Click to expand...
Click to collapse