Related
When I try to remove a link in Link2SD I will have the message
Remove link failure
rm failed for /data/sdext2..... Read-only file system
All files I can se have RW. Can it be a problem with the SD-card?
Is is not possible to make any new links either.
beani45 said:
When I try to remove a link in Link2SD I will have the message
Remove link failure
rm failed for /data/sdext2..... Read-only file system
All files I can se have RW. Can it be a problem with the SD-card?
Is is not possible to make any new links either.
Click to expand...
Click to collapse
It sounds like the partition got mounted to /data/sdext2 as read-only somehow. It doesn't matter what the actual file permissions are if the partition is not mounted as read/write. Try one of the following commands to see how it is mounted:
Code:
#If using a terminal emulator on your phone
mount
#If using adb on your computer
adb shell mount
#Here's the output I get:
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /sd-ext type ext2 (rw,noatime,nodiratime,errors=continue)
/dev/block/mtdblock4 on /data/dalvik-cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on [B][COLOR="Red"]/data/sdext2[/COLOR][/B] type ext2 ([B][COLOR="Red"]rw[/COLOR][/B],noatime,nodiratime,errors=continue)
/dev/block/vold/179:4 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:4 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
If yours says "ro" instead of "rw", you might have to modify the link2sd mounting script in /etc/init.d/
I would also suggest posting this in the Link2SD thread so more people, including the dev, can help you figure it out.
I too am having a similar problem, except when trying to create a link. The message i get is:
"Create Link Failure
: cannot create /data/sdext2/sampleapp.apk: read-only file system"
I checked to see if my sdext2 partition is RO - and it is. How do I fix this? I found the link2sd mounting script in the init.d directory, but I have no clue as to how to edit it in order to get things working. I checked in the link2sd thread u posted above, but found no answer to this problem after reading thru 94+ pages.
Help...please...
Bling_Diggity said:
The message i get is:
"Create Link Failure
: cannot create /data/sdext2/sampleapp.apk: read-only file system"
I checked to see if my sdext2 partition is RO - and it is. How do I fix this? I found the link2sd mounting script in the init.d directory, but I have no clue as to how to edit it in order to get things working.
Click to expand...
Click to collapse
Please post the output from the mount command so it will help us figure out how the link2sd script needs to be modified if that is the problem. It would be good if you could attach or post the contents of the link2sd script also. The easiest way might be to just open up either a terminal emulator or use an adb shell through your computer for two commands(filling in the appropriate script name):
Code:
su
cat /etc/init.d/LINK2SD_SCRIPT_NAME
Copy that output and post it here. If you get a read-only error, look below on how to remount /system as r/w and try again.
The script's mount command might use /dev/block/mmcblk0p2 instead of /dev/block/vold/179:2 as well as -o options and/or -t type possibly being specified but it should be similar to the following:
Code:
mount /dev/block/vold/179:2 /data/sdext2
#Only guessing until I get more info but you could try one of these:
mount -o rw /dev/block/vold/179:2 /data/sdext2
mount -o rw -t TYPE /dev/block/vold/179:2 /data/sdext2
#TYPE will be the format of your 2nd partition: ext2 or ext3 or ext4 or vfat(if fat32)
To edit the link2sd script, Root Explorer would work if you have it. If so, you can navigate to /system/etc/init.d/, click on the "mount rw" button at the top right, then long click on the link2sd script, choose "open in text editor" and make your changes. Another option is using adb. You can pull a copy of the script to your computer, edit it, then push it back. From a terminal/cmd prompt on your computer with adb set up:
Code:
#pull script to your current directory
adb pull /etc/init.d/LINK2SD_SCRIPT_NAME
#now edit the script then push it back and give correct permissions
adb push ./LINK2SD_SCRIPT_NAME /etc/init.d/
adb shell
su
chown 0:2000 /etc/init.d/LINK2SD_SCRIPT_NAME
chmod 750 /etc/init.d/LINK2SD_SCRIPT_NAME
Another option would be to use a terminal emulator on your phone:
Code:
su
cp /etc/init.d/LINK2SD_SCRIPT_NAME /sdcard/
#access the sdcard using a usb cable with your computer, edit the script, and disconnect from the computer
cp /sdcard/LINK2SD_SCRIPT_NAME /etc/init.d/
chown 0:2000 /etc/init.d/LINK2SD_SCRIPT_NAME
chmod 750 /etc/init.d/LINK2SD_SCRIPT_NAME
If you get read-only errors while trying to do any of the steps, you'll need to remount the /system partition as read/write. From terminal emulator or in adb shell:
Code:
su
mount -o remount,rw /system
Problem solved. Apparently something happened that caused Clockworkmod to create my partition in Read-Only mode. Couldn't figure out how to change that to R/W, so I did a complete wipe of everything (including SD card), changed over to Amon Ra, repartioned using it, reloaded everything back on to the SD card, re-flashed CM7/gapps, then booted and reinstalled L2SD. Works perfectly now. Not sure why CWM created my partition in read-only mode...but Amon Ra didn't have that issue...so I guess I'll be sticking with it from now on.
MongooseHelix said:
The script's mount command might use /dev/block/mmcblk0p2 instead of /dev/block/vold/179:2 as well as -o options and/or -t type possibly being specified but it should be similar to the following:
Code:
mount /dev/block/vold/179:2 /data/sdext2
#Only guessing until I get more info but you could try one of these:
mount -o rw /dev/block/vold/179:2 /data/sdext2
mount -o rw -t TYPE /dev/block/vold/179:2 /data/sdext2
#TYPE will be the format of your 2nd partition: ext2 or ext3 or ext4 or vfat(if fat32)
Click to expand...
Click to collapse
i seem to be getting closer with this solution but in terminal emul i'm entering
#mount -o rw -t vfat /dev/block/vold/179:2 /data/sdext2
and i'm getting failed device or resource busy
blkwhk said:
#mount -o rw -t vfat /dev/block/vold/179:2 /data/sdext2
and i'm getting failed device or resource busy
Click to expand...
Click to collapse
vfat? Obviously wrong, isn't it?
Getting a read-only mount probably means that the filesystem is corrupted (which would exactly match my experience regarding the partitioning/formatting capabilities of CWM... has nothing but trouble with that one).
doktornotor said:
vfat? Obviously wrong, isn't it?
Getting a read-only mount probably means that the filesystem is corrupted (which would exactly match my experience regarding the partitioning/formatting capabilities of CWM... has nothing but trouble with that one).
Click to expand...
Click to collapse
vfat because i used minitools to create a 2nd fat32 partition. the ext2,3,etc didn't work for me in link2sd
blkwhk said:
vfat because i used minitools to create a 2nd fat32 partition. the ext2,3,etc didn't work for me in link2sd
Click to expand...
Click to collapse
Well, FAT32 is extremely bad choice. They did not work for you pretty much for the reason stated above - you are using a broken tool to partition/format them. Forget about CWM, simply do it on PC or use AmonRA.
doktornotor said:
Well, FAT32 is extremely bad choice. They did not work for you pretty much for the reason stated above - you are using a broken tool to partition/format them. Forget about CWM, simply do it on PC or use AmonRA.
Click to expand...
Click to collapse
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
blkwhk said:
didn't use CWM, used minitools on PC
Click to expand...
Click to collapse
Never heard about minitools. Try something better next time. In case you wonder why FAT32 sucks then, first of all, it has no concept of permissions at all, so any process can write and delete the files there, and second, the filesystem gets corrupted all the time on unclean unmount.
blkwhk said:
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
Click to expand...
Click to collapse
I used minitools as well to create a FAT32, but still keep getting I/O mount-script-creation error when trying to load up link2sd.
I will say it again - do NOT use the fricking FAT32.
Same for me
Well, i just had the same problem.
To solve it, i just rebooted my cellphone (cuz i'm a lazy boy who doesn't like code lines^^).
I had the same problem and found the folder in /data/sdext2 listed as RO on my phone. I set it on RW and the problem was solved for me.
Hopefully it'll work for you guys too.
link2sd failure
Erikdeperik said:
I had the same problem and found the folder in /data/sdext2 listed as RO on my phone. I set it on RW and the problem was solved for me.
Hopefully it'll work for you guys too.
Click to expand...
Click to collapse
still failure when create link manually or automatic,...
......................................................................
any other sollution???
Uppppppppp. SAME problem.
I also noticed my error says /data/sdext2, but my partition type if ext4. Should that be a red flag?
I was getting an error specific to the dalvik-cache (/data/sdext2/dalvik-cache) claiming that it was read only. I used root explorer to try and change permissions for the folder, but root explorer was unable to (on a side note I WAS able to change permissions for the /data/sdext2 folder). I ended up using root explorer to edit the link2sd script..
MongooseHelix said:
To edit the link2sd script, Root Explorer would work if you have it. If so, you can navigate to /system/etc/init.d/, click on the "mount rw" button at the top right, then long click on the link2sd script, choose "open in text editor" and make your changes.
Click to expand...
Click to collapse
turns out my script included the /dev/block/vold/179:2 line AS WELL AS the /dev/block/mmcblk0p2 line.. however both were showing "rw". I removed the /dev/block/mmcblk0p2 line and added mount -t vfat -o rw /dev/block/vold/179:2 /data/sdext2/dalvik-cache
works like a charm now =D
Thank you MongooseHelix and everyone else for your help!
blkwhk said:
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
Click to expand...
Click to collapse
Worked for me too...No formats no nothing...thanks!
Solved ! Failure Link2SD package invalid
For friends who are having problems with the "Create Link" in Link2SD, here I will try to help resolve the problem, because some days I also mess around with "Failure Link2SD package invalid" on my phone. And here's how:
previously, ROM I use is miniROM with Stock Kernel, and Sandisk 8Gb MicroSD Class10
1. Create Partition as follows:
• FAT32 = 6.50 Gb *create as primary
• Ext2 = 600MB *create as primary
• Linux Swap = 200MB *create as primary
#Put MiniTool to create partitions, search on google for a tutorial
2. Link2SD *can use whatever version, I use the latest version V3.7.3
Download Link2SD only from Playstore, do not use version Link2SD Cracked / Mod, remember only from Playstore. If you are using a version of Crack / Mod then bound to fail in the Create Link in Link2SD, and it is based on my experience these days.
If you want Link2SD full version, try using Lucky Patcher. But I do not use it that way, because this is enough for me.
Sorry for my bad english, i used Google Translate to translate my language, (Indonesia to English) :silly:
#Screenshot on Attachment
{
"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"
}
Click to expand...
Click to collapse
hi @all,
is there a way to convert a mtd partition to another filesystem?
i've tryed the following procedure:
1.) boot to recovery
2.) login to system via adb (adb shell)
3.) mke2fs -m 5 -b 4096 /dev/block/mtdblock1
at point 3, it gives errors and nothing is happen.
now, i've tryed to flash a ext3 filesystem on this partition via
flash_image system system.ex3.img (found a explanation on how to create a ex3 system.img), but after mounting the /dev/block/mtdblock1 on /system it shows still device as "yaffs2".
would be nice, if someone can explain me if it's definitvly not possible to convert
mtd partitions or tell me a short tip what can i test
ThX
Andy
An anything known about this in the last year BUMP
How to partition and to have adopted storage at same time.
You don't need to root your device but the device i done this with is rooted
You need to enabled Developer Options.
Enable the USB Debugging option.
Make sure your SD card is formatted as portable, then get the adb executable from android sdk or any other source.
Connect your device to your PC and run the adb devices command. If your device is connected correctly you will see your device listed in the output.
Run adb shell sm list-disks adoptable. This will show you the list of disks that can be used for what we want.
For my device it showed me disk:179,128 so i ran adb shell sm partition disk:179,128 mixed 80 on my 32 GB SD card. It gave me 5 GB as adoptable storage and the rest for other uses. (This will format your SD card.)
How to decrypt adopted storage.
Your device must be rooted.
Using a file browser like ES Explorer, browse to /data/misc/vold.
The .key file there is the encryption key of your adopted storage.
Open that file with a hex editor to view the 16-byte key.
On any Linux distro you can do this first mount your SD card, in my case SD card was mounted at /dev/sdb2.
Then run this command dmsetup create crypt1 --table "0 `blockdev --getsize /dev/sdb2` crypt aes-cbc-essiv:sha256 <You put the 16 bytes of hex data from the file here> 0 /dev/sdb2 0" This might give you a error but ignore it.
If your key is correct you can mount it by mount -t ext4 /dev/mapper/crypt1 /mnt/1/
Finally you can run cd /mnt/1 to browse the decrypted storage.
How can I decrypt without the key? I saw something but i don't know how do. Can you help me?
Im lost the key file
Hello, I have the same situation like pedrolemoz.
Unfortunately, I did a hard reset to my cell phone and do not have the .key file stored in it. Do you still have the possibility to decrypt the sd card?
pedrolemoz said:
How can I decrypt without the key? I saw something but i don't know how do. Can you help me?
Click to expand...
Click to collapse
-CustomX- said:
Hello, I have the same situation like pedrolemoz.
Unfortunately, I did a hard reset to my cell phone and do not have the .key file stored in it. Do you still have the possibility to decrypt the sd card?
Click to expand...
Click to collapse
Ok its not possible to decrypt the SD with no key and you must have made a copy once you encrypted the SD
I had sdcard setup as adopted storage when I remove it from the phone it is not accesible in any way on the phone also is this possible to open it ? Any tool avaiable ?
This sdcard insided again to phone also don't work why ?
sebx_g1 said:
I had sdcard setup as adopted storage when I remove it from the phone it is not accesible in any way on the phone also is this possible to open it ? Any tool avaiable ?
This sdcard insided again to phone also don't work why ?
Click to expand...
Click to collapse
So once you made it adopted storage did it work at all before removing the SD card
Yes
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
sebx_g1 said:
Yes
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
Click to expand...
Click to collapse
Well i say the best thing is to retry to set it as adopted storage so just extract ur key and copy the data you got from SD and reformat it
Yes but system says it is corrupted and only option is to reformat sdcard... It is quite confusing situation isn't it?
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
Same problem here :\
I put my sdcard on my i9505 and from adb i run "su mount", this is what i get:
Code:
130|jfltexx:/ # mount
rootfs on / type rootfs (ro,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/bfqio type cgroup (rw,relatime,bfqio)
/dev/block/mmcblk0p16 on /system type ext4 (ro,seclabel,relatime,errors=panic,data=ordered)
/dev/block/mmcblk0p1 on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p2 on /firmware-mdm type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p10 on /efs type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered)
/dev/block/mmcblk0p18 on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
/dev/block/mmcblk0p29 on /data type f2fs (rw,seclabel,nosuid,nodev,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,multiuser)
Tried also to put my sdcard on a linux OS.. but can not find the filesystem..
Any solution ? :\
How can I reach the .key file?
Question on how to decrypt adopted storage... on phone
POQDavid said:
How to decrypt adopted storage.
Your device must be rooted.
Using a file browser like ES Explorer, browse to /data/misc/vold.
The .key file there is the encryption key of your adopted storage.
Open that file with a hex editor to view the 16-byte key.
On any Linux distro you can do this first mount your SD card, in my case SD card was mounted at /dev/sdb2.
Then run this command dmsetup create crypt1 --table "0 `blockdev --getsize /dev/sdb2` crypt aes-cbc-essiv:sha256 <You put the 16 bytes of hex data from the file here> 0 /dev/sdb2 0" This might give you a error but ignore it.
If your key is correct you can mount it by mount -t ext4 /dev/mapper/crypt1 /mnt/1/
Finally you can run cd /mnt/1 to browse the decrypted storage.
Click to expand...
Click to collapse
In steps 5 - 8, it says to use a linux computer to perform the commands. As I don't have a linux computer, I was wondering if those steps can be done on the Android phone, using Busybox and Android Terminal Emulator? If so, what would be the steps to do it (assuming they differ some from the ones posted there)?
Maybe the better question would be, is there a straight-forward way to decrypt the storage ON THE ANDROID DEVICE, so the SD card doesn't have to be removed and read in another machine?
uptwolait said:
In steps 5 - 8, it says to use a linux computer to perform the commands. As I don't have a linux computer, I was wondering if those steps can be done on the Android phone, using Busybox and Android Terminal Emulator? If so, what would be the steps to do it (assuming they differ some from the ones posted there)?
Maybe the better question would be, is there a straight-forward way to decrypt the storage ON THE ANDROID DEVICE, so the SD card doesn't have to be removed and read in another machine?
Click to expand...
Click to collapse
Well its possible i am sure android must have dmsetup and you can give it a try i never done it on android device using Busybox
How i Decrypt in windows enviroment
Dear I rooted my phone and get the .key file and actually they were 2 file
expand_8e6f0fc23f14e31581c6c0ded8a2bb5f.key
expand_a80d5d8eddaee648fd1f0f14cbb88ae2.key
I want to decrypt my adopted sd card to be able to repartition it again and return it into 1 partition 128gb
Please help
Dr.ahmed3386 said:
Dear I rooted my phone and get the .key file and actually they were 2 file
expand_8e6f0fc23f14e31581c6c0ded8a2bb5f.key
expand_a80d5d8eddaee648fd1f0f14cbb88ae2.key
I want to decrypt my adopted sd card to be able to repartition it again and return it into 1 partition 128gb
Please help
Click to expand...
Click to collapse
I download Ubuntu and install it and yet I could not decrypt my SD card using terminal and this commands.
Please Help
i dont have the key, the folder /data/data/vold is empty, i didnt factory reset or anything, i just rooted the phone to be able to get the key
Hello!!!!
POQDavid said:
Ok its not possible to decrypt the SD with no key and you must have made a copy once you encrypted the SD
Click to expand...
Click to collapse
i have created a backup of that .key file but after few days i formatted my Android and after placing it back to its folder my sdcard is still not working. i mean my sdcard is fully readed by my android device and i can write on it to but my old files are not showing but they are in sdcard because my stotage info is proving it.
CheifX said:
i have created a backup of that .key file but after few days i formatted my Android and after placing it back to its folder my sdcard is still not working. i mean my sdcard is fully readed by my android device and i can write on it to but my old files are not showing but they are in sdcard because my stotage info is proving it.
Click to expand...
Click to collapse
maybe try to copy your data using a linux distro like mint just to be safe then see if you can find the files or not
Is it possible to perform the decryption on a guest Ubuntu virtual machine (windows as a host) ? I followed a tutorial on how to link my sdcard onto the virtual machine, but I cannot seem to mount it in Ubuntu I get a "wrong fs type, bad option, bad superblock on /dev/sdb2" error, any help ?
Hi @POQDavid , I ve done the procedure, I can access the files and everything, but my question is, how do I format the sd to make it standard again?
fanfzero said:
Hi @POQDavid , I ve done the procedure, I can access the files and everything, but my question is, how do I format the sd to make it standard again?
Click to expand...
Click to collapse
You should be able to either simply format the card or use the phone to restore it
I have tested MIUI 10 and Android P DP2, but, with TWRP and Magisk there is no way to edit file or make any modifications to /system and subdirectory.
In terminal emulator I receive a error "Read-only file system".
I've already tried to sent "mount -o rw,remount /system", but I receive a error "'/dev/block/dm-0' is read-only". This is the permissions of /dev/block/dm-0:
brw------- 1 root root
How can I edit system file?
Up
i have the same problem with vendor partition.
i need write on it for using a NFC CARD EMULATOR
Yes, I have same issue. Any solution?
with xiaomi.eu i dont have this problem
I have a friend that updated an:
Mercedes Benz C-Class C204 (2012 - 2014) Android 7.1 HL-8204
with an unknown firmware from @Hal9k_ (I can tell by the bootscreen).
the system boots directly to recovery that has the flowing information:
Android Recovery
Android/px3/px3
7.1.2/NHG47L/hct12252004
userdebug/test-keys
Recovery V7.1.1.
I already tried to update to the latest and previus versions of Hal9k's Firmwares and Malaysk's Firmwares but always get the same error when installing a system image:
E:Can't open /dev/block/platform/emmc/by-name/parameter
E:Bad dest path /parameter
Update parameter...
E:Can't open /dev/block/platform/emmc/by-name/parameter
E:Bad dest path /parameter
Update parameter Failed (-6)
Update failed, please reboot and update again!
Update rkimage complete.
Installation rkimage aborted.
when installing a OTA update i get the flowing error:
E: failed to verify whole-file signature
Update package verification took 63.5 s (result 1).
E: Signature verification failed
E: error: 21
Instalation aborted.
mcu image apparently updates correctly:
------MSU customer:HA
------MSU Version:V3.37
------MSU verify success!!!
------MSU update start!!!
flowed by a full reboot to a blankscreen.
- what am I doing wrong?
- what are the right OTA, System and MCU images to install to bring this device back to life?
Thanks for considering helping me.
hallo, wenn du noch keine lösung hast:
soweit alles noch ok, auch die MCU version ist aktuell.
du musst nur deine hal9k firmware "dupdate" auf einen USB stick kopieren und folgendes vorgehen;
wenn du im recovery menü bist, musst wipe all data factory ausführen, danach install from usb, dann musste alles klappen!
wenn du noch fragen hast, gerne melden.
Gostivar said:
hallo, wenn du noch keine lösung hast:
soweit alles noch ok, auch die MCU version ist aktuell.
du musst nur deine hal9k firmware "dupdate" auf einen USB stick kopieren und folgendes vorgehen;
wenn du im recovery menü bist, musst wipe all data factory ausführen, danach install from usb, dann musste alles klappen!
wenn du noch fragen hast, gerne melden.
Click to expand...
Click to collapse
Thank you for the help Gostivar!
witch hal9k firmware "dupdate" file should I use?
I think I try this already but I can try again.