I broke my screen on my z5 compact. I cant unlock my phone.
So i tried a lot of things:
-OTG and usb debbugging is disabled, so this wont work.
However the upper part of the touchscreen is still working so I tried to remove the lockscreen, then go to the settings (phone tilt is active) to tilt my phone and use the working part of the touchscreen to activate OTG setting, but it seems that I need recovery-mode to disable/delete lockscreen. BUT of course it seems that the Xperia Z5 compact doesnt have a recovery mode, so i tried to install a custom recovery (aroma or clockworkmod), but i cant because usb debugging is disabled....
-Then I tried different ADB commands but it doesnt detect the phone (maybe because USB-Debgging is disabled?)
for example:
Code:
adb devices
The "List of devices" is empty.
When I type:
Code:
adb shell
it says "error: device not found"
I am really frustrated, im stranded for 2 days at the same problem PLEASE HEEEELP :crying:
Just guessing here, if you don't mind wiping the phone try turning it off, then while holding the volume down button, turning it on. Or try reinstalling the FW with Xperia Companion or Flashtool. However, how you will sign into your Google account after the reset, I don't know.
Related
I've noticed a few instances of people with problem flashing kernel (downgrading) Sony Xperia Mini Pro using Flashtool
"device connected, USB debugging off"
tl;dr hold "Volume down" instead of "Back"
Click to expand...
Click to collapse
There are suggestions about MSC mode or such. None work.
example here - Androxyde's suggested solution is problematic in that normally there is no driverid.properties inside x10flasher_lib until you install drivers, and you'll be prompted to install drivers only after you boot the phone to boot mode.
The problem is Flashtool tells you to plug the phone in while holding the BACK button. On Xperia Mini Pro both Menu and Back are made by expanding the touchscreen surface beyond the display surface, next to the physical Home button. Being an embedded programmer myself (not phones though) I know reading touchscreen coordinates and interpreting them as buttons is not something normally done in bootloader firmware. Simply put, Xperia never knows you hold "Back".
Of course that would make it impossible to flash for original developers too, so they had to create a workaround. Well, all that was left was trying all the physical keys. Vol- while plughing the USB did the trick, and the fact the phone was switched into MTP mode (after all my fruitless attempts with MSC) seemed to be entirely irrelevant.
So, just posting for future reference of anyone who stumbles upon this problem again.
Device connected with USB debugging off plz help
sharp_fang said:
I've noticed a few instances of people with problem flashing kernel (downgrading) Sony Xperia Mini Pro using Flashtool
"device connected, USB debugging off"
There are suggestions about MSC mode or such. None work.
example here - Androxyde's suggested solution is problematic in that normally there is no driverid.properties inside x10flasher_lib until you install drivers, and you'll be prompted to install drivers only after you boot the phone to boot mode.
The problem is Flashtool tells you to plug the phone in while holding the BACK button. On Xperia Mini Pro both Menu and Back are made by expanding the touchscreen surface beyond the display surface, next to the physical Home button. Being an embedded programmer myself (not phones though) I know reading touchscreen coordinates and interpreting them as buttons is not something normally done in bootloader firmware. Simply put, Xperia never knows you hold "Back".
Of course that would make it impossible to flash for original developers too, so they had to create a workaround. Well, all that was left was trying all the physical keys. Vol- while plughing the USB did the trick, and the fact the phone was switched into MTP mode (after all my fruitless attempts with MSC) seemed to be entirely irrelevant.
So, just posting for future reference of anyone who stumbles upon this problem again.
Click to expand...
Click to collapse
For 2011 devices line, be sure you are not in MTP mode
Device connected with USB debugging off
in my x8 e16
rahulgorain said:
For 2011 devices line, be sure you are not in MTP mode
Device connected with USB debugging off
in my x8 e16
Click to expand...
Click to collapse
I have a Tipo ST21i and I'm having the same problem. It's on when the phone's on, but when it's off the debugging turns off too. Please help!
Hi everyone, i got a pain in the ass problem that i cannot fix. I've been looking for 3 days in a huge labyrinth of forums before posting this.
The screen of my phone got broken and half of it doesnt respond, and i cant unlock the pattern screen because part of it is on the damaged part. I dont want to reset the phone, just try to skip the pattern screen or use it remotely on a PC, and seems very hard to achieve.
The phone is from a low-cost brand i bought in Mexico, the model is Vios 502015. The android version is 4.4.2. I think it is not root, but right now i dont know how to check it.
I tried using the device manager of Google to block the phone and change the pattern to a password that i can type with the unbroken side of the screen, but the phone has the wifi off and no sim because i lost it and till a couple of days i wont have another. Also tried to put a friend's sim in the phone for if the conection was on by magic or something like that. Didnt work, anyway new sim doesnt work.
I tried connecting a mouse with OTG and doesnt work either. It has not enabled the USB debugging mode and I ve been looking these days how to enable that option wihtout using the screen but it seems imposible.
When i connect the phone to the pc is only available the mass storage option. Also tried with adb commands but doesnt recognize any device using "adb devices".
But in recovery mode, if i select the option "install update from ADB" it does recognize it with the command "adb devices". The status of the device is sideload.
If i try the command to disable the pattern lock it returns error:closed. And also try to find the solution to this error, but nothing seems to work. Tried "adb usb", "adb kill-server" and "adb start-server". Nothing.
I dont know what else to do. Im starting to feel ill, haha.
So the question it would be: what can i do to skip the lock or a way to tun on the wifi mode or... i dont know, please help!!
Thanks to all of you for your time
Cheers!
------------------------------------------------------------------------------
Edit: i just noticed! i can write the pattern if i find a way to turn the screen upside down, any ideas?
FIXED: i used a program called gsm aladdin. I can use the phone again!
So I've been having a really unlucky day so far.
My Xperia Z2 6502 fell and the screen got cracked. The touch screen is going haywire. I had usb debugging mode enabled and was trying to recover the data using a screen mirror software but due to some bad luck, the random touches on the screen somehow turned debugging off. Also usb was set to charge only.
Is there anyway I can access the internal storage?
In summary:
- Running rooted marshmallow
- BL locked
- Touch screen going haywire
- No recovery installed ( the recovery I had installed was temporary, needed to be installed while booted with debugging enabled)
Any suggestions?
I tried using flashboot mode but I think it requires usb debugging to be enabled?
Can I do anything in fastboot mode?
dramon said:
So I've been having a really unlucky day so far.
My Xperia Z2 6502 fell and the screen got cracked. The touch screen is going haywire. I had usb debugging mode enabled and was trying to recover the data using a screen mirror software but due to some bad luck, the random touches on the screen somehow turned debugging off. Also usb was set to charge only.
Is there anyway I can access the internal storage?
In summary:
- Running rooted marshmallow
- BL locked
- Touch screen going haywire
- No recovery installed ( the recovery I had installed was temporary, needed to be installed while booted with debugging enabled)
Any suggestions?
I tried using flashboot mode but I think it requires usb debugging to be enabled?
Can I do anything in fastboot mode?
Click to expand...
Click to collapse
There is no need for usb debugging for fast boot
And did you tried using mouse with OTG???
If you can see the display, use an OTG cable to connect a mouse, so you can "click on" the screen and enable the USB debugging or make a backup.
First install the fastboot drivers, now enter fastboot mode by holding volume up while your phone is turned off and then plug it into your computer Unlock the bootloader by following these (https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/) instructions.
Now it's time to install twrp, download if from https://dl.twrp.me/sirius and then run fastboot flash recovery /path/to/file you should then be able to boot recovery and access mtp and adb
Happened to me.. grab an otg cable and a mouse, connect to your phone and navigate with the mouse
use the scroll to scroll up and down
Hello All,
I have strange problem with ADB debugging on my Smartwatch ASUS ZenWatch 3.
I´m on AW2.0 and I tryed custom AW2.0 kernel from here:
https://forum.xda-developers.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340
and all working fine except ADB debuging and ADB commands.
If I enable ADB debuging in developer option and plug my watch to the computer I not see any confirmation dialog about allow ADB. And I see only unauthorized device after ´adb devices´.
With stock kernel all worked fine.
For now I´m on stock recovery and I can´t use ADB commands in recovery. It´s totally..........
I need working ADB commands and main problem is missing confirmation dialog... not pop up....
I tryed everything.... Enable/disable ADB, rewoke ADB, restart computer and watch, new ADB drivers, start and kill ADB server, factory reset, delete RSA key... Nothing works for me
I tryed debugging over wifi and Bluetooth and same problem... Allow ADB dialog not pop up
And my watch is unauthorized...
I tryed also another computer and same situation...
Maybe some problem in kernel? Because ADB is enabled by default... I don't know...
Is there any other way to get working ADB commands?
Maybe some bypass?
Please could you help me? Thank you very much
Hello there,
Recently my Phone Screen died. I tried restarting it. Now i can only do 3 things.
1. Let it ring with smartthings
2. Use the Emergency call where it beeps
3. Restart the Phone with the Button combination
I am currently trying to get into recovery mode so I can backup my Data.
I have the most recent drivers installed. The Cable I use works with 3 different Phones.
I also tried a USB C to HDMI but had no luck. USB debugging is disabled.
ADB can enable USB debugging as far as i know.
Is there any aproach that i could try ?
a wireless mouse to enable adb and make the back up
Sorry, I should have specified that the screen is black.
What do you want to back up?