Blocked device - Xperia Z1 Q&A, Help & Troubleshooting

Hi
it's possible to download data from Z1 if device is blocked (user password, not pin).?
Thanks
Greetings

I can think of two ways...
Adb interface on PC using adb pull whilst in recovery or booted into system, if you previously enabled adb debugging before.
Backup data partition in recovery like TWRP, then wipe everything and restore it, I guess it might work.
Other than that, you can probably google or search around for more options.

Related

[solved]edit nandroid backup to posthumously enable usb debugging ?

Greetings!
tldr: USB debugging is probably not activated. is there still a way to get a bootlog via adb ?
edited tldr: can I (hex)edit a Nandroid backup to enable USB debugging, if I also have a nandroid of a clean install with USB debugging enabled for comparison ?
long story:
I'm running
HB3_Franzy 12 RC the final with devil kernel and have been for a while now. Yesterday, for some unknown reason, my phone suddenly decided to reboot. Now it hangs at the bootanimation.
I tried wiping cache and dalvik cache ;both with and without flashing the rom over the existing installation; reboot then went through "optimizing apps" and then hung at "updating android - starting apps"
I stupidly did not activate USB Debugging nor put the installed titanium backup to good use. You may flame and call me names, if you also supply any hint on how to proceed
Before I swallow the pill and wipe user data for a clean reinstall, I want to find out what happens, both as a last attempt at saving my data and to prevent this from occuring again.
Is there a way to access the bootlog via adb, even withoutt having activated USB debugging in the develloper options ? Are there any other ways to backup my data and reassemble it into a fresh reinstall ?
EDIT:
I did an Nandroid backup via recovery and, having that to get back, went on to factory reset. Phone boots, so no unrecoverable bricking. That's something. In the clean system, I can enable USB debugging and successfully adb logcat (after authorizing my pc on the phone). Restoring the backup, expectedly, set me back to where I started. I'm thinking it might be possible to edit (or copy from a nandroid of the clean, working system) the relevant configuration files in the broken system's Nandroid. Has anyone tried this before and knows which files are responsible ?
you can extract the apps via Titanium Backup... well atleast should titanium backup do it...
Actually it isnt really working for me: whenever i try to extract the apps out of the backup, titanium doesnt show me any apps to restore...
if you got the same error, you can try downloading Nandroid manager, install the app, you'd like to restore, via nandroid manager and restore the user data from the datadata.yaffs2.img... Its a little workaround, but it works fine for me...
adb enabled, more work needed
In case anyone finds this thread, looking for the solution: It is possible. As I'm not sure what the forum policy regarding hacks with potential evil application ist, I'll just point you to look into the files
data/property/persist.sys.root_access
data/property/persist.sys.usb.config
data/misc/adb/adb_keys
instead of posting step-by-step instructions.

[Q] Android Data Recovery no access to phone memory/SD

hi there,
after unlocking the phone I missed to see that all data would be lost. Obviously the ROM was set back to factory.
Two applications I found to recover the data:
1. 7-Data Android Recovery (can't even find the phone)
2. Android Data Recovery (finds the phone, phone tells me that superuser rights are granted everything ok, but then: "unable to get device storage information")
I would love to recover some data like photos, applications or contacts, before flashing another ROM.
ADB Drivers, fastboot etc is installed. Motorola Device Manager is installed. All Drivers have been successfully placed.
The Phone work works properly when plugged to PC and also USB Debugging is enabled.
Why do my data recovery programs don't access the phone?
TeamWin Recovery 2.7 has been installed, furnice Kernel 1.1.2 as well as SuperSU 2.4. has been installed.
maybe those are impedient`?
nordcupp_motoG said:
I would love to recover some data like photos, applications or contacts, before flashing another ROM.
Click to expand...
Click to collapse
Unlocking the phone will perform a factory reset. That means, everything that does not reside in your external sdcard is permanently lost.
If your device is properly set up with a google account, all your contacts, bookmarks,emails etc. will be restored. That means that everything you can access with your browser, like email, Chrome-bookmarks, are in sync with your device. If you allow google to backup your settings it will also try to restore your apps, but this is, and was, very unreliable.
If you must, you can manually backup your contacts with Contacts Backup Ultimate.
As for applications, nothing beats Titanium Backup. Ugly as hell but the most powerfull backup solution there is.
And last but not least, copy your photos, music, movies etc to your external sdcard.
All this has of course to be done before whiping your device.
P.S. Please update your recovery to the latest TWRP.
external sd may follow soon.
team win recovery that version is offically compatible to moto G14
so I chose that one.
thanks for the tipp. should have seen that earlier.
darryer said:
Titanium Backup is a good tool for Android. Or you can use Tenorshare This is a pro tool for Android data, it can recover all lost data like contacts, sms, call history, photos etc, even you have no backup.
Click to expand...
Click to collapse
I did use that tool as well as 7-Data Recovery and another one. None of them capable to access the phone.
Tenoshore told me after connecting the phone to the app and choosing what data to save, that the storage information is not accessible.
No clue as to how that happens.
nordcupp_motoG said:
No clue as to how that happens.
Click to expand...
Click to collapse
If you connect your device with usb-debugging enabled in the developer options, does a dialog pop up, presenting a RSA fingerprint, asking to allow usb-debugging? Allowing this is imperative.
that was done properly... the application does ask for this before you can chose what to save.
nordcupp_motoG said:
that was done properly... the application does ask for this before you can chose what to save.
Click to expand...
Click to collapse
What is the output of "adb devices" after you connect your device?
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ZX1D22HLNC unauthorized
C:\adb>
but usb tunnel is working right now...
usb debugging is enabled...
adb should be up to date...
mmmh every try delivers different ansers:
second time said: devices attached.
third time said: daemon failed to start
and adb server didnt ack
ok, there is a well known issue with some devices and adb
there is an adb fix for it, but I couldn't get it to work so far.
nordcupp_motoG said:
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ZX1D22HLNC unauthorized
Click to expand...
Click to collapse
Maybe this helps
http://stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized
thank you.
I installed the Android SDK Studio and used the ADB from there.
ADB now works properly.
USB Tunnel sucks hard still though.
The connection shows up to be established and skype and whats app do work,
but playstore and chrome refuse to work also no regular app can reach the net
like wikidroyd & co...
nordcupp_motoG said:
playstore and chrome refuse to work also no regular app can reach the net
Click to expand...
Click to collapse
Maybe manually change dns in wifi settings will help.
manually change it where?
I don't see any menu for this in usb tunnel...
guess I gonna get a USB wifi next week.
nordcupp_motoG said:
manually change it where?
I don't see any menu for this in usb tunnel...
guess I gonna get a USB wifi next week.
Click to expand...
Click to collapse
Not on the mobile, on your pc. Change it to e.g. 8.8.8.8

Stuck on lockscreen without ability to type in password

Samsung Galaxy S10
Android 10
TWRP
Rooted with Magisk
I just put my phone in ultra power saving mode, but unfortunately i cant unlock the lockscreen because i disabled samsung keyboard and now there is no keyboard where i can type in my password, and since i am in power saving mode it also disabled my other keyboards
So i tried removing the screenlock by deleting the locksetting files in /data/sys/, but since my phone is encrypted i can only see nonsensical filenames, so i dont know which files to delete
Can i safely delete every file there ?
I dont want to factory reset my device because i have a lot of important data on it
I already tried to remove the lock using https://findmymobile.samsung.com/, but it says that that function is disabled on my phone
I have no physical keyboard that i can plugin in into my phone
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
Can i safely delete the other files too ?
Because i dont know which encrypted filenames correlate to the files that i have to delete
EDIT: Thanks, i solved it by connecting a USB Keyboard to my phone using an USB-OTG connector included in the package of my Galaxy S10
If the device supports OTG, you can try connecting a full size PC USB keyboard via OTG.
I went through similar situation when I changed screen render resolution to less than half, then accidentally locked the phone, the keyboard and Screen-Guard were rendered at low resolution, and lock screen was not interactable.
The only way to restore that without prior arrangements was to flash stock Samsung ROM, via PC, with carefully choosing options to not format internal storage and data partitions.
If you have custom recovery, you could enable insecure USB debugging options in build.prop that always allows USB debugging via ADB, then re-install Samsung keyboard, or find some other solution with ADB.
If you have custom/twrp recovery, I'd say connect to PC in recovery mode and copy to PC all important files from /sdcard just in case.
Old Android versions like Android-5 had build.prop files where you could force USB debugging for development uses, that would Allow ADB even the device was locked.
I am not aware if newer Android versions allow that.
Once you get to TWRP, you need to use
Bash:
vi /system/build.prop
Or just
Bash:
echo "text-lines" >> /system/build.prop
To the build.prop file
in command line and enable debugging mode.
The build.prop lines :
Forced USB debugging
Harshiv989 said:
Old Android versions like Android-5 had build.prop files where you could force USB debugging for development uses, that would Allow ADB even the device was locked.
I am not aware if newer Android versions allow that.
Once you get to TWRP, you need to use
Bash:
vi /system/build.prop
Or just
Bash:
echo "text-lines" >> /system/build.prop
To the build.prop file
in command line and enable debugging mode.
Click to expand...
Click to collapse
I cant access /system/ from twrp, it just says that there is not such folder despite it being there, but i think that i have enabled debugging anyways and i already made a backup, which is somehow useless because of the encryption
Harshiv989 said:
If the device supports OTG, you can try connecting a full size PC USB keyboard via OTG.
Click to expand...
Click to collapse
I read in several other threads that in ultra-power-saving mode, android only allows USB devices to charge the phone, and i have no keyboard that i can plug in anyways, i cant buy one because everything is locked down (COVID)
The only way to restore that without prior arrangements was to flash stock Samsung ROM, via PC, with carefully choosing options to not format internal storage and data partitions.
Click to expand...
Click to collapse
As far as i know i cant just flash stock firmware without having to wipe my data
If you have custom recovery, you could enable insecure USB debugging options in build.prop that always allows USB debugging via ADB, then re-install Samsung keyboard, or find some other solution with ADB.
Click to expand...
Click to collapse
How could i reinstall samsung keyboard ? I have no access to the pm command in the twrp shell, and the files are encrypted anyways
Another related thing: https://forum.xda-developers.com/t/...-galaxy-s10-e-5g-exynos.4180287/post-84456927
I see that with combination of FBE, UPSM and disabled Samsung keyboard, you have put yourself in far more idiotically constrained situation than I had, as well as what Samsung devs imagined was possible.
With encrypted file system, you wouldn't even be able to flash an update.zip that includes a build.prop (from your stock ROM)with forced ADB enable-ment lines from recovery I guess. ( this is different than doing it from developer options, allows adb access without unlocking device )
I would still suggest you to charge your phone 100% and attempt a HW external keyboard method,
I am willing to bet Samsung was not stupid enough to block USB I/O devices at kernel level in UPSM.
You don't necessarily need to buy a new keyboard, just find one that connects to PCs via USB, wire or wireless dongle, either should work (no RGB/W backlights in keyboard if wired, we want a low powered keyboard, smaller if possible), from any other computer geek you know, and an OTG connector.
I have always been able to flash the stock ROM that only rewrites /system partition, and leave /data mostly untouched, have done it numerous times with odin, with new devices, you should be able to do that.
The device encryption is a hurdle which severely limits your options.
Also, my UPSM allows both wifi, and Bluetooth, if you had either of them ON, you could use a Bluetooth keyboard or debugging via wifi, if Bluetooth keyboard was previously paired(it auto connects), or wifi debug feature was set up already , ADB access might be possible, though wifi ADB is more secure, unlikely to work in locked screen guard state.
funny the most command and most upvoted answer for this issue on the internet for the average joe (not xda) is to reset the mobile.. disgusting reallly.. i also cannot imagine do the massive reconfiguration for this trivial issue. just had the gboard disappear and took a really short time to plug PC keyboard and an adapter i always have with me.
plug and play to the rescue...

Sort of a bootloop after Android 11 update

Hello guys,
I hope someone can help me with this problem...
So the thing is - yesterday I finally got OneUI 3 and Android 11 update (yay?). But ofcourse as soon as the phone rebooted and optimised all the apps and came back to main screen it rebooted after a minute or so...everytime. As soon as I enter my pin and unlock the phone it reboots after a short period.
The same problem happened when I de-bloated the phone a while ago via ADB - but I then enabled back all the apps except facebook and some "safe to debloat apps" which were not even system apps and it has since worked for almost a year. But here we go again....
I even "re enabled/installed" all the apps I could list in ADB ( so basically all the apps on the phone) and then went to wipe cache - but still no go.
I am also wondering if there is a posibility to somehow mount storage just to copy some files to my computer (which are important, and my latest backup is around a month old) and then I'll gladly do a a factory reset - no problem.
Any help would be appreciated, thanks!
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
TacoDeMuerte said:
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
Click to expand...
Click to collapse
Hello, thanks for the reply and helping out.
But all the commands and stuff is kinda useless because the phone reboots sooner than in 30 seconds after getting to the main screen. When I boot to recovery the storage doesn't get mounted.......
And I would've had TWRP but the phone is still under warranty so that's a shame, because on my backup phone I have it (and so did on all the previous ones) and it would be great. But IIRC if I install TWRP now, the phone needs to be wiped.
FFS samsung, what is this....because I now read a couple threads and posts on social media people having exactly same problem, and some didn't do anything with ADB prior to update. shame...

Date recovery no root advice?

I read many posts and articles the past few hours and realized a few things, would you correct me if they are wrong please.
My phone:
Pixel 4XL, adb reboot recovery gives "no command" it would seem it might have been rooted at some point before I bought it, but now the bootloader is locked and no custom recovery is on it.
Can I not recover data without root?
Saw few articles mention `adb pull' and `dd` to copy block device, which I can't do with no root.
Is it possible to just install busybox with adb and be able to copy block device?
As per this article https://www.andreafortuna.org/2018/...imaging-android-file-system-using-adb-and-dd/
I might have to wait a bit for TWRP as I did upgrade to Android 11 and it seems it is only supports Android 10 at the moment.
In order to put TWRP on my phone I probably need to unlock the bootloader and would that mean lose all user data? Then I really have no hopes of recovering the audio file I'm looking for as then I couldn't decrypt it?
I know the file's mount point and can figure out which block device it was on, but wouldn't the encryption get lost if android was wiped?
Is there a way to get TWRP without factory restore phone, or busybox or something that will help get block devices out.
Someone mentioned that these dm block devices are decrypted, are they? I will attach a screen shot with list of my block devs.
Thanks for any help or pointer, I can't be destroying this phone as I have money on it and other stuff needed for traveling, so I don't even feel like trying to install busybox to see if adb pull would work, and others mentioned if trying to get block dev off the phone while partition is mounted might lose some data, so they advised using TWRP while partition is unmounted and then copy it's image.
I also found this but I would need root, he mentions 'temporary root' is that even a thing?
Extract Android Userdata Partition for Recovery and Forensics - Root101 | Fundamentals of Linux Administration
Open Source and Linux. Guides and Ideas for Designing Highly Available and Scalable Production Environments
www.root101.net
@GogoAkira - Your long, rambling post is very confusing, and you do not clearly state what it is you are trying to do or the current state of your phone. I want to start by saying that if you have not done so already, you need to be on the very latest version of the adb/fastboot binaries. If the phone is working fine and you can access all your files, there are some non-root ways to back up almost all of your data, but you're NOT going to get anything near a nandroid backup. If your phone is working fine on 11 (why would you not be on 12?) you can also enable usb debugging from within the developer options menu and then use it from the RECOVERY mode. You cannot use adb from your PC without first enabling adb debugging. I say this because you claim "adb reboot recovery" won't work. Of course it won't work. You cannot access adb in the FASTBOOT mode. Probably the first thing you need to confirm is that you have enabled USB DEBUGGING and whether or not your ALLOW OEM UNLOCKING toggle can be set to yes. Whether or not you can do this will tell us alot. If it is greyed out in the off position your bootloader is a) currently locked, and b) probably will not be able to be unlocked. Knowing that, then clearly state what it is you are trying to accomplish and people will try to help.

Categories

Resources