Device: LeEco Le 2
I was using TWRP 3.0.0 and AOSP Android 7.1 uptil last week.
Last week, I flashed TWRP twrp-3.2.1-0-s2.img and ROM: AOSP Extended : https://forum.xda-developers.com/le-...-v6-0-t3841473
Guide Followed While Flashing TWRP and Magisk: https://www.guidingtech.com/59895/le...-installation/
Problem: Everything was fine until I tried Downloading an apk using chrome and it couldn't find storage/emulated/0 and none of the apps were able to access storage..
So I fired up ADB and $ adb shell gave me a list of folders with no storage folder.
~ # ls boot init.recovery.service.rc selinux_version cache init.recovery.usb.rc sepolicy charger license service_contexts data oem sideload default.prop persist supersu dev proc sys dsp property_contexts system etc recovery tmp file_contexts res twres firmware root ueventd.rc init sbin usbstorage init.rc sdcard init.recovery.hlthchrg.rc seapp_contexts
I realised I had no /storage/emulated/0 folder.
I tried reflashing the rom, it didn't make a difference. I tried flashing a different ROM, no result.
I tried to open the folder sdcard, it says 'sdcard' is not mounted.
I tried mounting it using adb but it didn't work. I tried symlinking storage/emulated/0 to sdcard, no results.
How to I get my sdcard back/mount it?
I tried format data from TWRP. I tried flashing this kernel too: https://forum.xda-developers.com/le-...-v1-0-t3677897
I tried other roms and twrp versions..
The internal sdcard just won't mount.
Any ideas on how to mount it manually using adb or something?
Related
Hey guys,
I had Dark Paranoid 2.3 with MemSwapMod on my SGS3, everything was fine. Today there was an update and i decided to do a full wipe.
So I deleted the mod, copied my files, wiped, flashed Dark Paranoid 2.5, installed the MemSwapMod and wanted to copy my files (from windows to phone). But i cant copy, evertime I got errors. then I checked permissions on sdcard0 (cause now my external SD is my internale and vice versa) and seen that they are d---rwxr-x instead of drwxrwxrwx and belongs to system:sdcard_rw. changing ownership in Terminal gives me a "operation not permitted" (IM ROOT?!?!?!?!) and changing permissions with chmod gives my no errors, but even no changes of the permissions.
any help, gues or whatever????
cheers
Nik
z0mg.jer1Cho said:
But i cant copy, evertime I got errors. then I checked permissions on sdcard0 (cause now my external SD is my internale and vice versa) and seen that they are d---rwxr-x instead of drwxrwxrwx and belongs to system:sdcard_rw. changing ownership in Terminal gives me a "operation not permitted" (IM ROOT?!?!?!?!) and changing permissions with chmod gives my no errors, but even no changes of the permissions.
any help, gues or whatever????
cheers
Nik
Click to expand...
Click to collapse
Try change it with adb shell and use adb remount to have writable phone access (need one insecure kernel or adbd insecure (by Chainfire)).
If it doesn't work, flash a stock rom and look what happened. If you can write data, your filesystem (ext4) may be broken.
Tried mount -o remount /storage/sdcard1 (flashed ROM without Mod), no succes.
Now My External is my External again, I can copy files via windows, but not on the phone itself.
Copy Files via FTP to SDCard (SolidExplorer) is working fine, too.
So my phone is in a bootloop. I flashed CWM recovery via Odin to try to mount the internal storage since i have some things i need to recover before flashing new rom. in CWM under "mounts and storage" i tried everything, but nothing would show up in a computer. Also, mounting system says "Error mounting system" and adb devices doesn't recognize my device now with CWM. it did with stock recovery though, when put in adb mode
edit: flashed original revocery, got adb working, found some adbfileexplorer.jar file from the forums, that shows my device and some files/folders, eg /efs, /preload , cache etc. so they are not the files i'm looking for.
And when writing adb shell in cmd, i get "- exec '/system/bin/sh' failed: No such file or directory (2) -" error
Try philz recovery and aroma file manager to access the data partition.
A sudden boot loop in normal use usually means one or more of the partitions are corrupt, so you may not be able to access data.
boomboomer said:
Try philz recovery and aroma file manager to access the data partition.
A sudden boot loop in normal use usually means one or more of the partitions are corrupt, so you may not be able to access data.
Click to expand...
Click to collapse
Ok well now i got to use adb and via command "adb pull /" i pulled everything there was (This is the right command to do it, right?)
but only two folders, sys and tmp were pulled, none of which contain any relevant data, it would appear
Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
*********** Restore Nabi to Factory 1.9.37 from ANDROID ****************
Install recovery to Internal or External SD card?
-If external make sure your card is installed-
1. Internal SD
2. External SD
Choose an option:1
Files are prepared. Press any key to begin restore.
Press any key to continue . . .
rebooting...
When TWRP is done booting press enter
Press any key to continue . . .
Pushing stock recovery to your device
Ignore external SD card error if you have none installed
This files are 1.2GB this will take many minutes. Please wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
mkdir: can't create directory '//data/media/TWRP/BACKUPS/0123456789ABCDEF/abcdst
ock123': No such file or directory
1332 KB/s (8388608 bytes in 6.149s)
9 KB/s (48 bytes in 0.005s)
Click to expand...
Click to collapse
jumbojimx said:
Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
Click to expand...
Click to collapse
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Thanks, got it fixed.
It was the wrong TWRP. Then I wasn't seeing any recovery files. ADB was giving me an odd generic serial number, I did a back up and then dumped the files in the TWRP created folder and they appeared.
Original Post.
aicjofs said:
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Click to expand...
Click to collapse
Thanks for the reply.
I tried all 3 versions of TWRP in your post . TWRPv263 for ICS Nothing (cache,data,system, extsdcard etc) will mount. TWRPv285 for JB&KK Everything but /system will mount.
Using all 3 versions of TWRP I tried to install 3013stock.zip and 3013bootloader. No files from the extracted zip show up in TWRP recovery tab.
So I assume the issue I am aiming at is getting /system to mount in either KK or JB version of TWRP. v285?
Click to expand...
Click to collapse
(Sorry for my english)
My phone, S3 16 GB wasn't rooted and installed custom recovery. Someday, it appears on the screen that "internal storage is damaged". So I want to backup internal storage, attempted flashing twrp and rooting the phone through CF-autoroot, but it unable to mount /data in twrp.
To create a internal memory dump, I find this article.
dfir.science/2017/04/Imaging-Android-with-root-netcat-and-dd.html
I tried to this.
adb devices
List of devices attached
4300********061 recovery
/data directory is empty.
adb shell
su
:: permission denied
I think phone isn't properly rooted. Installing a supersu.zip from twrp, it says "install failed".
adb forward tcp:8888 tcp:8888
dd if=/dev/block/mmcblk0 | busybox nc -l -p 8888
nc 127.0.0.1 8888 > android.dd
It created a dump file of 3.5 GB size on windows, although internal memory had 15 GB in use. And mounting the dump file from OSFMount is failed.
In this situation, is it possible to get a full memory dump of internal storage, specially /data partition?
--------------------
Update.
Retry dumping of /data partition, and view this dump file from testdisk in linux. It worked.
Hi all,
I'm tinkering with my OnePlus 6 and trying to backup so I can restore after I soft-brick it by removing bloatware.
I'm using OxygenOS 10.3.2 and seems that TWRP doesn't backup/restore as it should, it always bricks my phone whenever I restore /system or /data.
I'm trying to save and restore data via terminal at the moment, I mounted /system and I see I have access to dd.
Is it possible to just copy everything from /system and /data to /sdcard, move it to my pc, and whenever I brick the phone, just stock install OxygenOS 10.3.2 then TWRP and restore via terminal?
Anyone done this?
I presume the risk is low if I'm only touching /system and /data?
edit:
Managed to backup /system with DD but I don't know how to backup /data, as /data is the same device as /sdcard, and it would create a file equal to the whole partition size. I would not be able to store it on the same partition since /sdcard is basically a subfolder of /data.
Any way of backing up /data? on the same partition?
I would have tried with rsync then zip the whole thing and extract it on my pc. I know rsync keeps the file/folder permissions intact. But rsync is not available in TWRP recovery.
I tried to make a tar archive while inside /data, excluding the media folder, like this:
Code:
tar -pzcvf data.tar.gz --exclude=media *
The -p option should preserve SELinux attributes. I then copy data.tar.gz to /sdcard and pull it on my PC.
But, when I move it back, delete everything in /data except media folder, then unpack the archive and reboot, it goes into recovery.
I don't understand why wiping all files then putting them back from the archive breaks the system. What am I missing?
edit:
Apparently /data backup and restore work from TWRP modified by Mauronofrio, only the /system backup/restore is broken, but that can be done with DD from TWRP.
So my issues are solved at the moment.
mad_rock said:
I tried to make a tar archive while inside /data, excluding the media folder, like this:
Code:
tar -pzcvf data.tar.gz --exclude=media *
The -p option should preserve SELinux attributes. I then copy data.tar.gz to /sdcard and pull it on my PC.
But, when I move it back, delete everything in /data except media folder, then unpack the archive and reboot, it goes into recovery.
I don't understand why wiping all files then putting them back from the archive breaks the system. What am I missing?
edit:
Apparently /data backup and restore work from TWRP modified by Mauronofrio, only the /system backup/restore is broken, but that can be done with DD from TWRP.
So my issues are solved at the moment.
Click to expand...
Click to collapse
I'm not sure if -p is sufficient to also backup the selinux rights.
Have you tried the tar option --selinux ?
From the man1 page:
Code:
--selinux
Enable SELinux context support.