Hello,
I've spent the entire day trying to solve this issue, it seems paranormal but (sadly) it's true and I didn't find a way to solve it.
Yesterday I recorded a very important video using my Xiaomi and Quick Video Recorder. For privacy reasons I prefer not explaining why it's so important to me but it would help me proving something really essential (I also used it more than once and everything has always been great), I had something like 3Gb of free space but I didn't check it and I was recording with high quality. Android told me that was running out of space, so I suddenly stopped recording (after about 3 minutes). I checked the video and used VLC to replay it and everything seemed to work fine.
After about 30 minutes, the file was missing. I checked everywhere, rooted the phone and tried with recovery applications such as Dr.Fone, but the file is completely disappeared. To be 100% sure I didn't dream it I also checked on Google Takeout and it confirmed I actually used the camera during that time and suddenly opened VLC to replay it...
What I'm asking is, is it possible for a large video (like 3/4Gb) to completely disappear from my system? Leaving no tracks on logs or somewhere else?
Does Android delete an entire video when it's too large? If so, how is it possible that I have been able to replay it once?
I didn't know what to do so I opened adb shell and tried with
Code:
ls -Rlat | grap -i '2019-12-18\ 17:
' (I recorded and then replayed the video around that time) and this is the result:
Code:
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 files
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 .
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 ..
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 playlists
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 .
drwxrwx--x 2 u0_a187 sdcard_rw 4096 2019-12-18 17:07 1576685265
drwxrwx--x 2 u0_a187 sdcard_rw 4096 2019-12-18 17:07 .
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 ..
-rw------- 1 system system 0 2019-12-18 17:50 [email protected]
-rw------- 1 system system 0 2019-12-18 17:08 [email protected]
-rw------- 1 system system 0 2019-12-18 17:08 [email protected]
-rw------- 1 system system 0 2019-12-18 17:02 [email protected]
drwx------ 3 system system 4096 2019-12-18 17:34 org.videolan.vlc
drwx------ 3 system system 4096 2019-12-18 17:24 com.kimcy929.secretvideorecorder
drwx------ 3 system system 4096 2019-12-18 17:08 com.android.incallui
drwx------ 3 system system 4096 2019-12-18 17:02 com.android.contacts
-rw------- 1 system system 897 2019-12-18 17:02 total
drwx------ 3 system system 4096 2019-12-18 17:34 .
drwx------ 2 system system 4096 2019-12-18 17:34 13020307
drwx------ 2 system system 4096 2019-12-18 17:34 .
drwx------ 3 system system 4096 2019-12-18 17:34 ..
drwx------ 3 system system 4096 2019-12-18 17:24 .
drwx------ 2 system system 4096 2019-12-18 17:24 245
drwx------ 2 system system 4096 2019-12-18 17:24 .
drwx------ 3 system system 4096 2019-12-18 17:24 ..
drwx------ 3 system system 4096 2019-12-18 17:08 .
drwx------ 2 system system 4096 2019-12-18 17:08 27
drwx------ 2 system system 4096 2019-12-18 17:08 .
drwx------ 3 system system 4096 2019-12-18 17:08 ..
drwx------ 3 system system 4096 2019-12-18 17:02 .
drwx------ 2 system system 4096 2019-12-18 17:02 100
drwx------ 2 system system 4096 2019-12-18 17:02 .
drwx------ 3 system system 4096 2019-12-18 17:02 ..
-rw------- 1 u0_a131 u0_a131 0 2019-12-18 17:33 com.facebook.katana_3c8406f3-3e8a-80cd-85cb-0c1211088d8d.v3.txt_anr
-rw------- 1 u0_a131 u0_a131 0 2019-12-18 17:33 com.facebook.katana_3c8406f3-3e8a-80cd-85cb-0c1211088d8d.v3.txt_native
-rw------- 1 u0_a131 u0_a131 0 2019-12-18 17:33 com.facebook.katana_3c8406f3-3e8a-80cd-85cb-0c1211088d8d.v3.txt_wrotedump
-rw------- 1 u0_a131 u0_a131 250 2019-12-18 17:33 com.facebook.katana_3c8406f3-3e8a-80cd-85cb-0c1211088d8d.v3.txt_static
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:04 app_webview
drwxrws--x 4 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 cache
drwxrwx--x 2 u0_a87 u0_a87 4096 2019-12-18 17:03 shared_prefs
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:04 .
-rw------- 1 u0_a87 u0_a87 270 2019-12-18 17:04 pref_store
-rw------- 1 u0_a87 u0_a87 4885 2019-12-18 17:03 variations_seed_new
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:03 Default
-rw------- 1 u0_a87 u0_a87 0 2019-12-18 17:03 variations_stamp
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:04 ..
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:03 .
-rw------- 1 u0_a87 u0_a87 61440 2019-12-18 17:03 Web Data
-rw------- 1 u0_a87 u0_a87 0 2019-12-18 17:03 Web Data-journal
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:03 blob_storage
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:03 .
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:03 ..
drwx------ 2 u0_a87 u0_a87 4096 2019-12-18 17:03 aa41e68b-5b8c-4030-ab9b-9fd7dfb95ee8
drwx------ 2 u0_a87 u0_a87 4096 2019-12-18 17:03 .
drwx------ 3 u0_a87 u0_a87 4096 2019-12-18 17:03 ..
drwxrws--x 6 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 WebView
drwxrws--x 4 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 .
drwxrws--x 6 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 .
-rw------- 1 u0_a87 u0_a87_cache 19900 2019-12-18 17:03 font_unique_name_table.pb
drwxrws--x 4 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 ..
drwx--S--- 3 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 Default
drwxrws--x 6 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 ..
drwx--S--- 3 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 .
drwx--S--- 3 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 ..
drwxrws--x 6 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 ..
drwxrws--x 6 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 ..
drwxrws--x 6 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 ..
-rw------- 1 u0_a87 u0_a87_cache 40 2019-12-18 17:03 settings.dat
drwxrws--x 4 u0_a87 u0_a87_cache 4096 2019-12-18 17:03 ..
drwxrwx--x 2 u0_a87 u0_a87 4096 2019-12-18 17:03 .
-rw-rw---- 1 u0_a87 u0_a87 127 2019-12-18 17:03 WebViewChromiumPrefs.xml
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:50 android_pay_temp_files
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:50 token_selector_anim
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 WebView
drwx--x--x 3 u0_a16 u0_a16_cache 4096 2019-12-18 17:14 oat
-rw------- 1 u0_a16 u0_a16_cache 0 2019-12-18 17:34 5Pvideo5Nmedia19I637855801993076728-1570660531011
-rw------- 1 u0_a16 u0_a16_cache 0 2019-12-18 17:34 5Pvideo5Nmedia20I4589217858447806657-1570753081747
-rw------- 1 u0_a16 u0_a16_cache 0 2019-12-18 17:34 5Pvideo5Nmedia20I5819926639731977934-1570751273785
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:50 .
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:50 .
-rw------- 1 u0_a16 u0_a16_cache 24641 2019-12-18 17:50 07e11acfb6ad0a8825abe06d691f5a7c
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 Crash Reports
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 Crashpad
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 SafeBrowsing
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 attachments
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 completed
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 new
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 pending
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
drwx--S--- 4 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 HTTP Cache
drwx--S--- 6 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 4 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 .
-rw------- 1 u0_a16 u0_a16_cache 109082 2019-12-18 17:34 d495fa4a78df46ba_0
-rw------- 1 u0_a16 u0_a16_cache 5555 2019-12-18 17:34 dfe6b2497a7513ba_0
-rw------- 1 u0_a16 u0_a16_cache 24 2019-12-18 17:34 index
drwx--S--- 4 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
drwx--S--- 4 u0_a16 u0_a16_cache 4096 2019-12-18 17:34 ..
-rw------- 1 u0_a16 u0_a16_cache 280 2019-12-18 17:34 6aaed60636ee0201_0
-rw------- 1 u0_a16 u0_a16_cache 24 2019-12-18 17:34 index
drwx--x--x 3 u0_a16 u0_a16_cache 4096 2019-12-18 17:14 .
drwx--x--x 2 u0_a16 u0_a16 4096 2019-12-18 17:14 arm64
drwx--x--x 2 u0_a16 u0_a16 4096 2019-12-18 17:14 .
drwx--x--x 3 u0_a16 u0_a16_cache 4096 2019-12-18 17:14 ..
drwx------ 2 u0_a16 u0_a16 4096 2019-12-18 17:34 leveldb
drwx------ 2 u0_a16 u0_a16 4096 2019-12-18 17:34 .
-rw------- 1 u0_a16 u0_a16 322 2019-12-18 17:34 LOG
drwx--S--- 2 u0_a305 u0_a305_cache 122880 2019-12-18 17:14 picasso-cache
drwx--S--- 2 u0_a305 u0_a305_cache 122880 2019-12-18 17:14 .
-rw-rw---- 1 u0_a190 u0_a190 2511 2019-12-18 17:02 com.google.android.gms.appid.xml
-rw-rw---- 1 u0_a190 u0_a190 168 2019-12-18 17:02 io.fabric.sdk.android:fabric:io.fabric.sdk.android.l.xml
-rw------- 1 u0_a190 u0_a190_cache 917285 2019-12-18 17:07 ded7ae5db1953d37df58cda73b06c144b288976c03223f6912a34c6b5180e8a2.0
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 cache
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 .
drwx--S--- 4 u0_a143 u0_a143_cache 53248 2019-12-18 17:14 org.chromium.android_webview
drwx--S--- 2 u0_a143 u0_a143_cache 24576 2019-12-18 17:14 picasso-cache
drwx--S--- 3 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 WebView
drwx--S--- 4 u0_a143 u0_a143_cache 53248 2019-12-18 17:14 .
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwx--S--- 4 u0_a143 u0_a143_cache 53248 2019-12-18 17:14 ..
drwx--S--- 3 u0_a143 u0_a143_cache 8192 2019-12-18 17:14 js
drwx--S--- 4 u0_a143 u0_a143_cache 53248 2019-12-18 17:14 ..
drwx--S--- 3 u0_a143 u0_a143_cache 8192 2019-12-18 17:14 .
drwx--S--- 3 u0_a143 u0_a143_cache 8192 2019-12-18 17:14 ..
drwx--S--- 2 u0_a143 u0_a143_cache 24576 2019-12-18 17:14 .
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwx--S--- 3 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 .
drwx--S--- 2 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 Crashpad
drwx--S--- 2 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 .
drwx--S--- 3 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwxrws--x 10 u0_a143 u0_a143_cache 4096 2019-12-18 17:14 ..
drwxrws--x 7 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 cache
drwx--S--- 2 u0_a118 u0_a118_cache 12288 2019-12-18 17:14 fragment
drwx--S--- 2 u0_a118 u0_a118_cache 8192 2019-12-18 17:14 header
drwx--S--- 2 u0_a118 u0_a118_cache 28672 2019-12-18 17:14 volley
drwx--S--- 2 u0_a118 u0_a118_cache 20480 2019-12-18 17:14 downloads
drwxrws--x 7 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 .
drwx--S--- 3 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 cronet
drwx--S--- 2 u0_a118 u0_a118_cache 12288 2019-12-18 17:14 .
drwxrws--x 7 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 ..
drwx--S--- 2 u0_a118 u0_a118_cache 8192 2019-12-18 17:14 .
drwxrws--x 7 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 ..
drwx--S--- 2 u0_a118 u0_a118_cache 28672 2019-12-18 17:14 .
drwxrws--x 7 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 ..
drwx--S--- 2 u0_a118 u0_a118_cache 20480 2019-12-18 17:14 .
drwxrws--x 7 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 ..
drwx--S--- 3 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 .
drwxrws--x 7 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 ..
drwx--S--- 3 u0_a118 u0_a118_cache 4096 2019-12-18 17:14 ..
-rw-rw---- 1 u0_a139 u0_a139 2513 2019-12-18 17:34 com.google.android.gms.appid.xml
-rw-rw---- 1 u0_a139 u0_a139 411 2019-12-18 17:33 FBAdPrefs.xml
-rw-rw---- 1 u0_a139 u0_a139 168 2019-12-18 17:33 io.fabric.sdk.android:fabric:io.fabric.sdk.android.l.xml
-rw------- 1 u0_a139 u0_a139_cache 49670 2019-12-18 17:34 20f9fcfcbe9fdb98_0
-rw------- 1 u0_a139 u0_a139_cache 109037 2019-12-18 17:34 f038e94cb33282ab_0
-rw------- 1 u0_a139 u0_a139 4885 2019-12-18 17:34 variations_seed
-rw------- 1 u0_a139 u0_a139 0 2019-12-18 17:34 variations_stamp
-rw------- 1 u0_a139 u0_a139 1467 2019-12-18 17:33 com.crashlytics.settings.json
drwxrwxr-x 3 media_rw u0_a20187 4096 2019-12-18 17:07 files
drwxrwxr-x 3 media_rw u0_a20187 4096 2019-12-18 17:07 .
drwxrwxr-x 3 media_rw u0_a20187 4096 2019-12-18 17:07 ..
drwxrwxr-x 3 media_rw u0_a20187 4096 2019-12-18 17:07 playlists
drwxrwxr-x 3 media_rw u0_a20187 4096 2019-12-18 17:07 .
drwxrwxr-x 2 media_rw u0_a20187 4096 2019-12-18 17:07 1576685265
drwxrwxr-x 2 media_rw u0_a20187 4096 2019-12-18 17:07 .
drwxrwxr-x 3 media_rw u0_a20187 4096 2019-12-18 17:07 ..
drwxrws--x 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:22 cache
drwxrws--x 2 u0_a16 u0_a16_cache 4096 2019-12-18 17:22 .
-rw------- 1 u0_a16 u0_a16_cache 0 2019-12-18 17:22 .lib.lock
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 files
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 .
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 ..
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 playlists
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 .
drwxrwx--x 2 u0_a187 sdcard_rw 4096 2019-12-18 17:07 1576685265
drwxrwx--x 2 u0_a187 sdcard_rw 4096 2019-12-18 17:07 .
drwxrwx--x 3 u0_a187 sdcard_rw 4096 2019-12-18 17:07 ..
drwxr-x--- 3 u0_a187 everybody 4096 2019-12-18 17:07 files
drwxr-x--- 3 u0_a187 everybody 4096 2019-12-18 17:07 .
drwxr-x--- 3 u0_a187 everybody 4096 2019-12-18 17:07 ..
drwxr-x--- 3 u0_a187 everybody 4096 2019-12-18 17:07 playlists
drwxr-x--- 3 u0_a187 everybody 4096 2019-12-18 17:07 .
drwxr-x--- 2 u0_a187 everybody 4096 2019-12-18 17:07 1576685265
drwxr-x--- 2 u0_a187 everybody 4096 2019-12-18 17:07 .
drwxr-x--- 3 u0_a187 everybody 4096 2019-12-18 17:07 ..
drwxrwx--- 3 u0_a187 everybody 4096 2019-12-18 17:07 files
drwxrwx--- 3 u0_a187 everybody 4096 2019-12-18 17:07 .
drwxrwx--- 3 u0_a187 everybody 4096 2019-12-18 17:07 ..
drwxrwx--- 3 u0_a187 everybody 4096 2019-12-18 17:07 playlists
drwxrwx--- 3 u0_a187 everybody 4096 2019-12-18 17:07 .
drwxrwx--- 2 u0_a187 everybody 4096 2019-12-18 17:07 1576685265
drwxrwx--- 2 u0_a187 everybody 4096 2019-12-18 17:07 .
drwxrwx--- 3 u0_a187 everybody 4096 2019-12-18 17:07 ..
Also, I found different files into /data/system/dropbox folder (I think it's not referring to Dropbox cloud service because I didn't have it installed) created that same day and called like '[email protected]' and 'platform_stats_bookmarks.lost'. What they do refer to?
I would be so grateful to any help, my goal is to recover even a small portion of that video but if I can't at least I'd like to understand what happened under the hood to avoid it in the future..
Related
I tried to create my own edify_defs file to cook my own roms, but every time I try to flash the zip it fails because of that file it's not well. I don't know how to adapt it for my device. I tried to follow the template and other tutorials but it fails too.
Can anyone help me to create this file?
I attach some info:
recovery.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/bootimg /bootimg emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/dev/uboot /uboot emmc defaults defaults
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto vfat defaults voldmanaged=sdcard1:auto
Code:
~ # ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Oct 19 01:35 boot
drwxr-xr-x 2 root root 0 Oct 19 01:35 cache
drwxrwx--x 26 system system 4096 Oct 19 01:14 data
drwxr-xr-x 2 root root 0 Oct 19 01:35 datadata
-rwx------ 1 400 401 1618 Sep 24 20:19 default.prop
drwxr-xr-x 10 root root 3120 Oct 19 01:36 dev
drwxr-xr-x 2 root root 0 Oct 19 01:35 emmc
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p7
drwx------ 2 400 401 0 Oct 19 01:44 etc
drwxr-xr-x 2 root root 0 Oct 19 01:35 external_sd
-rwx------ 1 400 401 27410 Sep 24 20:19 file_contexts
-rwx------ 1 400 401 975 Sep 24 20:19 fstab.mt8127
-rwx------ 1 400 401 187840 Sep 24 20:19 init
-rwx------ 1 400 401 3151 Sep 24 20:19 init.rc
drwxr-xr-x 2 root root 0 Oct 19 01:35 internal_sd
drwxrwxr-x 5 root system 0 Oct 19 01:35 mnt
dr-xr-xr-x 108 root root 0 Jan 1 1970 proc
-rwx------ 1 400 401 2201 Sep 24 20:19 property_contexts
drwxr-xr-x 2 root root 0 Oct 19 01:35 recovery
drwx------ 3 400 401 0 Sep 24 20:19 res
drwx------ 2 root root 0 Aug 13 16:33 root
drwx------ 3 400 401 0 Sep 24 20:19 sbin
drwxr-xr-x 2 root root 0 Oct 19 01:35 sd-ext
lrwxrwxrwx 1 root root 13 Oct 19 01:35 sdcard -> /data/media/0
-rwx------ 1 400 401 663 Sep 24 20:19 seapp_contexts
-rwx------ 1 400 401 75012 Sep 24 20:19 sepolicy
d---r-x--- 3 root sdcard_r 60 Oct 19 01:35 storage
dr-xr-xr-x 17 root root 0 Oct 19 01:35 sys
drwxr-xr-x 3 400 401 0 Sep 24 20:19 system
drwxrwxr-x 2 root shell 140 Oct 19 01:38 tmp
-rwx------ 1 400 401 7275 Sep 24 20:19 ueventd.rc
Code:
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1017272 160 1017112 0% /dev
tmpfs 1017272 276 1016996 0% /tmp
tmpfs 1017272 0 1017272 0% /storage
tmpfs 1017272 0 1017272 0% /mnt/secure
tmpfs 1017272 0 1017272 0% /mnt/fuse
/[email protected] 28194832 7112272 21082560 25% /data
/dev/block/vold/179:97
1927480 679284 1248196 35% /storage/sdcard1
/[email protected] 1032088 662876 369212 64% /system
/[email protected] 705512 12632 692880 2% /cache
Thanks.
Hi everyone,
I was trying to flash a nightly update from cyanogen and was getting the error : CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system and so, troubleshooting the problem, I tried to extend the system partitions through the procedure I found in a thread that contained the code down bellow and I believe that was after that that I lost my recoverymode. After this I tried do full wipe and flash an earlier ROM to see if I could get the phone back and that was the last time I was able to enter in the recoverymode. Now I just have a black screen and also when I try to start my phone it took about 2 min on a black screen and then the OS starts. Besides that, all network connectivity was lost (wifi, call signal, 4g/3g) and user space-sdcard (/data partition) too (althoug it seems to be mounted). It appears that was all disabled. Without a recovery mode and internet I am completely stuck. I tried to install a cwm and a twrp through adb after install flash gordon and flashify apk but it did not worked since it cannot recognize a file inside my /data . And the idea I had to restore from rommanager apk failed in the moment it tried to connect on internet to download content.
Please help!! Follow details:
LG_E975
I did a full wipe partition / cache/ dalvik
cyanogemMod version: 11-20141115-SNAPSHOT-M12-E975
android : 4.4.4.
kernel version: 3.4.0-CM+
Code I found and ran when trying to solve CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in 2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300 repartition script"
sleep 5
reboot recovery
fi
Output from df command:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 905.8M 128.0K 905.6M 4096
/sys/fs/cgroup 905.8M 12.0K 905.8M 4096
/mnt/asec 905.8M 0.0K 905.8M 4096
/mnt/obb 905.8M 0.0K 905.8M 4096
/mnt/fuse 905.8M 0.0K 905.8M 4096
/system 1.5G 401.3M 1.1G 4096
/cache 788.4M 14.4M 774.0M 4096
/data 25.0G 271.0M 24.8G 4096
[email protected]:/ $
Output from /proc/partitions
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Output from /dev/block directory :
Code:
[email protected]:/dev/block $ ls -l
ls -l
brw------- root root 7, 0 1970-01-02 12:07 loop0
brw------- root root 7, 1 1970-01-02 12:07 loop1
brw------- root root 7, 2 1970-01-02 12:07 loop2
brw------- root root 7, 3 1970-01-02 12:07 loop3
brw------- root root 7, 4 1970-01-02 12:07 loop4
brw------- root root 7, 5 1970-01-02 12:07 loop5
brw------- root root 7, 6 1970-01-02 12:07 loop6
brw------- root root 7, 7 1970-01-02 12:07 loop7
brw------- root root 179, 0 1970-01-02 12:07 mmcblk0
brw------- root root 179, 1 1970-01-02 12:07 mmcblk0p1
brw------- root root 179, 10 1970-01-02 12:07 mmcblk0p10
brw------- root root 179, 11 1970-01-02 12:07 mmcblk0p11
brw-rw---- system system 179, 12 1970-01-02 12:07 mmcblk0p12
brw-rw---- system system 179, 13 1970-01-02 12:07 mmcblk0p13
brw-rw---- system system 179, 14 1970-01-02 12:07 mmcblk0p14
brw------- root root 179, 15 1970-01-02 12:07 mmcblk0p15
brw------- root root 179, 16 1970-01-02 12:07 mmcblk0p16
brw------- root root 179, 17 1970-01-02 12:07 mmcblk0p17
brw-rw---- root system 179, 18 1970-01-02 12:07 mmcblk0p18
brw------- root root 179, 19 1970-01-02 12:07 mmcblk0p19
brw------- root root 179, 2 1970-01-02 12:07 mmcblk0p2
brw------- root root 179, 20 1970-01-02 12:07 mmcblk0p20
brw------- root root 179, 21 1970-01-02 12:07 mmcblk0p21
brw------- root root 179, 22 1970-01-02 12:07 mmcblk0p22
brw------- root root 179, 23 1970-01-02 12:07 mmcblk0p23
brw------- root root 179, 24 1970-01-02 12:07 mmcblk0p24
brw------- root root 179, 27 1970-01-02 12:07 mmcblk0p27
brw------- root root 179, 28 1970-01-02 12:07 mmcblk0p28
brw------- root root 179, 29 1970-01-02 12:07 mmcblk0p29
brw------- root root 179, 3 1970-01-02 12:07 mmcblk0p3
brw------- root root 179, 30 1970-01-02 12:07 mmcblk0p30
brw------- root root 179, 31 1970-01-02 12:07 mmcblk0p31
brw------- root root 259, 0 1970-01-02 12:07 mmcblk0p32
brw------- root root 259, 1 1970-01-02 12:07 mmcblk0p33
brw------- root root 259, 2 1970-01-02 12:07 mmcblk0p34
brw------- root root 259, 3 1970-01-02 12:07 mmcblk0p35
brw------- root root 179, 4 1970-01-02 12:07 mmcblk0p4
brw------- root root 179, 5 1970-01-02 12:07 mmcblk0p5
brw------- root root 179, 6 1970-01-02 12:07 mmcblk0p6
brw------- root root 179, 7 1970-01-02 12:07 mmcblk0p7
brw-rw---- system system 179, 8 1970-01-02 12:07 mmcblk0p8
brw-rw---- system system 179, 9 1970-01-02 12:07 mmcblk0p9
drwxr-xr-x root root 1970-01-02 12:07 platform
brw------- root root 1, 0 1970-01-02 12:07 ram0
brw------- root root 1, 1 1970-01-02 12:07 ram1
brw------- root root 1, 10 1970-01-02 12:07 ram10
brw------- root root 1, 11 1970-01-02 12:07 ram11
brw------- root root 1, 12 1970-01-02 12:07 ram12
brw------- root root 1, 13 1970-01-02 12:07 ram13
brw------- root root 1, 14 1970-01-02 12:07 ram14
brw------- root root 1, 15 1970-01-02 12:07 ram15
brw------- root root 1, 2 1970-01-02 12:07 ram2
brw------- root root 1, 3 1970-01-02 12:07 ram3
brw------- root root 1, 4 1970-01-02 12:07 ram4
brw------- root root 1, 5 1970-01-02 12:07 ram5
brw------- root root 1, 6 1970-01-02 12:07 ram6
brw------- root root 1, 7 1970-01-02 12:07 ram7
brw------- root root 1, 8 1970-01-02 12:07 ram8
brw------- root root 1, 9 1970-01-02 12:07 ram9
drwx------ root root 1970-01-02 12:09 vold
[email protected]:/dev/block $
Output from cat /proc/mounts :
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
Hi,
I had to wipe /data and am now struggling with restoring the data of the Threema app.
Similar to the other apps, I installed it, started it once and copied back the directories databases, files and shared_prefs under /data/data/ch.threema.app/. After adapting ownership using chown, it now looks like this (directories "." and ".." omitted):
Code:
[email protected]:/data/data/ch.threema.app # ls -la
drwxrwx--x 2 u0_a87 u0_a87 4096 2016-01-11 18:44 cache
drwxrwx--x 2 u0_a87 u0_a87 4096 2016-01-12 19:11 code_cache
drwx------ 2 u0_a87 u0_a87 4096 2016-01-11 18:44 databases
drwxrwx--x 3 u0_a87 u0_a87 4096 2016-01-12 18:02 files
lrwxrwxrwx 1 root root 34 2016-01-12 19:32 lib -> /data/app/ch.threema.app-1/lib/arm
drwxrwx--x 2 u0_a87 u0_a87 4096 2016-01-12 19:11 shared_prefs
subdirectories:
Code:
[email protected]:/data/data/ch.threema.app # ls -la databases/
-rw------- 1 u0_a87 u0_a87 943104 2016-01-11 18:45 threema.db
[email protected]:/data/data/ch.threema.app # ls -la files/
-rw------- 1 u0_a87 u0_a87 64 2016-01-12 18:02 .crs-private_key
drwx------ 2 u0_a87 u0_a87 4096 2016-01-11 18:44 icu
-rw------- 1 u0_a87 u0_a87 45 2016-01-11 18:48 key.dat
-rw------- 1 u0_a87 u0_a87 32 2016-01-12 19:18 msgqueue.ser
[email protected]:/data/data/ch.threema.app # ls -la shared_prefs/
-rw-rw---- 1 u0_a87 u0_a87 130 2016-01-11 18:44 _has_set_default_values.xml
-rw-rw---- 1 u0_a87 u0_a87 2681 2016-01-12 19:11 ch.threema.app_preferences.xml
When I start Threema, I am asked for my passphrase (which is accepted). As next step, I'm asked to create a new ID or restore from backup.
How can I restore my Threema account (optionally including the messages from a /data backup).
I am running CyanogenMod 13.0
Thanks in advance!
With all data copied back and after starting threema and entering my passphrase, I started the restore process from my ID backup that I created long time ago. This worked and I then also had access to all previous messages.
hello , i can't root on u7 no matter cui4 3 or 2 , when i enter fastboot from the recovery bootloader all it says is entering fastboot mode... , and i can't flash anything it will just stuck on sending... , is it only me? or the root files aren't made for the international variant?
edit: systemless root rights(not sure if it does work at all) with the modified magisk , is downgrading possible?
127|:/ # sysrw
/system/bin/sh: sysrw: inaccessible or not found
127|:/ # cd system
:/system # ls -l
total 14692
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 apex
drwxr-xr-x 101 root root 4096 2008-12-31 17:00 app
drwxr-x--x 4 root shell 13180 2021-10-28 19:57 bin
-rw------- 1 root root 3486 2008-12-31 17:00 build.prop
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 cameradata
drwxr-xr-x 18 root root 4096 2021-10-28 19:54 etc
drwxr-xr-x 2 root root 12288 2008-12-31 17:00 fonts
drwxr-xr-x 5 root root 4096 2008-12-31 17:00 framework
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 hidden
-rw-r--r-- 1 root root 34 2008-12-31 17:00 info.extra
drwxr-xr-x 5 root root 24576 2008-12-31 17:00 lib
drwxr-xr-x 6 root root 28672 2008-12-31 17:00 lib64
-rw-r--r-- 1 root root 280 2008-12-31 17:00 lkm_sec_info
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 media
drwxr-xr-x 169 root root 4096 2008-12-31 17:00 priv-app
lrw-r--r-- 1 root root 8 2008-12-31 17:00 product -> /product
-rw-r--r-- 1 root root 14897702 2008-12-31 17:00 recovery-from-boot.pdrwxr-xr-x 5 root root 4096 2008-12-31 17:00 saiv
drwxr-xr-x 4 root root 4096 2008-12-31 17:00 system_ext
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 tee
-rw-r--r-- 1 root root 257 2008-12-31 17:00 tima_measurement_info
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 tts
drwxr-xr-x 7 root root 4096 2008-12-31 17:00 usr
lrw-r--r-- 1 root root 7 2008-12-31 17:00 vendor -> /vendor
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 vramdiskddata
:/system #
Hi, i am trying to dump the boot.img from a Huawei P Smart to flash it in another phone of the same model whose boot.img has been corrupted.
So most of the tutorials i have found on internet suggest to use this command:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
The problem is that there isn't any device named boot in the by-name directory, so i get a no such file or directory error.
I have also seen some tutorials checking the /proc/mtd file, but it is empty.
Help
You're probably A/B. Did you check for boot_a and boot_b?
Are you rooted? You need that for dd.
Renate said:
You're probably A/B. Did you check for boot_a and boot_b?
Are you rooted? You need that for dd.
Click to expand...
Click to collapse
What means being A/B? Is boot_a or b in the same directory of the normal boot image? I am not rooted because when i flashed the Magisk zip the boot.img got corrupted, so i want to make a backup boot.img first.
I don't know if this can help but I used the PotatoNV method to unlock the bootloader and when I selected the Kirin version i selected 65x (B).
This is the error i am getting in my phone: https://forum.xda-developers.com/t/...mode-after-flashing-magisk-from-twrp.4535311/
Edit: I have checked the by-name directory but there isn't neither boot_a nor boot_b, the only device which starts with boot is bootfail_info.
Renate said:
You're probably A/B. Did you check for boot_a and boot_b?
Are you rooted? You need that for dd.
Click to expand...
Click to collapse
I have made a list of all the files in the /dev/block/bootdevice/by-name/ directory: https://pastebin.com/6VXpNWeM
read Huawei section (deleted)
https://web.archive.org/web/20200922111028/https://topjohnwu.github.io/Magisk/install.html
aIecxs said:
read Huawei section
Installation
A Magic Mask to Alter Android System Systemless-ly
web.archive.org
Click to expand...
Click to collapse
Yes so I should find an update for the FIG-LX1 and extract a boot image from it.
The problem is that i have downloaded the update from Huawei Firmware, but inside i have found another phone model. (FIG-L31 if i remember well, are them the same thing?)
aIecxs said:
read Huawei section
Installation
A Magic Mask to Alter Android System Systemless-ly
web.archive.org
Click to expand...
Click to collapse
I have downloaded the Huawei Update Extractor to extract the .app file.
I am assuming that FIG-LX1 and LA1 are the same thing.
So what should i extract from that file?
In the update i have downloaded, in the dload directory there are FIG-L31_hw_eu and a file named update_sd.zip
aIecxs said:
read Huawei section (deleted)
https://web.archive.org/web/20200922111028/https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
So i have found the UPDATE.APP file in update_sd.zip, i have extracted it and now i am trying to open it in the update extractor.
I have got this error (Profile set to Unknown (worstenbrood)):
RECOVERY_RAMDIS.img: invalid header crc - Expected: 21611 Got: 49278
aIecxs said:
read Huawei section (deleted)
https://web.archive.org/web/20200922111028/https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Ok, solved it by disabling verifications in the Huawei Update Extractor settings.
LOL skipping checksum won't solve the issue. why don't you dump ramdisk.img off device with IDT Flash Tool?
if you post output of /proc/partitions we may able to help identify ramdisk partition.
Code:
# cat /proc/partitions
aIecxs said:
LOL skipping checksum won't solve the issue. why don't you dump ramdisk.img off device with IDT Flash Tool?
Click to expand...
Click to collapse
Now the Update Extractor works. And why should i extract ramdisk?
aIecxs said:
LOL skipping checksum won't solve the issue. why don't you dump ramdisk.img off device with IDT Flash Tool?
if you post output of /proc/partitions we may able to help identify ramdisk partition.
Code:
# cat /proc/partitions
Click to expand...
Click to collapse
Is it possible to use adb from TWRP? Because I cant paste it here if i run the command from the TWRP terminal.
yes official TWRP has adb root enabled by default. on terminal you can redirect output > to file
Code:
# cat /proc/partitions > /external_sd/partitions.txt
aIecxs said:
yes official TWRP has adb root enabled by default. on terminal you can redirect output > to file
Click to expand...
Click to collapse
This is the output:
Code:
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
179 0 30535680 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 2048 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 47104 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 12288 mmcblk0p27
179 28 24576 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 16384 mmcblk0p30
179 31 24576 mmcblk0p31
179 32 12288 mmcblk0p32
179 33 32768 mmcblk0p33
179 34 16384 mmcblk0p34
179 35 28672 mmcblk0p35
179 36 4096 mmcblk0p36
179 37 98304 mmcblk0p37
179 38 1024 mmcblk0p38
179 39 1024 mmcblk0p39
179 40 12288 mmcblk0p40
179 41 16384 mmcblk0p41
179 42 4096 mmcblk0p42
179 43 131072 mmcblk0p43
179 44 131072 mmcblk0p44
179 45 2048 mmcblk0p45
179 46 2048 mmcblk0p46
179 47 4096 mmcblk0p47
259 0 32768 mmcblk0p48
259 1 2048 mmcblk0p49
259 2 16384 mmcblk0p50
259 3 30720 mmcblk0p51
259 4 2367488 mmcblk0p52
259 5 1130496 mmcblk0p53
259 6 32768 mmcblk0p54
259 7 139264 mmcblk0p55
259 8 32768 mmcblk0p56
259 9 598016 mmcblk0p57
259 10 548864 mmcblk0p58
259 11 24637440 mmcblk0p59
179 144 4096 mmcblk0rpmb
179 96 4096 mmcblk0boot1
179 48 4096 mmcblk0boot0
aIecxs said:
yes official TWRP has adb root enabled by default. on terminal you can redirect output > to file
Code:
# cat /proc/partitions > /external_sd/partitions.txt
Click to expand...
Click to collapse
But will I be able to fix the other phone by flashing the ramdisk?
I attach the magisk that bricked it.
slx23 said:
I have made a list of all the files in the /dev/block/bootdevice/by-name/ directory: https://pastebin.com/6VXpNWeM
Click to expand...
Click to collapse
Code:
# ls -l /dev/block/bootdevice/by-name/* > /external_sd/names.txt
aIecxs said:
Code:
# ls -l /dev/block/bootdevice/by-name/* > /external_sd/names.txt
Click to expand...
Click to collapse
Output:
Code:
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/bootfail_info -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/cache -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/cust -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/dfx -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/dto -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/dts -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/eng_system -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/eng_vendor -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_kernel -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_ramdisk -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_vbmeta -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/hisitest0 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/hisitest1 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/hisitest2 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/kernel -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modem_fw -> /dev/block/mmcblk0p37lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modem_om -> /dev/block/mmcblk0p18lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modem_secure -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/odm -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/patch -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/preas -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/preavs -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/preload -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/product -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/recovery_ramdisk -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/recovery_vbmeta -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/recovery_vendor -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved3 -> /dev/block/mmcblk0p9lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved9 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/rrecord -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/system -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/userdata -> /dev/block/mmcblk0p59lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/vbmeta -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/vendor -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/version -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/vrl_backup -> /dev/block/mmcblk0p2
aIecxs said:
Code:
# ls -l /dev/block/bootdevice/by-name/* > /external_sd/names.txt
Click to expand...
Click to collapse
And how should i flash magisk if there isnt a boot image?
"boot" = kernel + ramdisk
I would expect there exist any 32768 KB mmcblk0p? partition for ramdisk, but seems that device doesn't have ramdisk in "boot" and therefore no separate ramdisk partition at all.
so what you're looking for is kernel.img (without ramdisk)
for rooting with Magisk you need to patch twrp.img, flash to recovery_ramdisk (mmcblk0p33) and boot into recovery all the time.
aIecxs said:
"boot" = kernel + ramdisk
I would expect there exist any 32768 KB mmcblk0p? partition for ramdisk, but seems that device doesn't have ramdisk in "boot" and therefore no separate ramdisk partition at all.
so what you're looking for is kernel.img (without ramdisk)
for rooting with Magisk you need to patch twrp.img, flash to recovery_ramdisk (mmcblk0p33) and boot into recovery all the time.
Click to expand...
Click to collapse
So wait, to unbrick that phone i have to flash the kernel.img?
And what do you mean with booting to recovery every time?
Also what that magisk zip patched if there isn't a boot image?