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 ).
Related
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
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
I have an answer to this. I had the problem, then I found the solution and now I'm sharing it:
Problem: I tried to put SuperSU on my M9 with CM-13 because I thought I needed root (you don't, under developer options there is the ability to turn on root essentially). So I flashed SuperSU from an apk and then it auto-updated itself then rebooted and got in a start up loop! Now I couldn't access the phone via adb, I'm not sure why. I think USB Debugging was off, but I'm not sure. AND I had not installed SuperSU from a zip so I didn't have that file laying around! So I went and got the latest SuperSU which I heard would work (it did) here: http://download.chainfire.eu/969/SuperSU/ THEN....how do I get it on my phone? I mean, who has a micro-SD reader laying around...not me today.
I DID have fastboot working but not adb. SO....I went into my phone and launched recovery mode then I chose this new thing called "adb sideload." That turns ON MTP so your phone comes up technically on your PC via USB but it doesn't show under my computer. But then I was able to go to my command prompt and type "adb-killserver" then "adb sideload NewSuperSU.zip" and it loaded!!! And I could then boot in!
Now I'm sure I shouldn't have SuperSU running but at least now I can put all the needed binarys (like CM and gApps to get started if I needed to from scratch) on !!!
So it works now.
Hi all,
I have in my possession a Galaxy S7 that is a "secured". Developer mode is restricted. No wifi. Can't install 3rd party apps. No Play store. Can't install APKs via the SD card, nor Android Studio.
Images of the phone is here: imgur.com/a/r7XLf
State of the phone is the following:
No adb, no access to wifi, I can use OTG cables to plugin in USB drives, Bluetooth devices work, and no developer options
Rebooting the device with volume down and power brings me into Odin Mode (see screenshot 1), not much happens, I just force restart it, and we're okay again.
(adb and fastboot does not detect the phone in this state).
Rebooting with Volume UP and power and home button, will bring me into a Custom TWRP with only Reboot and Wipe.
(adb and fastboot does not detect the phone in this state)
My goal is to be able to access the filesystem in some form to retrieve data on a device, or dual boot the system, then get access to the secured partition. If I can root the devices, that's better. I am allowed to break the phone open if needed.
Alternatively, if I can get adb installed or be able to use my computer's ADB to connect to the phone, and then run commands to do some backups of apps, that is probably the best thing I am looking for.
What are my options? I am okay with doing tasks that can brick the phone. This is purely an exercise to see if I can get into this secure phone.