Database Develop

[SOLVED] Flash custom ROM with ADB

Is there any way to flash a custom rom with ADB? I would assume there is, as ADB can do everything else, heh.
I have read up on the ADB tutorials and such that are on here, as well as the stuff that is supplied with a quick google search, and have not been able to find anything significant to this specific question.
Any advice would be great. Thanks
EDIT:
So, digging around in the DroidExplorer source code, I came across this:
Code:
public void ApplyUpdate ( string device ) {
/*
mkdir -p /cache/recovery/
echo 'boot-recovery' >/cache/recovery/command
echo '--nandroid' >> /cache/recovery/command
echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command
*/
ShellRun ( device, "mkdir -p /cache/recovery/" );
ShellRun ( device, "echo 'boot-recovery ' > /cache/recovery/command" );
//ShellRun ( device, "echo '--nandroid ' >> /cache/recovery/command" );
ShellRun ( device, "echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command" );
RebootRecovery ( device );
}
So I opened up ADB, and began plunking around.
I started from the recovery menu, in console mode.
Code:
C:\Users\Jason>adb shell
/ # recovery --update_package=/sdcard/update.zip
recovery --update_package=/sdcard/update.zip
C:\Users\Jason>
That restarted recovery mode, and attempted to mount/load/verify/flash update.zip. I did not have an update.zip on the SDCard, so naturally it errored out (yay).
Next, I decided to try a few things with the phone booted up:
Code:
C:\Users\Jason>adb remount
remount succeeded
C:\Users\Jason>adb shell "echo 'boot-recovery ' > /cache/recovery/command"
C:\Users\Jason>adb shell "echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command"
C:\Users\Jason>adb shell "reboot recovery"
C:\Users\Jason>
That in turn rebooted the G1, and again, attempted to install the update.zip.
Complete output of the RA-Dream-v1.5.2 is as follows:
Code:
Build : RA-dream-v1.5.2
Finding update package...
Opening update pacakge...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
That leads me to believe that this process should work flawlessly, as long as I point to the correct .zip file (update.zip, or SuperD-AOSP...zip).
Now, another thing that I need to do is to figure out how to perform the wipe actions that the recovery menu has. Does anyone know what is ran when I choose any of the 3 wipe options? (I assume they are just rm -rf on the appropriate directories, but I would like to be sure first)
EDIT2:
Gotta love open source After quite a bit more googling, this is what I found (located in the source code for ra-dream-v1.5.2):
Code:
* The arguments which may be supplied in the recovery.command file:
* --send_intent=anystring - write the text out to recovery.intent
* --update_package=root:path - verify install an OTA package file
* --wipe_data - erase user data (and cache), then reboot
* --wipe_cache - wipe cache (but not user data), then reboot
As well as:
Code:
recovery.c(849): "/sbin/wipe dalvik",
recovery.c(859): "/sbin/wipe ext",
recovery.c(869): "/sbin/wipe battery",
recovery.c(879): "/sbin/wipe rotate",
Using that information, I think I can finally start my lil applicatoin, heh. Thanks for letting me answer my own questions (I wont argue with a good learning experience)

Thanks dude been tryna figure this out for a week and stumbled on ur thread...played around with the commands and got data wipe cache wipe to work but couldnt figure out dalvik or ext wipe...flashed cyan rc3 and gapps. thanks again, my home button doesnt work and couldnt get anything done in the recovery menu. props!

Did you manage to write the application for ADB ROM flash? My home button and trackball do not work. ADB ROM install/flash is my only hope.
Shayind4

AWESOME!
I just ran the few lines as follows with all my info there, and it was the ONLY way to load a new rom. My cliq has a broken home key, making it impossible to use any recovery. Props for these lines, helped teach a newb something.
C:\Users\Jason>adb remount
remount succeeded
C:\Users\Jason>adb shell "echo 'boot-recovery ' > /cache/recovery/command"
C:\Users\Jason>adb shell "echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command"
C:\Users\Jason>adb shell "reboot recovery"

I was just thinking of giving this a try because i thought using adb might go faster than just going the cwm or watever route using just rom mgr or what have you, so does it go by as fast as it does using cwm? or does adb do it faster?
I assume its the same but I'm just wondering what your experience says

@jmhecker: Did you know how to install a ROM from my PC or maybe from CACHE or DATA directory? I'm trying to install this one http://forum.xda-developers.com/showthread.php?t=1011384 but I get errors while trying to do I think due to space because this ROM has 81MB and my phone is a HTC Magic without sdcard due to hardware problems. Any tip or help on this?
Cheers and thx in advance

Thank you!
You have no idea how much help you were to me.
I just bought this unbranded chinese tablet and i tried to set a pattern unlock to it, then to find out that it didn't accept my pattern afterwards.. I was essentially locked out of the thing that i just bought.. I eventually figured out the key combination to access recovery mode but for some reason it seemed to auto select update via sdcard... But the first thing it would check for is a file called "factory_update_param.aml", googled it and it was a simple text file with
--update_package=/sdcard/update.zip
within it. Searching for it i came across it your post, linking the two together i had realised the manufacturer had locked out the recovery mode and replaced it with a simple script that would run whatever stated in the file.
I just replaced it with the
--wipe_data
as you stated and it worked wonders! Factory reset and back to the way i first opened it out of the box!
You saved me 50$ for the shipping back to hong kong! Thank you!

This post is just what I'm looking for.
I have bricked my tablet: Storage Options Scroll 7". I've been looking for a solution and I think the only way is to flash the original Firmware with adb commands.
My only problem is when I write "adb shell" the computer says that can't find the device. I tried diferent drivers with no luck. On the device manager the Android is in yellow and doesn't recognize the device. I tried with the google drivers from SDK and the VTC drivers without any luck.
What drivers did you use?
If I can get the right drivers this method will save my scroll tablet.
Thanks

You saved my tab.
My tab sdcard not read, so I had to change little for adb commands.
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
adb shell "echo '--update_package=/nand/update.zip' >> /cache/recovery/command"
adb shell "reboot recovery"
Click to expand...
Click to collapse
)
( this didn't work for me: adb shell "echo '--update_package=nand:update.zip' >> /cache/recovery/command"
Thanks to you everything is ok

Hello i was trying to flash update.zip this way but i bumped into wall -.-
In my /cache/recovery/last_log i saw this lines
Finding update package...
I:Update location: SDCARD:/update.zip
E:unknown volume for path [SDCARD:/update.zip]
E:Can't mount SDCARD:/update.zip
Installation aborted.
Click to expand...
Click to collapse
i tryed with
--update_package=SDCARD:update.zip
and
--update_package=/sdcard/update.zip
Phone boot into recovery but end's with (dead xD) green android with opened chest
and big ugly red triangle with !
At that point adb is still working i write adb reboot and phone boot normally and then i take a look in last_log...
Any help with this one?
Edit: strange thing that in last_log before those error lines recovery seems to read my new build info
Code:
Starting recovery on Thu Jul 5 13:49:00 2012
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p16 (null) 0
3 /data ext4 /dev/block/mmcblk0p20 (null) 0
4 /misc emmc /dev/block/mmcblk0p8 (null) 0
5 /recovery emmc /dev/block/mmcblk0p17 (null) 0
6 /system ext4 /dev/block/mmcblk0p14 (null) 0
call get_bootloader_message
get_args:
I:Got arguments from /cache/recovery/command
I:fopen_path 1 /data/fota/ipth-muc.prop
I:fopen_path 2 /data/fota/ipth-muc.prop
I:fopen_path 3 /data/fota/ipth-muc.prop
I:Failed to open /data/fota/ipth-muc.prop, use default pkg location:/cache/fota
I:Delta package does not exist /cache/fota/ipth_package.bin
recovery.c : import_kernel_cmdline lge.frst = flag3
framebuffer: fd 4 (480 x 800)
Command: "/sbin/recovery" "--update_package=SDCARD:/update.zip"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.build.id=Optimus_L7_Revolution
ro.build.display.id=Optimus_L7_Revolution
ro.build.version.incremental=lgp700-V10g.rooted
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012. 06. 23. (토) 08:17:57 KST
ro.build.date.utc=1340407077
ro.build.type=user
ro.build.user=bgdonline
ro.build.host=anemone
ro.build.tags=test-keys
ro.product.model=LG-P700
ro.product.brand=lge
ro.product.name=u0_open_eu
ro.product.device=u0
ro.product.board=7x27
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=GB,en
ro.wifi.channels=
ro.board.platform=msm7627a
ro.build.product=u0
ro.build.description=u0_open_eu-user 4.0.3 Optimus_L7_Revolution lgp700-V10g.rooted test-keys
ro.build.fingerprint=lge/u0_open_eu/u0:4.0.3/Optimus_L7_Revolution/lgp700-V10g.rooted:user/test-keys
ro.build.characteristics=default
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.enabletr=false
debug.composition.7x27A.type=mdp
debug.composition.7x25A.type=mdp
persist.gsm.sms.forcegsm7=1
persist.cne.UseCne=none
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.fmc.mode=false
persist.cne.fmc.init.time.out=30
persist.cne.fmc.comm.time.out=130
persist.cne.fmc.retry=false
media.stagefright.enable-player=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
ro.opengles.version=131072
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
persist.ims.regmanager.mode=0
ro.bluetooth.request.master=false
ro.qualcomm.bluetooth.ftp=true
ro.qualcomm.bluetooth.sap=false
ro.qualcomm.bluetooth.hfp.wbs=false
ro.bluetooth.remote.autoconnect=true
persist.omh.enabled=1
ro.config.ehrpd=true
ro.qualcomm.cabl=1
ro.fm.analogpath.supported=true
ro.fm.transmitter=false
ro.fm.mulinst.recording.support=false
ro.hw_plat=7x27a
ro.emmc.sdcard.partition=20
debug.camcorder.disablemeta=0
ro.hiddenreset=0
ro.device.hapticfeedback=0
ro.lge.swversion=V10g-JUN-23-2012
ro.lge.hwversion=
ro.lge.factoryswversion=
ro.lge.basebandversion=MSM7227A-1-AA
hwui.render_dirty_regions=false
ro.max.fling_velocity=5000
ro.hwui.text_cache_width=1536
ro.hwui.text_cache_height=384
ro.build.target_operator=OPEN
ro.build.target_country=EU
ro.build.target_region=EU
ro.build.factory_operator=EUR
ro.build.factory_country=XX
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.yt=android-lge
ro.com.google.clientidbase.am=android-lge
ro.com.google.clientidbase.ms=android-lge
ro.camera.sound.forced=1
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Beyond_the_Dream.ogg
ro.config.notification_sound=Pebble.ogg
ro.config.alarm_alert=Alarm1.ogg
ro.vendor.extension_library=/system/lib/libqc-opt.so
persist.radio.cdg2_flag=false
wifi.supplicant_scan_interval=20
wlan.chip.vendor=qcom
ro.lge.touchkey=BACK|HOME|MENU
ro.device.networkmode=WCDMA
ro.telephony.default_network=3
ro.radio.ratdisplay=true
ro.config.bt.amp=no
ro.sf.lcd_density=240
media.video.max-width=854
media.video.max-height=480
media.divx-video.max-width=854
media.divx-video.max-height=480
ro.emmc=0
ro.sf.hwrotation=180
ro.lge.audio_scenario=SOUNDEXCEPTION
ro.lge.audio_soundexception=true
ro.lge.audio_soundprofile=true
lge.signed_image=true
dalvik.vm.heapstartsize=10m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
drm.service.enabled=true
ro.lge.capp_core=true
ro.lge.capp_drm=true
ro.lge.capp_divx_drm=true
ro.lge.capp_almond=true
ro.lge.capp_optimusui=true
ro.lge.capp_resource=true
ro.lge.capp_wapservice=true
ro.lge.lazy_service_bringup=true
ro.lge.capp_touch_scroller=true
ro.lge.capp_touch_ldi=true
ro.lge.capp_key_light_off=true
ro.lge.capp_key_exception=true
ro.lge.capp_keyled_timeout=true
ro.lge.capp_lockscreen=true
ro.com.google.gmsversion=4.0_r2
ro.setupwizard.mode=DISABLED
ro.livewallpaper.map=DISABLED
ro.nfc.port=I2C
lge.nfc.fwpatchv13=yes
lge.nfc.indicator=yes
lge.nfc.setype=uicc
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=bd28a52
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=u0
ro.revision=0
ro.crypto.fs_type=ext4
ro.crypto.fs_real_blkdev=/dev/block/mmcblk0p20
ro.crypto.fs_mnt_point=/data
ro.crypto.fs_options=barrier=1,data=ordered,noauto_da_alloc,errors=panic
ro.crypto.fs_flags=0x00000406
ro.crypto.state=unencrypted
ro.encrypt_state=0
persist.sys.usb.config=charge_only,adb
persist.radio.adb_log_on=0
persist.radio.mem_leak_debug=0
persist.radio.voip_enabled=0
persist.radio.sma_voice_3gpp=0
persist.radio.net_pref_0=2
persist.radio.net_pref_1=3
persist.radio.tuneaway=1
persist.radio.paging_priority=0
persist.radio.mcc-list=FFF
persist.radio.first_no_sim=
persist.radio.iccid-changed=0
persist.radio.iccid=8938105210033115009
persist.radio.prev-mcc=220
persist.radio.same-mcc=1
persist.radio.tmp-mcc=220
persist.radio.first-mcc=220
persist.radio.first-boot=11
persist.service.bt.bdaddr=c0:cc:e5:c6:a0:00
persist.sys.profiler_ms=0
persist.service.system.dirty=1
persist.lge.first_boot=0
persist.sys.timezone=Europe
persist.sys.language=en
persist.sys.country=GB
persist.sys.localevar=
persist.gsm.mms.enabled=true
persist.sys.system_volume=4
persist.sys.sound_enable=1
init.svc.brd=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.rmt_storage=running
init.svc.atd=restarting
Finding update package...
I:Update location: SDCARD:/update.zip
E:unknown volume for path [SDCARD:/update.zip]
E:Can't mount SDCARD:/update.zip
Installation aborted.

the android with the open chest is showing it is trying to apply update. the triangle with ! is the defult recovery screen.
so I take it you don't have a custom recovery, are you rooted?
Sent from my HTC Vision using xda premium

demkantor said:
the android with the open chest is showing it is trying to apply update. the triangle with ! is the defult recovery screen.
so I take it you don't have a custom recovery, are you rooted?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Rooted yes, custom recovery i still can't use untill Secure booting is off.... This lg model (optimus l7) have Secure boot and custom recovery can't work on stock rom, that is why i try this way....

got ya, don't know much about lgs - maybe ask in that forum
Sent from my HTC Vision using xda premium

This solution works generally in android im just curious why recovery can't mount sdcard and is it possible to flash it from internal memory? Because when im in root explorer and when im in / i have /sdcard < internal memory and /sdcard/external_sd < external memory
btw we still don't have our sub forum im only one currently working on this model

Will this only work with RA recovery or other ones like TeamWin?

dont know what teamwin recovery is (assume its for the evo 4g) but it should work fine as a few other posters got it workinig with other recoveries.
but even if it doest an unlocked bootloader should allow you to do all the commands via fastboot, wipe flash etc.

jmhecker said:
Code:
C:\Users\Jason>adb remount
remount succeeded
C:\Users\Jason>adb shell "echo 'boot-recovery ' > /cache/recovery/command"
C:\Users\Jason>adb shell "echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command"
C:\Users\Jason>adb shell "reboot recovery"
C:\Users\Jason>
Click to expand...
Click to collapse
I just tried to do that with my custom ROM but I got this error:
Code:
Finding update package...
I:Update location: /sdcard/my_custom_rom.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.
My ROM is signed with test-key same as the one in /res/keys, I can't understand why the error..

does your recovery support turning off sig check? if not you may need to find a new method of signing
Sent from my HTC Vision using xda premium

demkantor said:
does your recovery support turning off sig check? if not you may need to find a new method of signing
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I'm using CWM 5.0.2.8; from the menu I can disable the signature verification but can't do it via cmd line.
I'm wondering why I can't flash my ROM even if /res/keys and CERT.RSA using the same key?! I'm missing something?

How to flash roms using Amon RA 1.5.2

I ended up re-rooting my phone before I was using Cyanogen Recovery 1.4 and I was flashing my phone with roms just fine (also i'm using CM Update 4.2.14.1)...
But I have a question am I doing something wrong since im using a different recovery? I'm downloading the same roms that I had before such as the MLIGN-Hero V3.3 but for some reason they wont load it gets all they way up to copying files and all the roms abort with this error
E:Cant chown/mod/ system /xbin
(No such file or directory)
E:Failure at line 80:
set_perm_recursive 0 2000 0755 0
Installation aborted.
Could anyone help with this issue?

You need the 1.33.2005 spl.

Recovery / Edify / Data Mount Issue

Hi,
I'm trying to mount /data with GT-5570I using recovery / updater-script.
However, I'm stuck with an issue, I just don't know what's happening :
running the script :
Code:
run_program("/system/xbin/busybox","mount","-t rfs","/dev/stl11","/data");
the log in /cache/recovery/last_log says :
Code:
Mount : cannot mount /dev/stl11 on /data : no such device
however, if I start adbd using
Code:
run_program("/sbin/adbd")
right in recovery, and sending
Code:
# /system/xbin/busybox mount -t rfs /dev/stl11 /data
/data mounts fine.
Now the big question :
Why isn't it possible to mount /data using recovery script, but running adbd in recovery, I am able to mount /data in recovery ?
Any ideas ?

wrong section dude
and u manually boot into recovery? i turn off my phone and i boot it myself and i cant mount/ anything.....but u must tryboot yr device to recovery at ur power menu(only some rom got this option,in my exp gb no this option)...and it will solve the cache log prob...its work for me
Sent from my GT-S5570 using XDA

Wrong section bro!! This is for dev only, post such things in general!!
Sent from my GT-S5570 using xda premium

It's nothing general, it's dev actually. I'm not talking about how to enter recovery, but about scripting and developing own recovery / custom recovery.
But thanks so far for your answers.

recovery already has mount command...try this one to mout your /data partition
Code:
mount("rfs", "EMMC", "/dev/block/stl11", "/data");
if you want to use run_program command, you can make a file contain
Code:
#!/system/bin/sh
mount -t rfs /dev/block/stl11 /data
put that file on your root folder of your zip file. to run the script you'll need to use these command on updater script
Code:
package_extract_file("<your filename>", "/tmp/<your filename>");
set_perm(0, 0, 0777, "/tmp/<your filename>");
run_program("/tmp/<your filename>");
the first method is easier...

viperbjk said:
Hi,
I'm trying to mount /data with GT-5570I using recovery / update-script.
However, I'm stuck with an issue, I just don't know what's happening :
running the script :
Code:
run_program("/system/xbin/busybox","mount","-t rfs","/dev/stl11","/data");
the log in /cache/recovery/last_log says :
Code:
Mount : cannot mount /dev/stl11 on /data : no such device
however, if I start adbd using
Code:
run_program("/sbin/adbd")
right in recovery, and sending
Code:
# /system/xbin/busybox mount -t rfs /dev/stl11 /data
/data mounts fine.
Now the big question :
Why isn't it possible to mount /data using recovery script, but running adbd in recovery, I am able to mount /data in recovery ?
Any ideas ?
Click to expand...
Click to collapse
Hello
you use what
update-script ?
if yesy is wrong for edify on edify is caled
updater-script and commande on it is diferant from amend script [ update-script]

viperbjk said:
Hi,
I'm trying to mount /data with GT-5570I using recovery / update-script.
However, I'm stuck with an issue, I just don't know what's happening :
running the script :
Code:
run_program("/system/xbin/busybox","mount","-t rfs","/dev/stl11","/data");
the log in /cache/recovery/last_log says :
Code:
Mount : cannot mount /dev/stl11 on /data : no such device
however, if I start adbd using
Code:
run_program("/sbin/adbd")
right in recovery, and sending
Code:
# /system/xbin/busybox mount -t rfs /dev/stl11 /data
/data mounts fine.
Now the big question :
Why isn't it possible to mount /data using recovery script, but running adbd in recovery, I am able to mount /data in recovery ?
Any ideas ?
Click to expand...
Click to collapse
If you are still using update-script then, I suggest you switch to updater-script and update-binary since, latest clockwork mod (v3 and above use these Edify scripting methods...).
I believe you are trying to mount data to copy files to or from /data/ partition on your device...
Here's a script to do so in recovery and I'm sure it's the exact thing you are looking for :
http://handyinformation.freevar.com/showthread.php?tid=12
Good luck!

try it
Code:
mount("rfs", "/dev/block/stl11", "/data");

ahmadsafar said:
try it
Code:
mount("rfs", "/dev/block/stl11", "/data");
Click to expand...
Click to collapse
This one is leading into "E:Error in /tmp/sideload/package.zip (Status 0)"
last_log says that :
MountFn, 53
MountFn : type is rfs
MountFn : rfs type
MountFn result is : /data
;(

kurotsugi said:
recovery already has mount command...try this one to mout your /data partition
Code:
mount("rfs", "EMMC", "/dev/block/stl11", "/data");
if you want to use run_program command, you can make a file contain
Code:
#!/system/bin/sh
mount -t rfs /dev/block/stl11 /data
put that file on your root folder of your zip file. to run the script you'll need to use these command on updater script
Code:
package_extract_file("<your filename>", "/tmp/<your filename>");
set_perm(0, 0, 0777, "/tmp/<your filename>");
run_program("/tmp/<your filename>");
the first method is easier...
Click to expand...
Click to collapse
The first one doesn't work with my update-binary as it's the new AOSP one only taking 3 variables instead of four.
using mount("rfs", "/dev/block/stl11", "/data") or mount("emmc","/dev/block/stl11","/data") leads to "E:Error in /tmp/sideload/package.zip (Status 0)"
Using the second one, the sh method, this leads into the same error message, "No such device".
I'm guessing that the main problem might be some driver/init adbd does for mounting ....

yagya said:
If you are still using update-script then, I suggest you switch to updater-script and update-binary since, latest clockwork mod (v3 and above use these Edify scripting methods...).
I believe you are trying to mount data to copy files to or from /data/ partition on your device...
Here's a script to do so in recovery and I'm sure it's the exact thing you are looking for :
http://handyinformation.freevar.com/showthread.php?tid=12
Good luck!
Click to expand...
Click to collapse
Yeah, I basically just try to mount /data to access files. Sorry for the typo, it's updater-script of course.
When I just try to use
run_program("/system/xbin/busybox", "mount", "/data");
it isn't accepted because of
"mount: can't read '/etc/fstab': No such file or directory"

Ok, guys ... found the solution ...
mount("rfs", "EMMC", "/dev/stl11", "/data");
is working, but only using old updater-binary. Seems the AOSP
one doesn't work ... no idea why.
Many thanks for helping me out !

there's a possibility that the AOSP one doesn't compatible with the recovery.

viperbjk said:
Yeah, I basically just try to mount /data to access files. Sorry for the typo, it's updater-script of course.
When I just try to use
run_program("/system/xbin/busybox", "mount", "/data");
it isn't accepted because of
"mount: can't read '/etc/fstab': No such file or directory"
Click to expand...
Click to collapse
Well, it's probably because you don't have busybox installed. Are you sure you are rooted and have latest busybox version installed on your system?
Also, which rom do you have now?

I'm using stock rom, and yes, busybox and root is also done in recovery.
The GT-5570i hasn't got a fstab file, so that's fine.
Everything is working fine now, it was obviously that the samsung update-bin didn't work with mobiles with broadcom chipset.

try this, it's working
http://forum.xda-developers.com/showthread.php?p=27018781

meccaandroid said:
try this, it's working
http://forum.xda-developers.com/showthread.php?p=27018781
Click to expand...
Click to collapse
No. This has to do with the binary n not amend.
The issue has been resolved, so rip thread.

[Q]Install CyanogenMod 10

I would to install cyanogenmod 10... I started from GB stock firmware(overcome I think)... I rooted device, then I put the zip file on internal memory... I started device holding power on and volup key... I wiped data/factory reset, then wiped cache... I finally chose install zip card but I received this error:
Installing /sdcard/cm-10-20120908-NIGHTLY-p1.zip
Finding update package
Opening update package
Installing update
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-10-20120908-NIGHTLY-p1.zip
(status 7)
Installation aborted.
I did a sho log in advanced menu:
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't partition unsafe device:/dev/block/mmcblk1p1
I don't understand what I should to do... Can you help me???
My device is a p1000(gsm)... Now is accessible only in download mode and in CWM recovery...

I solved with one more step... First I returned to stock GB, then installed CM9 and updated to CM10 with cdesai instruction... Installation finished...

[Q] assert failed Status 7

I am currently running cm-10.2-20131225-UNOFFICIAL-tenderloin.zip. I decided to install latest build 20140110. I wipe the dalvik cache and cache partition then try to install zip from /sdcard/0/Download but get the following
assert failed: getprop("ro.product.device") == || "tenderloin" || getprop("ro.build.product") == "tenderloin"
E:Error in /data/media/0/Download/cm-10.20140110-UNOFFICIAL-tenderloin.zip
(Status 7)
Installation aborted.
Since i installed 20131225 i have increased the system partition from 512mb to 600mb using Tailor and upgraded Datamedia CWM from 6.0.3.6 to 6.0.4.6 in preparation for trying Kitkat.
I get the same whatever the zip. I thought maybe 6.0.4.6 is only for Kitkat and tried going back to 6.0.3.6. but same error and same with other builds.
Prior to 20131225 i have done many dirty flashes without any problem.
Any ideas on how to fix?

Cranleigh said:
I am currently running cm-10.2-20131225-UNOFFICIAL-tenderloin.zip. I decided to install latest build 20140110. I wipe the dalvik cache and cache partition then try to install zip from /sdcard/0/Download but get the following
assert failed: getprop("ro.product.device") == || "tenderloin" || getprop("ro.build.product") == "tenderloin"
E:Error in /data/media/0/Download/cm-10.20140110-UNOFFICIAL-tenderloin.zip
(Status 7)
Installation aborted.
Since i installed 20131225 i have increased the system partition from 512mb to 600mb using Tailor and upgraded Datamedia CWM from 6.0.3.6 to 6.0.4.6 in preparation for trying Kitkat.
I get the same whatever the zip. I thought maybe 6.0.4.6 is only for Kitkat and tried going back to 6.0.3.6. but same error and same with other builds.
Prior to 20131225 i have done many dirty flashes without any problem.
Any ideas on how to fix?
Click to expand...
Click to collapse
I just updated from CM9 to CM10.2 Nightlies and had this problem while flashing. I followed this: h**p://forums.androidcentral.com/optimus-v-rooting-roms-hacks/182438-solved-assert-failed.html
Essentially, I extracted the ONE file (/META-INF/com/google/android/updater-script), opened it up in Notepad, removed the first line of code up to, and including, the semi-colon (for me it was assert(getprop("ro.product.device") == "tenderloin" || getprop("ro.build.product") == "tenderloin");
mount("ext4", "EMMC", "/dev/store/cm-system", "/system");), and then replaced this modified one back into the .zip file. Flashed it and it finally installed!

Fixed
Thanks. Did as you suggested and it installed as normal.
It would be nice to know what the problem is. My build.prop looks OK, so is it looking in the wrong folder or...?

Error "Status 7" on update ...
I got the same issue trying to install cm-10.2-20140203-UNOFFICIAL-tenderloin.zip.
Actual running version: 10.2 - 20140116
Same issue when selecting/updating other image versions (older one and newest 20140204).
Changing updater-script helpts to update with image.
Before that I do mass of updates on several TPs without any issues.
Whats going wrong there? Do we have to edit all the time the updater-script?
There seems to be wrong parameters on TP because "ro.product.device" or "ro.build.product" seems not to be "tenderloin" any more.
Where to check these parameters?
Thanks for help.
---------- Post added at 11:18 AM ---------- Previous post was at 10:39 AM ----------
dr.schnappata said:
I got the same issue trying to install cm-10.2-20140203-UNOFFICIAL-tenderloin.zip.
Actual running version: 10.2 - 20140116
Same issue when selecting/updating other image versions (older one and newest 20140204).
Changing updater-script helpts to update with image.
Before that I do mass of updates on several TPs without any issues.
Whats going wrong there? Do we have to edit all the time the updater-script?
There seems to be wrong parameters on TP because "ro.product.device" or "ro.build.product" seems not to be "tenderloin" any more.
Where to check these parameters?
Thanks for help.
Click to expand...
Click to collapse
OK, I found parameter file: /system/build.prop
All parameters are still correct:
ro.product.model=TouchPad
ro.product.brand=HP
ro.product.name=touchpad
ro.product.device=tenderloin
ro.product.board=tenderloin
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HP
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=tenderloin
On touchpad as well as in image file ...
Whats the issue? Is there anyone who can answer or explain?

fix
dr.schnappata said:
I got the same issue trying to install cm-10.2-20140203-UNOFFICIAL-tenderloin.zip.
Actual running version: 10.2 - 20140116
Same issue when selecting/updating other image versions (older one and newest 20140204).
Changing updater-script helpts to update with image.
Before that I do mass of updates on several TPs without any issues.
Whats going wrong there? Do we have to edit all the time the updater-script?
There seems to be wrong parameters on TP because "ro.product.device" or "ro.build.product" seems not to be "tenderloin" any more.
Where to check these parameters?
Thanks for help.
---------- Post added at 11:18 AM ---------- Previous post was at 10:39 AM ----------
OK, I found parameter file: /system/build.prop
All parameters are still correct:
ro.product.model=TouchPad
ro.product.brand=HP
ro.product.name=touchpad
ro.product.device=tenderloin
ro.product.board=tenderloin
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HP
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=tenderloin
On touchpad as well as in image file ...
Whats the issue? Is there anyone who can answer or explain?
Click to expand...
Click to collapse
just delete line strarting with :victory:assert