data recovery – How do I find which app on my phone is putting photos deleted by Google photos in a Recycling Bin? (I can’t find the bin. Phone full.)

Stack Exchange Network


Stack Exchange network consists of 177 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

How to reset “wm size” changes from recovery or unlock android phone with graphic key via keyboard/mouse?

After entering wm size 1920×1080 in terminal I was unable to reset this setting.

Now I have TWRP running and no information about how wm store its parameters in memory. Using adb is not possible (for adb shell wm size reset) as I cannot unlock phone (nor with usb keyboard nor with usb mouse)

So the quiestion is: how to reset changes of wm command or unlock a phone with usb keyboard or mouse (graphical key)?

Can you change recovery mode from simple to full with users working on the server?

Yes you can. However I do prefer to do this during a maintainence window or during off hours with less load. Best bet to start from all lower env to test and go all the way to prod to see if you find any impacts.

From msdn as a note

Note! If you switch to the full recovery model during a bulk operation, bulk operations logging changes from minimal logging to full logging, and vice versa

After changing you also might want to revisit the backup strategy and change as per RTO and RPO

filevault – Is there a Recovery Key for encrypted external drives?

The short answer is no.

When you use FileVault, you are encrypting the entire boot volume, not just a single volume or folder.

If you’re looking for something where you can encrypt a removable volume (i.e. USB drive), take a look at VeraCrypt where it allows you to have both password and keyfile authentication. It’s also cross platform which is definitely a plus.

recovery mode – Bricked phone Huawei P10 – adb and fastboot cannot detect (ubuntu 20.04)

I messed around with my phone (Huawei P10 VTR-L29) and unfortunately bricked it.

what happened

To give you the whole story, I tried to root it, but during the root process I found out that the device is encrypted so I had to “rollback”. That worked fine and my phone was working ok with one issue – I wasn’t able to update firmware via regular system updates. I saw the update, but wasn’t able to download and install – it always ended up with some error.

That made me decide to reinstall the firmware from scratch. I followed general steps but yeah, I messed up.

current status

The only thing I can see now is

Emui Recovery

When I click on download latest version and recovery

Downloading

But after a while it fails:

Failure

And I am stuck 🙁 I can’t get any further .. I tried to connect via ADB (but since I cannot get in the phone to enable USB Debugging (which might be the problem) I am unable to connect (nor ADB neither FASTBOOT can see the device).

I tried to create this file:

/etc/udev/rules.d/51-android.rules 

But when I run

sudo adb kill-server
sudo adb start-server
adb devices

It’s still empty … I can’t even get to the “FACTORY RESET” by pressing and holding POWER + VOL:DOWN for some time; it always brings me back to the Huawei eRecovery

Do you guys have any idea how to fix this?
Or is that phone dead for good?

I don’t care about the data inside.. I would only love to make it work again

wallet recovery – Need help retrieving bitcoin from an old phone

A bitcoin app would not stop your phone from being formatted, so it must be something else.

That said, if you still have bitcoin in a wallet on your old phone, then you should definitely transfer it to a wallet on your new phone (or maybe just recreate your old wallet on your new phone). Just open up the bitcoin wallet, and transfer the funds / export the seed phrase.

Retrieving the bitcoin won’t fix your problem of being unable to format the phone, but you should definitely not sell your phone until you have done so!

recovery mode – Is there a way to save this tablet from bootloop?

I have several generic tablets running Jelly Bean 4.2.2. Recently one of them started bootlooping out of the blue. Unfortunately, the tablets have proprietary, stripped versions of android and recovery. There are no options to data reset in recovery and adb recovery –wipe_data or adb –wipe_data do not work. The tablet in loop can be accessed by adb but services such as activity manager or package manager are not running. Following is the top of logcat for both an operating tablet as well as the looper.

Bootlooper
——— beginning of /dev/log/system
I/RegionTag( 106): —————-running drmservice—————
I/RegionTag( 106): ———-serianno =X2QU82WEPG
I/RegionTag( 106): auto generate serialno,serialno = X2QU82WEPG
I/RegionTag( 106): detect keybox enabled
I/Vold ( 97): Vold 2.1 (the revenge) firing up
D/Vold ( 97): Volume flash state changing -1 (Initializing) -> 0 (No-Media)
E/Vold ( 97): ———get mtd_name is user—
E/Vold ( 97): ————find mtd name is user, num is 9—-
E/Vold ( 97): ———get mtd_name is user—
E/Vold ( 97): ————find mtd name is user, num is 9—-
I/Vold ( 97): Call notifyStateKernel No.1 in the file of VOlume.cpp
D/Vold ( 97): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 97): Volume udisk state changing -1 (Initializing) -> 0 (No-Media)
E/Vold ( 97): Start Misc devices Manager…
D/Vold ( 97): Volume flash state changing 0 (No-Media) -> 1 (Idle-Unmounted)
I/SystemServer( 360): Entered the Android system server!
I/SystemServer( 360): Enabled StrictMode logging for UI Looper
I/SystemServer( 360): Waiting for installd to be ready.
I/SystemServer( 360): Enabled StrictMode logging for WM Looper
I/Installer( 360): connecting…
I/SystemServer( 360): Entropy Mixer
I/SystemServer( 360): Power Manager
I/SystemServer( 360): Activity Manager
I/ActivityManager( 360): Memory class: 64
I/UsageStats( 360): Deleting usage file : usage-20110101
——— beginning of /dev/log/main
D/dalvikvm( 360): GC_CONCURRENT freed 404K, 11% free 4277K/4776K, paused 2ms+2ms, total 12ms
D/dalvikvm( 360): GC_CONCURRENT freed 404K, 11% free 4277K/4776K, paused 1ms+1ms, total 9ms
D/dalvikvm( 360): GC_CONCURRENT freed 404K, 11% free 4277K/4776K, paused 2ms+2ms, total 12ms
D/dalvikvm( 360): GC_CONCURRENT freed 404K, 11% free 4277K/4776K, paused 2ms+2ms, total 12ms
D/dalvikvm( 360): GC_CONCURRENT freed 404K, 11% free 4277K/4776K, paused 2ms+2ms, total 12ms
D/dalvikvm( 360): GC_CONCURRENT freed 404K, 11% free 4277K/4776K, paused 2ms+2ms, total 11ms
D/dalvikvm( 360): GC_CONCURRENT freed 404K, 11% free 4277K/4776K, paused 2ms+2ms, total 12ms

Working tablet
——— beginning of /dev/log/system
I/RegionTag( 106): —————-running drmservice—————
I/RegionTag( 106): ———-serianno =J1VQXV9RYH
I/RegionTag( 106): auto generate serialno,serialno = J1VQXV9RYH
I/RegionTag( 106): detect keybox enabled
I/Vold ( 96): Vold 2.1 (the revenge) firing up
D/Vold ( 96): Volume flash state changing -1 (Initializing) -> 0 (No-Media)
E/Vold ( 96): ———get mtd_name is user—
E/Vold ( 96): ————find mtd name is user, num is 9—-
E/Vold ( 96): ———get mtd_name is user—
E/Vold ( 96): ————find mtd name is user, num is 9—-
I/Vold ( 96): Call notifyStateKernel No.1 in the file of VOlume.cpp
D/Vold ( 96): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 96): Volume udisk state changing -1 (Initializing) -> 0 (No-Media)
E/Vold ( 96): Start Misc devices Manager…
D/Vold ( 96): Volume flash state changing 0 (No-Media) -> 1 (Idle-Unmounted)
I/SystemServer( 370): Entered the Android system server!
I/SystemServer( 370): Waiting for installd to be ready.
I/SystemServer( 370): Enabled StrictMode logging for UI Looper
I/SystemServer( 370): Enabled StrictMode logging for WM Looper
I/Installer( 370): connecting…
I/SystemServer( 370): Entropy Mixer
I/SystemServer( 370): Power Manager
I/SystemServer( 370): Activity Manager
I/ActivityManager( 370): Memory class: 64
I/SystemServer( 370): Display Manager
I/ActivityManager( 370): Enabled StrictMode logging for AThread’s Looper
I/SystemServer( 370): Telephony Registry
I/SystemServer( 370): Scheduling Policy
I/DisplayManagerService( 370): Display device added: DisplayDeviceInfo{“Built-in Screen”: 600 x 1024, 57.727 fps, density 160, 177.2093 x 168.89351 dpi, touch INTERNAL, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, rotation 0, type BUILT_IN, address null}
I/SystemServer( 370): Package Manager
I/PackageManager( 370): Need to read from backup settings file
W/PackageManager( 370): Cleaning up settings file /data/system/packages.xml

How Data Recovery Software Work?

Have you ever accidentally deleted a file on your computer from the file you jump into the computer drive and formatted the memory card from the device? Or don’t you find your valuable file or malware attacked by your system? Fortunately, lost files and folders can often be recovered using data recovery software.

.

recovery mode – Data recover with broken screen

yesterday my beloved OnePlus 3T fell and the screen cracked 🙁
At first half of it was still usable and visible, shame on me for not recovering the data I needed at that time. now the upper half is still usable but completely black, also the battery died without me noticing so it turned off.

Now I’m stuck with the following situation: phone is turned on, but the pin is preventing me from logging in (I can’t type the pin blindly as the bottom half of the screen doesn’t get touch inputs), the pc doesn’t recognize the phone beyond the driver “disk”, so sending commands via adb it’s not an option.

I tried booting in recovery mode with volume down+power and I think it got booted in recovery, but I don’t remember If I can use the buttons to navigate it. I pressed volume down 3 times to move to english, pressed power to select english, pressed power to select “install from adb”, pressed power to select “Ok”. at this point I expected the phone to be visible (assuming everything is set up correctly on the pc) when running “adb devices” on cmd, but it doesn’t. can anyone confirm that these steps are correct?

I’ll later try an otg cable and connect mouse/keyboard as a last resort.

I’m running out of ideas, so if anyone has any idea on how to recover files (don’t care about contacts and stuff) from the phone is more than welcome.