[Q] What the hell is going on? (SOLVED)

---

I'm trying to load a new CM ROM but I keep getting an abortion message. Here's the log. Can anyone tell me what I'm doing wrong? I'm using rom manager with clockwork.


Starting recovery on Thu May 31 12:03:15 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext ext4 /dev/block/mmcblk0p2 (null)

I:Completed outputting fstab.
I:Processing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRJ22
ro.build.display.id=GRJ90
ro.build.version.incremental=eng.koush.20110905.10 3150
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Sep 5 10:32:20 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Nexus One
ro.product.brand=google
ro.product.name=passion
ro.product.device=passion
ro.product.board=mahimahi
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=passion
ro.build.description=passion-user 2.3.4 GRJ22 121341 release-keys
ro.build.fingerprint=google/passion/passion:2.3.4/GRJ22/121341:user/release-keys
keyguard.no_require_sim=true
ro.sf.lcd_density=240
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.telephony.default_network=0
ro.opengles.version=131072
dalvik.vm.heapsize=32m
media.a1026.nsForVoiceRec=0
media.a1026.enableA1026=1
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,12 0,122,110,119,995
ro.ril.emc.mode=2
ro.modversion=CyanogenMod-7.1.0-RC1-N1-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT0CJP801701
ro.bootmode=recovery
ro.baseband=5.08.00.04
ro.carrier=GOOGLE
ro.bootloader=0.35.0017
ro.hardware=mahimahi
ro.revision=132
init.svc.recovery=running
init.svc.adbd=running

I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
f532ff99d0b616d54bd1fec6e4b345de

f532ff99d0b616d54bd1fec6e4b345de

I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.7");
ui_print("May 31, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
format("/cache");
format("/data");
format("/sd-ext");
assert(install_zip("/sdcard/update-cm-7.2.0-RC3-p500-signed.zip"));

parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.7
May 31, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Formatting /cache...
mtd: not erasing bad block at 0x01360000
mtd: not erasing bad block at 0x020e0000
mtd: not erasing bad block at 0x03600000
Formatting /data...
mtd: not erasing bad block at 0x00b00000
mtd: not erasing bad block at 0x02220000
mtd: not erasing bad block at 0x067e0000
mtd: not erasing bad block at 0x0af80000
mtd: not erasing bad block at 0x0b7e0000
Formatting /sd-ext...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2

-- Installing: /sdcard/update-cm-7.2.0-RC3-p500-signed.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/update-cm-7.2.0-RC3-p500-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "thunderg" || getprop("ro.build.product") == "thunderg" || getprop("ro.product.board") == "thunderg" ||
getprop("ro.product.device") == "p500" || getprop("ro.build.product") == "p500" || getprop("ro.product.board") == "p500"
assert failed: getprop("ro.product.device") == "thunderg" || getprop("ro.build.product") == "thunderg" || getprop("ro.product.board") == "thunderg" || getprop("ro.product.device") == "p500" || getprop("ro.build.product") == "p500" || getprop("ro.product.board") == "p500"
E:Error in /sdcard/update-cm-7.2.0-RC3-p500-signed.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update-cm-7.2.0-RC3-p500-signed.zip")

You're trying to install CM for Optimus One, not for Nexus One. No wonder it fails while checking the type of device.

That's the one I got right from CyanogenMod for my particular phone.

Originally Posted by dieselfiend

That's the one I got right from CyanogenMod for my particular phone.

sometime it does that your best bet is use aroma 1st if that fails then use 4ext recovery

Hmm, what are you doing in Nexus One forums, asking questions about Optimus One?

In any case, your recovery (whatever it is) doesn't like the variables in your build.prop, of your current ROM. To force it to install, you can change updater-script to disable the assertion that fails, or change the build.prop for the assertion to pass.

Originally Posted by Jack_R1

Hmm, what are you doing in Nexus One forums, asking questions about Optimus One?

In any case, your recovery (whatever it is) doesn't like the variables in your build.prop, of your current ROM. To force it to install, you can change updater-script to disable the assertion that fails, or change the build.prop for the assertion to pass.

hahaha what he said

Man, I admire your knowledge level on this. Can you put in dummy terms?

Sent from my GT-I9100 using Tapatalk 2

I'll try to explain:

There is a file in your current ROM, as in any Android ROM. It's called build.prop, and it sits under /system, as in: /system/build.prop.
This file holds many variables' values, useful for Android boot-up and operation.

3 values interest you:
ro.product.device
ro.build.product
ro.product.board

"Assertion" = some part of the update script of the ROM that runs when you're trying to flash it. This part is checking the variables above, looking for specific values.

If assertion doesn't find the values it's looking for - it errors out and stops the update.

So, 2 ways to deal with it:

1) Change the file /system/build.prop, edit the values of those variables to something that won't trigger assertion failure.

2) Remove the assertion from the update script that is in your ROM.

Given that you have root, the first way should be easier. Just edit the values of those variables, find them in the file, add if some are missing (unlikely), and set all of them to "p500".

I got it to work. I was actually trying to install a ROM for another phone. I didn't realize that I clicked a link that was for a bunch of different phones rather than just mine. I downloaded the right ROM for my phone and all is well. It installed perfectly. Thanks for all the help!