Hi, i m searching for a way to recover the files from a xiaomi note 10 pro, with broken display.
I activated debug usb, an the phone turn on, but when i connect to the computer i cant select the notification to select trasfering files
Any help
Thanks
If Android is either FDE ( Full-disk - Android 4.4 - 6, some devices with Android 7 - 9 ) or FBE ( File-based - Android 10+, some devices with Android 7 - 9 ) encrypted then forget it, because files then are unuseable.
You can check this by means of ADB ( works whether Android is rooted or not )
Code:
adb devices
adb shell "getprop ro.crypto.state"
You'll get the response block for FDE, get the response file for FBE.
Related
Hello xda,
Recently We have heard about ubuntu for phones and tablet now this is the time that the first developer preview has rolled out!
Your device must be unlocked! (you can do thiscalso by installing this preview!)
Supported devices are:
- Galaxy Nexus maguro
- Nexus 4 mako
- Nexus 7grouper
- Nexus 10 Manta
What are the Fuetures at the moment?
Shell and core applications
Connection to the GSM network (on Galaxy Nexus and Nexus 4)
Phone calls and SMS (on Galaxy Nexus and Nexus 4)
Networking via Wifi
Functional camera (front and back)
Device accessible through the Android Developer Bridge tool (adb)
How to get the developer preview image?
Deploying Image to Device
To install the Ubuntu Touch Developer Preview on your device, you will need to execute the command below. Please note, this will wipe the contents of the device so ensure you have made a back-up. To install and get updates,
run the following command: phablet-flash -b The -b performs a full bootstrap on the device.
If the device is already unlocked it will carry on.*If you have already bootstrapped once and want to install a daily just do:
phablet-flash, This will deploy the latest build onto your device. Your device should reboot into the Ubuntu Unity shell.
Note: the files are saved in*Downloads/phablet-flash.
Rolling back to android?
The Ubuntu Touch Preview image is not for everyone and may not suit your current needs (yet). If you wish to roll back to an Android factory image, follow these steps:
- Recall the version that was installed before flashing.
- Download the factory image corresponding to your device's model and version (initial table has links).
- Ensure the device is connected and powered on.
- Extract the downloaded file and cd into the extracted directory.
- run*adb*reboot-bootloaderrun*./flash-all.sh*(use*sudo*if lack of permissions on the workstation don't allow you to talk to the device).
Your device should boot into Android after the process is finished.
For more info see:
https://wiki.ubuntu.com/Touch/Install?action=show&redirect=TouchInstallProcess
Left behind in the comments what you think about Ubuntu Touch
Greetings SK.
Porting Ubuntu Touch:
https://wiki.ubuntu.com/Touch/Porting
Hello
I successfully booted android 4.4 RC2 on surface pro 3 using a method developed for the Sony Vaio tap 11
It is basically the android image from x86 website on a USB drive configured to boot as an EFI USB disk
https://groups.google.com/forum/#!searchin/android-x86/UEFI/android-x86/D85Jq02cLrE/RhTWtOjH3H0J
However, I get stuck at the first android screen asking you to specify the language since the touch screen/keyboard is not working at all, so you cannot click through Android initial setup
Does anyone have the experience to change config files to enable touch screen support
Thanks
Hello, I'm interested in buying Realme 5 Pro, since it only costs 189 USD in my country for the 4GB/128GB combination. I think that's quite a steal.
But, since development were quite slow, I'm looking forward on using GSI thanks to Project Treble. So my question is, like the title, does Realme 5 Pro fully support Treble with being VNDK compliant? VNDK is used to support newer GSI so it's possible to flash Android 10 or R for this device.
to check, you could use the guide here.
or I'll just paste it here.
1) Root your device
2) Open terminal (download from play store)
3) write this
Code:
adb shell cat /system/etc/ld.config.version_identifier.txt \
| grep -A 20 "\[vendor\]"
4) press enter
5) in the output, check [vendor] section and look for
Code:
namespace.default.isolated
if the value is "true", then this device fully support VNDK.
Could anybody check it for me?
Thanks in advance!
Ah, I tried to check it on android terminal ?* I'm quite tired. Will check tomorrow.
Edit.: Realme 5 Pro seems to support treble but not seamless system updates for it has only one partition for system not A and B.
Can someone plz give appropriate answer to this?
I am looking forward to it!
namespace.default.isolated = false
but the file name is /system/etc/ld.config.vndk_lite.txt
What a loss..
Well. Theoretically it doesn't support AB but in fact it completely supports treble and AB. Tried a load of GSI and ROMs till now and they all work AB.
Hi to all.
I have three android devices:
1) a rooted asus me302kl modded with nitrogen os (android 8.1)
2) a stock not rooted moto g5 with android 8.1
3) a stock not rooted xiaomi redmi 9 pro with android 10
When I connect an usb pendrive under the first two devices it is mounted under /storage/[uidd] (being [uidd] replaced by the uid of the pendrive lihe 1234-5678) and I can access and modify its contents from within every app I'm using.
When I connect the same pendrive under the third device (the one with android 10), the pendrive is not mounted under /storage/[uidd] and even if I can use a file browser to navigate it, a lot of apps I'm using do not see the pendrive as available and so became useless.
Is it possible to recreate under android 10 the same behavior of android 8.1 so that when a pendrive is connected it is mounted under /storage/[uidd]? Is it an operating system bug?
Mirror:
Why usb otg pendrive is not mounted under /storage using android 10 as it is when using an android 8.1 device?
Hi to all. I have three android devices: 1) a rooted asus me302kl modded with nitrogen os (android 8.1) 2) a stock not rooted moto g5 with android 8.1 3) a stock not rooted xiaomi redmi 9 pro with android 10 When I connect an usb pendrive under the first two devices it is mounted under...
xiaomi.eu
jwoegerbauer said:
Mirror:
Why usb otg pendrive is not mounted under /storage using android 10 as it is when using an android 8.1 device?
Hi to all. I have three android devices: 1) a rooted asus me302kl modded with nitrogen os (android 8.1) 2) a stock not rooted moto g5 with android 8.1 3) a stock not rooted xiaomi redmi 9 pro with android 10 When I connect an usb pendrive under the first two devices it is mounted under...
xiaomi.eu
Click to expand...
Click to collapse
Is it a problem to do the same question to the OEM too?
Hi everyone,
I've had the nasty surprise of my pattern not being recognized a few days ago. Might be a memory corruption (bit flip from cosmic rays ) or just a very rare bug. Either way, I've won the lottery, because this hasn't happened in 4 years ...
My aim is to unlock the phone without losing internal storage data.
Fortunately, the fingerprint unlock still worked for three days, so I've:
- enabled USB debugging and approved my PC
- backed-up to SD card with Samsung's Smart Switch and did a backup via USB with adb backup (not sure how safe that is)
Currently the fingerprint doesn't work anymore, it forces me to unlock with the pattern. Haven't restarted yet to see if my original pattern will be restored, out of fear that ADB won't work anymore or the backup I did wasn't good enough and I've lost my chance to do a good backup. I'm waiting for my brute-force to finish (more on that below) and some replies from you guys .
My phone is:
Galaxy S8 (Android 9 - firmware G950FXXS5DSJ1 build date Sep 30 2019)
not rooted
My main question is, does this command silently fail after a number of attempts?
adb.exe shell locksettings verify --old xxxxxxx
I've written a script that loads the pattern combinations from file (kudos to delight.im for sharing the list) and saves the command output to file. I've tested it on Android 10 (updated nov 2020) and it throttles after 4 requests - command output is "Request throttled". On my locked phone (Android 9) it appears to never throttle, the output is always "Old password 'xxxxxxx' didn't match".
Found this comment of alecxs on StackOverflow where he says:
there is a 30 seconds timeout after x attempts (timeout may increase) and twrp will silently fail during this waiting period (even with the right pin) - it can even wipe your data (depends on gatekeeper settings and device).
Click to expand...
Click to collapse
Does this apply also to the locksettings verify command?
Can I view the "gatekeeper" settings somewhere?
If you've got any other suggestion on how to unlock the phone or do a better backup before factory reset, please feel free to write!
Thanks a lot!