Database Info

How to enable usb debugging on xperia m4 aqua in boot loop

Hi all!
I've read several threads about boot loop and how to fix it. All very helpful and insightful BUT I have several issues that's making it very hard to sort the phone out. Sony Xperia M4 Aqua in boot loop.
1. Carrier / Service provider unwilling to resolve issue with phone - I've made peace with this.
2. USB debugging is NOT enabled.
3. Bootloader not unlocked - reason is says "ALLOW UNLOCK: NO" - I haven't tried the carrier but if they aren't willing to sort the boot loop issue I'm sure they won't solve the unlock issue.
Now....I've tried flashing the ROM in Flashtool. All goes well until I get to the part were it tells me that the USB debugging must be enabled. I'm guessing if I get past this issue I might be able to get the new ROM on and perhaps if the universe is fair and just the issue will be sorted.
I have also tried another program that supposedly gets past the "ALLOW UNLOCK: NO" issue but this program only tells me "Waiting for device..."
Phone works in Flash mode and Fastboot mode.
I would really like some help.

Stuck at bootloop after update, can't access ADB.

Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error

I switched boot slots using fastboot and now I can't access my phone via adb or fastboot

I was having some issues with installing a factory update on my Pixel 2, and tried using fastboot to switch the boot slot to slot B. Now I'm unable to access the phone via USB cable because adb does not see my device. The phone isn't even recognised in Device Manager anymore and nothing I do seems to fix that, including different cables and different PCs.
In bootloader mode, I can see:
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: Slot Unbootable: Load Error
Any help would be appreciated. If I could just get Device Manager or adb to see my phone again, that would be a fix.

Tersnaus said:
I was having some issues with installing a factory update on my Pixel 2, and tried using fastboot to switch the boot slot to slot B. Now I'm unable to access the phone via USB cable because adb does not see my device. The phone isn't even recognised in Device Manager anymore and nothing I do seems to fix that, including different cables and different PCs.
In bootloader mode, I can see:
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: Slot Unbootable: Load Error
Any help would be appreciated. If I could just get Device Manager or adb to see my phone again, that would be a fix.
Click to expand...
Click to collapse
Hook your device up to your PC and open adb/fastboot whilst in bootloader screen and then hold down the power button until the phone vibrates and check if your pc has recognised it. It may well take many attempts but I revived mine from a similar scenario doing the above. If you search the forum for slot unbootable you will find a thread for exactly this issue also.
Good luck

Junglism93 said:
Hook your device up to your PC and open adb/fastboot whilst in bootloader screen and then hold down the power button until the phone vibrates and check if your pc has recognised it. It may well take many attempts but I revived mine from a similar scenario doing the above. If you search the forum for slot unbootable you will find a thread for exactly this issue also.
Click to expand...
Click to collapse
Thanks for the advice - I managed to fix the problem in just this way, although I needed to do it on a friend's machine that was running Linux. Windows was hopeless. I was quite sure at that moment that I was going to need a new phone.

Tersnaus said:
Thanks for the advice - I managed to fix the problem in just this way, although I needed to do it on a friend's machine that was running Linux. Windows was hopeless. I was quite sure at that moment that I was going to need a new phone.
Click to expand...
Click to collapse
At least your back up and running mate, that's the main thing. Yeah, I know what you mean, i thought mine was a paperweight the first time I ran into this problem!

T-Mobile OP8 5g (IN2017); I have my unlock token from T-mobile, but I'm unable to flash it.

Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.

Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?

FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...

Have u try using other cable or even try on different PC?

hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next

No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.

UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!

I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/

EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.

Question Need Help - ROG 5s bootloop

Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver

Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.

Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?

dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.

I believe it's more likely motherboard. Is there any fix for it?