admin please close this thread.
for which the kernel is this rom ?
nAa14/Alfs9c
Re: [ROM][PORT]MIUI-Expression[V1.0][05/02/13][nAa 14|Alfs9c|
212mb RAM??? Is this true?
Sent from my E15i using xda premium
Finally miui for GB. <3
Re: [ROM][PORT]MIUI-Expression[V1.0]&Mi-EVO[1.0][05/02/13][nAa 14|Alfs9c]
Good work yair..
sent from my phone using hands and brain...
get prop error....... cannot install this rom ... using alfs v9c
sneshy02 said:
get prop error....... cannot install this rom ... using alfs v9c
Click to expand...
Click to collapse
try to flash it with nAa kernel or try the 2nd miui rom Mi-EVO
getprop error solution = remove first few getprop lines in updater-script.
sgt. meow said:
getprop error solution = remove first few getprop lines in updater-script.
Click to expand...
Click to collapse
but why it's happning for some and for me it's work great?
same error on alfs....will try naa kernel now
same error on naa........ anyone else experienced the same :/
sneshy02 said:
same error on alfs....will try naa kernel now
same error on naa........ anyone else experienced the same :/
Click to expand...
Click to collapse
getprop error solution = remove first few getprop lines in updater-script.
Nice rom but the question whether the rom has many languages?
all the languages i think
finally good news for the JB miui , it's working and i'm uploading it right now
sgt. meow said:
getprop error solution = remove first few getprop lines in updater-script.
Click to expand...
Click to collapse
How to do this? sorry I'm a noob...
@sneshy02
Simple.
Open up the ROM.zip. Navigate to META-INF>google>android>updater-script. Open up updater-script in Notepad (or any other text editing software). Remove the lines that say assert getprop blah blah.
Done.
sgt. meow said:
@sneshy02
Simple.
Open up the ROM.zip. Navigate to META-INF>google>android>updater-script. Open up updater-script in Notepad (or any other text editing software). Remove the lines that say assert getprop blah blah.
Done.
Click to expand...
Click to collapse
Now it's working, thank you so much!
@yair25
You can put it up in the OP.
root doesnt work..create a patch.. do not build the entire rom!
Related
i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.
chchia said:
i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.
Click to expand...
Click to collapse
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...
You can send the "update-script" to me,then let me give a look.
My email addrress:[email protected]
Or just paste it here so that it can help everyone.
dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Well.Take it onder in the web,let me try to download it.
So,I can take a look.
dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Maybe it is this:"write_raw_image tmp/boot.img boot"
zeaxion said:
Maybe it is this:"write_raw_image tmp/boot.img boot"
Click to expand...
Click to collapse
No .... that is wrong syntax. Won't even work in an update-script. For the Incredible S you need an updater-script (not update-script). Commands are followed by parentheses, with each parameter followed by a comma, and then a semi-colon at the very end. Run the kitchen on your ROM to get the proper syntax.
Anyways, nothing can be done at this point unless the original poster provides more detail, like at least posting his updater-script.
I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App
Mattix724 said:
I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App
Click to expand...
Click to collapse
That's correct syntax, but it doesn't work on newer htc devices because of the new filesystem formats. Boot.img has to be copied to /tmp folder before it can be flashed to device. You have to use updater-script to accomplish that.
dsixda said:
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...
Click to expand...
Click to collapse
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way
I never had any issues using
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
in my updater-script for Incredible S.
lars.oakland said:
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way
Click to expand...
Click to collapse
Status 7 usually means you are using the wrong update-binary.
dsixda said:
Status 7 usually means you are using the wrong update-binary.
Click to expand...
Click to collapse
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.
chchia said:
assert failed: write_raw_image("tmp/boot.img","boot")
Click to expand...
Click to collapse
Should tmp/boot.img be /tmp/boot.img?
Mioze7Ae said:
Should tmp/boot.img be /tmp/boot.img?
Click to expand...
Click to collapse
Good catch!
rsxtypes72 said:
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.
Click to expand...
Click to collapse
Update-binary is not the update-script.
The update-binary file is supposed to be included with the updater-script and contains all the command implementations that are used in the script... however there are three main types of update-binary and you have to know which one to include. They are mostly differentiated by the number of parameters supported for the 'mount' command for your updater-script.
All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App
rsxtypes72 said:
All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
On your G2 you should have only an update-script in the ROM, or else the two other files (updater-script and update-binary), not both at the same time. The updater-script is a more advanced script than the update-script yet very similar.
The new versions of ClockworkMod only support the updater-script + update-binary however.
dsixda said:
The new versions of ClockworkMod only support the updater-script + update-binary however.
Click to expand...
Click to collapse
This is why the roms have both. I have not come across a single htc vision rom that only has an update-binary in it. They all have both
Sent from my T-Mobile G2 using XDA App
Update.
I just wanted to add that I have tried countless times to make a rom. I check that update script has no error and still I get the same error.
The weird thing is if I use a custom rom from one of the devs that does boot and I use the kitchen to go from edify to amend and then try to
convert it back later after I have made changes using the kitchen it wont boot and results in same write error.
Has anyone been able to make a bootable vision rom using the kitchen? If you have can you tell me where I can look or can you give me some answers. Yes I have checked google. No luck. Thanks
Im almost ready to give up.
I did make one rom that booted up and worked fine. Except when i went thru the steps to make the zip I removed the updater-script and update-binary created by the kitchen and replaced them with the udpater-script and update binary from one of the dev roms I use. This is the only way I have gotten a rom to flash and boot.
Just a thought. I know you said the htc vision is supported but would adding an edify_def for it help solve the problem?
Sent from my T-Mobile G2 using XDA App
Do i need to resign update.zip after removing bloatware?
You mean, you unpack the zip, remove some apks and then pack it again as zip? afaik: This won't work.
If you use the nice dsixda kitchen it is quiet simple to make signed packages or even without signing (not recommended as you will need to apply these in a special way, afaik)
Snoopo said:
You mean, you unpack the zip, remove some apks and then pack it again as zip? afaik: This won't work.
If you use the nice dsixda kitchen it is quiet simple to make signed packages or even without signing (not recommended as you will need to apply these in a special way, afaik)
Click to expand...
Click to collapse
No, Actually like just removing APKs directly from the .zip (with WinRAR)
no need. it will work anyway.
Chumby_666 said:
no need. it will work anyway.
Click to expand...
Click to collapse
Naah, i get a lot of symlink errors while trying to create my Sense Rom.
((
owain94 said:
A lot of BORING work!
Click to expand...
Click to collapse
))
ServerBoost100 said:
Naah, i get a lot of symlink errors while trying to create my Sense Rom.
(())
Click to expand...
Click to collapse
Bumpity Bummmmmmp
Use update script from froyocomb or my rom. Itll set correct symlinks
Sent from my U20i using XDA Premium App
slade87 said:
Use update script from froyocomb or my rom. Itll set correct symlinks
Sent from my U20i using XDA Premium App
Click to expand...
Click to collapse
Ok, i will (Just need to reroot my phone and Re install xRec first (Reflashed stock today because of a little battery drain)
slade87 said:
Use update script from froyocomb or my rom. Itll set correct symlinks
Sent from my U20i using XDA Premium App
Click to expand...
Click to collapse
With your update script it gets error at line 92 with /system/xbin/echo (cant find it error)
ServerBoost100 said:
With your update script it gets error at line 92 with /system/xbin/echo (cant find it error)
Click to expand...
Click to collapse
add from my rom /system/xbin/echo to your rom
do this with everything missing.
slade87 said:
add from my rom /system/xbin/echo to your rom
do this with everything missing.
Click to expand...
Click to collapse
except for it is not in yours.
((4.0))
ServerBoost100 said:
except for it is not in yours.
((4.0))
Click to expand...
Click to collapse
use /system/bin/busybox from mine in your rom and it should run through fine
slade87 said:
use /system/bin/busybox from mine in your rom and it should run through fine
Click to expand...
Click to collapse
Ok. I will try that tommorow.
ServerBoost100 said:
Ok. I will try that tommorow.
Click to expand...
Click to collapse
E: Can't Symlink /system/diff
E: Failure atline 91:
symlink busybox SYSTEM: /xbin/diff
Installation aborted.
It is not in mine but not in yours too.
ServerBoost100 said:
E: Can't Symlink /system/diff
E: Failure atline 91:
symlink busybox SYSTEM: /xbin/diff
Installation aborted.
It is not in mine but not in yours too.
Click to expand...
Click to collapse
Bumpity Bump!!
ServerBoost100 said:
Bumpity Bump!!
Click to expand...
Click to collapse
sense rom is weird..
it can't make symlinks out of box... all symlink which exist is original rom must be used no more no less...
Chumby_666 said:
sense rom is weird..
it can't make symlinks out of box... all symlink which exist is original rom must be used no more no less...
Click to expand...
Click to collapse
Which means a pure re-port...
ServerBoost100 said:
Which means a pure re-port...
Click to expand...
Click to collapse
Sorry People, i dont think sense will happen in the near future, I have to say it. It's symlinks is wrong always. - It cant make it out of the box. And (quoting from owain)
owan94 said:
It's a lot of boring work
Click to expand...
Click to collapse
I have been cooking a customized ICS ROM using dsixda's kitchen and all I done was deodex the ROM and add some other stuff like bash, nano etc. I then built and signed it. When I attempt to flash it tells me there is an error in the .zip file and displays (status 0). I am guessing I have done something wrong when building the ROM in dsixda's kitchen.
Does anyone know what a status 0 error means in CWM and how I can fix it?
Wrong update-binary
私のEVO 3Dから送信される。
Ahh right thank you!
Sent from my Nexus S using xda premium
dastin1015 said:
Wrong update-binary
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
what shoukd it be update or updater
Sent from my GT-S5670 using xda premium
Mr.Oug said:
what shoukd it be update or updater
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
update-binary, update-script and updater-script are three different things.
私のEVO 3Dから送信される。
I had faced the same problem what should i do ....?
I have the same problem!
how can i solve this problem?
same here, my galaxy note is bricked
I have the same problem.. on LG 2x
find out if your device takes update-script(Amend)or updater-script(Edify)
Sent from my HTC VLE_U using Tapatalk 2
ourcumnt THIRD
How to find out if your device takes update-script(Amend)or updater-script(Edify)?? :good:
Pranjal Joshi said:
How to find out if your device takes update-script(Amend)or updater-script(Edify)?? :good:
Click to expand...
Click to collapse
Look in the Meta-inf then com>Google > android then you will see the script one the binary and the update or updater script
If you got update-script then amend
Updater-script you got edify
Sent from my PG86100 using Tapatalk 2
try to find an update-binary from another custom rom and use that one
globula_neagra said:
try to find an update-binary from another custom rom and use that one
Click to expand...
Click to collapse
please don't try that, i just used JMP xtreme's update binary file on my custom rom, and i just CEMENTED my Micromax canvas 2.
i'm also stuck at the status 0 error.
SOMEONE HELP US !!!!!!
FirmShark said:
I have been cooking a customized ICS ROM using dsixda's kitchen and all I done was deodex the ROM and add some other stuff like bash, nano etc. I then built and signed it. When I attempt to flash it tells me there is an error in the .zip file and displays (status 0). I am guessing I have done something wrong when building the ROM in dsixda's kitchen.
Does anyone know what a status 0 error means in CWM and how I can fix it?
Click to expand...
Click to collapse
Status 0 means that you have a wrong script.Put a correct script in "/META-INF/com/google/android" floder in your rom.
quadratic_function said:
Status 0 means that you have a wrong script.Put a correct script in "/META-INF/com/google/android" floder in your rom.
Click to expand...
Click to collapse
I use dsxda and when i build the rom i use updater script, the ROM was coocked by 0, from system folder and boot.img, any solutions?
The update-binary for mtd type phones from dsixda kitchen no longer run on some new mtd phones. You may try to replace the update binary with other update binary and modify the scripts to mount using busybox and the format partition command should be removed and do the format from cwmr menu.
I´ve got update-binary, update-binary.orig, updater-script, updater-script.orig and update-script
What should i do to fix the status 0 error?
thanks for help
sgt_R04CH said:
please don't try that, i just used JMP xtreme's update binary file on my custom rom, and i just CEMENTED my Micromax canvas 2.
i'm also stuck at the status 0 error.
SOMEONE HELP US !!!!!!
Click to expand...
Click to collapse
Ofc, you have to use one, from the same phone, eg: OTA UPDATE
Instalation aborted
how to solve this problem?
Hi friends im having trouble writing the update-script for a flashable zip with deodexed system/app & system/framework. this is my first attempt at one. could anyone tell me where im going wrong please ive been trying all day with no luck. But its not for my ray its for my j theres not many devs to help me on the j forum.
heres my zip: https://dl.dropbox.com/u/90938124/deodex_xj-signed.zip
gavster26 said:
Hi friends im having trouble writing the update-script for a flashable zip with deodexed system/app & system/framework. this is my first attempt at one. could anyone tell me where im going wrong please ive been trying all day with no luck. But its not for my ray its for my j theres not many devs to help me on the j forum.
heres my zip: https://dl.dropbox.com/u/90938124/deodex_xj-signed.zip
Click to expand...
Click to collapse
just give me the updater script. file
here it is thanks
There is no mount and unmout cmd's in the script..
Well iam on phone now...
Simple solution for u is to use any any existing mod's meta-inf folder in ur mod.
Sent from my SK17i using XDA Premium HD app
Have a look at a working updater-script and you will see a huge difference
For example you need a command like
Code:
extract_dir
More set perms and mounting/unmounting system. Please check out a "real" updater-script :good:
Sent from my Nexus 7 running Android 4.2.1
sandy7 said:
There is no mount and unmout cmd's in the script..
Well iam on phone now...
Simple solution for u is to use any any existing mod's meta-inf folder in ur mod.
Sent from my SK17i using XDA Premium HD app
Click to expand...
Click to collapse
ok i'll try thanks
mihahn said:
Have a look at a working updater-script and you will see a huge difference
For example you need a command like
Code:
extract_dir
More set perms and mounting/unmounting system. Please check out a "real" updater-script :good:
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
i think i'll just give up i'm no dev lol
my next attempt still cant get it right please someone help me
well here what u did wrong...updater script was a txt file...and there was no updater binary script.
so next time use Notepad++ to edit these files..
here i only fixed everything...it should work now....
http://d-h.st/Gai
sandy7 said:
well here what u did wrong...updater script was a txt file...and there was no updater binary script.
so next time use Notepad++ to edit these files..
here i only fixed everything...it should work now....
http://d-h.st/Gai
Click to expand...
Click to collapse
Thankyou so much for your efforts but its not flashing error status6 i looked it up and resigning fixes the problem but then it just aborts. i'll just forget about it i'm sure you all have better things to do than help silly nooby me lol. Thanks again.
gavster26 said:
Thankyou so much for your efforts but its not flashing error status6 i looked it up and resigning fixes the problem but then it just aborts. i'll just forget about it i'm sure you all have better things to do than help silly nooby me lol. Thanks again.
Click to expand...
Click to collapse
I think the best thread you can start to learn it: How to make a flashable zip
I started here too once a time...
Wechy
Wechy77 said:
I think the best thread you can start to learn it: How to make a flashable zip
I started here too once a time...
Wechy
Click to expand...
Click to collapse
thats where iv been trying to learn from but its not really explanatory enough for a noob. im just a factory worker lol not a dev all thought id love to be able to do all this. iv read other threds aswell but none of them said anything about the update binery either. i'm probably just not smart enough. i'll keep trying though
gavster26 said:
thats where iv been trying to learn from but its not really explanatory enough for a noob. im just a factory worker lol not a dev all thought id love to be able to do all this. iv read other threds aswell but none of them said anything about the update binery either. i'm probably just not smart enough. i'll keep trying though
Click to expand...
Click to collapse
Try download some flashable zips and view updater scripts with notepad++
This is the best way to understand how it works.
If I have some time I write a little guide
Sent from my Xperia Ray using xda premium
Wechy77 said:
Try download some flashable zips and view updater scripts with notepad++
This is the best way to understand how it works.
If I have some time I write a little guide
Sent from my Xperia Ray using xda premium
Click to expand...
Click to collapse
ok thanks. i'll study up lol. how would i remove the .txt extension on notepad++ when i save it turns into a txt file.
gavster26 said:
ok thanks. i'll study up lol. how would i remove the .txt extension on notepad++ when i save it turns into a txt file.
Click to expand...
Click to collapse
delete extension
but the best way is open one of the updater-script (download any flashable zip) and edit with notepad++
(be sure you edit with notepad++ othervise you will see status6 error when flashing)
Hello everyone. So I am trying to port CM9 to my device htc Desire C. The build compiles correctly but when I flash it, it results in a bootloop.
I have attached the logcat. If some one could help me with this , it would be great
Heres the paste bin link http://pastebin.com/5u6ymXgk
Add this line to build.prop and reflash it;
dalvik.vm.dexopt-data-only=1
forumber2 said:
Add this line to build.prop and reflash it;
dalvik.vm.dexopt-data-only=1
Click to expand...
Click to collapse
Thank you so much bro
Those lines fixed the error.