• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Issues with self-built ROM

17 posts in this topic

Posted · Report post

I compiled a ROM from source and I'm having issues flashing it. I think (and will stress think) the ROM compiled correctly and I ended up with the relevant boot.img and system.img files, which I then imported into my dsixda kitchen setup. All this went as expected but when I flashed the ROM I get the following error:

assert failed: write_raw_image("/tmp/boot.img". "/dev/block/platform/omap/omap_hsmc.0/by-name/boot")

E:Error in/sdcard/update.zip

(Status 7)

Installation aborted.

Anyone have any ideas what could be wrong?

0

Share this post


Link to post
Share on other sites

Posted · Report post

I compiled a ROM from source and I'm having issues flashing it. I think (and will stress think) the ROM compiled correctly and I ended up with the relevant boot.img and system.img files, which I then imported into my dsixda kitchen setup. All this went as expected but when I flashed the ROM I get the following error:

assert failed: write_raw_image("/tmp/boot.img". "/dev/block/platform/omap/omap_hsmc.0/by-name/boot")

E:Error in/sdcard/update.zip

(Status 7)

Installation aborted.

Anyone have any ideas what could be wrong?

Status 7 is a problem with your updater-script - an assert can't complete.

Check the syntax and target locations for the boot.img line in your script.

0

Share this post


Link to post
Share on other sites

Posted · Report post

I'm using the updater-script that the kitchen made, I've not changed it at all:

show_progress(0.1, 0);

format("ext4", "HSMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system");

mount("ext4", "HSMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");

package_extract_dir("system", "/system");

symlink("toolbox", "/system/bin/setconsole");

symlink("toolbox", "/system/bin/setprop");

symlink("toolbox", "/system/bin/newfs_msdos");

symlink("toolbox", "/system/bin/kill");

symlink("toolbox", "/system/bin/ln");

symlink("mksh", "/system/bin/sh");

symlink("toolbox", "/system/bin/id");

symlink("toolbox", "/system/bin/vmstat");

symlink("toolbox", "/system/bin/renice");

symlink("toolbox", "/system/bin/getevent");

symlink("toolbox", "/system/bin/wipe");

symlink("toolbox", "/system/bin/nandread");

symlink("toolbox", "/system/bin/hd");

symlink("toolbox", "/system/bin/umount");

symlink("toolbox", "/system/bin/top");

symlink("toolbox", "/system/bin/cat");

symlink("toolbox", "/system/bin/smd");

symlink("toolbox", "/system/bin/stop");

symlink("toolbox", "/system/bin/netstat");

symlink("toolbox", "/system/bin/ionice");

symlink("toolbox", "/system/bin/schedtop");

symlink("toolbox", "/system/bin/ls");

symlink("toolbox", "/system/bin/start");

symlink("toolbox", "/system/bin/uptime");

symlink("toolbox", "/system/bin/date");

symlink("toolbox", "/system/bin/chown");

symlink("toolbox", "/system/bin/sendevent");

symlink("toolbox", "/system/bin/mv");

symlink("toolbox", "/system/bin/sleep");

symlink("toolbox", "/system/bin/chmod");

symlink("toolbox", "/system/bin/df");

symlink("toolbox", "/system/bin/iftop");

symlink("toolbox", "/system/bin/insmod");

symlink("toolbox", "/system/bin/ifconfig");

symlink("toolbox", "/system/bin/ps");

symlink("toolbox", "/system/bin/dd");

symlink("toolbox", "/system/bin/rmmod");

symlink("toolbox", "/system/bin/rm");

symlink("toolbox", "/system/bin/getprop");

symlink("toolbox", "/system/bin/lsmod");

symlink("toolbox", "/system/bin/mount");

symlink("toolbox", "/system/bin/rmdir");

symlink("toolbox", "/system/bin/log");

symlink("toolbox", "/system/bin/sync");

symlink("toolbox", "/system/bin/notify");

symlink("toolbox", "/system/bin/printenv");

symlink("toolbox", "/system/bin/mkdir");

symlink("toolbox", "/system/bin/ioctl");

symlink("toolbox", "/system/bin/lsof");

symlink("toolbox", "/system/bin/watchprops");

symlink("toolbox", "/system/bin/dmesg");

symlink("toolbox", "/system/bin/touch");

symlink("toolbox", "/system/bin/r");

symlink("toolbox", "/system/bin/route");

symlink("toolbox", "/system/bin/cmp");

symlink("toolbox", "/system/bin/reboot");

set_perm_recursive(0, 0, 0755, 0644, "/system");

set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");

set_perm(0, 3003, 06755, "/system/bin/ip");

set_perm(0, 3003, 02750, "/system/bin/netcfg");

set_perm(0, 3004, 02755, "/system/bin/ping");

set_perm(0, 2000, 06750, "/system/bin/run-as");

set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");

set_perm(0, 0, 0755, "/system/etc/bluetooth");

set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");

set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");

set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");

set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");

set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");

set_perm(0, 0, 04755, "/system/bin/bash");

symlink("/system/bin/bash", "/system/bin/sh");

set_perm(0, 0, 04755, "/system/xbin/nano");

set_perm(0, 0, 04755, "/system/xbin/sysrw");

set_perm(0, 0, 04755, "/system/xbin/sysro");

set_perm(0, 0, 06755, "/system/bin/su");

symlink("/system/bin/su", "/system/xbin/su");

set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");

set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");

set_perm_recursive(0, 2000, 0755, 0755, "/system/vendor/bin");

set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");

set_perm(0, 2000, 0755, "/system/vendor/firmware");

set_perm(0, 2000, 0755, "/system/vendor/lib");

set_perm(0, 2000, 0755, "/system/vendor/lib/egl");

set_perm(0, 2000, 0755, "/system/vendor/lib/hw");

set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");

set_perm(0, 1000, 0755, "/system/xbin/busybox");

symlink("/system/xbin/busybox", "/system/bin/busybox");

package_extract_file("installbusybox", "/tmp/installbusybox");

set_perm(0, 0, 0777, "/tmp/installbusybox");

run_program("/tmp/installbusybox");

show_progress(0.1, 10);

show_progress(0.2, 0);

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot"),

delete("/tmp/boot.img"));

show_progress(0.2, 10);

unmount("/system");

0

Share this post


Link to post
Share on other sites

Posted · Report post

I've compared it to Paul's ROM, and can see the difference:

Mine:

write_raw_image("/tmp/boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot"),

As opposed:

package_extract_file("boot.img", "/tmp/boot.img");

run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");

delete("/tmp/boot.img");

I'd imagine changing them over would work?

0

Share this post


Link to post
Share on other sites

Posted · Report post

New release of dsixda kitchen so gonna try that now - fingers crossed!

0

Share this post


Link to post
Share on other sites

Posted · Report post

I've compared it to Paul's ROM, and can see the difference:

Mine:

write_raw_image("/tmp/boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot"),

As opposed:

package_extract_file("boot.img", "/tmp/boot.img");

run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");

delete("/tmp/boot.img");

I'd imagine changing them over would work?

Yes... beacuse you haven't extracted the boot.img from your update.zip before you're trying to write it... :)

0

Share this post


Link to post
Share on other sites

Posted · Report post

Strange how HTC devices don't have this issue, the kitchen just works as is (but then again it was written to HTC devices originally)

Just making the ROM now and will double-check the updater-script. If it's still the same I'll nick it from Paul's script

0

Share this post


Link to post
Share on other sites

Posted · Report post

updater-script now correct :D

0

Share this post


Link to post
Share on other sites

Posted · Report post

Spoke to soon, came error code :(

Gonna have to look into this a bit deeper

0

Share this post


Link to post
Share on other sites

Posted · Report post

It extracts but does it differently:

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot"),

delete("/tmp/boot.img"));

I'm guessing it's still the issue?

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

It extracts but does it differently:

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot"),

delete("/tmp/boot.img"));

I'm guessing it's still the issue?

Is the boot.img actually being extracted to /tmp? Maybe its not extracting the file properly due to perms & then fails to do the write?

I guess a logcat would show if it extracted the boot.img ok?

Also, what development environment are you using to compile the etc? I'm interested in making my own roms too.

Edited by MonkeyBoy451
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Initial ICS was compiled in a VirtualBox Ubuntu 64-bit VM environment, following this guide:

http://www.freeyoura...ide/compile-ics

Once I had the resulting .IMG files I use my normal Ubuntu 11.10 VirtualBox VM to use the dsixda kitchen (v0.182) which works as normal but gives me THAT error when trying to flash.

How can I logcat if I'm not in Android? HTC devices are a piece of piss compared to compiling from source! :D

Edited by EddyOS
0

Share this post


Link to post
Share on other sites

Posted · Report post

Initial ICS was compiled in a VirtualBox Ubuntu 64-bit VM environment, following this guide:

http://www.freeyoura...ide/compile-ics

Once I had the resulting .IMG files I use my normal Ubuntu 11.10 VirtualBox VM to use the dsixda kitchen (v0.182) which works as normal but gives me THAT error when trying to flash

Cheers. will give it a look over. :)

any luck with looking in the logcat to see if boot.img actually exists/extracts to /tmp ?

0

Share this post


Link to post
Share on other sites

Posted · Report post

See my edit - how do I logcat when not in Android?

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Edited updater-script to same as Paul's and it works - will have to report it to dsixda and see if he can fix it

EDIT: Spoke to soon - boot loop! :(

This is annoying

Edited by EddyOS
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

See my edit - how do I logcat when not in Android?

You can get the logs via adb I believe. adb logcat > logcat.log if the phone is visible to adb - even while its bootlooping, or pull the log from the phone with ADB pull.

or try running DDMS from the SDK.

Edited by MonkeyBoy451
0

Share this post


Link to post
Share on other sites

Posted · Report post

FINALLY got the ROM to boot but it's lagging like hell, and it has no setup wizard which is a bit annoying - even though the setup wizard app is in the ROM. As for Gapps, I got them from the 4.0.2 Google image and all seemed to work fine

Also got no lock screen :blink:

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.