Error opening '/data/media' (no such file or directory) - Nexus 7 Q&A, Help & Troubleshooting

I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition

Most unfortunate. Nobody is there to help on this ?

YOu have installed bootloader version 4.18 while the latest bootloader version for Nexus 7 is 4.23 which means you have an outdated bootlaoder installed on your device while TWRP 3.1.1 is the latest version available supporting android 7.x. I am not sure but this already might cause some issues. Additionally there were some changes in handling /data/media and /sdcard/internal/
To get out of your situation you should either install a factory image with a current (4.23) bootloader (but be aware that there are some factory images out which have a buggy bootloader (!))
Otherwise you could install a working bootloader 4.23 and TWRP 3.1.1 using fastboot and and then a custom ROM based on Android 7.x

vsrkmurthy said:
I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition
Click to expand...
Click to collapse
The exact same thing happens to me on my redmi note 9s
What can I do?

Just Open Terminal from TWRP Recovery then open `data`. now create Media folder thats all
cd data & mkdir media
This one works for me in redmi k20 pro, Now your Internal storage mount in PC

Related

Motorola not installing system from twrp and adb

Dear friends, I am really despaired. My brand new does not work.
Yesterday I wanted to root the phone, and so unlocked the bootloader first ( phone was updated to mashmallow) . All was done ok and the boatlodear was freed. Then I flashed the twrp version 2.8.7.0 and was installed too. Then went to install the supsersu and did it, but when i restarted the phone is got stuck in the warning unlocked bootloader screen and does not intendted to boot, nothing.... .
I donwloaded 3 diverse roms, 2 custom and one official, I pushed to the phone through twrp and they go to the phone but when try to install I always get errors.
for example i get : could not detect filesystem for /dev/block/bootdevice/dy-name/system at system no such file or directory
mount failed to mound ( the above )
unmount of /system failed no such volume
script succeded result was ( 0.200000)
and even that for one of the roms I get succesfull nothing is installed and the phone bots only on fastboot, there is no operative system at all there, even that the internal storage seems ok because I can access to in via PC!
I tried also via abd to install and even that the phone does connect and show in the abd devices when I send a command in adb i get only the flushing of the help screeen of adb!!
Please anyone help, I just bought that phone one week ago!
Then you flashed an old version of TWRP. Use the updated version.
didn't you take backup before flashing SU ??

Asus Zenfone Max (ZC550KL, Z010D), Android M, Unable To Unlock Bootloader

Hi there! I have this question which I'd love to have answered because I've been on this issue for around 2 days straight.
Long story short:
Tried to flash custom recovery using fastboot, didn't work because bootloader locked
Kept on trying the unlocker apps, none of them even installed fully (THIS WAS WHEN I WAS STILL ON LOLLIPOP)
Somehow, at some point, I just randomly rebooted and BOOM THERE WAS TWRP (Sorry, I don't remember how exactly I managed that. As far as I remember, I was only using fastboot and nothing else)
Flashed CM 14.1 unofficial, device gave an error message regarding boot.img (something like "could not load boot.img"
Used stock ROM to flash OTA Android 6.1
Now the Asus unlocker app downloads but on reboot it says "error: unlock fail !!!"
Obviously, fastboot is unable to flash a recovery right now. I tried ignoring the error message and rebooting to recovery to stop the device from loading the stock recovery again but the device still loads the stock recovery.
I'm really tired
P.S: NO, there is no Enable OEM option in my Developer Options menu and YES, I have all the drivers necessary.
Did you get anywhere with this? I have a similar problem except that I couldn't flash Android 6.1 because the vendor had flashed WW 5.0.2 on a CN phone without also updating the CN recovery to WW. So the update failed its consistency check.
I've got TWRP on there now, but can't unlock the bootloader in 5.0.2 - I think this is why TWRP can't flash anything. It can't see the update files, won't switch to external SD, etc. .
I also found and tried flashing a WW recovery but that didn't work either. I'm wondering now if I got the 615 software by mistake.

Possibly Dead Device? [P8/P9 Lite (2017)][PRA-LX1]

Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.

Soft-bricked, messed up /vendor partition?

Ok, so I’m trying to fix this phone my friend messed up like a year ago and then gave up on..
Huawei P10 Lite
Build No: WAS-LX1C432B183
Bootloader: unlock
FRP: unlock
Rooted (or used to be I guess)
These are his notes from back then:
Flashed an unstable Lineage build and provided the wrong vendor.img –
tried to flash stock Nandroid backup through TWRP, which failed, phone was still running Lineage. Bugs got worse every reboot, finally stuck in bootloop on Lineage booting screen. Then did a full wipe and flashed stock ROM again - update_data_full_public.zip worked, update_full_WAS-L01_hw_eu.zip failed ("error:9")
finally flashed vendor.img the same way as with the wrong file in the beginning dd if=/external_sd/vendor.img of=/dev/block/bootdevice/by-name/vendor
now device can't mount /vendor anymore and bootlooping on the “ur device can’t be trusted” screen
Ok, so now I honestly don’t know what the last command actually does or if he got it wrong, he can't remember where he got it from and so far I didn't really find anything on it either..
I can now
• boot into erecovery, which starts but fails every time ("file does not exist"),
• do 3 button method, which gets to 5% then stuck again and returns to bootloop
• fastboot flash just about anything successfully according to logs – still bootloop
• use Unbrick option in the Multi Tool (which does the same as far as I can tell), again successful according to logs but still bootloop
• get into TWRP, flash stuff from there (stock, Lineage), also success but no change
I keep getting “failed to mount /vendor” in the logs though, and still can’t mount /vendor from TWRP and it says it’s 0MB.. I honestly don’t dare messing with partitions on my own as I’m not sure what the exact problem is..
Can someone please help?
Thanks already (and sorry this is so long..)

Can't access system/recovery/bootloader

About phone: Huawei P9 lite VNS-L21C432B161 (central Europe)
First modifications
A long time ago i unlocked bootloader and successfully rooted the phone. I turned off OEM unlock option in settings after rooting, because someone said i should do so for security. Then came EMUI 5 OTA. It somehow updated itself without me agreeing. Android nougat detected, that the bootloader was unlocked and so it assumed that OEM unlock option was also ENABLED when it really wasn't, making me unable to re-enable the option.
So i used the https://forum.xda-developers.com/huawei-p9lite/how-to/tutorial-rollback-n-to-mm-c432-devices-t3563955432-devices-t3563955" <-- official rollback package and installed stock ROM through dload.
Here is the part where i messed up horribly
Now i wanted to update to android 7 again, but updater wasn't giving it to me and i was unable to flash it through TWRP. I installed the rollback package again through download mode as it said it allows any ROM to be installed, hoping i could then install android 7 through Download mode, which would in turn allowed me to install newer version of TWRP to then install a nougat based custom ROM.
Current situation
Now i am stuck at the 'Your device has been unlocked and can't be trusted. TWRP 3.0.1 should be installed but it never boots. Can't access bootloader, phone doesn't seem to be detecting the Power+Volume down combination. Recovery gets stuck at the shorter warning screen during boot, erecovery gets stuck as well. This has been like this even before i tried this, no idea what caused it. I can't even access download mode, which gets stuck at the shorter warning screen as well.
What i hope to achieve now
At best: To make it work again.
At worst: To at least be able to turn it off somehow so the text doesn't get burnt into the screen in case i ever manage to fix it.
Thanks in advance

Categories

Resources