I tried to install Xposed through Magisk on my device and then it got stuck in a boot loop. I was going to use magisk module uninstaller with twrp but with the usb connected to my computer it only comes up as a cd drive. I tried putting it into download mode but adb wouldn't recognise it.
Edit: Hisuite asked me to install usb driver and it then it worked or it might of been me turning on mtp
Download Mode aka fastboot mode need fastboot.exe, no adb. Fastboot devices and see your phone id.
Related
Hi
when i use condi`s aoi to flash custom firmware it gets to a point
where it reboots and tell you to hold volume+ until recovery mode.
all the drivers work fin in normal mode but in recovery mode all i
get on computer hardware is yellow flag next to mtp driver and when
i try to install it reports a code 10 could not start device problem.
and there is no phone entry for adb.exe and tryed to install driners again
and it go`s fine but still no adb or mtp drivers for recovery.
i am on winxp pro.any ideas would be much appreciated.!
[edit]
sony tablet s not recognized by mtp and adb drivers-mtp show that device could not start. this is only in recovery mode!
phc1234 said:
Hi
when i use condi`s aoi to flash custom firmware it gets to a point
where it reboots and tell you to hold volume+ until recovery mode.
all the drivers work fin in normal mode but in recovery mode all i
get on computer hardware is yellow flag next to mtp driver and when
i try to install it reports a code 10 could not start device problem.
and there is no phone entry for adb.exe and tryed to install driners again
and it go`s fine but still no adb or mtp drivers for recovery.
i am on winxp pro.any ideas would be much appreciated.!
Click to expand...
Click to collapse
Need to manual install MTP. See here http://forum.xda-developers.com/showthread.php?p=22350827
For whatever reason fastboot on my PC (win10) doesn't detect my phone, adb detects it fine when it's in recovery or booted normally, I cannot send fastboot commands as it says waiting for device. I've tried a few things like the LG Mobile Driver and a universal driver but it still isn't working. Any ideas?
Just to clarify I am in Fastboot mode when trying this.
Edit: Also tried the Google USB drivers from the SDK manager, didn't make a difference
I ended up simply doing it on an Ubuntu installation. Works perfectly on there, not sure why Win10 doesn't work though.
My problem is solved.
I upgraded couple of days ago to new PC - Ryzen 5 2600/rog strix b450-f gaming with clean windows 10/64 and now i have problems with adb bootloaader driver and cmd commands. Before i was on intel xeon/gigabyte motherboard socket 775 windows 7/64
I use tool all in one, install usb drivers. When phone is turn on, with usb debuging, i can enter phone storage, device manager see phone as poco,everything is ok. When i start tool all in one i can see device id,i can go into fastboot mode(phone restart and go into fastboot). When phone goes into fastboot,device manager see it as Kedacom usb device/android bootloader interface, or sometimes as android phone/android composite usb device. I have adb/fastboot files all i need on pc. When i enter some command trough cmd,for example fastboot devices,or fastboot reboot bootloader, on phone screen goes to dark and in left top corner with small font is written phone will turn off. On cmd i see afther command i set and pres enter only ??????? questionmarks. So i must again manually enter fastboot mode.
I cant get fastboot/adb to work. I try to install other adb/fastboot drivers(xiaomi and google original from tool all in one),try to connect phone cable to other usb port(2.0/3.0/3.1) at the back of pc chase,also 2.0 in front case. I try other usb cable also. Try to manually update google drivers from this forum,then i cant bcouse some ini file is missing or if i set have disc and do manualy with some other driver it cant see phone in adb-fastboot mode. I try all that fall on my mind with no luck.
At the and i goes to my friend and try to install tool all in one,install google usb drivers from that tool,install adb/fastboot files. Try to enter fastboot and do same commands as before with cmd,and everything is working fine as it was with my old pc setup. Device manager see it as Kedacom usb device/android bootloader. He also have amd cpu/chipset - but it is not ryzen with fresh w10/64
Is there any fix for my case? Does anybody have same problem?
Thanks for reading.
I have Android Studio installed, and installed the USB drivers from Samsung's site.
On the phone (SM-J337P) I have enabled USB debugging and granted my PC access. I have also enabled OEM Unlocking.
adb works fine:
Code:
C:\Users\Stretch\Desktop> adb devices
List of devices attached
52004c578d1c16cd device
C:\Users\Stretch\Desktop>
I can easily but the phone into download mode by holding Vol-, Power, and Home. Once I have the phone in download mode, fastboot cannot see it:
Code:
C:\Users\Stretch\Desktop> fastboot devices
C:\Users\Stretch\Desktop>
When the phone is in download mode, Windows' Device Manager lists it under USB devices as "SAMSUNG Mobile USB CDC Composite Device"
If I try to update the drivers and select The Google USB Driver (from Android Studio) or the driver I downloaded from Samsung is says I already have the latest version.
How should I proceed to troubleshoot this and get fastboot to recognize the phone?
UPDATE: Never mind. I was in Odin mode, not Download mode. There is no download mode on this phone. I'm a moron.
Hi,
I was able to install custom rom on my v300s
but found out that twrp wasn't installed.
I used my computer adb to open twrp and installed custom rom
Then i found our something was wrong, any way to install twrp from now on?
i tried to open twrp with adb again,
when i use adb devices I was able to find lge~~~ on there.
but when i try fastboot boot twrp, it shows awaiting for devices then nothing happen
(I set my phone as ptp mode then usb debugging was on.
on my laptop the phone was resister as portable device and using MTP usb driver, wasn't able to change it to adb driver)
then i tried to boot my v30 as bootloader but pressing volume down key didn't work.
any way to install twrp from this state?
sorry for my bad English
I think you need to ensure you have the correct drivers installed. Even when they are, you need to also check in Device Manager that the correct driver is used when the phone is connected. It also sounds like you don't have USB debugging enabled.
ldeveraux said:
I think you need to ensure you have the correct drivers installed. Even when they are, you need to also check in Device Manager that the correct driver is used when the phone is connected. It also sounds like you don't have USB debugging enabled.
Click to expand...
Click to collapse
Ah the usb debugging was enabled.
I found something called qfil from qualcom and was able to reinstall my bootloader img file with it.
then i was able to connect my device as ADB devices
Thanks btw