Hi. I had Oxygen 1.0 installed with N1 Table. I fancied a change back to a HD Sense Rom - therefore I changed back to the Sense Partition Tables within S-Off. However when attempting to install the rom I keep getting an error message:-
E: Can't chown/mod /system/xbin
(No such file or directory)
E: Failure at Line 24:
set_perm_recursive 0 2000 0755 0755 SYSTEM:xbin
I have done a search and discovered I may need to reflash my SPL?
How is this done?
Regards
Andy
do you have an ext partition? hd roms are to big and the don't just fit in NAND, so they mostly require you to have an ext partition atleast 512mb.
murdoch1 said:
Hi. I had Oxygen 1.0 installed with N1 Table. I fancied a change back to a HD Sense Rom - therefore I changed back to the Sense Partition Tables within S-Off. However when attempting to install the rom I keep getting an error message:-
E: Can't chown/mod /system/xbin
(No such file or directory)
E: Failure at Line 24:
set_perm_recursive 0 2000 0755 0755 SYSTEM:xbin
I have done a search and discovered I may need to reflash my SPL?
How is this done?
Regards
Andy
Click to expand...
Click to collapse
Related
Does anyone know where I can find information about the commands that can be used in the update-script file. Some of the commands are simple enough to understand but commands such as set_perm aren't. I also don't understand the numbers that are used in the show_progress command, in one script 0.1 0 is used then 0.5 0 after that 0.2 0 and 0.2 10 are used, i'm confused of which numbers i'm supposed to use can anyone tell me. Thanks Glennlh.
it uses the android init language http://www.kandroid.org/android_pdk/bring_up.html
Thank You, I'll check the link you posted.
I still don't understand which numbers to use, I would be very grateful if someone can explain:
which numbers to use after the show_progress command as in this example the numbers 0.200000 0, 0.200000 10, 0.100000 0 are used in that order.
set_perm_recursive command.
set_perm command.
Also my test script shown below doesn't work will someone have a look through and tell me the problem, thanks.
Code:
show_progress 0.1 0
format BOOT:
format SYSTEM:
show_progress 0.2 0
copy_dir PACKAGE:system SYSTEM:
write_raw_image PACKAGE:boot.img BOOT:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.2 10
try this, i think the main problem was the missing "progress 0.1 10":
Code:
show_progress 0.1 0
format SYSTEM:
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
show_progress 0.2 0
format BOOT:
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.2 10
idk how it works exactly, but it seems like the progress meter has two stages, that need to be started and ended (or at least one of them, iirc i have seen update-scripts with only the 0.1 meter commands).
set_perm sets unix-style permissions, google and wikipedia help you there.
set_perm_recursive does the same for the contents of a directory.
your update-script doesn't that much sense (you are trying to make apk files executable, which they shouldn't be), what exactly are you trying to do?
and please people, "doesn't work" is not an error msg. call an autoshop and say "my car doesn't work, can you tell me why?" what would they say...
Sorry i'll try and explain better, after installing the ROM there are no errors, but it boots straight back to the recovery menu. I believe this must be something to do with the boot.img not writing properly but the code for the boot.img seems to be correct, any ideas why it doesn't work.
Edit: I was trying to make the files executable from using the code giving in the tutorial by lox, I don't know why its there.
Edit 2: Tried using your code, still wont boot goes straight to recovery.
i need to know what you want to do... and where your boot.img comes from.
btw, if you are trying to flash a complete rom with that script it won't work. check the update-script of a generic rom to see what is the minimal action necessary to create a bootable rom on the phone.
if you attach your update.zip or upload it somewhere i can have a look.
What ive done is converted the newest ROM from the three network called RUU_Hero_H3G_UK_2.73.771.73_release_signed_NoDriver.exe to an update.zip. Using the update-script file that is suggested in the lox tutorial, the ROM works fine but the kernel image isn't updated. Using both scripts posted above I get the problem above. I kernel I used was the one which came packed with the official update.
Here is the script that works but doesn't update the kernel (which came from the tutorial here):
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
I've figured out the problem, sort of. The line format BOOT: seems to just overwrite the existing kernel without problems so thanks for the help and problem solved.
I'm getting constant errors when trying to install any Sense HD ROMs. I've partitioned my SD and all that, rooted, S-OFF'ed, running on Sense HBOOT. The latest error I'm getting is:
E:Can't chown/mod /system/xbin
(No such file or directory)
E:Failure at line 93:
set_perm_recursive 0 200 0755 0755 SYSTEM:xbin
Installation aborted.
I have no idea what's going on.
You need Bravo stock image, not bravo sense.
Finally worked, I was wondering what the hell was wrong, thanks a lot man.
+1
Hi developers
I am developing my first ROM. I'm using dsixdas Android Kitchen. It's a mysense rom. I have only change some Images. Now when i flash the rom, there is the follow fail:
Code:
Copying Files...
E:Can't chown/mod /system/etc/bluz
(no such file of directory)
E:Failure at line 384:
set_perm_recursive 1002 1002 0755 0440 System:etc/bluz
Installation aborted.
Can someone help me?
have someone an idea?
try toggle verification
and how can i toggle verification?
can i do this with disxda's Android Kitchen?
Maybe you shouldn't be cooking a ROM you might break your phone lol
Sent from my HTC Desire using XDA Premium App
tischn said:
and how can i toggle verification?
Click to expand...
Click to collapse
You do that form recovery. If you are. Just find toggle signature verification, and click it. It should say signature verification disabled
tischn said:
Hi developers
I am developing my first ROM. I'm using dsixdas Android Kitchen. It's a mysense rom. I have only change some Images. Now when i flash the rom, there is the follow fail:
Code:
Copying Files...
E:Can't chown/mod /system/etc/bluz
(no such file of directory)
E:Failure at line 384:
set_perm_recursive 1002 1002 0755 0440 System:etc/bluz
Installation aborted.
Can someone help me?
Click to expand...
Click to collapse
ehm, the error message is clear:
E:Can't chown/mod /system/etc/bluz
(no such file of directory)
did you check if the directory exists in the folder structure of your rom?
Hypercaine said:
You do that form recovery. If you are. Just find toggle signature verification, and click it. It should say signature verification disabled
Click to expand...
Click to collapse
i'm using the ClockworkMod Recovery v2.5.0.7 but i can't find anywhere.
greg17477 said:
ehm, the error message is clear:
E:Can't chown/mod /system/etc/bluz
(no such file of directory)
did you check if the directory exists in the folder structure of your rom?
Click to expand...
Click to collapse
jes i did, but i isn't there.
Is that only a folder, than i can create?
Help !
I’m having strange issues with my DHD – Every time I try loading Android Rev. 6.1.5 or LeeDroid v4.0 my phone just hangs at the White HTC Screen…
I tried loading both Roms with Rom Manager and 4EXT – But seems to make no difference…
Even stranger if I load a small rom such as Miui or CM7 they both install ok!
Before you ask if the file is corrupt i did MD5 checks on both Andoird Rev. and LeeDroid after download and they pass!
Looking through my SD card I found the recovery log from trying to install Adriod Rev. Not being used to this Op sys. I was hoping someone could shed some light on these errors for me ?
symlink: failed to symlink /system/xbin/bb/ifconfig to /system/xbin/ifconfig: No such file or directory
symlink: failed to symlink /system/xbin/bb/route to /system/xbin/route: No such file or directory
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
about to run program [/system/xbin/busybox] with 4 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
about to run program [/sbin/grep] with 3 args
run_program: child exited with status 1
>>> Creating toolbox symlinksset_perm: chown of /system/xbin/su to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/su to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/openvpn to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/openvpn to 755 failed: No such file or directory
Help !
Did you in any way edit the roms?
Also did you do a full wipe
Sent from my Desire HD using xda premium
Hi,
No the Rom was original and i ran the super_wipe as instructed...
Have been looking around to see if it maybe my SD card, But i can extract the Rom zip with no errors....
Cheers
And this error came from recovery
Sent from my HTC Desire HD A9191 using xda premium
No errors are reported during install, But when i reboot it just hangs at the white screen HTC screen...
Have You tried flash another radio? Once i flashed ARHD ROM and when reboot it hanged at the white screen, then i flashed recommended radio and problem was solved
Finally fixed, restored phone back to factory then rooted again...
Installs all roms no probs
Sent from my Desire HD using XDA App
Hi all.
I have a new issue. I'm close to restoring my htc 816 desire, but when I do a CWM backup it gets stuck:
Checking MD5 sums....
Erasing boot before restore....
Restoring boot image....
Restoring system....
Can't mount /system!
Does anyone know a way to get around not being able to mount /system.
ajcbrown said:
Hi all.
I have a new issue. I'm close to restoring my htc 816 desire, but when I do a CWM backup it gets stuck:
Checking MD5 sums....
Erasing boot before restore....
Restoring boot image....
Restoring system....
Can't mount /system!
Does anyone know a way to get around not being able to mount /system.
Click to expand...
Click to collapse
Flash stock recovery, wipe /system there. Then reflash cwm.
FoxyDrew said:
Flash stock recovery, wipe /system there. Then reflash cwm.
Click to expand...
Click to collapse
Hey foxy, thanks for the advice.
I'm not sure if I can find the stock recovery though. Are you sure it needs to be stock? Can I just have any cwm recovery and format the /system in it?
Edit: Alternately, would the stock recovery be the one inside the cwm backup?
Does anyone know whether I need the stock recovery to format /system? Even with CWM Recovery it should just wipe the OS no? And there's no OS on there currently so it shouldn't affect my ability to boot into cwm or fastboot?
ajcbrown said:
Does anyone know whether I need the stock recovery to format /system? Even with CWM Recovery it should just wipe the OS no? And there's no OS on there currently so it shouldn't affect my ability to boot into cwm or fastboot?
Click to expand...
Click to collapse
Well before performing a restore you should wipe all partitions. But I had assumed you already tried that. So if that doesnt work, you need to flash the stock recovery, which can be found here. Wipe /system there.
If you don't know how to flash a recovery, google it.
And no the stock recovery isn't inside the backup.
FoxyDrew said:
Well before performing a restore you should wipe all partitions. But I had assumed you already tried that. So if that doesnt work, you need to flash the stock recovery, which can be found here. Wipe /system there.
If you don't know how to flash a recovery, google it.
And no the stock recovery isn't inside the backup.
Click to expand...
Click to collapse
Pardon my ignorance, still learning it all. When you say wipe all partitions, are you saying wipe /data, /cache, /radio and so on? The previous time I tried to recover it was getting stuck at checking md5 sums which I solved by wiping the cache.
EDIT: NEVERMIND, googled my partition question. All good
Okay, how do i wipe any partitions in stock recovery? All I get is a phone symbol with a red triangle and excalamation mark on it.
http://i.imgur.com/1fXDo3w.jpg
^ Is this meant to be the stock recovery?
ajcbrown said:
http://i.imgur.com/1fXDo3w.jpg
^ Is this meant to be the stock recovery?
Click to expand...
Click to collapse
Yes
FoxyDrew said:
Yes
Click to expand...
Click to collapse
Thanks, I couldn't find that you needed to hold down the volume up button and tap power to get the blue menu thing. Only found it on HTC One forums :S.
ajcbrown said:
Thanks, I couldn't find that you needed to hold down the volume up button and tap power to get the blue menu thing. Only found it on HTC One forums :S.
Click to expand...
Click to collapse
It seems like whenever I can mount /system, my recovery will crash after a few actions are performed . And it doesn't crash when I can't mount /system. I've tried wiping the partitions, not sure what else I can do unless changing to TWRP would fix anything, don't know if it would though.
Anyone got an idea of how I can get around /system being a pain? I'm almost out of ideas. I don't get it, the internal sd card isn't broken because I can push files to it, but I can't mount /system even after formatting it
Also: Stock recovery only gave me the option of wiping data and cache, not system.
FoxyDrew said:
Yes
Click to expand...
Click to collapse
Hey bud, I might need your help a bit further
1: I don't think the cwm restore I was using is the correct one because /system won't mount at all when I try to install it.
2: I tried installing this instead: http://forum.xda-developers.com/showthread.php?t=2712315 . I flashed the boot.img that comes in the rom download, not the seperate boot.img listed because I can't download it from that chinese site, and then installed the rom and it installs fully but boots back into HTC logo and doesn't progress.
3: Could I fix my issues with an OTA update? I now know how to install them using stock recovery, but I don't have the OTA update on my phones internal memory. Is there a manual download?
ajcbrown said:
Hey bud, I might need your help a bit further
1: I don't think the cwm restore I was using is the correct one because /system won't mount at all when I try to install it.
2: I tried installing this instead: http://forum.xda-developers.com/showthread.php?t=2712315 . I flashed the boot.img that comes in the rom download, not the seperate boot.img listed because I can't download it from that chinese site, and then installed the rom and it installs fully but boots back into HTC logo and doesn't progress.
3: Could I fix my issues with an OTA update? I now know how to install them using stock recovery, but I don't have the OTA update on my phones internal memory. Is there a manual download?
Click to expand...
Click to collapse
What model do you have?
FoxyDrew said:
What model do you have?
Click to expand...
Click to collapse
816x dual sim international version. As far as I can tell, it's /system causing problems. If it mounts, my recovery crashes after I select a few things, when I can't mount it the recovery won't crash. If I flash twrp or Philz recovery it crashes after i select one thing :/. I'm confused as to whether it's a fixable software issue or a hardware issue, because right now I cannot boot into any rom.
I took a look at the log file when installing the following rom: http://forum.xda-developers.com/showthread.php?t=2712315, the concerning things I found are:
set_perm: chown of /system/vendor/media to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/media to 755 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt to 755 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models to 755 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection to 755 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7 to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.7 to 755 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6 to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/yaw_roll_face_detectors.6 to 755 failed: No such file or directory
set_perm: chown of /system/vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N.bin to 644 failed: No such file or directory
set_perm: chown of /system/xbin/vold to 0 2000 failed: No such file or directory
set_perm: chmod of /system/xbin/vold to 755 failed: No such file or directory
set_perm: chown of /system/lib/modules/s2w_mod.ko to 0 0 failed: No such file or directory
set_perm: chmod of /system/lib/modules/s2w_mod.ko to 644 failed: No such file or directory
set_perm: chown of /system/etc/init.d/KingSenseGMD to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/KingSenseGMD to 755 failed: No such file or directory
set_perm: chown of /system/etc/init.d/99superuser to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/99superuser to 755 failed: No such file or directory
Is this normal since I have no OS currently, or should it be setting permissions in the system files it should have written?
Interestingly the end of the log ends: "Installer Sucessfull (Status 0)", so I thought that would mean it's all okay.
The only other thing that is probably holding me back from booting into the rom after it's "succesfully installed" is that I can't download the damn boot.img from this link: http://pan.baidu.com/s/1sj0LRRZ , but I'm still concerned about the /system playing up.