busybox problem after installing gives error that "the file is read only FATAL error we have all died"
Please post a solution
What kind of busybox is it and where did you get and how did you install it?
"We have all died" does not sound like an error busybox would give...
Hello,
Please for a better readability of the forum, put a title more explicit, Thx
Related
Hey, looking for a little bit of input here...
(Made the ROM from this tutorial)
Code:
http://forum.xda-developers.com/showthread.php?t=566235
Everytime I try to flash it, it throws an error.
Code:
E:Can't symlink /system/bin/bugreport
E:Failure at line 7: symlink dumpstate SYSTEM:bin/bugreport
Installation Aborted
Any help would be appreciated.
Also, I've compiled unyaffs so that it wouldn't create duplicate symbolic links, and its still throwing the error.
DarkOne951 said:
Hey, looking for a little bit of input here...
(Made the ROM from this tutorial)
Code:
http://forum.xda-developers.com/showthread.php?t=566235
Everytime I try to flash it, it throws an error.
Code:
E:Can't symlink /system/bin/bugreport
E:Failure at line 7: symlink dumpstate SYSTEM:bin/bugreport
Installation Aborted
Any help would be appreciated.
Also, I've compiled unyaffs so that it wouldn't create duplicate symbolic links, and its still throwing the error.
Click to expand...
Click to collapse
Does the image contain "dumpstate"? If you're just trying to make it go away, modify META-INF/com/google/android/update-script to remove the offending script line, or make sure that the thing it's trying to symlink is in your image.
Removing the conflicting lines did enable it to flash properly, I'm just wondering what exactly was lost in the process of removing those steps. I'll see if I cant figure more of it out. Thanks though
I do not understand why some one erase my thread please do not erase it because I have a problem whith thise t959. (but if you going to erase my post at least giveme a reason and give me some help please.
please I have thise pro:
Code:
in the screen of my t959 it said the next:
--movi_chec start..!!
checksum confirmation need_check[0]
not need checksum confirmation
--movi_checksum already executed!!...
--movi_checking done!...
update media. please wait
E:can`t mount/dev/block/st110
(invslid argument)
E:copy_dbdata_media:can`t mount DBDATA:
copy default media content failed.
and when I reinstall packeges it would said:
Code:
--install from scard...
finding update package...
opening update package...
E:can`t open /scard/update.zip
(no such file or directory)
installation aborted
.
please can any one helpme???
please if you now haw to solved thise I apreciated you
Post this here http://forum.xda-developers.com/forumdisplay.php?f=747
I just install KA12 ROM into my Sony Xperia S. I found the problems between developing an application via eclipse.
When I try to run the application through my mobile phone, I occur errors as follows:
Installation error: INSTALL_FAILED_DEXOPT
Please check logcat output for more details.
Launch canceled!
Logcat:
unable to open log device '/dev/log/main' no such file or directory
I already search about this issue and I think KA12 ROM doesn't enable.
So, can anyone guide me step by step to solve this problem.
Thank you in advance.
hallo, im new in forum and very glad to be here, my device is a Coby tablet android 4.0.3, my problem is that installing ubuntu an error interrupt installation, the error is segmentation fault permission denied and happend when i run SU in terminal, device is rooted with unlockroot through computer, how can i resolve and fix this error in short way, because i am not very good in android, thank you
update the su binary from within the superuser app
Error while executing ta_poc fix: "scripts\disable_sony_ric.sh: ./ta_poc: not found".
Hello,
Can somebody help me out with the fact that ta_poc fix doesn't complete and halts with the error: "scripts\disable_sony_ric.sh: ./ta_poc: not found".
Shellscript disable_sony_ric.sh is present in the folder scripts. Binary ta_poc isn't moved. Hence I can't grasp why something can't be found when ta_poc fix is tested by many others.
Since ta_poc fix didn't finish I have more questions. It isn't clear to me how I should apply the generated ramdisk in a firmware. Maybe this question would be solved when ta_poc fix would complete and would pack the ramdisk into recognizable binaries.
P.S. I would have loved to post this message in the thread "https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893", but I wasn't allowed. :crying: