[Critical] [Q] Android 5.0 Lollipop, Random Corrupted Files - Nexus 5 Q&A, Help & Troubleshooting

Clean flashed Lollipop from scratch, flashed TWRP 2.8.1.0 with SuperSU 2.16, ElementalX 2.03, root and recovery working good, but some files on /sdcard/ seems to behave differently under TWRP file manager and when booted into system.
For ex, in the screenshot below from ES File Explorer:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP and airdroid folders are not readable neither in Root Explorer/ES, nor in MTP mode connected to PC, though these folders show fine in TWRP file manager, also i can't read any of the files (everything shows just 4KB) and neither delete anything without booting into recovery file manager. Is this some permissions conflict, how to fix it?

anyone? The problem seems to be application specific as any file i copy through adb from my pc is readable everywhere.

Related

Possibly bricked Acer Iconia Tab 8 (A1-840FHD)

My cousing handed me over this device asking for help. Checking it out it seems either the internal storage (or storage controller) went bad or it got corrupted somehow. I tried loading the ROM over the external SD card but it won't mount. The errors happen with both custom and stock recovery, so I believe the storage controller went caput.
In order to have more options I loaded a custom recovery with fastboot (which worked) but it won't do anything regarding storage (won't format, won't mount), be it internal or external. My cousing said this happened when he was downloading a map to use on a GPS app.
Given the popularity of this device I also did not find all img files (specially system) that I could load with fastboot.
This is what it looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this something fixable or is this e-waste?
Thanks!

Restoring TA Partition Error: adb error: connect failed: closed

Hi, I am trying to restore my TA Partition on my XPERIA XZ but everytime I attempt to with ADB I get the following error? Am I doing something wrong?
Thank you for your support.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try connecting your device when booting twrp and windows explorer instead of adb push, it's far easier than having to work with command-line tools. if you really want to use adb, your phone is in the wrong mode. you can't push a file on it in sideload mode (as far as i know, correct me if i'm wrong) but only apply a zip file. to have it "long-term" on the device, you have to enable mtp mode, either by choosing "transfer files" from the notification slider when you can normally boot to your rom or as i said before by just booting twrp (fastboot.exe boot twrp.img)

Titanium Backup doesn't see old backups

I've made following actions:
1. Backed up all user apps
2. Copied TitaniumBackup folder to my pc
3. Wiped all data from my device
4. Flashed zip with new rom
5. Flashed magisk
6. Flashed gapps
7. Installed busybox from magisk manager, rebooted device
8. Installed Titanium Backup from play store
9. Copied TitaniumBackup folder back to internal sdcard
10. Made sure TitaniumBackup folder is selected in the app
The only warning I get is about 16.0:MAGISKSU possibly not working reliably.
In the app I can see there are all the gz.zip and txt files present. The only backup it sees is one I made on the new rom to make sure titanium backup is working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Data recovering apps (with root) can't find internal memory for recovering data

Hi, i have Mi 9T with lineageOS 17.1, that i deleted accidentally a folder with pictures, but as precaution, i have a few data recovering apps that use root and can do a proper "full" scan for recovery, instead of just "deleted" recovery.
they use root, but they don't see the partition where the user data is, and find nothing after scan. tried 3 apps that use root for a proper recovery, all result the same. nothing is found to recover. some don't let select where to scan, but the ones that have this option, only show this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't know if is a magisk problem, or if the "list" of partitions that is show to an root app is configurable, or i need to mount something to make it able to see the user data (i think /storage)
any help appreciated

ADB PULL ERROR

I am facing with error when trying to pull files from internal storage from AVD . I have rooted my device but even can not access some application data folder. Tried multiple explorers, all showing app such as youtube applications folder but target app folder not showing up. Any missing ?
Using ADB with a rooted mobile, a common method to pull files only accessible to root ( like the ones in /data/data ) is moving those files with root to the SD-card attached to the mobile ( which is formated with FAT32 and thus doesn't have file permission restrictions ) and then adb pull those files from the SD-card.
I did not get you. Can you please explain clearly ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See this page to see the difference between rooted, rootable and non-rootable.

Categories

Resources