[FIXED] Urgent help, how to restore \efs to get lost IMEI ? "Input/output error"
Greeting,
Tonight I flashed a custom kernel to my phone, just\ lost the Singal and my phone show no sim card inserted!.
anyway, i figure it out that... the IMEI lost.
in \efs there's no nv_data.bin file!!
So i went to restore the \efs.
but something not right here!
Hope someone can help here.
i tried these commands but no chance tel now!.
here to restore nv_data.bin
Code:
su
# cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
[COLOR="red"]cp: can't stat '/efs/nv_data.bin': Input/output error[/COLOR]
and here to restore \efs
Code:
# busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
efs/
efs/cryptprop_rebootMode
[COLOR="Red"]tar: can't remove old file efs/cryptprop_rebootMode: Read-only file system[/COLOR]
#
tried to flash back to many FW but no chance,
now i'm in KF1 rooted.
tried root explorer to copy the files but \efs is read only can can't not be changed!.
Hi.
Sounds like your /efs is mounted read-only, try re-mounting for rw access:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p1 /efs
(either via adb or terminal app running on the phone itself)
and then try to copy the files back again.
If it doesn't want to work from a running system, you can also try it in recovery mode (given you have a recovery that allows you a root shell) - you have to use adb in that case ("adb shell", get a root shell ("rootsh" when you're using CF-Root) and then the above).
Maybe the actual FS on the EFS partition is corrupted, so as a very last resort maybe formatting it and then restoring the full backup might work.
here's what i got
Code:
su
# mount -o rw,remount /dev/block/mmcblk0p1 /efs
mount -o rw,remount /dev/block/mmcblk0p1 /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp: can't stat '/efs/nv_data.bin': Input/output error
will trey via recovery,
but,, how to format it ?
It's one of the mkfs commands, but at first glance I could only find the ext2 version of it - /efs is (like everything else of the internal partitions on the SGS2) ext4....
Maybe someone else can shed some light if either mkfs.ext2 can be used, or how else to format it ext4.
Also, you should use tar to write back your backup, to keep the proper permissions.
Now i see no nv_data.bin in the /efs
and I couldn't copy the file, it's read only, even with the mount!
I think this is the only solution for me.
Some have restored efs/IMEI by flashing a stock firmware .
jje
Ah, also found this command:
Code:
make_ext4fs
but I have no idea about its parameters....
Yeah, try flashing a stock FW, maybe one of the "_user_low" ones, AFAIK they clean out a bit more stuff....
I got this
Code:
su
# ls
ls
acct fota.rc res
app-cache init sbin
cache init.goldfish.rc sdcard
config init.rc sys
d init.smdkc210.rc system
data init_kernel_only.rc tmp
dbdata lib ueventd.goldfish.rc
default.prop lpm.rc ueventd.rc
dev mnt ueventd.smdkc210.rc
efs proc vendor
etc recovery.rc
# cd efs
cd efs
# ls
ls
[COLOR="Red"]ls: ./nv_data.bin: I/O error
ls: ./nv.log: I/O error
ls: ./nv_data.bin.md5: I/O error
ls: ./dmp: I/O error[/COLOR]
cryptprop_applied_result cryptprop_securewipedata
cryptprop_onetimeboot edk_p
cryptprop_persist.sys.language imei
cryptprop_persist.sys.timezone redata.bin
cryptprop_rebootMode
#
hope this help ?
FIXED...
here's the full Solution http://forum.xda-developers.com/showthread.php?p=15666725#post15666725
Related
I wanna install a custom ROm on my lg optimus one but something goes wrong. I installed z4root and rooted the phone. Then i installed terminal emulator and typed the specific code starting with su .The phone restarted and i pressed and kept pressing the 3 buttons (power+vol. down+home) but no menu apeared. I did the procedure 10 times but the menu didn't apeared. Am i doing something wrong or my pfone is brocken?
Did u copy paste all commands at once?
I did it manually tiping it by hang on my phone. I didn't coppy the text from my computer.
seems you didnt unzip the two recovery image files. Check it.
I unzipped all the files the image file, the recovery file, everithing. And i coppyedboth the zipped and the unzipped files
I checked it again and i have ony one recovery file and not 2... Which is the second recovery file?
Read this, I just instructed another user on how to upgrade to version 1.2 of the custom recovery. You should install it too. You will find links to the two files and the commands to type in the terminal.
Good luck!
flash_image.zip ??
I have flash_image zipped and unzipped
Use this: http://forum.xda-developers.com/showthread.php?t=971245
when i type the code it says:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cannot create system/binflash_image: read-only file system
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/LGp500-recovery-v12.img
# reboot recovery
Use what I told you and forget about those lines !
Try copy paste each command one by one....
I did just like here: http://forum.xda-developers.com/showthread.php?t=971245 but an error apeared: "windows cannot find groot.exe". I saw that there was anotxer member with the same problem but i didn't understood how to fix it.
try copy paste from stock browser on phone to terminal
Original question post below...
IF YOU DO NOT HAVE THIS PROBLEM PLEASE BACKUP YOUR /EFS NOW!!! this will save you pain in the future.
One of the things I see over and over in the DEV forum for different ROM's is I flashed this ROM and I do not have any cell service. This seemed common enough that I wanted to put what I found in one place. I am not an expert on this and I will credit the posts and users that helped me. I am actually looking for help in creating a fool proof way to fix a broken /efs, product code (Vibrant is SGH-T959ZKBT), and IMEI.
It seems that the issue here is a corrupt /efs partition/folder (/dev/block/spl3)
You can check this a couple ways first look at your /efs folder in Root Explorer (show hidden files) or via "adb shell ls -a -l /efs". As many of you know this is where you find the nv_data.bin file used for unlocking and stores your product code (needed to be accurate for Kies to work). It is also where the phone stores your IMEI. My good /efs looks like this:
Code:
adb shell ls -a -l /efs
drwxrwxrwx root root 2009-12-31 23:00 .android
-rwx------ radio radio 2097152 2011-05-30 00:44 nv_data.bin
-rw-rw-rw- radio radio 15 2011-05-28 17:46 .imei
drwxrwxrwx radio radio 2010-09-12 03:29 imei
-rwx------ radio radio 2097152 2011-05-07 18:24 .nv_data.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv_data.bak.md5
-rwx------ radio radio 32 2011-05-30 00:44 nv_data.bin.md5
-rw-rw-rw- radio radio 801 2011-05-07 18:24 nv.log
-rw-rw-rw- radio radio 1 2011-05-07 18:24 .nv_state
-rwx------ radio radio 1048576 2011-05-07 18:24 .nv2.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv2.bak.md5
The .imei file holds your IMEI in hex format.
You can also check your IMEI by pressing *#06#. You should check that against your IMEI printed on the back of your phone under the battery.
To get your radio working again with correct IMEI you will need a good backup of your /efs folder or partition. You may have a backup and not know it, some ROM porters have added a script to backup your /efs to /sdcard/backup/efs you should look for it. If you are not lucky enough to have one then find a ROM where you see the generic IMEI number (004999010640000) when you press *#06# in the dialer. I used an old Galaxy S 4G port by Eugene373 (he has removed it) to get the generic IMEI.
There are disadvantages to using the generic IMEI as some services will not work (i.e. security on corporate email)
Now that all that is out of the way let's get to the steps for getting you cell service back:
STANDARD DISCLAIMER APPLIES!!! I cannot be responsible for bad things that could happen playing with your /efs folder/partition
Create a copy of your current /efs partition (/dev/block/stl3) with this command: (Thanks Candanga http://forum.xda-developers.com/showthread.php?t=859914)
Code:
# busybox cat /dev/block/stl3 > /sdcard/efs-stl3-backup.img
Mount this file to another location like /testefs:
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Copy all the files from your backup into /testefs and overwrite them
Set all the files and directories (except .android should be root) to the owner and group radio:
Code:
# busybox chown 1001:1001 nv_data.bin
# busybox chown 1001:1001 .imei
# busybox chown -R 1001:1001 imei
# busybox chown 1001:1001 .nv_data.bak
# busybox chown 1001:1001 .nv_data.bak.md5
# busybox chown 1001:1001 nv_data.bin.md5
# busybox chown 1001:1001 nv.log
# busybox chown 1001:1001 .nv_state
# busybox chown 1001:1001 .nv2.bak
# busybox chown 1001:1001 .nv2.bak.md5
Set the file permissions as follows:
Code:
# busybox chmod 700 nv_data.bin
# busybox chmod 666 .imei
# busybox chmod 700 .nv_data.bak
# busybox chmod 700 .nv_data.bak.md5
# busybox chmod 700 nv_data.bin.md5
# busybox chmod 666 nv.log
# busybox chmod 666 .nv_state
# busybox chmod 700 .nv2.bak
# busybox chmod 700 .nv2.bak.md5
Unmount /testefs
Code:
# busybox umount /testefs
Now your /sdcard/efs-stl3-backup.img should be all fixed. If you have the generic IMEI you can try editing the .imei file with a hex editor of your choice and change it to your IMEI it is just the hex representation of your IMEI and nothing else in the file. (I did not test this as I had the files backed up.
Next we are going to create an odin tar to flash to the phone: (Thanks cellgeek http://forum.xda-developers.com/showpost.php?p=10622481&postcount=12)
Code:
# cd /sdcard/
# busybox cat efs-stl3-backup.img > /sdcard/efs.rfs (this is the key step!!)
# tar -cf efs.tar efs.rfs
# exit
Now your back at your PC. Do the following step to get the .tar file off your phone.
Code:
c:\Android\tools> adb pull /sdcard/efs.tar
This tar file can be put in the PDA section of Odin and flashed in download mode.
If all worked you should not have a repaired /efs that should work on most/all ROMs.
What I did not cover here was how to fix the Product code but this post from bames explains how to do that for a Captivate and should work the same for our Vibrants. Difference is our Product Code is SGH-T959ZKBT and you may need to be on Stock JI6 to do the steps in the post.
http://forum.xda-developers.com/showthread.php?t=881162
I hope this helps some and feel free to let me know if I missed something or if it does not work or if there are easier ways.
Original Question:
philow said:
I have been flashing ROMs on my Vibrant for a while and all has worked OK. I never really bothered to look at my IMEI number but I am sure somewhere along the line it changed and probably my Product Code. I just decided to go back to stock and clean up the phone a bit before I continue now that CM7 is officially supported
I Odin back to JFD with the 512.pit and partition. After the reboot the phone will only stay on for a short time then reboot or turn off and I have no signal.
I then Odin to JI6 w/o repartitioning and it will boot and is stable. I root the phone then I look in the /efs folder and all that is there is a .android folder. I have no signal at this point. I can copy a backup of my /efs or just mount as r/w with root explorer and I will get the nv_data files that I need and get signal. If I copy my backup first then I will also have the correct IMEI for my phone. If I do not restore from my backup my IMEI is null/null.
My problem is that if I reboot my phone I again have no files in /efs just the .android folder.
I have tried to change permissions and ownership on the files to radio (1001) but no matter what I do the files disappear.
Anyone else having this problem? Does anyone have a solution?
Thanks
Click to expand...
Click to collapse
what rom did you came from?
Sent from my SGH-T959 using XDA App
iynfynity said:
what rom did you came from?
Click to expand...
Click to collapse
It was my Son's phone so I am not sure what all he has had on it or when it started having a problem but the latest was the 5/7/2011 MIUI rom.
MIUI worked fine on reboot as far as signal is concerned. Not sure what IMEI it had.
Thnaks
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Sent from my SGH-T959 using XDA App
iynfynity said:
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Click to expand...
Click to collapse
I have tried that post and this one from the Captivate forum.
http://forum.xda-developers.com/showthread.php?t=881162
And it still deletes the files when I reboot. I have actually contacted Tmobile and they have sent a new phone but I am trying to see what has happened in case it happens again.
Also, I just flashed an old GalaxyS4G ROM my son had on it and it seems to work OK as well but with a generic IMEI and the 4G Product code.
strange!!!
Thanks for your quick reply
Added possible Solve
I added what I did to solve my issue in the OP! Hope it helps someone!
Thanks
No EFS backup and EFS got currupted| How to recover Vibrant
philow said:
Original question post below...
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Original Question:
Click to expand...
Click to collapse
How to repair IMEI and get back signal If you dont have efs back up or NV_data.bin backup?
I am in big trouble.
Flash to stock using ODIN and it should be fixed, check your IMEI with the one in the back of your phone.
The easiest way to do it is using this http://forum.xda-developers.com/showthread.php?t=954509, as it comes with the pit and pda files you need. (Many thanks to bay_wofl)
how if I don't have the stl3, in fact my /dev/block is empty !!!
do I still have chance to restore my phone with only the efs backup ?
NO Signal ** no /efs folder
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
serginhog said:
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
Click to expand...
Click to collapse
Did you find a solution? I just received my goophone i5 and have no service
You almost made me cry !!! Followed about 90% of all the guides to restore my backed up efs. Went from no signal to bootloop and back. Spend 6 days trying to fix my phone and you were my last resort. If your guide wouldn't work I would've given up. I did push the Thanks button but wanted to say thank you too
Hi all,
im working on making a ROM for the Asus Transformer and im struggling a bit. im totall new to Linux, using mint and just getting used to it.
Basically im just trying to take a stock ROM and add root but adding superuser.apk and SU binary but im running into problems.
Asus Roms are a bit unusual, packed into blob files, ive unpacked that no problem, the system image is called blob.APP but its just the same as system.img just the name as i understand it.
ok so what ive done:
Code:
mkdir system
sudo mount -t ext4 -o loop blob.APP system/
so this mounts the ext4 fs as a loop device and allows me to copy the contents out
Code:
sudo cp -ar system new_system
then ive copied superuser.apk to /app and SU binary to /dev with drop and drag.
then make the filesystem image
Code:
sudo ./make_ext4fs -l 512m -a system blob.APP new_system/system
then just pack it up and flash it, flashing works fine, no errors but when i go to reboot it warns that theres no OS so somethings not worked. ive tried everything i can find googeling!
i just started learning linux on weds so go easy on me
any advice or help would be really great. thanks!
mkdir system here you will mount the old system
mkdir system_new here you will mount the new system
we now create the actual image
dd if=/dev/zero of=system_new.img bs=4k count=60000
bs=4k is the block size
count=60000 the number of blocks of 4kb size
so is something like 60000*4= 240000 which is actually 240 Mb
so it depends to you how big you want the image.
now we format the system.img in ext4
mkfs.ext4 system_new.img
Proceed anyway? (y,n) y
now we override the filesystem check
tune2fs -c0 -i0 system_new.img
Now we mount the the 2 directories that we created in the first step
mount -o loop system_new.img system_new/
mount -o loop system_new.img system/
Now we copy the contet of the old image to the new one with all the perimissions
cp -v -r -p system/* system_new/
We sinc the files
sync
We unmount the partitions
umount system_new/
umount system/
And voila, the system.img in ext4 is created.
Tips: you will need superuser acces.
if you will copy new files besides the ones from the old system you will have to set by hand all the permissions.
If you are using ubuntu just type
sudo su
and you will be root and no more sudo at each command.
Thank u so much for your guide this is exactly what I'm looking for so massive thanks!
So to add root I.can drop and drag superuser.apk and the binary into the new image?
Also do I need to worry about the android mountpoint?
Sent from my HTC Sensation Z710e using xda premium
yes you can do that, as long as you set the permissions right. (you can google for them)
and from what i remeber you will have to set also the ownership of the su, and superusers files
you need to do tests first, and then try
the mountpoint should be ok as it is now.
globula_neagra said:
mkdir system here you will mount the old system
mkdir system_new here you will mount the new system
we now create the actual image
dd if=/dev/zero of=system_new.img bs=4k count=60000
bs=4k is the block size
count=60000 the number of blocks of 4kb size
so is something like 60000*4= 240000 which is actually 240 Mb
so it depends to you how big you want the image.
now we format the system.img in ext4
mkfs.ext4 system_new.img
Proceed anyway? (y,n) y
now we override the filesystem check
tune2fs -c0 -i0 system_new.img
Now we mount the the 2 directories that we created in the first step
mount -o loop system_new.img system_new/
mount -o loop system_new.img system/
Now we copy the contet of the old image to the new one with all the perimissions
cp -v -r -p system/* system_new/
We sinc the files
sync
We unmount the partitions
umount system_new/
umount system/
And voila, the system.img in ext4 is created.
Tips: you will need superuser acces.
if you will copy new files besides the ones from the old system you will have to set by hand all the permissions.
If you are using ubuntu just type
sudo su
and you will be root and no more sudo at each command.
Click to expand...
Click to collapse
U said, we have to set permissions by ourselves. So what are the permissions that needs to be set when I add a new folder with an APK in it?
Sudo chmod 777 filepath/filename.apk
Sudo chmod a-rwx filepatch/filename.apk.
This is what I remember from top of my head. Google it a bit if it does not work from the first try as I have not used this like in 5 years.
If you allready have root you can you a file manager and just copy the file/folder where you want and set the permissions via thw file manager or using terminal commanda or via adb.
From what remember you can t make a folder in the apk folder as you won t be able to run the apk.
Hello i need help.
I have galaxy mega GT i9200, Now i have updated it to 4.4.2 and my efs is deleted i dont know how.
Not phone have no imei and signals.
I followed youtube video about touch not working it worked but signal not coming .
I updated to megafires downloaded from this site.
pls tell me what to do for signal?
Did you have any previous backups of the system?
Did you try flashing the full stock ROM via PC Odin?
Sent from my GT-I9205 using Tapatalk
Yes
AndroidSlave said:
Did you have any previous backups of the system?
Did you try flashing the full stock ROM via PC Odin?
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
No i dont have any backup.
I installed ROM from sammobil 4.4.2 after that install touch was not working then i follow youtube video, now touch works but no signals..
An EFS backup is required , I guess!
I've restored a friend's efs, but it's a bit tricky and I don't know if it will work for you.
Note that you need to be rooted.
I guess you can't mount the efs folder while in recovery?
It happens sometimes when one changes ROM, the efs partition gets corrupted and changes from ext4 to swap.
The following works for Mega I9200 running JB, on KK you may have to change all the fields with mmcblk0p10 with whatever mount point efs has on KK.
To find out about it go to dev/block/platform/msm_sdcc.1/by-name and check which number efs has, or type in adb:
su
ls -al /dev/block/platform/msm_sdcc.1/by-name
Now you are ready to repair efs, let's go!
I - Connect you phone through adb, then type:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.img
mke2fs /dev/block/mmcblk0p10
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p10 /efs
DO NOT REBOOT YOUR PHONE
Now your efs is mounted and don't unmount it.
Check what's inside your efs and remember it for later in case you need to go to step II:
cd /efs
Reboot, your efs is fixed.
If everything works you are done, if it doesn't it means that some files inside the efs folder are missing or corrupted so now proceed to part II to rebuild it.
II - Type the following to recreate efs content (order may change depending the case, and for example if you /efs is empty you don't need the 2 first commands):
rm /efs/FactoryApp/keystr (this will erase keystr)
rm /efs/FactoryApp/factorymode (this will erase factorymode)
mkdir /efs/FactoryApp (this will recreate the FactoryApp folder in case you don't have any it anymore, if you still have it ignore this command)
echo -n ON >> /efs/FactoryApp/keystr (this recreates keystr)
echo -n ON >> /efs/FactoryApp/factorymode (this recreates factorymode)
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
Once everything works make an efs backup:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.img
To restore efs:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p10
Good luck!
Hi, I'm completly lost. I'm trying to get Daydream running on a Sony Xperia XZ Premium (XZP). I read that 2 files must be modified for this. I already edited the build.prop file in /system. But the second one, the handheld_core_hardware.xml is for some reason not where it should be. I backed up the TA-partion and flashed the firmware "G8141_MobilTel EAD BG_1309-2357_47.2.A.10.62_R2C" with the kernel "boot-G8141-47.2.A.10.62-hideunlock-magisk-19.3.img" following the instructions here on XDA. Using ADB I open a root shell (ADB shell, su) and try to copy a modified version of the XML file from data/local/tmp to system/etc/permissions after re-mounting /system in rw-mode. I got the file by extracting the ext4-image in the system.sin of the firmware pack and pushed it to tmp using ADB. When I try to copy the file, I either get "I/O error" or no error. In the latter case the file is nevertheless not copied and I get the I/O error when mounting to ro-mode again. It's also strange that in this case I can cat the contents and list it via ls -l but only if I use the exact name no wildcards. On next boot or when ro-mounting succeeds its completely gone.
This is how it looks on the shell:
Code:
127|G8141:/system/etc/permissions # ls -l handheld_core_hardware.xml
ls: handheld_core_hardware.xml: No such file or directory
1|G8141:/system/etc/permissions # cp /data/local/tmp/handheld_core_hardware.xml /system/etc/permissions
cp: /system/etc/permissions/handheld_core_hardware.xml: I/O error
1|G8141:/system/etc/permissions # ls -l /data/local/tmp
total 12
-rw-rw-rw- 1 shell shell 4877 2019-09-06 10:03 handheld_core_hardware.xml
drwxr-xr-x 2 root root 4096 2019-09-06 11:47 test
G8141:/system/etc/permissions # mount | grep system
/dev/block/dm-0 on /system type ext4 (rw,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr)
/dev/block/sde33 on /system/vendor/firmware_mnt type vfat (ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmas
k=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sde37 on /system/vendor/bt_firmware type vfat (ro,context=u:object_r:bt_firmware_file:s0,relatime,uid=1002,gi
d=3002,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sde34 on /system/vendor/dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/sbin/.magisk/block/system on /sbin/.magisk/mirror/system type ext4 (ro,seclabel,relatime,block_validity,discard,delallo
c,barrier,user_xattr)
G8141:/system/etc/permissions #
What am I doing wrong?
Is there maybe a better way meanwhile to enable Daydream on unsupported devices?
I mean, it's a bad joke, Sony makes this great 4k display but doesn't support VR properly. Daydream even starts and is working just to block the view a second later with a big PopUp telling that the device is not compatible.