Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Hi mates,
My TF300t(unlocked) is bricked:crying: Im only able to go into TWRP(2.6.3) but i can't go into the bootloader(for using fastboot and co)
BTW, there is no Rom installed, so if i start the tablet (no matter if i press Power+Vol Down or not) i allays end in TWRP.
My TWRP is also "buggy". It has some problems, like: Unable to mount... / Unable to set emmc bootloader message.... / unable to find partition size for xyz.... So i cant use TWRP to flash/install something and factory resets didnt work.
There are a lot of good guides how to UNBrick the tf300t, but they all need fastboot. Does someone knows how i could Fix fastboot with ADB? ADB is working fine. Maybe i can use ADB to fix TWRP or even better Fastboot.
Sry for my bad english, please help my
Have you tried
adb reboot-bootloader
?
alponte said:
Have you tried
adb reboot-bootloader
?
Click to expand...
Click to collapse
Thanks to you, it worked!!! with adb i could killed TWRP and after i used this:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
After:
fastboot -i 0x0B05 flash system blob
now i back in Asus Stock rom, and i will stay there^^
THX
Access via adb on twrp 2.4.4.0
Hi folks - time to activate an really old post
I do have also problems like manckosy in 2014:
The TF300t I have here has TWRP 2.4.4.0:
- Android booting is not possible
- it's not possible to mount SD-Card
- I don't have the permission to enter the tab via adb
Does anyone of you have an idea how I can get access with adb?
Thx a lot in advance!
f_lux said:
Does anyone of you have an idea how I can get access with adb?
Click to expand...
Click to collapse
Yes, I do! Hopefully you have "Minimal ADB and Fastboot" installed on your PC.
First of all, check whether you are able to reach fastboot protocol by pressing Power and Volume down together. Fastboot protocol should appear. That means now you have ADB access via USB and you will find further help here: https://forum.xda-developers.com/sho....php?t=2179759.
ebonit said:
Yes, I do! Hopefully, you have "Minimal ADB and Fastboot" installed on your PC.
First of all, check whether you are able to reach fastboot protocol by pressing Power and Volume down together. Fastboot protocol should appear. That means now you have ADB access via USB and you will find further help here: https://forum.xda-developers.com/sho....php?t=2179759.
Click to expand...
Click to collapse
I Have a similar problem and the link above goes to a 404 page.
In my case, My Tablet boots directly to the TWRP splash screen, and freezes. I can get status and serial number via ADB, but that's all.
If I try to reboot (via ABD) I get no response.
The device appears on Windows10 devices list, but Fastboot can't see it (I get that "<waiting for device>" message). I guess that my TWRP is damaged somehow, only part of the ADB protocol is getting up.
That happened when I tried to clean up the cache and ended up messing it all up.
The Status on ADB says that the tablet is on recovery mode.
Is there a way of flashing TWRP with ADB only? Or it is bricked forever?
Thanks for any help
mau0968 said:
I Have a similar problem and the link above goes to a 404 page.
Click to expand...
Click to collapse
Sorry for the dead link. Here we go: https://forum.xda-developers.com/showthread.php?p=44244313#post44244313
Please note if you cannot reach fastboot or recovery, your device is bricked for good!
Hello everyone, I urgently need help, brought this tablet to repair, hangs on the download logo, does not start any further, customers do not have a cable to connect to the computer, I have tried all possible ways to download recovery, fastboot, and indeed where Either it does not give out, a permanent download logo, tell me who knows what, maybe I'm doing it wrong
Recently I installed a custom ROM that is meant to be installed on a Huawei P8, for my Huawei P8 lite as my new OS because I accidentally deleted my whole OS. When I plug my mobile phone to a power source it shows the Huawei logo, I cannot get it into fastboot/rescue mode. If I try the dload folder to sd-card method it will not do anything. Does anyone know what to do.
Flash the stock firmware. I'm 100% sure your problem would be solved.
munimjaffer said:
Flash the stock firmware. I'm 100% sure your problem would be solved.
Click to expand...
Click to collapse
How do I flash it without fastboot?
pim8181 said:
How do I flash it without fastboot?
Click to expand...
Click to collapse
What do u see when u try to enter fastboot?
munimjaffer said:
What do u see when u try to enter fastboot?
Click to expand...
Click to collapse
When I try to enter fastboot I just see the Huawei logo
pim8181 said:
When I try to enter fastboot I just see the Huawei logo
Click to expand...
Click to collapse
Ok can u enter into recovery mode?
munimjaffer said:
Ok can u enter into recovery mode?
Click to expand...
Click to collapse
Nope....
Your phone got hardbricked with flashing a wrong rom,hardbrick is really hard to unbrick,
i already have one phone that got hardbricked due to flashing a wrong rom,since now i can't find the solution to unbrick it,
hope you find the solution soon..
pim8181 said:
Nope....
Click to expand...
Click to collapse
Is the device recognized by PC? If not, what is device manager labeling the device as?
If it connects to PC and is recognized you can.........
Use adb to clear cache and dalvik/ART cache, then see if the device will boot to recovery or fastboot, if not then power the device off and remove the battery then reinsert the battery(if it has a removable battery). Then leave the device off and connect it to PC then open a adb terminal and type:
adb reboot bootloader (press enter, sometimes the deamon has to start, if nothing happens then type adb reboot bootloader a second time, some devices can be booted from a powered off state with adb)
If that doesn't work try typing:
adb reboot fastboot (press enter).
If none of that works to boot fastboot then try turning the device on, when it gets to the logo, connect the device to PC, open a adb terminal and type:
adb devices (press enter, if it returns a serial number the device is recognized)
Then type:
adb reboot bootloader (press enter and it may boot to fastboot)
Or type:
adb reboot fastboot (press enter)
Or type:
reboot fastboot (press enter)
If none of that gets you to fastboot and you can't boot it manually with the buttons then you're bricked, its not hardbricked though because it boots to logo so that means bootloader is at least there even if it is corrupted and whether anything else is there or works or not.
Whatever you flashed must have had some differences in partitions that flashed over your partitions in places that weren't correct for your device, its more than just the software not being for your device, it is structured completely different than your device.
You've got to get to fastboot someway to flash the stock firmware, that's the only thing I see being able to correct your partitions and put the .imgs in the places they are meant to go.
There is also the possibility that you can download your stock firmware, then extract the kernel(Zimage, its sometimes bundled with/called boot.img or recovery.img, depending on device and android version), the boot.img, the recovery.img and the system.img and then do some research on your device model number and find out which partition(mmcblk0) each of those imgs go in(I could tell you how to use adb to find the partitions but that wouldn't help if flashing the wrong things has screwed up their placements). Then, if adb is working with the device you can use the dd command to manually push the boot.img to its mmcblk0, the recovery.img to its mmcblk0 and the system.img to its mmcblk0.
I would start with dd-ing the recovery, then seeing if it will boot to recovery, if the recovery is a custom recovery and you have a nandroid backup or a correct ROM zip, try restoring or flashing. If it doesn't then dd the boot.img to its mmcblk0 and see if it boots to recovery, if not, dd the system.img to its mmcblk0, you can repeat this process with each of the .imgs in your stock firmware. Maybe if you can push enough to the device it will restore some functionality that will allow you to get booted to a state will allow you to completely reflash the device.
If the confused you then I might have confused myself typing it, lol.
I need some help. My phone is stock in fastboot mode. If i make a fastboot -reboot command, it will just reboot back to fastboot mode. I cant restart the bootloader. Im thinking i need to try and flash a fastboot rom with a stock image, but my skills are rusty. Any guidance would be much appreciated.:crying:
Hey , Just download the fastboot rom , below is the link , you will find instructions there
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
to make it easy things to remember
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
HOW TO FLASH
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 6 in fastboot mode (Power and volume-);
Connect the OnePlus 6 to PC;
Run .bat flasher you need;
Wait until the process end;
With new .bat you need to manually reboot the phone.
and i use this command flash-all-partitions.bat
_frog hair said:
I need some help. My phone is stock in fastboot mode. If i make a fastboot -reboot command, it will just reboot back to fastboot mode. I cant restart the bootloader. Im thinking i need to try and flash a fastboot rom with a stock image, but my skills are rusty. Any guidance would be much appreciated.:crying:
Click to expand...
Click to collapse
Same thing appened to me yesterday... now im in holiday withiut the pc and i cant to restore it. Did you try to install hydrogen os beta before to brick?
_frog hair said:
I need some help. My phone is stock in fastboot mode. If i make a fastboot -reboot command, it will just reboot back to fastboot mode. I cant restart the bootloader. Im thinking i need to try and flash a fastboot rom with a stock image, but my skills are rusty. Any guidance would be much appreciated.:crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
I wish people would understand what the term brick means! I will also say it is 100% impossible to brick a oneplus 6 WITHOUT physical hardware damage. also fastboot mode is bootloader mode.
Thank you @Ajaykumar21066. I did some reading aswell, and first off -i must apologize for calling it a brick, since it really is a fastboot bootloop situation. Will report back when solved.
Solved using unbrick tool. Fast and easy.
Is there any way to get root/custom recovery/custom roms on the A502DL or A501DL? If so, how?
lehmancurtis said:
Use the boot mode tool from here for the a501dl. It definitely is unlockable! You can grab the TWRP.img I compiled for the a501dl from this link.
Click to expand...
Click to collapse
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
lmgnsa said:
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
Click to expand...
Click to collapse
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
fliproc said:
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
Click to expand...
Click to collapse
Use a tool that controls bootmode. Mtk-mode-selector
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Please help, it says "waiting port" forever
Thanks for the reply! I tried this tool, along with adb commands, etc., and I just can't even get fastboot. This would be an AWESOME phone, if not for this dumb crap!! The phone I had before this one is a Z717VL, and it sucks as well. They are both Tracfone phones that were given to me by my wife. I think I'll just get a Galaxy S8 or so and just root it instead. All other phones that I had on Verizon in the past have been super easy... just a One-Click-Root. Thanks everyone for your time and help!
lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Are you sure the method you thought of works? The bootmode tool you linked cannot get the A501DL to fastboot mode, it just says "waiting port" forever.
@lehmancurtis I feel like you might be lying about whether or not your method works, as the boot mode tool does not work. @lmgnsa did it work for you?
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
williamhancock328` said:
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
Click to expand...
Click to collapse
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
mickeybeats said:
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
Click to expand...
Click to collapse
I have already installed the MTK VCOM drivers multiple times, I don't know why it still doesn't work.
T
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
lmgnsa said:
To keep recovery from being replace several files need to be disable (various approaches are effective i.e. removed, replace, or renamed). Magisk usually handles this task, but sometimes there are exceptions. But, you need to address that before flashing gsi's for multiple reason and none are fun to deal with. Yes, this is A only and does not use A/B update method (at least not entirely as a few partitions are making use of the A/B partition labels). I've not been doing much with this particular device since mine was cracked and the usb port messed up when I got it, so nature took its course before I was able to achieve a fully stable custom setup.
Click to expand...
Click to collapse
sj78 said:
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Click to expand...
Click to collapse
It sometime takes a few tries to get the phone and tool to do what its supposed to, but if you get the waiting message start over until the program reboots the device. It will work, it's just not a perfect process.
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
You need to modify a few files. It's almost just like the 5059 devices and you can look up the 5041c thread to see what needs edited. Use the fstab.mt6739 from the 5041c.
Here's the tool. I think some of the links to it got messed up. Make sure you turn on developer options and check that oem unlock is ticked as well as adb usb options. Once in fastboot, issue the following
Code:
fastboot oem unlock-go
Follow the instructions on the device. Then boot into system and complete setup so that you can turn on developer options again since your device was just reset. Boot to fastboot once again and issue these.
Code:
fastboot flash recovery ./recovery.img
Code:
fastboot oem reboot-recovery
That should be the custom recovery you just installed. It will be replace on reboot if steps are not taken. I was in the process of working this issue when my beat up a501dl succumbed to its varied and multiple impact injuries. If I can find the time to repair it I will finish where I left off, but in the mean time I will help as much as I can.
Regular drivers are built into the phone but you may need vcom drivers. I'm going to attempt to repair mine enough to reset and flash again. I'll probably have to nav my screen via commands, but I will attempt to capture the process and show you.
I've got a A501DL, I enabled usb debugging and oem unlock, seems like the A501DL in fastboot does not talk with the pc, i've installed so many driver things its crazy butat fastboot when typing fastboot reboot bootloader, it reboots the phone but it skips fastboot and turns on to my home screen, I used volume up and power, I get in fast boot butthe device isnt being detected by windows 10 64 bit. Also in fast boot there is only
reboot system now
wipe data/factory reset
wipe cache partition
power off
im going nut that fastboot isnt working with this device.