Hello,
I have a Motorola Razr Maxx that is running the latest OS, and is rooted. I recently broke my screen and cannot get past the lock screen so I can start my VNC server (to continue using my phone without the screen). I have searched through what seems to be all posts on bypassing pattern lock and I have not been able to succeed yet due to permission denial for super user in ADB, not having sqlite3 on my phone, and not being able to flash anything onto it in recovery mode.
Does anyone have any ideas on how to bypass the lock screen without any use of the touchscreen? I have debugging mode on, and I have a access to view what is on the screen via hdmi cable or remote viewer.
Thanks in advance.
thazzle said:
Hello,
I have a Motorola Razr Maxx that is running the latest OS, and is rooted. I recently broke my screen and cannot get past the lock screen so I can start my VNC server (to continue using my phone without the screen). I have searched through what seems to be all posts on bypassing pattern lock and I have not been able to succeed yet due to permission denial for super user in ADB, not having sqlite3 on my phone, and not being able to flash anything onto it in recovery mode.
Does anyone have any ideas on how to bypass the lock screen without any use of the touchscreen? I have debugging mode on, and I have a access to view what is on the screen via hdmi cable or remote viewer.
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2620456
Do you have the SafeStrap recovery? Root adb commands might work from there.
thazzle said:
Hello,
I have a Motorola Razr Maxx that is running the latest OS, and is rooted. I recently broke my screen and cannot get past the lock screen so I can start my VNC server (to continue using my phone without the screen). I have searched through what seems to be all posts on bypassing pattern lock and I have not been able to succeed yet due to permission denial for super user in ADB, not having sqlite3 on my phone, and not being able to flash anything onto it in recovery mode.
Does anyone have any ideas on how to bypass the lock screen without any use of the touchscreen? I have debugging mode on, and I have a access to view what is on the screen via hdmi cable or remote viewer.
Thanks in advance.
Click to expand...
Click to collapse
As long as your phone is rooted you should be able to do
Code:
adb shell su
.
If you've never given adb su priviledges before it may not work, in which case you should boot to recovery (if your rooted I'm assuming you have proper recover installed, and if you don't shame on you )
Any recover based on TWRP (SafeStrap, ClockworkMod, etc.) should give you adb access, you might need to mount the system partition though.
Tory Gaurnier said:
As long as your phone is rooted you should be able to do
Code:
adb shell su
.
If you've never given adb su priviledges before it may not work, in which case you should boot to recovery (if your rooted I'm assuming you have proper recover installed, and if you don't shame on you )
Any recover based on TWRP (SafeStrap, ClockworkMod, etc.) should give you adb access, you might need to mount the system partition though.
Click to expand...
Click to collapse
is there any way to boot to recovery without seeing whats on the screen? my hdmi doesn't recognize a connection until the phone is fully on
EDIT: I also never gave adb su priviledges, i rooted the phone shortly before breaking it.
Tory Gaurnier said:
As long as your phone is rooted you should be able to do
Code:
adb shell su
.
If you've never given adb su priviledges before it may not work, in which case you should boot to recovery (if your rooted I'm assuming you have proper recover installed, and if you don't shame on you )
Any recover based on TWRP (SafeStrap, ClockworkMod, etc.) should give you adb access, you might need to mount the system partition though.
Click to expand...
Click to collapse
Crap, I didn't think about that, if you have CWM then hold Volume up and Power, but it's going to be impossible to tell when it gets to recovery. If you have SafeStrap the touchscreen will have to work, if the touchscreen functions at all, then keep pressing the bottom left corner until you feel the vibration of the Recovery button.
Otherwise you might be out of luck.
Sent from my XT1049 using xda app-developers app
Related
My screen and digitizer are broken on my S4. It is running the ME7 firmware (bought it that way), so I can't go back to MDK or apparently use any sideload stuff (such as CWM recovery).. At least, don't think so. I tried blindly doing it, but no luck.
I want to get app data off the phone (not just apks, but save data), was thinking adb, but when I boot into recovery, it shows unauthorized (on the PC that I rooted it with). When I plug in while it's booted, it never shows in the list of devices at all. Yes, I have the latest drivers from Samsung, yes, I have the latest adb, yes I have tried different cables. No, I cannot click or accept or navigate the phone at all through the touchscreen, nor even see what is displayed (broken!)
Is there any way to override this somehow and get access to the internal memory? I already copied everything that it shares by default through the file sharing mode (that still worked fine), but that doesn't give access to /data/data/ etc...
adb Summary:
- Recovery mode shows unauthorized. If I use the menu options (blindly), I can get it into sideload mode. I did something to get it into recovery status in adb, but I have no idea how I did that, and I wasn't able to get any data off in that mode either anyway.
- I can get it into Download mode, but flashing CWM didn't work (with heimdall), and adb shows nothing useful in that mode.
- Booted, it goes into the regular share files mode, but adb devices lists nothing.
Really hoping I won't have to either lose all my save data, or buy the docking station..
Thanks in advance!
Have exactly the same problem
Lander3 said:
My screen and digitizer are broken on my S4. It is running the ME7 firmware (bought it that way), so I can't go back to MDK or apparently use any sideload stuff (such as CWM recovery).. At least, don't think so. I tried blindly doing it, but no luck.
I want to get app data off the phone (not just apks, but save data), was thinking adb, but when I boot into recovery, it shows unauthorized (on the PC that I rooted it with). When I plug in while it's booted, it never shows in the list of devices at all. Yes, I have the latest drivers from Samsung, yes, I have the latest adb, yes I have tried different cables. No, I cannot click or accept or navigate the phone at all through the touchscreen, nor even see what is displayed (broken!)
Is there any way to override this somehow and get access to the internal memory? I already copied everything that it shares by default through the file sharing mode (that still worked fine), but that doesn't give access to /data/data/ etc...
adb Summary:
- Recovery mode shows unauthorized. If I use the menu options (blindly), I can get it into sideload mode. I did something to get it into recovery status in adb, but I have no idea how I did that, and I wasn't able to get any data off in that mode either anyway.
- I can get it into Download mode, but flashing CWM didn't work (with heimdall), and adb shows nothing useful in that mode.
- Booted, it goes into the regular share files mode, but adb devices lists nothing.
Really hoping I won't have to either lose all my save data, or buy the docking station..
Thanks in advance!
Click to expand...
Click to collapse
Did you find a fix?
My e970 got smashed, and touch screen is out.
I cannot get into the phone as the lock screen is impossible to swipe. I tried the ADB method of editing the lock screen settings of the ROMs . However I am not able to get into the ADB shell to execute the commands. ADB only works in recovery and lists device as a recovery and not as a device proper.
There a way thru the ADB in recovery by executing pull command but ADB cannot access the System / data folders for the Build.prop file to be edited. In my situation, as ADB only connects in recovery mode, it is not entering the sytem area and file cannot be found.
Please advise on the way forward, as I cannot find a guide in this situation, most guides show the ADB pull command, which in my case does not work.
Milind
milindchitale said:
My e970 got smashed, and touch screen is out.
I cannot get into the phone as the lock screen is impossible to swipe. I tried the ADB method of editing the lock screen settings of the ROMs . However I am not able to get into the ADB shell to execute the commands. ADB only works in recovery and lists device as a recovery and not as a device proper.
There a way thru the ADB in recovery by executing pull command but ADB cannot access the System / data folders for the Build.prop file to be edited. In my situation, as ADB only connects in recovery mode, it is not entering the sytem area and file cannot be found.
Please advise on the way forward, as I cannot find a guide in this situation, most guides show the ADB pull command, which in my case does not work.
Milind
Click to expand...
Click to collapse
Hmm, what are you planning to do after unlocking the phone? If it's to back up files, I think TWRP automatically mounts your phone storage (it does for me) when plugged in and started up.
Vampir1c said:
Hmm, what are you planning to do after unlocking the phone? If it's to back up files, I think TWRP automatically mounts your phone storage (it does for me) when plugged in and started up.
Click to expand...
Click to collapse
NO there is a specific app from the Govt. in Singapore that is not compatible with my standby Samsung s3. It requires synching my data by blue tooth, which I am not able to do without my e970 touch functionality. Hence need this help:
I need to be able to get into the phone unlock, then enable bluetooth to sync my data to the app.
Hope that explains why I need to get more than data which I also knew long back.
regards.
Milind
try http://forum.xda-developers.com/showthread.php?t=2620456
Hi there,
My girlfriend managed to broke her phone's screen to a point which it stays black even if the phone is on.
The device is password protected, the password however is known, but no way to type it as the screen is broken. Device is NOT rooted, nor does it have a custom recovery installed and more importantly, it does NOT have ADB/USB Debugging enabled.
I read some stories that it could be possible though Download -mode, but I haven't tested it yet.
She needs the photos from the phone and they were not stored on the SD-card, but rather on the phone's internal storage for some reason.
Working with Windows.
What can be done in order for me to recover them?
Without ADB you ate out of luck. You will need it to pull the files even in download mode.
zelendel said:
Without ADB you ate out of luck. You will need it to pull the files even in download mode.
Click to expand...
Click to collapse
So you're saying that it's not possible, by any method?
Please keep in mind that the device's buttons DO work so I should be able to get into recovery and/or download mode and flash the custom recovery so I can access the files.
I have a MOTO z with a shattered screen. Wanted to use it as a device to fiddle with. But in order to operate it all the tools seem to require adb. It is rooted, and twrp installed, and it has been adb connected before (authorisation wouldnt be a problem), but adb is switched off now. How can I switch it back on without access to the screen (nothing to see)?
boot into twrp - it has adb enabled by default. At the very least you'll be able to pull data off the device, even a decrypted one, assuming you know the key
This is still twrp you're going to be adb'ing in not your rom - from there you should be able to flash a custom rom with adb enabled before hand, manually. but then you'd have to solve authorization issue again, as the previous one wouldn't work with the "new" rom ( i think ).
Not sure if this is the proper place for this question; if not, please move. I picked up an Irulu Expro No. X9 Android tablet on eBay. It seems to work fine, except I can't get past the login screen. I tried many times the various key combinations to get it into recovery mode but none worked. Other suggestions had me putting it in debug mode first, but how to do that if you can't get logged in? I'm not concerned about saving any data, I would just like to be able to use it. I would appreciate any help to solve my problem. Thanx.
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
jwoegerbauer said:
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
Click to expand...
Click to collapse
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
jrockow said:
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
Click to expand...
Click to collapse
OK, so I'm somewhat of a rookie when it comes to ADB and FASTBOOT.
I'm not sure I have everything correct. I'm using an app called "Minimal ADB and Fastboot".
I have another tablet, same as the one I can't access, and I have turned on the developer options.
Even with that, I still can't see any devices when I run ADB.
FYI: When I look at devices in my PC it shows up as X9, which I believe is correct.
With my no password tablet, I can actually see all the directories of my Android on my PC.
If I try that with the other one don't see any directories.
jrockow said:
With my no password tablet, I can actually see all the directories of my Android on my PC.
Click to expand...
Click to collapse
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
jrockow said:
I'm using an app called "Minimal ADB and Fastboot".
Click to expand...
Click to collapse
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
jwoegerbauer said:
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
Click to expand...
Click to collapse
I was incorrect in my earlier post, when I said I turned on the developer mode on my "good" tablet and I still couldn't access it thru ADB.
I found out I really didn't have it turned on, and when I did I was able to execute the ADB commands.
That gets me back to my earlier post about not being able to turn on the developer mode on my "bad" tablet if I can't log in.
I would think with all the guys working on this stuff someone has come up with a way to get around a lost password?
I remind you, I tried the power+volume sequence many times, many ways, so I need a different approach; if there is one?
Thanx.
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
jwoegerbauer said:
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
Click to expand...
Click to collapse
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
jrockow said:
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
Click to expand...
Click to collapse
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
jrockow said:
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
Click to expand...
Click to collapse
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
jwoegerbauer said:
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
Click to expand...
Click to collapse
If I could boot into Recovery Mode my problem would be solved.