Hi All,
MY OPO is stuck in lockscreen and I cant unlock it because the screen freezes. Below are all the details/observations till now. Your help is appreciated in advance
1) How my OPO got stuck at Lock screen?
- I enable privacy guard for google play services and enabled NOT WAKE UP henceforth
2) What happened after that?
- OPO reboots to the lock screen and the screen freezes there. Touch doesnt work but phone reboots and is in an infinite loop
P.S - I can access RECOVERY MODE and FASTBOOT mode with no problems
3) What do I want to do with my OPO now?
- I want to take a backup of my data before I factory reset it.
4) What did I try till now?
- I installed adb drivers and android sdk
- When I run the command "ADB DEVICES" in CMD, i see the "UNAUTHORIZED" response
5) The solution I googled and found out?
- http://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300
- the above URL explains the detailed solution but needs the lockscreen to be unlocked and enable access
As i cannot go past the lockscreen, the solution doesnt work for me. Is there any way i can enable it?
Once it is enabled i will use ADB PULL command to backup my photos etc before FACTORY RESET
Use TWRP to backup your photos.
Did you try connecting your device in recovery mode with your PC? May be you can access the internal memory. This feature is available on Custom recovery,you should try this for your stock recovery.
Try thishttp://android.stackexchange.com/questions/134987/disable-cyanogen-privacy-guard-from-shell first
In order to install TWRP, i have to unlock bootloader which will wipe all data
Yes i did connect my phone to PC in stock recovery, but cannot access my internal memory
Thanks for this, but only people with TWRP, CWM or PHIL'Z recovery can delete the appops.xml
I am on stock recovery. is there any way i can do this?
Boot recovery
Connect device to computer
Open command prompt
Adb shell
cd data /system
ls
-rm appops.xml
Related
Hey All,
My Dad's Xoom died over the weekend - 13months after purchase so is not covered by the warranty. He was browsing a site, it came up with a "Internet is not responding - do you want to continue to wait" message and he clicked Wait - after a second the tablet knocked off. It will not come on by pressing Power and only turns on by pressing Power and Vol +
It gets past the Motorolo logo screen and the device starts the boot animation, about 20 seconds into this it freezes and reboots - this continues in a loop. It's been GEDified and was running the last OTA update 4.1.2 - no root etc.
I can get into the stock recovery and performed a factory reset - but the same thing happens. I've also tried Update From USB with an OTG cable but the screen just shows Choose a package to install and under it has /sdcard but nothing else. I have a dummy zip on both the Flash disk and SD card so it's not reading either.
I've also tried to perform update via ADB - when I select it and connect to a PC (Win 7 32bit) it tries to install drivers but I see In Computer Management that it shows under Unknown. ADB Devices returns List of devices message but nothing under it.
I've also selected the fastboot command at boot, tried fastboot devices and the command does see the Xoom.
So my questions
1) Anyone seen anything like this issue before and know how to fix it?
2) Is it best to try to reinstall the ROM? If so, how do you suggest I can see it with ADB?
3) As I have Fastboot command, could I try to install CWM and see if that sees a ZIP on the sdcard - so I can install a new ROM.
Any help much appreciated :good:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
claned said:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
Click to expand...
Click to collapse
So just to add to this, I found the stock recovery.img, boot.img, userdata.img and system.img and used the fastboot commands to send all to the motorola - all succeeded without error....still the same problem though.
I installed RSD lite and tried a few SBF files but I'm getting an INI error - off to google possible solutions to that now
stock, non-rooted Android 5.0
Phone is soft bricked, turns on and freezes on the yellow Sprint splash screen.
I need to recover some files on internal storage.
I know that I could install ADB and use the adb pull command to transfer files to a PC, but I am under the impression that USB debugging needed to be turned on, it is not.
Other options? Thank you.
Actually, it turns out that usb debugging was enabled.
while stuck in the bootloop at the sprint screen I use adb.exe with command prompt:
adb devices
device is recognized
adb pull /sdcard c:/recovered_files
"device unauthorized"
have to figure out how to get around the authorization
Also tried to flash a custom recovery (Philz and TWRP) Odin says it was successful every time, then it boots into and sticks at the Sprint screen. I reboot (remove battery) and it's still the stock recovery
Edit: fixed it. Learned that "install-recovery.sh" resets the recovery at each OS boot, so just needed to turn off "auto-reboot" in Odin. Once I had Philz recovery installed, used adb to pull all the files I needed.
Hi,'
I think I disabled google app on my nexus 5 (stock android) and since then my phone is stuck in boot loop. (My phone does not go past logo of marshmallow rolls or message saying starting apps 10 of 10). I have very important data that is not yet backed up and I need them to be recovered.
From various threads, I did following in recovery mode
1. Wipe cache option under recovery menu - as it was mentioned, that it would not delete any user data on my sdcard. (No help, still stuck with boot loop)
2. In recovery mode - there was an option to mount phone memory and I did that. My phone shows a message at the bottom of the screen that it is successfully mounted. But I am not familiar how to proceed further or to recover data from my phone.
My phone is running stock android and I think I have not disabled USB debugging. I am not familiar about ADB, but can follow your guidelines and execute them. When I connect my phone to windows laptop, I see my laptop trying to install the MTP device driver, but fails saying unable to find the driver.
I need to recover my data and Any help is greatly appreciated.
Is your bootloader unlocked? I'm guessing not.
Sent from my Nexus 5X using XDA Free mobile app
If the bootloader is unlocked, you could flash twrp and then mount the data partition from twrp. If the bootloader is not unlocked, you could try pulling the data from the phone using adb commands. Was debugging enabled in the rom?
I have not unlocked my boot loader. Is there a guide to use adb with stock android?
Only if you enabled debugging in developer options.
Today, I installed 15sec ADB installer and booted my device in to recovery mode by pressing power and volume keys.
Then under recovery menu there was an option called - Mount / System. I selected it by pressing power key and from ADB ran adb devices.
No devices was listed, when I ran ADB devices.
But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the pacakge you want to apply to the device with adb sideload filename".
Now, when I execute ADB devices in my PC cmd prompt, I see my device with its serial number.
then I tried to use ADB Pull /sdcard/ to recover files from PC command prompt. But I got a message - saying error closed.
Am I doing the right things? Can you guys guide me to recover files from this point.
My bootloader version is HHZ20h. Product - Hammerhead.
I noticed from below link a user has had luck with sideloading a launcher. Has anyone here tried it ? will it affect my data on phone?
https://code.google.com/p/android/issues/detail?id=64773#c22
Any guide to sideload google search app in recovery mode?
Have you considered side loading the OTA from Google? https://developers.google.com/android/nexus/ota Directions are on the site.
When you get to this point
(But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the package you want to apply to the device with adb sideload filename".), you send the ota zip. (Adb sideload <name of zip> ). You have to make sure the zip file is in the folder with adb files.
Sent from my Nexus 9 using Tapatalk
I tried to install OTA update and did the reboot. But it did not help.
Can anyone provide me a launcher that I can sideload in recovery mode? Reading from various threads, I think my phone is in this state because I disabled the google app, which is also the launcher.
Thank you
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
santi1993 said:
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
Click to expand...
Click to collapse
How to perform this flash without wiping my user data? Any guide for it?
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
audit13 said:
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
Click to expand...
Click to collapse
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
smartey said:
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
Click to expand...
Click to collapse
Boot ur phone in fastboot mode (From power off to vol down + power), then connect it to the pc and install latest_google_drivers for nexus devices, ull need to manually install them, after that ur fastboot will recognize ur device.
From that type fastboot devices, if u see ur device connected u simply need to get into the commands that the other user gave to you, i u are lucky ur device will boot.
if u had unlocked bootloader the thing was easy as installing twrp 3.0.2.0 and backup all ur data via MTP
Hey guys, in a little bit of a dilemma.
My s6, for some reason, cannot pass the flashing "Samsung" logo when booting it up. I have not rooted this phone, nor have I installed a custom recovery or rom. This phone is stock as it gets.
And I need to recover the photos off the phone. Issue is, I thought it would be simple as going into recovery mode and doing adb pull/sdcard/DCIM/Camera or something like that.
BUT I do not have USB debugging enabled!!! Never even turned on developer settings.
I tried to get into bootloader and use fastboot, but fastboot devices shows up with nothing. adb commands do not work, except when I press "install update from ADB", then only the very basic ADB commands work such as adb reboot, adb sideload etc.
So I am not sure what to do from here. Fastboot is not working (I have installed the Samsung drivers from the official webpage, but I haven't restarted my computer so i will try that).
Please help me to recover these photos :crying::crying::crying:
Hi,
If Download mode is working, flash TWRP recovery with Odin.
Go to Mount, select Data partition > Enable MTP and access files from PC.
Recover your data, then flash fresh new ROM https://forum.xda-developers.com/galaxy-s6/general/guide-tutorial-howto-samsung-galaxy-s6-t4108425
For some reason, when I go to my fastboot mode, it shows blank screen. Any idea how i can get back to the default fastboot mode screen which usually shows device state, etc. My phone boots up fine , its OEM unlocked but without fastboot im unable to flash custom recovery or rom or do anything to be honest. One plust 6T. Please help
crmemaster said:
For some reason, when I go to my fastboot mode, it shows blank screen. Any idea how i can get back to the default fastboot mode screen which usually shows device state, etc. My phone boots up fine , its OEM unlocked but without fastboot im unable to flash custom recovery or rom or do anything to be honest. One plust 6T. Please help
Click to expand...
Click to collapse
with normal boot, i can access adb commands, its just that fastboot mode is blank and hence unable to access commands. Ive installed all possible drivers, i think the kernel is broken. Any possible way to fix this?
crmemaster said:
with normal boot, i can access adb commands, its just that fastboot mode is blank and hence unable to access commands. Ive installed all possible drivers, i think the kernel is broken. Any possible way to fix this?
Click to expand...
Click to collapse
Is developer options and usb debugging enabled in your phones settings? Also no screen lock set? If so if you have another Android device that's also rooted with magisk you can use Osm0sis and Surge's fastboot/adb magisk module, (a quick search in magisk will pull it up) Install it on your other device and use an otg cable ($5 online or make one yourself) and using termux app from "other phone" with connected otg & magisk root type: su (hit enter) grant root once it pops up then type: adb reboot bootloader then tick the pop up on phone you are trying to boot recovery on when it pops up. Then type: fastboot boot twrp_3.4.0-9-11.img (hit enter) Just make sure you put your TWRP recovery.img in correct directory on phone you you're using termux app on with otg and fastboot/adb module to boot the phone you are trying to boot to recovery.
Using root explorer directory in termux is: /data/data/com.termux/files/home/
place your TWRP_3.4.0-9-11.img ,, which ever TWRP image you are trying to boot in that directory...
Hope this makes sense. I don't use Windows and haven't for many years now. I've unlocked bootloader's and rooted many devices using another Android device this way now for years. Super easy! Not sure why you would be getting a black screen. Have you searched for solution to this? I would definitely search , a lot about the black screen situation.. Make sure you have a charged battery too. Sounds stupid I know but it's possible you are at 0%.. Hope this helps...
(Edit)