sd-card file-systems keeps breaking when I write to it - General Questions and Answers

EvolutionX_4.6_ginkgo-10.0-20200819-0341-OFFICIAL
(same problems with crDroid; stock ROM (Pie) works fine)
Redmi Note 8
Clean install: Format & wipe
After adopting SD and migrating data I'm having some problems. Tested with 2x 128GB cards and 1x 64GB cards, same problems every time. Also tried fresh re-installs with format & wipe, same problems.
When copying files to "/sdcard" (aka "/mnt/runtime/full/emulated", aka "/storage/emulated/0/") I keep getting corrupted directories; directories that I can't write to, I can't delete, I can't move/rename, I can't change permissions, I can't change owner/group. Every time this happens, "df" shows more space being used, but files can't be found.
Problem happens when copying files to adopted storage via "adb push", tar, zip, cpio, and MTP.
I've also tried extracting from a zip file using a GUI app, and also deleting borked directories with a GUI app: No joy.
This is a major problem. This is making it impossible to load up the SD card with the files I need.
Just trying to "adb push" a TitaniumBackup directory to the new phone, and it gets to about 70-80% and then dies with this error:
Code:
adb: error: failed to copy 'TitaniumBackup/com.android.theme.font.xxxx-xxxxxx.apk.gz' to '/sdcard/test/com.android.theme.font.xxxx-xxxxxx.apk.gz': remote couldn't create file: Invalid argument
It keeps dying at slightly different points, but every time it dies it corrupts the directory that I'm copying into; I can't delete it, I can't move/rename it, I can't add anything to it, etc. "df" shows that space is being consumed, but there's no files. The sdcard just keeps getting corrupted, every time.
Code:
rm -rfv test*
rm: test: Directory not empty
rm: test2: Directory not empty
rm: test3: Directory not empty
Code:
find test*
test
test2
test3
Code:
mv test xxx
mv: bad 'test': No such file or directory
Code:
stat test
File: test
Size: 516096 Blocks: 864 IO Blocks: 512 directory
Device: 1fh/31d Inode: 11108 Links: 2
Access: (0771/drwxrwx--x) Uid: ( 0/ root) Gid: ( 1015/sdcard_rw)
Access: 2020-09-03 20:45:01.248588627 +1200
Modify: 2020-09-03 20:50:58.918624257 +1200
Change: 2020-09-03 20:50:58.918624257 +1200
This does nothing:
Code:
find . -inum 11108 -delete
Any ideas?
Linux localhost 4.14.193-QuicksilveR™ #1 SMP PREEMPT Wed Aug 19 05:58:46 CEST 2020 aarch64

Screenshots, error messages while trying to use a GUI tool to extract a zip file.

This is the only type of log entry that I'm seeing consistently when there's a failure (via "adb push"), but I'm also seeing a lot of them when there's no failure:
Code:
[ 09-04 12:27:30.567 891: 891 W//system/bin/adbd ]
type=1400 audit(0.0:26467): avc: denied { search } for comm=73796E6320737663203139 name="oem" dev="mmcblk0p86" ino=45 scontext=u:r:adbd:s0 tcontext=u:object_r:oemfs:s0 tclass=dir permissive=0
And after some testing, it's really trashing the file-system.
Code:
$ du -hcs .
487M .
487M total
df -h .
Filesystem Size Used Avail Use% Mounted on
/mnt/expand/b780ec4a-2dac-4b9e-bf9e-a044afdcad6b/media 118G 61G 57G 52% /storage/emulated

Just me? Any ideas? This is a new phone, and it's really not usable until I get this sorted out.
Code:
pwd
/sdcard
find . \! -type d
<no output>
du -hcs .
4.7M .
4.7M total
df -h .
Filesystem Size Used Avail Use% Mounted on
/mnt/expand/b7cc023f-4716-4010-8078-6a44f560a496/media 118G 82G 36G 70% /storage/emulated
rm -rfv *
rm: test1: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: test2: Directory not empty
rm: test3: Directory not empty
rm: test4: Directory not empty
rm: test5: Directory not empty
rm: test6: Directory not empty
rm: test7: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
find . -exec ls -lhd {} +
drwxrwx--x 20 root sdcard_rw 3.4K 2020-09-04 13:31 .
drwxrwx--x 2 root sdcard_rw 24K 2020-09-04 10:12 ./test1
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:34 ./test10
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:40 ./test10/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:45 ./test11
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:51 ./test11/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:57 ./test12
drwxrwx--x 2 root sdcard_rw 504K 2020-09-04 12:02 ./test12/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:09 ./test13
drwxrwx--x 2 root sdcard_rw 504K 2020-09-04 12:15 ./test13/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:19 ./test14
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:25 ./test14/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:30 ./test15
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:36 ./test15/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:40 ./test16
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:47 ./test16/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 13:01 ./test17
drwxrwx--x 2 root sdcard_rw 420K 2020-09-04 13:04 ./test17/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 13:18 ./test19
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 13:22 ./test19/TitaniumBackup
drwxrwx--x 2 root sdcard_rw 56K 2020-09-04 10:21 ./test2
drwxrwx--x 2 root sdcard_rw 56K 2020-09-04 10:26 ./test3
drwxrwx--x 2 root sdcard_rw 20K 2020-09-04 10:57 ./test4
drwxrwx--x 2 root sdcard_rw 20K 2020-09-04 10:57 ./test5
drwxrwx--x 2 root sdcard_rw 92K 2020-09-04 11:07 ./test6
drwxrwx--x 3 root sdcard_rw 116K 2020-09-04 11:12 ./test7
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:20 ./test8
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:26 ./test8/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:27 ./test9
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:33 ./test9/TitaniumBackup

Code:
logcat '*:V'
I'm watching the logs in one window, while I get failures in another window. I'm not seeing anything in the logs that corresponds to the failures.
And the sd-card has passed "badblocks" with zero errors.

Nevermind… The problem is being reproduced with stock firmware.
After following these instructions to Enable Adoptable Storage On Mi Phone, I can very consistently reproduce the problem with a stock ROM.
Seems like a hardware fault.

Update: Just got a brand new Redmi Note 8. Out of the box, everything is stock. Same problem with Adata 128GB cards.
I'm trying to get these cards to puke in another machine, but they're testing perfectly.
In the phone, I'm testing with a Lexar 64GB card, and I can't find any problems with it.
Is it possible that these particular Adata cards (brand new!) just aren't compatible with this phone? Is anyone else using 128GB Adata cards with this phone?
I guess I'll have to get a different brand 128GB (or maybe 256GB?) card and do more testing.

And… I got the same error while un-taring 8GB of podcasts. This is with the 64GB Lexar card.
Now what???

Related

Cannot write direclty to /mnt/extSdCard with adb or Android Commander

In adb shell, with myself set as su, I cannot write directly to /mnt/extSdCard. Get's "permission denied"
When I do a chmod or chown to root, I get an "operation not permitted"
I have to copy (push) files to /mnt/sdcard and use the device to move/copy stuff over to /mnt/extSdCard.....pretty annoying.
I guess the reason is because the ownership looks like this:
ls -al
...
drwxrwxr-x system media_rw 2012-10-12 10:07 extSdCard
drwxr-xr-x root system 2012-10-11 09:10 obb
drwxrwxr-x root sdcard_rw 2012-10-12 10:29 sdcard
drwx------ root root 2012-10-11 09:10 secure
Any ideas how I can write to /mnt/extSdCard - even Android Commander is not doing anything
I think you have to mount it first with something that should look like,
"Adb mount /mnt/blk/[some wierd path here]/" or something
Not sure but that's my best guess since no one else was offering insight
Sent from my GT-N8013 using xda app-developers app
Same problem here, have you already found a solution or workaround?

[Q] TWRP Folder Permission Denied

Update: Fixed by
command !
Guys,
I am currently Running STOCK LRX21O.Rooted using Chainfire's AutoRoot and TWRP -2.8.1.0. I made backup but I am unable to access it using ES file explorer(with root option enabled). Also tried Root explorer but It just doesnt show the Folder itself.
When I boot into TWRP it shows the Backup folder there. So I tried to check it with adb to do a ls and it shows its there. I need to copy that folder to cloud just incase. I dont see permission issues. Plese suggest how to fix this ?
Code:
C:\Users\Zaibrockstar>adb shell ls -l /sdcard/
drwxrwx--- root sdcard_r 1971-01-05 22:48 Alarms
drwxrwx--x root sdcard_r 2014-11-12 21:00 Android
drwxrwx--- root sdcard_r 2014-11-12 23:29 DCIM
drwxrwx--- root sdcard_r 2014-11-13 08:44 Download
drwxrwx--- root sdcard_r 1971-01-05 22:48 Music
drwxrwx--- root sdcard_r 2014-11-12 21:34 Notifications
drwxrwx--- root sdcard_r 2014-11-12 23:26 Pictures
drwxrwx--- root sdcard_r 1971-01-05 22:48 Podcasts
drwxrwx--- root sdcard_r 1971-01-05 22:48 Ringtones
[B][U]lstat '/sdcard//TWRP' failed: Permission denied[/U][/B]
drwxrwx--- root sdcard_r 2014-11-13 09:27 backups
drwxrwx--- root sdcard_r 2014-11-12 21:32 baidu
drwxrwx--- root sdcard_r 2014-11-12 23:13 media
Code:
C:\Users\Zaibrockstar>adb shell ls -R /sdcard/
/sdcard/:
Alarms
Android
DCIM
Download
Music
Notifications
Pictures
Podcasts
Ringtones
[COLOR="Red"]TWRP[/COLOR]
backups
baidu
media
[B][COLOR="Red"]/sdcard//TWRP: Permission denied[/COLOR]
[/B]
Thanks
Zaib
http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749

[Q] /data filesystem problem

In the ADB shell as root I get the following results
Code:
/data # ls -la dalvik-cache/
ls -la dalvik-cache
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
drwxrwx--x 4 root root 57344 Mar 14 12:36 .
drwxrwx--x 41 system system 4096 Mar 15 07:45 ..
drwx--x--x 2 root root 53248 Mar 15 07:45 arm
drwx--x--x 2 system system 20480 Mar 14 20:56 profiles
/data # ls -la property/
ls -la property
ls: property/persist.atvc.allow_res_core: No such file or directory
ls: property/persist.atvc.allow_all_core: No such file or directory
ls: property/persist.radio.adb_log_on: No such file or directory
drwx------ 2 root root 4096 Mar 15 08:25 .
drwxrwx--x 41 system system 4096 Mar 15 07:45 ..
-rw------- 1 root root 1 Jan 2 2009 persist.atvc.adb
-rw------- 1 root root 1 Mar 15 07:45 persist.atvc.allow_res_panic
....
This doesn't seem right. Since /data is an F2FS partition I can't fsck it.
Any ideas on how to get rid of those errors?
What I've tried:
listing (ls), removing, stat'ing, fsck.f2fs'ing, nothing works from the shell.
Is there possibly a better forum to ask this question? I have plenty *nix experience, but am stumped on how to solve this. Normally filechecking tools are necessary but a good one for F2FS doesn't seem available (on Android).
Which ROM are you running on your phone? I'm not sure if that makes a difference since GPE uses ext4 and stock uses f2fs.
I've only run stock KK and L.
In the end I could only solve it by completely wiping the /data partition with dd and reformatting with mkfs.f2fs.
Done from adb shell in recovery.
I dunno how I ended up in this situation but it's solved now.
Running the Brzilian XT1032 ROM now, will reinstall sometime when the EU image is available.
Sent from my XT1032 using XDA Free mobile app
Quark^2 said:
I've only run stock KK and L.
In the end I could only solve it by completely wiping the /data partition with dd and reformatting with mkfs.f2fs.
Done from adb shell in recovery.
I dunno how I ended up in this situation but it's solved now.
Running the Brzilian XT1032 ROM now, will reinstall sometime when the EU image is available.
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Could you give a link to the file and a list of commands you used?
I'm probably stuck in the same situation as you were.

Redmi Note 7 Pro with MIUI 11 in bootloop, as I chanded the dpi in developer option

I've increased the dpi in developer option and once I changed the dpi the phone screen turned black and the phone started to reboot, after each reboot it lands in recovery mode. Is there any way to take my phone out of this while preserving my data.
Is there any way to back up the data using adb sideload (MiPCSuite), or fastboot commands (or reinstall the MIUI 11.0.5.0 zip file if it helps).
My Phone runs latest MIUI 11 and usb debugging is enabled, (unfortunately oem unlocking is disabled)
Thankyou!
P.S: Changing dpi was perfectly fine in MIUI 10.
[email protected] said:
I've increased the dpi in developer option and once I changed the dpi the phone screen turned black and the phone started to reboot, after each reboot it lands in recovery mode. Is there any way to take my phone out of this while preserving my data.
Is there any way to back up the data using adb sideload (MiPCSuite), or fastboot commands (or reinstall the MIUI 11.0.5.0 zip file if it helps).
My Phone runs latest MIUI 11 and usb debugging is enabled, (unfortunately oem unlocking is disabled)
Thankyou!
P.S: Changing dpi was perfectly fine in MIUI 10.
Click to expand...
Click to collapse
Bl is locked??
Sent from my Redmi Note 7 Pro using XDA Labs
same problem with my mix mix2. accidentally changed dpi 600 to 6000. now phone stucked on bootloop, any way to revert back, somebody help me
thanks
Unlock bootloader using mi unlock tool. then flash the latest fastboot rom. Unlocking bootloader wipes internal storage also.
Vishal P said:
Unlock bootloader using mi unlock tool. then flash the latest fastboot rom. Unlocking bootloader wipes internal storage also.
Click to expand...
Click to collapse
i want my personal files too
iMesutOzil said:
i want my personal files too
Click to expand...
Click to collapse
No u cant. If bl is locked then use a deep flash cable to flash in edl mode using mi flash tool. Downlaod lattest fastboot rom from mi website and then flash it in edl mode.
Sent from my Redmi Note 7 Pro using XDA Labs
Same thing happened to my mi mix 3... big ****ing bug
If you set up ADB on your PC before the bootloop happened, you might still be able to enter adb shell when the phone is in the boot animation phase. Try that and if so, reset the DPI from ADB.
adb shell wm density reset
That should work.
I changed my dpi from default (392) to 411 on my POCO F1, MIUI 11, nothing happened.
Do NOT change the Smallest width / DPI to an absurd number. If you do, and if you don't have ADB enabled or you don't have an unlocked bootloader, there's no way to restore the default DPI nor is there a way to reset your phone to factory defaults (unless the built-in MIUI recovery has the option to wipe data).
hackermssharma said:
Bl is locked??
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Yupp
[email protected] said:
Yupp
Click to expand...
Click to collapse
So u have to now flash miui lattest fastboot rom using deep flash cable in edl mode.
Sent from my Redmi Note 7 Pro using XDA Labs
Bug
did anyone find w solutions except erase all data
for me i have adb but #wm density reset throw Permission error :crying::crying:
i really need to copy my files before wipe but can't find solution
going to /storage/emulated/0/ seems to have encrypted folders/files
HTML:
$adb shell ls -halt /storage/emulated/0/
total 39K
-rw-rw---- 1 root sdcard_rw 72 2020-02-03 00:35 FgiQtKyeKzw6kG+F1MzmSA
drwxrwx--x 22 root sdcard_rw 3.4K 2020-02-02 18:17 .
drwxrwx--x 2 root sdcard_rw 3.4K 2020-02-02 18:17 dKMxDxL7j7oMuXS0dTZLvD
drwxrwx--x 2 root sdcard_rw 3.4K 2020-01-31 12:06 wgQKDk,UYBX5+QCmtp3TgA
drwxrwx--x 5 root sdcard_rw 3.4K 2020-01-30 20:48 DWB,QUyj4QsWQDdjnD2TmC
-rw-rw---- 1 root sdcard_rw 74 2020-01-29 19:20 +Sa1tuwh8qDNX70,cXkG8A
drwxrwx--x 2 root sdcard_rw 3.4K 2020-01-29 19:20 ae60B1sKAy7DVYxwogwqSC
-rw-rw---- 1 root sdcard_rw 2 2020-01-29 19:20 r5PwopcfV04Svv5nJlDgDC
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-27 12:18 m,vKs+YZOwVf727Hnr5ENA
drwxrwx--x 5 root sdcard_rw 3.4K 2020-01-22 21:48 T0oYyqREd0bnaJ0UUPpXqC
drwxrwx--x 7 root sdcard_rw 3.4K 2020-01-18 22:24 Ru8BfHo31O0e5zQU1P9BYC
drwxrwx--x 9 root sdcard_rw 3.4K 2020-01-17 02:00 28oc9z9OmfErUWpCmQCKgB
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 23:00 D,hr3l9Fb6Yr2KCMjYMxeC
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 07:57 cRMXNSqqlqXji2+RIz1UfA
drwxrwx--x 2 root sdcard_rw 3.4K 2020-01-16 07:43 6YeHUpP585MuMASMaPH6KA
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-13 22:29 0cjhLjEMgL5o2Vubeumb3B
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-31 17:05 RqW9BJOAk6,u,RFRhe95PA
drwxrwx--x 2 root sdcard_rw 3.4K 2019-12-26 01:39 KMnWNXgD46Ld4wq+NNt0iA
drwxrwx--x 2 root sdcard_rw 3.4K 2019-12-16 03:26 E,cwkt4ZnQv4TKNdDoDwaA
drwxrwx--x 5 root sdcard_rw 3.4K 2019-12-15 17:33 wgsU61k+WwJUAOSkx6us3C
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 11:36 9LFK1i4G+RHy8asXFe7XpA
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 10:54 ,JRes9ZrBhL,YHcMCdFbVIlpkdN
drwxrwx--x 7 root sdcard_rw 3.4K 2019-12-15 10:43 MKbC4maFyMRpw7A4o1nH5D
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-13 17:17 1,lyeBF4+FXLquN8Bti5zC
drwx--x--x 4 root sdcard_rw 3.4K 2008-12-31 17:01 ..
HTML Code:
$adb shell du -sh 'storage/emulated/0/*'
4.0K storage/emulated/0/+Sa1tuwh8qDNX70,cXkG8A
7.0K storage/emulated/0/,JRes9ZrBhL,YHcMCdFbVIlpkdN
23K storage/emulated/0/0cjhLjEMgL5o2Vubeumb3B
3.9M storage/emulated/0/1,lyeBF4+FXLquN8Bti5zC
4.1M storage/emulated/0/28oc9z9OmfErUWpCmQCKgB
3.5K storage/emulated/0/6YeHUpP585MuMASMaPH6KA
22K storage/emulated/0/9LFK1i4G+RHy8asXFe7XpA
11K storage/emulated/0/D,hr3l9Fb6Yr2KCMjYMxeC
3.0M storage/emulated/0/DWB,QUyj4QsWQDdjnD2TmC
3.5K storage/emulated/0/E,cwkt4ZnQv4TKNdDoDwaA
4.0K storage/emulated/0/FgiQtKyeKzw6kG+F1MzmSA
3.5K storage/emulated/0/KMnWNXgD46Ld4wq+NNt0iA
2.6G storage/emulated/0/MKbC4maFyMRpw7A4o1nH5D
2.9M storage/emulated/0/RqW9BJOAk6,u,RFRhe95PA
10G storage/emulated/0/Ru8BfHo31O0e5zQU1P9BYC
8.2M storage/emulated/0/T0oYyqREd0bnaJ0UUPpXqC
3.5K storage/emulated/0/ae60B1sKAy7DVYxwogwqSC
27K storage/emulated/0/cRMXNSqqlqXji2+RIz1UfA
3.5K storage/emulated/0/dKMxDxL7j7oMuXS0dTZLvD
47M storage/emulated/0/m,vKs+YZOwVf727Hnr5ENA
4.0K storage/emulated/0/r5PwopcfV04Svv5nJlDgDC
465M storage/emulated/0/wgQKDk,UYBX5+QCmtp3TgA
645M storage/emulated/0/wgsU61k+WwJUAOSkx6us3C
i can read my density but not write i think USB debug (secure Security) is not enable .. is there a way to enable via adb in this stat !!!
killuadk said:
did anyone find w solutions except erase all data
for me i have adb but #wm density reset throw Permission error :crying::crying:
i really need to copy my files before wipe but can't find solution
going to /storage/emulated/0/ seems to have encrypted folders/files
$adb shell ls -halt /storage/emulated/0/total 39K-rw-rw---- 1 root sdcard_rw 72 2020-02-03 00:35 FgiQtKyeKzw6kG+F1MzmSAdrwxrwx--x 22 root sdcard_rw 3.4K 2020-02-02 18:17 .drwxrwx--x 2 root sdcard_rw 3.4K 2020-02-02 18:17 dKMxDxL7j7oMuXS0dTZLvDdrwxrwx--x 2 root sdcard_rw 3.4K 2020-01-31 12:06 wgQKDk,UYBX5+QCmtp3TgAdrwxrwx--x 5 root sdcard_rw 3.4K 2020-01-30 20:48 DWB,QUyj4QsWQDdjnD2TmC-rw-rw---- 1 root sdcard_rw 74 2020-01-29 19:20 +Sa1tuwh8qDNX70,cXkG8Adrwxrwx--x 2 root sdcard_rw 3.4K 2020-01-29 19:20 ae60B1sKAy7DVYxwogwqSC-rw-rw---- 1 root sdcard_rw 2 2020-01-29 19:20 r5PwopcfV04Svv5nJlDgDCdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-27 12:18 m,vKs+YZOwVf727Hnr5ENAdrwxrwx--x 5 root sdcard_rw 3.4K 2020-01-22 21:48 T0oYyqREd0bnaJ0UUPpXqCdrwxrwx--x 7 root sdcard_rw 3.4K 2020-01-18 22:24 Ru8BfHo31O0e5zQU1P9BYCdrwxrwx--x 9 root sdcard_rw 3.4K 2020-01-17 02:00 28oc9z9OmfErUWpCmQCKgBdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 23:00 D,hr3l9Fb6Yr2KCMjYMxeCdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 07:57 cRMXNSqqlqXji2+RIz1UfAdrwxrwx--x 2 root sdcard_rw 3.4K 2020-01-16 07:43 6YeHUpP585MuMASMaPH6KAdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-13 22:29 0cjhLjEMgL5o2Vubeumb3Bdrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-31 17:05 RqW9BJOAk6,u,RFRhe95PAdrwxrwx--x 2 root sdcard_rw 3.4K 2019-12-26 01:39 KMnWNXgD46Ld4wq+NNt0iAdrwxrwx--x 2 root sdcard_rw 3.4K 2019-12-16 03:26 E,cwkt4ZnQv4TKNdDoDwaAdrwxrwx--x 5 root sdcard_rw 3.4K 2019-12-15 17:33 wgsU61k+WwJUAOSkx6us3Cdrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 11:36 9LFK1i4G+RHy8asXFe7XpAdrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 10:54 ,JRes9ZrBhL,YHcMCdFbVIlpkdNdrwxrwx--x 7 root sdcard_rw 3.4K 2019-12-15 10:43 MKbC4maFyMRpw7A4o1nH5Ddrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-13 17:17 1,lyeBF4+FXLquN8Bti5zCdrwx--x--x 4 root sdcard_rw 3.4K 2008-12-31 17:01 ..HTML Code:$adb shell du -sh 'storage/emulated/0/*'4.0K storage/emulated/0/+Sa1tuwh8qDNX70,cXkG8A7.0K storage/emulated/0/,JRes9ZrBhL,YHcMCdFbVIlpkdN23K storage/emulated/0/0cjhLjEMgL5o2Vubeumb3B3.9M storage/emulated/0/1,lyeBF4+FXLquN8Bti5zC4.1M storage/emulated/0/28oc9z9OmfErUWpCmQCKgB3.5K storage/emulated/0/6YeHUpP585MuMASMaPH6KA22K storage/emulated/0/9LFK1i4G+RHy8asXFe7XpA11K storage/emulated/0/D,hr3l9Fb6Yr2KCMjYMxeC3.0M storage/emulated/0/DWB,QUyj4QsWQDdjnD2TmC3.5K storage/emulated/0/E,cwkt4ZnQv4TKNdDoDwaA4.0K storage/emulated/0/FgiQtKyeKzw6kG+F1MzmSA3.5K storage/emulated/0/KMnWNXgD46Ld4wq+NNt0iA2.6G storage/emulated/0/MKbC4maFyMRpw7A4o1nH5D2.9M storage/emulated/0/RqW9BJOAk6,u,RFRhe95PA10G storage/emulated/0/Ru8BfHo31O0e5zQU1P9BYC8.2M storage/emulated/0/T0oYyqREd0bnaJ0UUPpXqC3.5K storage/emulated/0/ae60B1sKAy7DVYxwogwqSC27K storage/emulated/0/cRMXNSqqlqXji2+RIz1UfA3.5K storage/emulated/0/dKMxDxL7j7oMuXS0dTZLvD47M storage/emulated/0/m,vKs+YZOwVf727Hnr5ENA4.0K storage/emulated/0/r5PwopcfV04Svv5nJlDgDC465M storage/emulated/0/wgQKDk,UYBX5+QCmtp3TgA645M storage/emulated/0/wgsU61k+WwJUAOSkx6us3C
i can read my density but not write i think USB debug (secure Security) is not enable .. is there a way to enable via adb in this stat !!!
Click to expand...
Click to collapse
Well it looks encrypted, You can't copy your files this way...You would have to unlock the BL and reset it...
Naveenthemi said:
Well it looks encrypted, You can't copy your files this way...You would have to unlock the BL and reset it...
Click to expand...
Click to collapse
unlock BT without erase DATA !! can you guild me !!
killuadk said:
unlock BT without erase DATA !! can you guild me !!
Click to expand...
Click to collapse
I'm sorry....... Xiaomi currently offers no method to unlock the bootloader without formatting the internal storage. There are NO third party tools either. You would have to undergo formatting to unlock the BT. Even the service centre can't avoid that.
Naveenthemi said:
I'm sorry....... Xiaomi currently offers no method to unlock the bootloader without formatting the internal storage. There are NO third party tools either. You would have to undergo formatting to unlock the BT. Even the service centre can't avoid that.
Click to expand...
Click to collapse
is it possible to recover photo after wipe data !! if yes suggest any software !!
killuadk said:
is it possible to recover photo after wipe data !! if yes suggest any software !!
Click to expand...
Click to collapse
It usually isn't possible to recover photos in this case, but it wouldn't kill to try.
Use (https://play.google.com/store/apps/details?id=com.defianttech.diskdigger)
It's the only free, working app I've come across for photo recovery. Even then it's only a chance you would get the photos back in the original quality or fully.
Naveenthemi said:
It usually isn't possible to recover photos in this case, but it wouldn't kill to try.
Use (https://play.google.com/store/apps/details?id=com.defianttech.diskdigger)
It's the only free, working app I've come across for photo recovery. Even then it's only a chance you would get the photos back in the original quality or fully.
Click to expand...
Click to collapse
I did try it but he found nothing (encryption ) know i will try to pull all the hard into my pc and use another soft
Help! I have the same problem on my Redmi Note 8. BT is locked, too

[GUIDE] Extract OTA links & update file from Realme/OPPO devices

So people were asking about how to capture OTA link in Realme devices. Unlike other devices Realme/OPPO devices won't log OTA update link, maybe because colorOS engineers are too smart that they don't want users to have it & update manually or whatever the reasons are. Below is the process to extract OTA link & OTA Package if downloaded.
Prerequisite:
1. Bootloader unlocked device
2. Rooted or custom recovery
Process:
For only extracting OTA link
1. This is the database file where links & other info is stored.
Code:
/data/data/com.oppo.ota/databases/ota.db-wal
Copy it to laptop/PC or whatever so you can be able to read it.
2. Now use Notepad or any other text reader open the ota.db file, you will find random characters which aren't readable by Humans. Scroll until you find https://otafsg.realmemobile.com/* & few other lines which includes MD5 hash, full changelog link which is html webpage & version name etc., Use brain & figure out which is which.
3. Now you got what you want. Mission Accomplished
For extracting OTA Package (OZIP):
This hidden directory contains downloaded OTA Package
Code:
/data/oppo/coloros/OTA/.otaPackage/
. Pull it via ADB or anything whichever you are comfortable with.
Unable to find ota package
Hi I followed the path mentioned to locate the ota package that I had downloaded which is close to 3 GB in size, however, what I got is just a 1000b ozip file. Could you please help?
Yes your file manager is not able to read the size correctly. Try to copy it to your internal storage(with ES file explorer {process will be invisible wait for a minute or two}) and then check the size it will be of 3 gb....hope it helped
thanks! it's help a lot to me
so smart. thanks man
any way without root?
4j17h said:
So people were asking about how to capture OTA link in Realme devices. Unlike other devices Realme/OPPO devices won't log OTA update link, maybe because colorOS engineers are too smart that they don't want users to have it & update manually or whatever the reasons are. Below is the process to extract OTA link & OTA Package if downloaded.
Prerequisite:
1. Bootloader unlocked device
2. Rooted or custom recovery
Process:
For only extracting OTA link
1. This is the database file where links & other info is stored.
Code:
/data/data/com.oppo.ota/databases/ota.db-wal
Copy it to laptop/PC or whatever so you can be able to read it.
2. Now use Notepad or any other text reader open the ota.db file, you will find random characters which aren't readable by Humans. Scroll until you find https://otafsg.realmemobile.com/* & few other lines which includes MD5 hash, full changelog link which is html webpage & version name etc., Use brain & figure out which is which.
3. Now you got what you want. Mission Accomplished
For extracting OTA Package (OZIP):
This hidden directory contains downloaded OTA Package
Code:
/data/oppo/coloros/OTA/.otaPackage/
. Pull it via ADB or anything whichever you are comfortable with.
Click to expand...
Click to collapse
This aint working anymore with ColorOS 11/realmeUI2.0 Update. Also Update Server has been changed to http://ota-manual-in.allawnofs.com/ota/* , followed by some md5 hashes . Any Comments @4j17h
4j17h said:
So people were asking about how to capture OTA link in Realme devices. Unlike other devices Realme/OPPO devices won't log OTA update link, maybe because colorOS engineers are too smart that they don't want users to have it & update manually or whatever the reasons are. Below is the process to extract OTA link & OTA Package if downloaded.
Prerequisite:
1. Bootloader unlocked device
2. Rooted or custom recovery
Process:
For only extracting OTA link
1. This is the database file where links & other info is stored.
Code:
/data/data/com.oppo.ota/databases/ota.db-wal
Copy it to laptop/PC or whatever so you can be able to read it.
2. Now use Notepad or any other text reader open the ota.db file, you will find random characters which aren't readable by Humans. Scroll until you find https://otafsg.realmemobile.com/* & few other lines which includes MD5 hash, full changelog link which is html webpage & version name etc., Use brain & figure out which is which.
3. Now you got what you want. Mission Accomplished
For extracting OTA Package (OZIP):
This hidden directory contains downloaded OTA Package
Code:
/data/oppo/coloros/OTA/.otaPackage/
. Pull it via ADB or anything whichever you are comfortable with.
Click to expand...
Click to collapse
Any way without unlocking device ..??
As once unlocked then it's easy but with locked bootloader any steps ..??
I've tried to follow your guide but unfortunately on RMX3241 it doesn't seem to be stored at this location. The folder only has an sqlite db and it contains no links
RMX3241:/data # find . -path "*ota*database*"
./data/com.oppo.ota/databases
./data/com.oppo.ota/databases/enterprise_ota.db
./data/com.oppo.ota/databases/enterprise_ota.db-journal
and
RMX3241:/data # ls /data/oppo/coloros/ -lah
total 41K
drwxrwxrwx 27 system system 3.4K 2021-11-21 10:59 .
drwxrwxr-x 15 system system 3.4K 2021-11-21 10:49 ..
drwx------ 2 system system 3.4K 2021-11-21 10:49 animation
drwx------ 2 system system 3.4K 2021-11-21 10:52 appswitch
drwx------ 2 system system 3.4K 2021-11-21 11:01 bpm
drwx------ 2 system system 3.4K 2021-11-21 10:52 colordirect
drwx------ 2 system system 3.4K 2021-11-21 10:52 config
drwx------ 2 system system 3.4K 2021-11-21 10:49 darkmode
drwx------ 2 system system 3.4K 2021-11-26 01:33 dataupdate
drwx------ 2 system system 3.4K 2021-11-21 10:52 displaycompat
drwxrwxrwx 2 system system 3.4K 2021-11-21 10:49 eap
drwxrwxrwx 4 system system 3.4K 2021-11-21 10:49 eap_moa
drwx------ 2 system system 3.4K 2021-11-21 10:52 freeform
drwx------ 2 system system 3.4K 2021-11-21 10:52 gamespace
drwxrwxrwx 2 u0_a111 u0_a111 3.4K 2021-11-21 10:52 keylayout
drwx------ 2 system system 3.4K 2021-11-21 10:52 notification
drwx------ 2 system system 3.4K 2021-11-25 11:41 oppoguardelf
drwxrwxrwx 2 system system 3.4K 2021-11-21 10:52 permission
drwx------ 2 system system 3.4K 2021-11-21 10:52 recenttask
drwx------ 2 system system 3.4K 2021-11-23 14:12 removableapp
drwx------ 2 system system 3.4K 2021-11-21 10:52 repairmode
drwx------ 2 system system 3.4K 2021-11-21 10:59 safecenter
drwx------ 2 system system 3.4K 2021-11-21 10:53 securepay
drwx------ 2 system system 3.4K 2021-11-21 22:09 startup
drwx------ 2 system system 3.4K 2021-11-21 10:49 toast
drwx------ 2 system system 3.4K 2021-11-21 10:52 trafficProtect
drwx------ 2 system system 3.4K 2021-11-21 10:52 zoom
Any ideas where else to extract the link to the download for the OTA image?
aryankaran said:
Any way without unlocking device ..??
As once unlocked then it's easy but with locked bootloader any steps ..??
Click to expand...
Click to collapse
No you can't
maintanosgr said:
I've tried to follow your guide but unfortunately on RMX3241 it doesn't seem to be stored at this location. The folder only has an sqlite db and it contains no links
RMX3241:/data # find . -path "*ota*database*"
./data/com.oppo.ota/databases
./data/com.oppo.ota/databases/enterprise_ota.db
./data/com.oppo.ota/databases/enterprise_ota.db-journal
and
RMX3241:/data # ls /data/oppo/coloros/ -lah
total 41K
drwxrwxrwx 27 system system 3.4K 2021-11-21 10:59 .
drwxrwxr-x 15 system system 3.4K 2021-11-21 10:49 ..
drwx------ 2 system system 3.4K 2021-11-21 10:49 animation
drwx------ 2 system system 3.4K 2021-11-21 10:52 appswitch
drwx------ 2 system system 3.4K 2021-11-21 11:01 bpm
drwx------ 2 system system 3.4K 2021-11-21 10:52 colordirect
drwx------ 2 system system 3.4K 2021-11-21 10:52 config
drwx------ 2 system system 3.4K 2021-11-21 10:49 darkmode
drwx------ 2 system system 3.4K 2021-11-26 01:33 dataupdate
drwx------ 2 system system 3.4K 2021-11-21 10:52 displaycompat
drwxrwxrwx 2 system system 3.4K 2021-11-21 10:49 eap
drwxrwxrwx 4 system system 3.4K 2021-11-21 10:49 eap_moa
drwx------ 2 system system 3.4K 2021-11-21 10:52 freeform
drwx------ 2 system system 3.4K 2021-11-21 10:52 gamespace
drwxrwxrwx 2 u0_a111 u0_a111 3.4K 2021-11-21 10:52 keylayout
drwx------ 2 system system 3.4K 2021-11-21 10:52 notification
drwx------ 2 system system 3.4K 2021-11-25 11:41 oppoguardelf
drwxrwxrwx 2 system system 3.4K 2021-11-21 10:52 permission
drwx------ 2 system system 3.4K 2021-11-21 10:52 recenttask
drwx------ 2 system system 3.4K 2021-11-23 14:12 removableapp
drwx------ 2 system system 3.4K 2021-11-21 10:52 repairmode
drwx------ 2 system system 3.4K 2021-11-21 10:59 safecenter
drwx------ 2 system system 3.4K 2021-11-21 10:53 securepay
drwx------ 2 system system 3.4K 2021-11-21 22:09 startup
drwx------ 2 system system 3.4K 2021-11-21 10:49 toast
drwx------ 2 system system 3.4K 2021-11-21 10:52 trafficProtect
drwx------ 2 system system 3.4K 2021-11-21 10:52 zoom
Any ideas where else to extract the link to the download for the OTA image?
Click to expand...
Click to collapse
For the new update it's located
/data/ota_package/OTA/.otaPackage
TechyMinati said:
This aint working anymore with ColorOS 11/realmeUI2.0 Update. Also Update Server has been changed to http://ota-manual-in.allawnofs.com/ota/* , followed by some md5 hashes . Any Comments @4j17h
Click to expand...
Click to collapse
It now located in
/data/ota_package/OTA/.otaPackage
Engrudhy said:
It now located in
/data/ota_package/OTA/.otaPackage
Click to expand...
Click to collapse
at realme UI 3.0 cant find anything now
Does anyone know the location of ota after ui 3.0

Categories

Resources