Today i broke the screen of my moto g
I am with android 6.0, it has root, but I can not connect throught adb on my computer, it says this, when i do "adb shell":
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
I would like to recovery my personal data, and to unlock my phone (to still continue to use with half of screen working)
pmj_pedro said:
Today i broke the screen of my moto g
I am with android 6.0, it has root, but I can not connect throught adb on my computer, it says this, when i do "adb shell":
I would like to recovery my personal data, and to unlock my phone (to still continue to use with half of screen working)
Click to expand...
Click to collapse
I was lucky and I entered on recovery mode and did:
adb pull -p /sdcard ./
Click to expand...
Click to collapse
and is now performing the backup
But how can I enter the pass of the sim card and deactivate the lock screen?
Solved
I deleted the keys through adb shell. This thread can be closed or delete
Related
I hope this is the right place to post this. I have been trying to 2 hours now to get my phone to either work with Odin so I can factory reset but stuck on file analysis, so I decide to skip that and use some of the adb methods (Ultimate goal is to update to one of these new roms.) On ADB, my device manager shows ADB, but as soon as the script in CMD shows it rebooting ADB service, ADB disappears from device manager and my phone locks up. I have tried everything that I can think of and am pulling my hair out.
-On the Odin, I did verify that only those 2 items were checks and device shows. Please help and let me know if this posting is acceptable. Thanks in advance.
I am dying here and want to throw this m*fer against the wall. LOL... I really am tired and about to go to sleep I think. If anyone has any ideas, please let me know.
I forgot to mention that Odin sees my device. It always shows 0:[COM4] or some random number.
That's really odd. Do normal adb commands work for you (i.e. can you get into adb shell or can you do an adb push)?
richse said:
That's really odd. Do normal adb commands work for you (i.e. can you get into adb shell or can you do an adb push)?
Click to expand...
Click to collapse
Yeah, I can do initial ADB commands, but any script that says "reboot ADB shell" freezes my phone and then no ADB in dev manager and my phone is mostly frozen. I have already factory reset it to see if it was something I put on it, but no luck. I'm still messing with Odin and I can't get that to work either...... sucky.
billecorgan said:
Yeah, I can do initial ADB commands, but any script that says "reboot ADB shell" freezes my phone and then no ADB in dev manager and my phone is mostly frozen. I have already factory reset it to see if it was something I put on it, but no luck. I'm still messing with Odin and I can't get that to work either...... sucky.
Click to expand...
Click to collapse
how long did you give the script to reboot adb shell? One time it took like 10 minutes for no reason. I just let it sit and finally it worked.
Start from scratch. Load up adb (using the developer sdk) and type adb kill-server. Then adb devices (server should restart) and then try your adb commands again. Report back with success/problems.
Sent from my SPH-D700 using XDA App
I have a Huawei U8180. I intalled ROM Manager, backed up the system and applied a new mod. After the mod installed, the phone turned on, it showed the hour-glass (like it always has done when starting up) and the showed a black screen saying android when it used to say 'yes' Optus (I know that it is part of the mod). The problem is that the phone just stays on the black screen that says android without doing anything. I waited for a long time and nothing happened. I don't know of any way to enter clockworkmod recovery to restore the phone other than on ROM Manager, but I can't get there unless my phone finishes starting up. I tried to press volume+power, but it doesn't work on my phone. Is there any (free) way of restoring the phone (either on the computer or on the phone)?
Plug USB to computer & see if you can communicate to the device using ADB.
-- Sent from my TouchPad using Communities
yes
post-mortem said:
Plug USB to computer & see if you can communicate to the device using ADB.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
yes.
is there a command i'm meant to type in?
tzzeri said:
yes.
is there a command i'm meant to type in?
Click to expand...
Click to collapse
try and type "adb devices" and see if it shows any device or not.
If you are able to send commands with adb, type "adb reboot recovery" and it will cause your phone to reboot from the recovery partition. Then, you can use the menu there to restore from your latest backup.
For a bit of reading on adb & fastboot, check this: http://forum.xda-developers.com/showthread.php?t=1590800
-- Sent from my TouchPad using Communities
thanks
post-mortem said:
if you are able to send commands with adb, type "adb reboot recovery" and it will cause your phone to reboot from the recovery partition. Then, you can use the menu there to restore from your latest backup.
For a bit of reading on adb & fastboot, check this: http://forum.xda-developers.com/showthread.php?t=1590800
-- sent from my touchpad using communities
Click to expand...
Click to collapse
worked!!! Thanks!!!
So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?
flash factory image with fastboot.
Tapatalked from my Hammerhead.
Timoooo said:
So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?
Click to expand...
Click to collapse
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
upndwn4par said:
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..
Timoooo said:
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..
Click to expand...
Click to collapse
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.
rootSU said:
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.
Click to expand...
Click to collapse
thanks got everything to work that way!
Timoooo said:
thanks got everything to work that way!
Click to expand...
Click to collapse
No problem. Cool
Hello,
My friend gave me his locked out phone AppTab Dual talk...( a company name unheard of) and asked me to unlock it for him. He doesn't know his account password. Now I tried booting into recovery or anything. I held power and vol down. Some stuff in Chinese came up. Image attached.
And language barrier apart, only vol down and up buttons work in that to scroll through the options . I've tried everything to try and select an option in that. But no luck!
If I hold down vol up and power buttons, something like a broken Android logo screen comes up which I believe is recovery mode for this device.
Then I plugged it on to my PC and installed the adb drivers for it.
adb devices --> I can see the device listed
Fastboot devices --> I can't see the device
adb reboot bootloader --> the stupid phone just reboots into actual rom instead of bootloader.
I tried to see if the bootloader is locked..now how do I unlock it? fastboot OEM unlock? Damn thing doesn't get recognised in fastboot.
I thought I'll enable USB debugging..which I believe isnt enabled.
So I searched online and came across this command.
adb pull /data/property/persist.sys.usb.config ~/
But the out put of this is either "error: no device" or "permission denied"
I don't know what to do. Here it doesn't go into bootloader. If I want to flash a custom recovery, fastboot commands ain't working, if fastboot shud work I shud enable USB debugging some how, and that too isn't working. If I hold down some random buttons also there is no bootloader mode or anything.
And the options which it gives and which I believe will have the factory reset option also doesn't work bcoz I can't select any option in that.
And yeah...I tried one more thing
adb shell recovery --wipe_data
Which also dint work
I tried
adb shell
Wipe /data
Wipe /system
Wipe /all
I also tried to side load one zip package which could disable the pattern lock
Bt that also dint work.
I tried adb USB and then adb side load <file>
Still no luck.
I might just recommend my friend to throw this phone into the water!
Thanks in advance
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Art Vanderlay said:
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Click to expand...
Click to collapse
Well, that still keeps me in the loop. I have to enable usb debugging & if i have to do that i have to root & so on.
Thanks for the reply. No luck with the thread you linked either.
My Xiaomi Mi 9T just fell and the screen now just flashes black and green. I'm sure that the phone is working but not so sure about the touch screen (can't see anything).
I wanted to access the screen from PC and recover my data but adb devices shows "unauthorized", and obviously I can't see the dialog box on the phone asking for adb authorization.
I already tried rebooting in recovery mode but trying to adb push the key to the device gives an error, and adb shell outputs "error: closed".
Installing a custom recovery afaik requires unlocked bootloader and unlocking it means losing all the data so that's not an option.
Am I 100% screwed or is there anything I didn't think of that could help?
e-ew--w said:
My Xiaomi Mi 9T just fell and the screen now just flashes black and green. I'm sure that the phone is working but not so sure about the touch screen (can't see anything).
I wanted to access the screen from PC and recover my data but adb devices shows "unauthorized", and obviously I can't see the dialog box on the phone asking for adb authorization.
I already tried rebooting in recovery mode but trying to adb push the key to the device gives an error, and adb shell outputs "error: closed".
Installing a custom recovery afaik requires unlocked bootloader and unlocking it means losing all the data so that's not an option.
Am I 100% screwed or is there anything I didn't think of that could help?
Click to expand...
Click to collapse
Unless you unauthorize adb from operating sytem you can't access it from recovery, unless you do adb sideload. One thing is that the screen doesn't display, an other that doesn't react to touches. Anyway adb backup will not backup everything. I recommend you to buy a counterfeit screen for $15 and replace it at least to power on and recover your data.
...