I'm new in ROMs creating and I've followed a LOT of tutorials to create my own ROM. Only one ROM works in my device, but the problem is this one have their bugs and isn't compactible very well. So I decided begin develop my ROM with the stock. I installed kitchen and made my ROM, deodexed the apps, installed busybox and root support, everything. I did not touched in any apps or other thinks, only in kitchen menu. After everything I builded the ROM with kitchen and tryed to flash it in my device.
In TWRP, when I flash I get the following error:
E:Error executing updater binary in zip 'external_sc/rom_name.zip
Click to expand...
Click to collapse
So, I got the Droidwin v3.1 update-binary (it's the unique ROM which worked in my device). After some errors corrections in the updater-script (and a lot of errors), I decided debugging the script, placing puts commands before every line. Now I stuck in this line (with the same error, "Error executing updater binary", but before commands are runned):
Code:
package_extract_dir("system", "/system");
I don't know what to do now, I don't have other META-INF folder to copy into my ROM.
All my updater-script: http://pastebin.com/eM48k1fu.
That's all, I hope you can help me. Sorry my english.
Related
Tried to get a clockworkmod working on my Visual Land 7L. Found a thread that gave me a clockwork recovery that worked with the Visual Land 7 (NOT 7L) but it still installed normally and even booted into it. Volume rocker didn't interact with the recovery so I rebooted. Took the recovery that same recovery and used CWM's Recovery Builder but added touch support. It finished successfully so I flashed the new recovery, now I can move through the menu but when I restart my phone it always goes into clockworkmod. Any help fixing this would be great. If I could just downgrade the recovery to the one that didn't mess up my tablet I'm sure I'd be fine but I only have a recovery.img and somewhere I read putting it in a zip named update by itself should be fine but installation always fails. The error is "Installation aborted."
Ok so I've made some progress, turns out I can install another recovery (the one that didn't brick my device) but it needs to be a recovery.img inside of a .zip file. On top of that a META-INF file with four or five subdirectories with two files at the end. One of which I think is just initializes the other one. I was able to edit the updater-script because I kept getting status errors. Now it'll start to install the image and show a progress bar but comes up with an error when it has to ask me if it's ok to keep going. The error is now just with Assert. No idea what I need to change. This is what my updater-script looks like when you open it in notepad.
show_progress(1.000000, 0);
ui_print("");
ui_print(" Notion Ink Adam Clockworkmod 3.0.2.8 051311 ");
ui_print("");
ui_print("---------------installing recovery.img----------");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "/system/bin/recovery"), delete("/tmp/recovery.img"));
ui_print("-----------------------------------------------");
ui_print("Installation done! Please reboot");
squirrelthingy said:
Ok so I've made some progress, turns out I can install another recovery (the one that didn't brick my device) but it needs to be a recovery.img inside of a .zip file. On top of that a META-INF file with four or five subdirectories with two files at the end. One of which I think is just initializes the other one. I was able to edit the updater-script because I kept getting status errors. Now it'll start to install the image and show a progress bar but comes up with an error when it has to ask me if it's ok to keep going. The error is now just with Assert. No idea what I need to change. This is what my updater-script looks like when you open it in notepad.
show_progress(1.000000, 0);
ui_print("");
ui_print(" Notion Ink Adam Clockworkmod 3.0.2.8 051311 ");
ui_print("");
ui_print("---------------installing recovery.img----------");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "/system/bin/recovery"), delete("/tmp/recovery.img"));
ui_print("-----------------------------------------------");
ui_print("Installation done! Please reboot");
Click to expand...
Click to collapse
Im in the same boat i cant get out of CWM for nothing it keeps saying cant mount well anything
Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
did you try to update script directly into zip file ?
I don't know which OS you are using (maybe windows ?), with linux, you can edit a file directly a zip file (file roller for me). After saving your file, zip is automatically updated.
if you are using winzip, i guess you can drag and drop updated file into your zip.
of course, you need to edit the zip file out of your tab.
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Kokapelly said:
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Click to expand...
Click to collapse
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
BatBat said:
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
Click to expand...
Click to collapse
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Kokapelly said:
Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
Click to expand...
Click to collapse
If you're seeing that, then you should update your CWM. It's not recognizing your tablet device. I'm using CWM 5.5.0.4 and it does recognize the P7510 as "p4wifi".
Kokapelly said:
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
Click to expand...
Click to collapse
If it's easier, edit the file and just insert a "#" before the "assert". That will comment it out. However, I'd recommend updating the recovery instead.
Success Story - you figure out how...
This is a SUCCESS story...
I got by this somehow, not sure what it was but will over communicate so someone else can figure out specifics.
updating my gt-p7510 from android 3.1 to Android 4.1.2 (CM 10 ROM 20121215 nightly)...
My tab was in weird state from a prior rom sequence (I had rooted it long ago.. some programs said it was rooted, but programs trying to get the permission, like titanium backup, would fail)
so I followed the instructions to root again from HERE
up to the point to the point where you load a ROM. ie. I loaded CWM 5.5.0.4 using odin3.
Then I downloaded the latest CM 10 , copied it to root folder on my tab... and tried to use CWM to install it...
got the "assert(getprop("ro.product.device") == "p4wifi" ... Failure...
went wild and tried other programs (ROM Manager, System Updater etc. avail from "Play Store" ... actually I had tried these prior to rooting again...
they failed before (not able to get root permissions) and after (not able to perform the update... assuming they got and hid similar error)
Tried to edit out the assert in the updater-script as in the prior post... but unzipping had a lot of duplicate file overrides (into clean folder) and they were not all exactly the same file (ie some had different sizes)... so gave up that path.
I had been avoiding updating CWM further because of k1mu's success above ... and avoided the "CWM Touch" flash as I thought base CWM would be better.
Went back to try to update CWM (went to www.clockworkmod.com) and was annoyed when I could not download the CWM zips... links returned characters in browser...
Finally went wild again... used ROM Manager Pro to update CWM to the latest "CWM Touch"
Surprisingly this updated CWM easily...
Then used it to Load the latest CM 10 nightly ... again shockingly easy AND successful... (no Assert failure)
ROM Manager did not automatically update the google apps ... so I got my first look at the CWM Touch interface installing gapps...
But it all worked... So LOVE ROM Manager...
(although for grins I also found and tried CM 10 downloader and retried System Updater Pro etc.. .they all work now)
But hats off to ROM Manager's update and to CWM touch for seemingly fixing all my problems.
lightman33 said:
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Click to expand...
Click to collapse
I open in notepad++ and here is the code from updater-script
Code:
assert(!less_than_int(1383478437, getprop("ro.build.date.utc")));
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
So do I need to delete full 1st line or 2nd line?
If I follow your instruction, I have to delete 2nd line...
EDITED:
Line 2 deleted! And done flashing
The answer to all of this: The problem is the recovery, not the update package, or the updater script.
The assert fails because CWM, TWRP, and some other modified recoveries do not include the getprop command in their small, ramdisk linux OS. So, when the assert tries to run getprop to check ANY property for the installed system, it fails.
Apparently CWM Touch has this binary included.
Custom recoveries generally don't think to include it because pretty much the only thing being flashed through them are custom roms, with their own custom installer scripts, and these rarely (have they ever?) include asserts checking for properties.
can anyone help me with uot kitchen. I am having no luck.
I am getting error in 'filename' (status 0)
i am on the stock rom (global) but rooted (fake ciid)
i have used uot on my other 2 phones with no issues even with odexed roms
i want a simple battery mod (version s, big sense) for now
i uploaded the proper files but it wont flash. so
which update binary should I use. I always used the type mtd default but I never had twrp before
suggestions
am I using the wrong update binary
should I just push them manually
do I need to delete the odex ( i didnt have to do this before)
pushing the files manually made no difference even though I checked the framework and it was fixed
renaming the framework-res.odex and framework-res.jar made the phone not boot i fixed tha tin fwrp filemanager (a great recovery by the way. I could not remount system in adb at the time)
So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.
Hey guys.
I am trying to combine a few flashable zips.
For the main system , modem and my tweaks this was no problem since all three zips use normal updater-script.
I'd like to add gapps and magisk as well as a custom kernel as well. problem: those don't use updater-script but 'misuse' update-binary as shell script.
How can i merge those ?
i tried putting the unzipped folders in the root directory of the flashable zip and added this to the updater-script but the outcome wasn't what i wanted..
Code:
...
ui_print("Installing Gapps... You wont see this....");
package_extract_dir("gapps", "/tmp/gapps");
run_program("/sbin/busybox","sh", "/tmp/gapps/META-INF/com/google/android/updater-binary");
ui_print("Installing custom Kernel... You wont see this....");
package_extract_dir("kernel", "/tmp/kernel");
run_program("/sbin/busybox","sh", "/tmp/kernel/META-INF/com/google/android/updater-binary");
ui_print("Installing Magisk... You wont see this....");
package_extract_dir("magisk", "/tmp/magisk");
run_program("/sbin/busybox","sh", "/tmp/magisk/META-INF/com/google/android/updater-binary");
...
something happens... takes about as long as the gapps/kernel/magisk install should take, however afterward no gapps/kernel/magisk available in the booted os.
If anyone can give me a hint how to merge those into one zip that'll be great
Cheers,
dreadkopp