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
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?
I really want to create a rom and I'm doing everything right with the Android Kitchen but after I flash my rom I get status 6/7 errors in CWM.
Can someone explain me please how I do updater-script file that don't provide this errors?
Ok but, you need to tell us what errors are you getting...
RoberGalarga said:
Ok but, you need to tell us what errors are you getting...
Click to expand...
Click to collapse
Status 6 and sometimes status 7.
Huh? There aren't any other errors, like "no such file bla,bla,bla"?
There is an updater-script FAQ in Android Software General Section. Post your updater-script there, they will surely help you.
I would have given you a link but I am on mobile now
hie guys,i have this ROM_0 file from sp flash tools.tried processing it using mtk droid tool to get a yaff2 image i can open change my build.prop but it happens that every tool i tried using couldnt open the yaffs2 image.
my real problem is i edited the build.prop and my phone is stuck in a boot loop.Since it is a china phone with information below, couldnt get the ROM anywhere online but managed to do a rollback using SP Flash Tools.Now the problem is i cant open this ROM to replace the build.prop.
Phone Information:
Model is N7100
Rom is ALPS.ICS2.MP.V1.15.
Brand SANSVMG.
CPU is MT6577
any help guys is greatly appreciated.THANKS IN ADVANCE
Tashaa78 said:
hie guys,i have this ROM_0 file from sp flash tools.tried processing it using mtk droid tool to get a yaff2 image i can open change my build.prop but it happens that every tool i tried using couldnt open the yaffs2 image.
my real problem is i edited the build.prop and my phone is stuck in a boot loop.Since it is a china phone with information below, couldnt get the ROM anywhere online but managed to do a rollback using SP Flash Tools.Now the problem is i cant open this ROM to replace the build.prop.
Phone Information:
Model is N7100
Rom is ALPS.ICS2.MP.V1.15.
Brand SANSVMG.
CPU is MT6577
any help guys is greatly appreciated.THANKS IN ADVANCE
Click to expand...
Click to collapse
there must be anyone in the world with same phone like you just contact him and ask him to give you the backup or build.prop and just flash it
got the build.prop
Hell_X said:
there must be anyone in the world with same phone like you just contact him and ask him to give you the backup or build.prop and just flash it
Click to expand...
Click to collapse
i happen to have the original build.prop but how do i flash it back or replace it if i cant open the rom
Tashaa78 said:
i happen to have the original build.prop but how do i flash it back or replace it if i cant open the rom
Click to expand...
Click to collapse
send me your build.prop
Hell_X said:
send me your build.prop
Click to expand...
Click to collapse
also in the attachment in the first post are links to all files you may need, the ROM_ from flash tools, the scatter file
thanks in advance
Tashaa78 said:
also in the attachment in the first post are links to all files you may need, the ROM_ from flash tools, the scatter file
thanks in advance
Click to expand...
Click to collapse
I am sure you have cwm recovery or not?
Hell_X said:
I am sure you have cwm recovery or not?
Click to expand...
Click to collapse
nah,dont have one,still searching on how to get a cwm recovery
Tashaa78 said:
nah,dont have one,still searching on how to get a cwm recovery
Click to expand...
Click to collapse
do you remember the lines that you edited???
Hell_X said:
do you remember the lines that you edited???
Click to expand...
Click to collapse
YAP,I DO :
ro.build.host=wsyz
Code:
[QUOTE][U]ro.build.product=bird77_c_cu_ics2[/U][/QUOTE]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=bird77_c_cu_ics2-user 4.0.4 IMM76D eng.root.1359077894 test-keys
ro.build.fingerprint=alps/bird77_c_cu_ics2/bird77_c_cu_ics2:4.0.4/IMM76D/1359077894:user/test-keys
AND THE FINGER PRINT TOO,
thanks man for the effort u putting into helping me,u the man
[Q&A] [PORT][RECOVERY] Carliv Touch Recovery v3.0 [Kitkat] for porting to MTK phones
Q&A for [PORT][RECOVERY] Carliv Touch Recovery v3.0 [Kitkat] for porting to MTK phones
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [PORT][RECOVERY] Carliv Touch Recovery v3.0 [Kitkat] for porting to MTK phones. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello, please tell me. Ported CTR v 3 iOcean elite. For a basis took recovery with P780, tailored for your screen resolution, like all good, but there is one at the new mount memory to the computer recording speed is very very low (for example, when copying the firmware of 600 mb- while copying takes about 15 minutes), what to do ?
r-miheev said:
Hello, please tell me. Ported CTR v 3 iOcean elite. For a basis took recovery with P780, tailored for your screen resolution, like all good, but there is one at the new mount memory to the computer recording speed is very very low (for example, when copying the firmware of 600 mb- while copying takes about 15 minutes), what to do ?
Click to expand...
Click to collapse
That could have multiple causes: antivirus software, low class sdcard, usb port old version (1.1, 1.2), bad cable, etc. It's not related to recovery.
@carliv, i have tried the recovery that you have tag for me but, it does not work... It does not boot into recovery , it just loop into a normal way of booting.... Is this already tested? Or I am the first who tried it?
Update: I guess I'm wrong, I have tried to flash it again with an updated Rasher tool and it works but it take a long time to flash it . Thanks Sir @carliv, by any chance who ported it sir?
Sir @carliv , so now that you have verified that it is working with our device you can now add our unit myphone agua rio v2 (with version 2 because theres a myphone agua rio v1 with a jellybean os)
Kyzrael said:
Update: I guess I'm wrong, I have tried to flash it again with an updated Rasher tool and it works but it take a long time to flash it . Thanks Sir @carliv, by any chance who ported it sir?
Sir @carliv , so now that you have verified that it is working with our device you can now add our unit myphone agua rio v2 (with version 2 because theres a myphone agua rio v1 with a jellybean os)
Click to expand...
Click to collapse
For flashing recovery on Mediatek phones is better to use Mobileuncle from phone or SPflashtools from PC. Some people said Flashify works too, but I didn't checked.
I did the port for this recovery, because I did that for other phones too and I thought to do it for this one too. You were lucky I found infos about the phone online, because you didn't provided any.
Ok, I'll add it on working device list, since the test was successful.
carliv said:
For flashing recovery on Mediatek phones is better to use Mobileuncle from phone or SPflashtools from PC. Some people said Flashify works too, but I didn't checked.
I did the port for this recovery, because I did that for other phones too and I thought to do it for this one too. You were lucky I found infos about the phone online, because you didn't provided any.
Ok, I'll add it on working device list, since the test was successful.
Click to expand...
Click to collapse
@carliv, when i try to mount the sdcard0 it keeps on saying "Error Mounting /storage/sdcard0". What would be the problem with that? Is it in the recovery.fstab? Btw, i enjoy using it now. Thanks again so much
Kyzrael said:
@carliv, when i try to mount the sdcard0 it keeps on saying "Error Mounting /storage/sdcard0". What would be the problem with that? Is it in the recovery.fstab? Btw, i enjoy using it now. Thanks again so much
Click to expand...
Click to collapse
It's the voldmanager number for internal sdcard, probably wrong - I told you I didn't have any info about your phone since you didn't provide something, and as I don't even seen this phone I can't know what is that number. If you change that in fstabs it will work well.
carliv said:
It's the voldmanager number for internal sdcard, probably wrong - I told you I didn't have any info about your phone since you didn't provide something, and as I don't even seen this phone I can't know what is that number. If you change that in fstabs it will work well.
Click to expand...
Click to collapse
If by any chance that I want to correct that, where should I look into? Is my dumpchar info will help me to find the correct value or I should also look into the stock recovery's fstab?
Kyzrael said:
If by any chance that I want to correct that, where should I look into? Is my dumpchar info will help me to find the correct value or I should also look into the stock recovery's fstab?
Click to expand...
Click to collapse
Usually the fat block number in dumchar_info is the voldmanaged number, but sometimes you need to look in the phone. There are few methods to find that through adb commands. Search here on xda and you will find that somewhere.
carliv said:
Usually the fat block number in dumchar_info is the voldmanaged number, but sometimes you need to look in the phone. There are few methods to find that through adb commands. Search here on xda and you will find that somewhere.
Click to expand...
Click to collapse
So, i need to use a linux machine to be able to run commands. Ok, I'll try.... Thanks for an early response
I much confuse with where to look in phone.. In phones root? Using root explorer?
Kyzrael said:
So, i need to use a linux machine to be able to run commands. Ok, I'll try.... Thanks for an early response
I much confuse with where to look in phone.. In phones root? Using root explorer?
Click to expand...
Click to collapse
Hm, you easily skip my first clue, which is the easiest one (posting the dumchar_info) and jump to the hardest part, searching the voldmanaged numer in the phone (usually the content of /dev/block/vold will tell you that in a regular phone)....
carliv said:
Hm, you easily skip my first clue, which is the easiest one (posting the dumchar_info) and jump to the hardest part, searching the voldmanaged numer in the phone (usually the content of /dev/block/vold will tell you that in a regular phone)....
Click to expand...
Click to collapse
I have uploaded pictures... I dont know if /dev/block/vold will help me but i found /dev/block/platform is much informative
Kyzrael said:
I have uploaded pictures... I dont know if /dev/block/vold will help me but i found /dev/block/platform is much informative
Click to expand...
Click to collapse
Well, and you still didn't posted here the dumchar_info content....
carliv said:
Well, and you still didn't posted here the dumchar_info content....
Click to expand...
Click to collapse
Sorry I forgot to attach... In mobile mode of posting with pictures I'm only allowed to attach 4 pictures ... Sorry Sir @carliv again . Btw, here my dumpchar_info
Kyzrael said:
Sorry I forgot to attach... In mobile mode of posting with pictures I'm only allowed to attach 4 pictures ... Sorry Sir @carliv again . Btw, here my dumpchar_info
Click to expand...
Click to collapse
Ok, first, if you quote one of my posts don't use mention too (@).
Second, your phone has an emulated internal sdcard. Post here a stock boot and recovery image from kitkat rom. If external sdcard is working, make a backup and copy from it the boot and recovery images if you don't have in official ROM.
carliv said:
Ok, first, if you quote one of my posts don't use mention too (@).
Second, your phone has an emulated internal sdcard. Post here a stock boot and recovery image from kitkat rom. If external sdcard is working, make a backup and copy from it the boot and recovery images if you don't have in official ROM.
Click to expand...
Click to collapse
I cannot attach the zip here so i uploaded my stock boot and recovery img's here :https://mega.co.nz/#!c98ETRqb!em1QWTOBMotIq149hsadnmPRgOiexJo2T1w7ZQTjGSY
Dont worry sir , my phone is still in the pure stock
Help Carliv!!
Hellow Carliv,
I need your help to install carliv recovery with flashtools, not find the "Scatter" file to download, please help
NekoDk said:
Hellow Carliv,
I need your help to install carliv recovery with flashtools, not find the "Scatter" file to download, please help
Click to expand...
Click to collapse
You can create a scatter file with the use of MTKdroid Tools... After creating scattter file use that to flash ur recovery. You can also flash ur recovery without using flashtool, just install rashr tool.apk or mobileuncle tool to flash it via mobile.
Kyzrael said:
You can create a scatter file with the use of MTKdroid Tools... After creating scattter file use that to flash ur recovery. You can also flash ur recovery without using flashtool, just install rashr tool.apk or mobileuncle tool to flash it via mobile.
Click to expand...
Click to collapse
Q.Q but my phone is bricked, how I can create without phone?
It is a M-Horse S80
Thanks!!
NekoDk said:
Q.Q but my phone is bricked, how I can create without phone?
It is a M-Horse S80
Thanks!!
Click to expand...
Click to collapse
Is there no available dump rom for your unit available in the internet? Try to find someone who is similar with your phone then ask him to do a full back up using mtkdroidtools then ask him to send to you the created scatter file