I just noticed this a week ago and I'm not sure when it started but it was probably after updating to 2.3.3. The thing is that those radio dumps won't stop popping up on my external storage and I have no clue where they are coming from. Does anyone know anything about this?
Here is my ls -l | grep radio output:
Code:
----rwxr-x system sdcard_rw 38797312 2011-02-18 15:59 radio_dump_20110218145859.bin
----rwxr-x system sdcard_rw 38797312 2011-02-27 14:04 radio_dump_20110227130433.bin
----rwxr-x system sdcard_rw 38797312 2011-03-02 04:34 radio_dump_20110302033352.bin
----rwxr-x system sdcard_rw 38797312 2011-03-02 08:00 radio_dump_20110302080036.bin
----rwxr-x system sdcard_rw 38797312 2011-03-02 08:01 radio_dump_20110302080054.bin
----rwxr-x system sdcard_rw 38797312 2011-03-02 14:26 radio_dump_20110302132613.bin
----rwxr-x system sdcard_rw 38797312 2011-03-02 14:26 radio_dump_20110302132637.bin
----rwxr-x system sdcard_rw 38797312 2011-03-02 23:35 radio_dump_20110302233522.bin
----rwxr-x system sdcard_rw 38797312 2011-03-03 20:29 radio_dump_20110303192938.bin
----rwxr-x system sdcard_rw 38797312 2011-03-03 20:30 radio_dump_20110303193002.bin
----rwxr-x system sdcard_rw 38797312 2011-03-04 16:05 radio_dump_20110304160539.bin
----rwxr-x system sdcard_rw 38797312 2011-03-04 16:06 radio_dump_20110304160602.bin
----rwxr-x system sdcard_rw 38797312 2011-03-05 10:08 radio_dump_20110305100750.bin
----rwxr-x system sdcard_rw 38797312 2011-03-05 13:01 radio_dump_20110305130150.bin
----rwxr-x system sdcard_rw 38797312 2011-03-05 13:02 radio_dump_20110305130208.bin
----rwxr-x system sdcard_rw 38797312 2011-03-05 15:22 radio_dump_20110305152245.bin
----rwxr-x system sdcard_rw 38797312 2011-03-05 15:23 radio_dump_20110305152301.bin
----rwxr-x system sdcard_rw 38797312 2011-03-06 20:08 radio_dump_20110306190802.bin
----rwxr-x system sdcard_rw 38797312 2011-03-10 14:44 radio_dump_20110310134436.bin
----rwxr-x system sdcard_rw 38797312 2011-03-10 14:45 radio_dump_20110310134455.bin
----rwxr-x system sdcard_rw 30973952 2011-03-11 17:47 radio_dump_20110311174713.bin
----rwxr-x system sdcard_rw 38797312 2011-03-12 20:27 radio_dump_20110312202656.bin
----rwxr-x system sdcard_rw 38797312 2011-03-14 03:28 radio_dump_20110314032801.bin
----rwxr-x system sdcard_rw 38797312 2011-03-15 08:10 radio_dump_20110315080959.bin
----rwxr-x system sdcard_rw 38797312 2011-03-15 10:31 radio_dump_20110315103138.bin
----rwxr-x system sdcard_rw 38797312 2011-03-15 10:32 radio_dump_20110315103159.bin
I get them from time to time. Think it happens when I use a internet radio app. I just delete them
jerrycycle said:
I get them from time to time. Think it happens when I use a internet radio app. I just delete them
Click to expand...
Click to collapse
... i dont use internet radios and I get them (not as much now), the word "radio" doesnt mean radio. radio is a baseband, im not even sure why they drop there but just delete them.
zephiK said:
... i dont use internet radios and I get them (not as much now), the word "radio" doesnt mean radio. radio is a baseband, im not even sure why they drop there but just delete them.
Click to expand...
Click to collapse
i get them every once in a while too, they are kinda mysterious. i just delete them.
{
"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"
}
As stated by Kevan19 in another post:
"There was a thread about this before and if memory serves me, the belief was that these files were created when your cell radio "dies" from being out of service. I had a few of these on my phone from before I started using NoBars and since then have had none created. "
So, go on and delete them, it´s ok.
gasparzim said:
As stated by Kevan19 in another post:
"There was a thread about this before and if memory serves me, the belief was that these files were created when your cell radio "dies" from being out of service. I had a few of these on my phone from before I started using NoBars and since then have had none created. "
So, go on and delete them, it´s ok.
Click to expand...
Click to collapse
That is pretty much what I suspected but it is weird that they only started to show up on ny phone after updating to 2.3.3. Maybe some kind of debug option that is enabled?
Sent from my Nexus S using XDA App
nicholasbgr said:
That is pretty much what I suspected but it is weird that they only started to show up on ny phone after updating to 2.3.3. Maybe some kind of debug option that is enabled?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If it´s a debug option, I never found where to disable it. In my case, I used to have those files on 2.3.2, never happened on 2.3.3.
Related
Cyanogenmod 7 for the Lenovo Ideapad A1, by Milaq and myself.
BEFORE YOU BEGIN
You should install the modified bootloader that allows you to get into fastboot mode if necessary. This is because there is only one kernel on the A1, and if the kernel causes problems (unlikely, but it's better save yourself the risk) you won't be able to boot normally or into recovery. Being able to boot into fastboot mode gives you a way out of this by allowing you to flash a kernel through usb with the fastboot command. See this post: http://forum.xda-developers.com/showpost.php?p=25186171&postcount=120
Simple installation guide
David Artiss has written a beginners' guide that walks you through the process of installing CM7 starting from the stock system. Get to it here:
http://www.artiss.co.uk/2012/04/installing-cyanogenmod-on-a-lenovo-ideapad-a1
Syncing and building it:
Clone the Cyanogenmod repository:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
Then add the local manifest:
Code:
git clone https://github.com/milaq/android.git local-android
cd local-android
git checkout gingerbread
cd ..
cp local-android/local_manifest.xml android/.repo
They sync the repo, get rom manager, and build:
Code:
cd android
repo sync
./vendor/cyanogen/get-rommanager
source build/envsetup.sh && brunch A1_07
What works:
Graphics HW acceleration
Touchscreen
Buttons (vol, power, menu, back, home)
Removable SD card
Audio
Accelerometer
Wifi (see caveat below)
Bluetooth
Vibration
Internal SD card
Front and back camera for still images, video recording from back camera
GPS
HW accelerated decoding (h.264 etc)
Issues
No 3G on the 3G versions.
Video recording from the front camera
Accelerometer switch not working
Market gives phone layout instead of tablet layout after update
Modified partition layout used with CWM 5.0.2.8 seems to prevent the internal SD card mounting.
GPS Time from android.location.Location.getTime() is wrong (1 day ahead?).
DSPManager sometimes crashes when headphones are inserted.
Bluetooth file transfer doesn't work, but Bluetooth HID seems to work.
IRC Channel
#ideapad-a1 on irc.freenode.net.
Recent logs at http://shron.de/irclogs/ideapad-a1.log
Some older logs at http://shron.de/ideapad-a1.log
Download page
Nightly builds, built by Milaq and hosted by goo.im:
http://goo.im/devs/milaq/a107/cm-7
Acknowledgments
Many thanks to:
Milaq - fixing loads of things: Camera, GPS, vibration, autobrightness, cpu responsiveness, scrolling performance, wifi geolocation, disabling background blur, hiding phone signal by default, density fixes, etc, etc, ...
SpiegelEiXXL - many discussions and thoughts, setting up nightly builds, hosting nightly builds.
Pati- for spotting how to prevent the reboots and internal SD card fixes.
Templis - Channel logs
Collaboration
Please feel free to discuss this porting effort here, point out errors, fork the repositories, submit patches/pull requests etc!
Latest updates:
18 Feb: Nightly downloads added. Please follow the commit log on Github for further details of updates: https://github.com/gmarkall/android_device_ideapad_a1/commits/gingerbread
12 Feb: Fixed the 5:43 reboot issue, wifi (sort of), and accelerometer. New version on download page.
17 Jan: Got it booting, added download page.
15 Jan: Made some very hacky changes that allow an otapackage to be built.
14 Jan: Tried flashing it - so far not quite booting as far as the home screen, but does get to the boot screen.
13 Jan: I had the wrong size for the system partition, which was causing make_ext4fs to fail. This is now corrected, and the build finishes.
13 Jan: I created an IRC channel for discussion of Clockworkmod, Cyanogenmod and development on the A1. It is #ideapad-a1 on irc.freenode.net.
12 Jan: I've added a few more bits and bobs to the build - in particular editing BoardConfig.mk to include settings for building libaudio.so, using the camera stub for the time being, bluetooth settings, etc. Also added some missing files: /etc/media_profiles.xml and vold.a1.fstab, overlay.omap3.so.
11 Jan: added a script that pulls the proprietary libraries off the device and creates a vendor/lenovo/a1 folder for them.
I have a 16GB Lenovo A1 and am more than happy to help out with any testing you need with CM7!
Just drop me a PM if you want any private testing done or I will test out the moment you post a Rom here to flash.
Thanks, Charlie.
awesome! did you already try to flash and run it?
BuzzyB said:
awesome! did you already try to flash and run it?
Click to expand...
Click to collapse
Not yet. At the moment the build system doesn't quite work for making a flashable zip suitable for the ideapad. I want to get the build system to make the update.zips without any manual intervention, rather than just putting one together by hand - otherwise it will be a pain every time I change something to have to manually make a new update.zip.
BuzzyB said:
awesome! did you already try to flash and run it?
Click to expand...
Click to collapse
I tried flashing it - I'm not quite getting as far as the home screen in booting yet, but it's a start:
{
"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"
}
nice teaser
Awesome!!!
Simply wonderful!
Update
something new...
:sehorn:
Cool beans!
So with the latest version I have, after bootup there's some problems with dalvik-cache.
The files in /cache/dalvik-cache and their permissions are:
Code:
# ls -l
-rw-r--r-- 1 system system 850744 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 57112 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 232920 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 27960 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 266000 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 194352 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 13880 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 778656 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 7448 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 24128 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 root root 4798600 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 root root 1391096 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 root root 8087736 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 6816 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 4504 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 61616 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 89720 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 28496 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 1638216 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 147728 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 8496 Aug 1 2008 [email protected]@[email protected]
Logcat is at: http://www.doc.ic.ac.uk/~grm08/ideapad/cm7-a1-logcat-jan-17.txt
Any suggestions?
Did you try to chmod 777 /cache/dalvik-cache
Just for testing it?
OTA use data/dalvik-cache and have the same File right like you do.
# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770
mkdir /cache/lost+found 0770
---------- Post added at 09:47 PM ---------- Previous post was at 09:35 PM ----------
What rights have your /cache/dalvik-cache Folder?
It schould have 771
But i think that /cache have only 770
xbdesign said:
Did you try to chmod 777 /cache/dalvik-cache
Just for testing it?
Click to expand...
Click to collapse
I did try that, but it didn't make any difference unfortunately.
So what rights you have now for that Folder (after/at boot)?
xbdesign said:
So what rights you have now for that Folder (after/at boot)?
Click to expand...
Click to collapse
Code:
# ls -l
drwxrwx--x 2 system system 3072 Jan 17 21:02 dalvik-cache
I just noticed that it's only things that run as app_XX that have a problem opening /cache/dalvik-cache/[email protected]@ ...
Things that run as system, e.g. com.android.settings, don't seem to have a problem.
I feel like I'm missing something obvious now!
Right,
all Positions that have root have a Problem
-rw-r--r-- 1 root root
On STOCK ROM there are no Files that have one root root.
They are all having
system system
or
system app_<AppNr>
or
system radio
xbdesign said:
Right,
all Positions that have root have a Problem
-rw-r--r-- 1 root root
Click to expand...
Click to collapse
What is the problem? Those are the same permissions as on my CM7 Desire which doesn't have this issue.
No Problem.
Just wondering why every one of them giving an Error.
I have no working CM7 to compare it to.
---------- Post added at 10:59 PM ---------- Previous post was at 10:52 PM ----------
Are you at stage where you can Wipe dalvik-cache, or it is hapening by building/restoring it?
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
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
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???
I tried using lpunpack as suggested in Extract super.img.lz4 but once it unpacked the partitions to the output directory i was not able to open the images as archives.
Could anyone explain why this is happening?
Hey please Try Crb v14.
Link:-https://forum.xda-developers.com/t/tool-windows-kitchen-crb-v3-0-0-beta14.3947779/
nilsha said:
Hey please Try Crb v14.
Link:-https://forum.xda-developers.com/t/tool-windows-kitchen-crb-v3-0-0-beta14.3947779/
Click to expand...
Click to collapse
Since it is based out of imjtool & lpunpack it is not working.
Bump
73sla said:
I tried using lpunpack as suggested in Extract super.img.lz4 but once it unpacked the partitions to the output directory i was not able to open the images as archives.
Could anyone explain why this is happening?
Click to expand...
Click to collapse
I think they are in sparse format and you need to convert them (I think the tool is called simg2img)
73sla said:
I tried using lpunpack as suggested in Extract super.img.lz4 but once it unpacked the partitions to the output directory i was not able to open the images as archives.
Could anyone explain why this is happening?
Click to expand...
Click to collapse
Now system.img vendor.img etc are f2fs and at present most common kitchen/Tools doesnt mount it. You may try Fedora linux to mount to extrcat it, someone reported it is working.
dr.ketan said:
Now system.img vendor.img etc are f2fs and at present most common kitchen/Tools doesnt mount it. You may try Fedora linux to mount to extrcat it, someone reported it is working.
Click to expand...
Click to collapse
I tried mounting in Ubuntu without success, not sure if it's different in fedora
Using partitions backup app to backup super.img, is this super.img useful?
{
"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"
}
donkeyman1234 said:
Using partitions backup app to backup super.img, is this super.img useful?
Click to expand...
Click to collapse
Nope, it will be same like one packed in stock firmware.
dr.ketan said:
Nope, it will be same like one packed in stock firmware.
Click to expand...
Click to collapse
I see.
Bump as I still need a Windows-based solution.
The 6 imgs obtained after decompressing the super.img of S22 cannot be decompressed
Extracting system.img with Python ...
Traceback (most recent call last):
ext4.MagicError: Invalid magic value in superblock: 0x0002 (expected 0xEF53)
unbutu can not mount system.img too
which tools extract contents of system.img
Bump
Hi guys, I successfully extracted super.img using SuperR's Kitchen on linux. Good luck!
I have now unpacked the boot.img. Took me some time to figure out what Sammy had done.
Haven't done this sine my S9 and a lot has changed. Unpacking the .lz4 file was no problem, giving me a boot.img, which could not be extracted using any of my current tools...
But since I work in Linux, everything is possible.
I have some special tools installed, making it possible to run Android executables in Ubuntu tetminal. So I used Sammys own Android unpack boot image command. This gave me an unpacked boot image and a ram disk.
Again things has changed, RAMDISK is no longer packed like I used to see it, I had to unpack it with a Linux cpio command.
After all this work, just to find out that RAMDISK is more or less empty, only containing the init file, a short txt file and some empty folders.
But this work was required for me before I can build a custom kernel. Because things need to packed same way again.
Regards DeHAWK
Edit: Seems like sammy is f*cking with us. Why is the SamMobile firmware 8GB...they have done something strage and I'm about to find out. Take an example; a lz4 file is 365Kb packed, but unpacked its 8MB, don't make sense. Look at the end of the lz4 packed file.
Regards DeHAWK
SkylinesHD said:
Hi guys, I successfully extracted super.img using SuperR's Kitchen on linux. Good luck!
Click to expand...
Click to collapse
have you been able to get bin files from a vendor.img that uses f2fs as file system?
1. unpack S22's super.img ，your will get 6 imgs
2.copy system.img to your s22 phone /sdcard
3.adb shell su
4.mount -o loop /sdcard/system.img /sdcard/tmp
then you can cd /sdcard/tmp ，ls -l find all files！
tomatolei said:
1. unpack S22's super.img ，your will get 6 imgs
2.copy system.img to your s22 phone /sdcard
3.adb shell su
4.mount -o loop /sdcard/system.img /sdcard/tmp
then you can cd /sdcard/tmp ，ls -l find all files！
Click to expand...
Click to collapse
mount: bad /etc/fstab: No such file or directory
when trying the mount command
E:\tar>adb shell
b0q:/ $ su
b0q:/ # mkdir /sdcard/tmp
b0q:/ # mount -o loop /sdcard/vendor.img /sdcard/tmp
'/dev/block/loop34' is read-only
b0q:/ # cd /sdcard/tmp
b0q:/sdcard/tmp # ls -l
total 28772
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 apex
drwxr-xr-x 7 root shell 4096 2021-01-01 08:00 app
drwxr-x--x 4 root shell 20480 2021-01-01 08:00 bin
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 bt_firmware
-rw------- 1 root root 14406 2021-01-01 08:00 build.prop
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 dsp
drwxr-xr-x 40 root shell 8192 2021-01-01 08:00 etc
drwxr-xr-x 6 root shell 8192 2021-01-01 08:00 firmware
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 firmware-modem
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 firmware_mnt
drwxr-xr-x 3 root shell 4096 2021-01-01 08:00 gpu
drwxr-xr-x 10 root shell 118784 2021-01-01 08:00 lib
drwxr-xr-x 8 root shell 118784 2021-01-01 08:00 lib64
lrw-r--r-- 1 root root 4 2021-01-01 08:00 odm -> /odm
drwxr-xr-x 3 root shell 4096 2021-01-01 08:00 odm_dlkm
drwxr-xr-x 8 root shell 4096 2021-01-01 08:00 overlay
-rw-r--r-- 1 root root 29118684 2021-01-01 08:00 recovery-from-boot.p
drwxr-xr-x 5 root shell 4096 2021-01-01 08:00 rfs
drwxr-xr-x 6 root shell 4096 2021-01-01 08:00 saiv
-rw-r--r-- 1 root root 39446 2021-01-01 08:00 ueventd.rc
drwxr-xr-x 3 root shell 4096 2021-01-01 08:00 usr
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 vm-system