Related
Hi,
I can't mount the "sdcard" when I'm in recovery, I just get an error like this: "Unable to write to ums lunfile"
I run the latest CWM on a Galaxy Nexus GSM.
What should I do to get this working?
I am having the same issue, if I try mounting usb storage or sd card I get "Unable to write to ums lunfile"
I'm using v5.0.2.7 and I want to know if it's the version of cwm or whether it's my phone.
Help please
The phone does not support USB mass storage., therefore it will not work.
joshnichols189 said:
The phone does not support USB mass storage., therefore it will not work.
Click to expand...
Click to collapse
so how can you flash roms.. ?
What? You use MTP to put roms on the phone.
hey people, i've lost some data (precisely a file .dat that was containing all my messages) and would like to recover it, but if i can't mount USB Mass Storage how can i recover this file? Is there an app that recovers from MTP and PTP devices? thanks very very much, it's really an emergency!
Is there any way to access the internal storage whilst in CWM?
Janzomaster said:
Is there any way to access the internal storage whilst in CWM?
Click to expand...
Click to collapse
NO. I found this out a while back. Because as stated above the Nexus uses MTP and not USB to connect it is not possible to see your internal memory in CWM.
jd1001 said:
NO. I found this out a while back. Because as stated above the Nexus uses MTP and not USB to connect it is not possible to see your internal memory in CWM.
Click to expand...
Click to collapse
So, if a solution arises, it would be from the side of CWM, right?
Janzomaster said:
So, if a solution arises, it would be from the side of CWM, right?
Click to expand...
Click to collapse
I don't think so. I think it would be Google would have to allow USB support. Then CWM would work.
jd1001 said:
I don't think so. I think it would be Google would have to allow USB support. Then CWM would work.
Click to expand...
Click to collapse
Couldn't CWM "just" enable MTP support in their recovery?
Janzomaster said:
Couldn't CWM "just" enable MTP support in their recovery?
Click to expand...
Click to collapse
Maybe dude but I don't think it is that simple!
Janzomaster said:
Is there any way to access the internal storage whilst in CWM?
Click to expand...
Click to collapse
If you mean the content of /sdcard:
Shure, boot into cwm recovery, mount data and you can find all your sd card/user data via adb under /data/media/.
gokpog said:
If you mean the content of /sdcard:
Shure, boot into cwm recovery, mount data and you can find all your sd card/user data via adb under /data/media/.
Click to expand...
Click to collapse
Doesn't work!
jd1001 said:
Doesn't work!
Click to expand...
Click to collapse
It does. I'm just looking at it. Get adb in recovery working and see for yourself.
I think they're saying it doesn't work in the traditional sense. ADB does work though, as shown above
gokpog said:
It does. I'm just looking at it. Get adb in recovery working and see for yourself.
Click to expand...
Click to collapse
Sorry got that wrong, I meant in the traditional sense! Thanks though good to know this.
EddyOS said:
I think they're saying it doesn't work in the traditional sense. ADB does work though, as shown above
Click to expand...
Click to collapse
You are right, mounting as UMS doesn't work. But Janzomaster later asked "Is there any way to access the internal storage whilst in CWM?", which you can (via adb).
Well, just hitting a button and you can access the files through the explorer would have been perfect. But adb is a good alternative to have
This litte app comes in very handy: https://qtadb.wordpress.com/
GUI for adb, including file explorer -> perfect for CWM recovery
When I go to twrp recovery and try to wipe internal storage or even see whats inside the internal storage folder it says "Cannot mount internal storage". Does anyone have a fix for this?
its a bug of twrp u flashed an old version u need to flash a more recent one try the 3.2.1 version
nekos95 said:
its a bug of twrp u flashed an old version u need to flash a more recent one try the 3.2.1 version
Click to expand...
Click to collapse
It's not a bug, the data partition is encrypted. It needs to be formatted.
ashyx said:
It's not a bug, the data partition is encrypted. It needs to be formatted.
Click to expand...
Click to collapse
How do I do that if I can't format in twrp?
NreL said:
How do I do that if I can't format in twrp?
Click to expand...
Click to collapse
What's stopping you from Formatting?
ashyx said:
What's stopping you from Formatting?
Click to expand...
Click to collapse
I can't format internal storage because it's not mounted so it just says error
NreL said:
I can't format internal storage because it's not mounted so it just says error
Click to expand...
Click to collapse
Well that's the whole point. If it was mountable you wouldn't need to Format it.
Just Format it anyway, regardless of the mount errors.
I have installed android O and have TWRP installed but when i try and flash Super SU through TWRP it fails and does not root, i dont know why or if ayone else has experienced this problem on the A5 2017 but if someone has and knows how to fix it please let me know
elderwolf123 said:
I have installed android O and have TWRP installed but when i try and flash Super SU through TWRP it fails and does not root, i dont know why or if ayone else has experienced this problem on the A5 2017 but if someone has and knows how to fix it please let me know
Click to expand...
Click to collapse
47 views and no reply, come on. i had to update and reformat as my phone was playing up, i have data for work apps that i need to restore. how can an old thread about the january security update be active still yet one about the Android O update gets ignored
What error do you get while installing in twrp. send logs screenshots
Btw you have to be patient mate. It takes time for people to understand your problem and find solution
You can try magisk also if you want
jfk999 said:
What error do you get while installing in twrp. send logs screenshots
Btw you have to be patient mate. It takes time for people to understand your problem and find solution
You can try magisk also if you want
Click to expand...
Click to collapse
it wont mount data and then when it mounts it spits out an error saying it cant patch the ram disk, also i have had it too many times where i have asked a question just to have it ignored to this day
Your device is encrypted, you need to format data to decrypt device and flash root and flash the zip to disable encryption, dont know where the zip file is.
24imelqui said:
Your device is encrypted, you need to format data to decrypt device and flash root and flash the zip to disable encryption, dont know where the zip file is.
Click to expand...
Click to collapse
if i disable encryption then safety check will always fail. i didn't have to earlier but every time i delete data and try it fails saying ram disk cant be patched or restored
I have the same issue as jfk999 except having data wiped, i have tried everything i know and so far to no avail. last time i isued the no encrypt zip it broke safety net and most of my apps including the phones stability. https://forum.xda-developers.com/samsung-a-series-2017/help/root-issues-oreo-t3800852
elderwolf123 said:
I have the same issue as jfk999 except having data wiped, i have tried everything i know and so far to no avail. last time i isued the no encrypt zip it broke safety net and most of my apps including the phones stability. https://forum.xda-developers.com/samsung-a-series-2017/help/root-issues-oreo-t3800852
Click to expand...
Click to collapse
SuperSU isn't really compatible with Oreo as it needs some patches to work which it's unlikely to get.
Magisk is now the premier root solution and the most up to date for Oreo and includes the relevant patches.
ashyx said:
SuperSU isn't really compatible with Oreo as it needs some patches to work which it's unlikely to get.
Magisk is now the premier root solution and the most up to date for Oreo and includes the relevant patches.
Click to expand...
Click to collapse
I tried magisk and it failed, i must just be unlucky and also some root apps and pc programs dont like Magisk
elderwolf123 said:
I tried magisk and it failed, i must just be unlucky and also some root apps and pc programs dont like Magisk
Click to expand...
Click to collapse
Failed in what way?
If you have an app that has issues then you need to notify the developer of that app.
Failing in patching ramdisk points to possible error in boot image.You can try the method given by moozer in my post that helped me patch the boot image.I guess that would solve your problems
Also try starting from scratch..try downloading clean rom from sammobile and start over.
Hope that helps
ashyx said:
Failed in what way?
If you have an app that has issues then you need to notify the developer of that app.
Click to expand...
Click to collapse
same as Super Su, wiped data and it failed to patch the ramdisk and then it couldnt restore it, it looped my device so I had to use the Magisk uninstaller to fix it. All i have done since updating is install TWRP and tried rooting which is failing
elderwolf123 said:
same as Super Su, wiped data and it failed to patch the ramdisk and then it couldnt restore it, it looped my device so I had to use the Magisk uninstaller to fix it. All i have done since updating is install TWRP and tried rooting which is failing
Click to expand...
Click to collapse
Please post the TWRP recovery log(file only) so I can fix this.
ashyx said:
Please post the TWRP recovery log(file only) so I can fix this.
Click to expand...
Click to collapse
I tried dumping the logs but it failed, magisk sais there is already root and super SU says another error. i dont have root so i cant fix it for starters and im not wiping my phone again if i can avoid it as even with backing up my data im losing some and last thing i need is to lose a really important photo i have
elderwolf123 said:
I tried dumping the logs but it failed, magisk sais there is already root and super SU says another error. i dont have root so i cant fix it for starters and im not wiping my phone again if i can avoid it as even with backing up my data im losing some and last thing i need is to lose a really important photo i have
Click to expand...
Click to collapse
How do you mean it fails?
Just select save recovery.log and save to sd card.
ashyx said:
How do you mean it fails?
Just select save recovery.log and save to sd card.
Click to expand...
Click to collapse
i did that and the logs didnt save
elderwolf123 said:
i did that and the logs didnt save
Click to expand...
Click to collapse
When i do it my phone picks up the main storage as an SD and always has then there is the Micro SD. it tries mounting the data partition to copy it but it fails
elderwolf123 said:
When i do it my phone picks up the main storage as an SD and always has then there is the Micro SD. it tries mounting the data partition to copy it but it fails
Click to expand...
Click to collapse
That's why I said save to micro sd card. Just select micro sd as default storage then save.
ashyx said:
That's why I said save to micro sd card. Just select micro sd as default storage then save.
Click to expand...
Click to collapse
And how am i ment to do that? cant do it through Android and i dont think i can do it through TWRP
This is what the TWRP log says when I try and dump logs to SD
Could not mount /data and unable to find crypto footer
Failed to mount '/data' (invalid argument)
Unable to recrate /data/media folder.
updating partition details...
Failed to mount '/data' (invalid argument)
... done
Unable to mount storage
Failed to mount '/data' (invalid argument)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (invalid argument)
Copied recovery log to /data/media.
I am running 3.0.2-0 TWRP as thats all i could find and get
elderwolf123 said:
And how am i ment to do that? cant do it through Android and i dont think i can do it through TWRP
This is what the TWRP log says when I try and dump logs to SD
Could not mount /data and unable to find crypto footer
Failed to mount '/data' (invalid argument)
Unable to recrate /data/media folder.
updating partition details...
Failed to mount '/data' (invalid argument)
... done
Unable to mount storage
Failed to mount '/data' (invalid argument)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (invalid argument)
Copied recovery log to /data/media.
I am running 3.0.2-0 TWRP as thats all i could find and get
Click to expand...
Click to collapse
Mount/select storage/micro sd card.
Hi everyone..I tried to flash pixel-10-dp5 by formatting everything except internal storage, but after typing the boot password I get this issue, so how to solve it.. please help
format DATA....some says it delete the encryption problem.
kira0007 said:
format DATA....some says it delete the encryption problem.
Click to expand...
Click to collapse
Is there deferent between wipe and format?
nope! i usually encounter that error on twrp...but i used orangefox then no error...
Thank you guys..I solved it by format ( not just wipe) the data and the phone now is not encrypted ?
How did you solve it?
slymbone.gh said:
How did you solve it?
Click to expand...
Click to collapse
By format data using twrp recovery
Help me please.
My phone is in a bootloop and twrp cant mount /data. I tried formatting and changing file system but it all failed. I cant flash rom in MiFlash and it says "flash xbl error" or "FAILED (File is too large to download)"
What did you do before the phone went into bootloop? Also did you format on TWRP via Wipe -> Format Data?
just format data and install rom through micro sd if your internal storage not working in twrp
kek-mex said:
What did you do before the phone went into bootloop? Also did you format on TWRP via Wipe -> Format Data?
Click to expand...
Click to collapse
first my phone went to edl then i paid someone to flash it with ufi and it failed while it is flashing user data (he refunded my money though) then my phone booted then i flashed twrp in fastboot. Yes I also did the formatting and failed
nneko904 said:
just format data and install rom through micro sd if your internal storage not working in twrp
Click to expand...
Click to collapse
I've tried that already but it really doesn't work for me:crying:
re install twrp(3.3.1-10) ,and vbmeta.img and reboot to twrp again
loopypalm said:
re install twrp(3.3.1-10) ,and vbmeta.img and reboot to twrp again
Click to expand...
Click to collapse
sadly it didn't work for me
I forgot to attach these.
/s/h/t said:
first my phone went to edl then i paid someone to flash it with ufi and it failed while it is flashing user data (he refunded my money though) then my phone booted then i flashed twrp in fastboot. Yes I also did the formatting and failed
Click to expand...
Click to collapse
Alright. Im not that experienced with edl. Can you send picture of Wipe -> Advanced Wipe that we can see all of the partitions? Maybe also if you can send pictures of every partitions details by ticking them and then going to "Repair or Change File System" and taking screenshots? Don't know if this is gonna help, but it's worth a try.
kek-mex said:
Alright. Im not that experienced with edl. Can you send picture of Wipe -> Advanced Wipe that we can see all of the partitions? Maybe also if you can send pictures of every partitions details by ticking them and then going to "Repair or Change File System" and taking screenshots? Don't know if this is gonna help, but it's worth a try.
Click to expand...
Click to collapse
Thanks for responding..
/s/h/t said:
Thanks for responding..
Click to expand...
Click to collapse
Try changing the filesystem of /data to ext4, and then back to f2fs, and then rebooting into TWRP. I've had this problem before, and that worked for me.
kek-mex said:
Try changing the filesystem of /data to ext4, and then back to f2fs, and then rebooting into TWRP. I've had this problem before, and that worked for me.
Click to expand...
Click to collapse
It failed sadly.
/s/h/t said:
It failed sadly.
Click to expand...
Click to collapse
That's pretty weird. Sadly I have no more ideas. Good luck with your problem!
kek-mex said:
That's pretty weird. Sadly I have no more ideas. Good luck with your problem!
Click to expand...
Click to collapse
Thanks for you help!:angel: