Every time i try to install any kitkat rom on my Xperia u it give error status 7 and now if i edited updater script not its giving installation failed after updating partition details.... really need help got irritated with this problem...help.HELP
Status 7 Details...
Which ROM were you trying to flash, specifically?
However,
Status error 7 is not only due to a logical error in updater-script, but it can also be caused due to an out dated update-binary. Try using the update binary below and if it does not help, report it to your ROM developer to fix the issue in updater-script.
Happy Flashing...
try this
http://forum.xda-developers.com/showthread.php?t=2522762
it worked for me on xperia P. should work on U either, i guess.
danishsajjad said:
Which ROM were you trying to flash, specifically?
However,
Status error 7 is not only due to a logical error in updater-script, but it can also be caused due to an out dated update-binary. Try using the update binary below and if it does not help, report it to your ROM developer to fix the issue in updater-script.
Happy Flashing...
Click to expand...
Click to collapse
Most error 7 updater errors are due to failed assertions, which re there for a reason. Some kernels/CWM recoveries do not have the right props set so the assertions will fail.
@danaksim, "fixing" the script is not a solution unless you realy know what you are doing and may be a death sentence for the device.
@loveymangal, when you asking such a question provide detailes for what ROM you are trying to install, link, or if you cannot post link at least the exact title and site it's on. Also provide the steps you made, and which ROM/kernel/CWM recovery you are using now.
ChikeD said:
@danaksim, "fixing" the script is not a solution unless you realy know what you are doing and may be a death sentence for the device.
.
Click to expand...
Click to collapse
yeah, you're right. it wasn't too wise to give that advice since i don't know which rom he's trying to flash.
Thanks to all finally fixed the problem
With the help of replies i was finally able to fix the problem by changing the binary and using twrp i was trying to install xperia u Sirius Xperiance Rom http://forum.xda-developers.com/xperia-u/u-development/aosx-z2-sirius-xperience-t2725846 and it worked
Related
Hi all,
I started playing with my Samsung Galaxy Ace and would want at some point to install CyanogenMod on it.
An issue that arise is that I have the GT-S5830D variant (Telus, TLKI4).
To flash the recovery, I downloaded recovery-clockwork-4.0.0.9-galaxyace.img from http://download.clockworkmod.com/recoveries/ and tried to use "flash_image" as recommended on CyanogenMod's wiki, but flash_image fails. I think flash_image tries to access /proc/mtd which is non-existent on the GT-5830D while present on other GT-5830 variants.
So I used recovery-clockwork-5.0.2.6-galaxyace-fix.zip from http://forum.xda-developers.com/showthread.php?p=18178563#post18178563 but this failed too. Looking at the updater-script in it showed an assert against certain models. I thus added mine to the assert, repackaged and resigned it. It flashed fine.
Before installing CM 7.2.0-RC1, I want to make sure I wont brick my phone. Looking at its updater-script, I see it's writing "boot.img" to "boot". My guess is that "boot" is a partition, but since the GT-5830D seem to be different enough, I wanted to verify first.
So my question is, does anybody knows the exact difference between the GT-5830D and any other GT-5830 variants??
Thanks a lot!!
The assert thingy allows you to specify what model this one should be flashed with .
It has no real effect .
Herpderp Defy.
Ok thanks.
The assert is there to protect the user from installing a rom on a different phone. The assert needs to be strict so the rom is installable only on the supported phone, but not too strict as to prevent variants of the phone...
I was just unsure as to if the S5830D was enough the same as the S5830 so that even if the assert passes, flashing wouldn't brick the phone.
Yesterday, I installed CM 7.2.0-RC1 (da26c44f36032e202e7dd21c13bf14b7 from here get.cm/?device=cooper) successfully. The assert passed fine.
I must say I am deeply impressed by CM compared to stock!
Issues I've found:
Torch does not work. The application stays open, crashes all the time and restart. Only way to disable it is restarting.
Screen does not turn off during conversation. Proximity sensor not working?
"Menu" and "Back" buttons kind of randomly lights up for a couple of seconds every couple of minutes.
These are known issues though. Even the camera works!
Thanks CM dev and supporters
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Clous87 said:
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Click to expand...
Click to collapse
Why are you digging up old threads......
Sent from my Jelly Beaned Ace
erm... thought it was pretty well explained.
Feel free to suggest a newer one that i can ask my question in...
Clous87 said:
erm... thought it was pretty well explained.
Feel free to suggest a newer one that i can ask my question in...
Click to expand...
Click to collapse
Just create a new thread...
You don't have to post your problem in another thread...
Clous87 said:
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Click to expand...
Click to collapse
As long as you don't mess up your bootloader and have a working Odin install, it's pretty hard to completely brick an Ace. And yeah, don't necro old threads please.
Clous87 said:
have you had any other problems come up on the phone?have you managed to flash the stable version?
Click to expand...
Click to collapse
All issues I had are now fixed. Cyanogenmod 7.2.0 is working as expected, no problem. Only 3 issues remain open for the Ace:
http ://code.google.com/p/cyanogenmod/issues/list?can=2&q=model=cooper&colspec=ID%20Type%20Status%20Version%20Model%20Network%20Owner%20Summary%20Stars%20Priority
There are some nightly builds but more often then not they are translation fixes. See this url for some sort of changelog:
http ://changelog.bbqdroid.org/#cooper/cm7/next
Clous87 said:
if this does work, is there a step by step guide to change the assert within the rom?
Click to expand...
Click to collapse
The assert does not fail on my S5830D when flashing. I think changing the assert is as simple as extracting the .zip file, editing the META-INF/com/google/android/updater-script (see the top for the assert) and finally re-zip. Note that I haven't tried this so be careful not to brick your phone...
nbigaouette said:
All issues I had are now fixed. Cyanogenmod 7.2.0 is working as expected, no problem. Only 3 issues remain open for the Ace:
http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
There are some nightly builds but more often then not they are translation fixes. See this url for some sort of changelog:
http://changelog.bbqdroid.org/#cooper/cm7/next
The assert does not fail on my S5830D when flashing. I think changing the assert is as simple as extracting the .zip file, editing the META-INF/com/google/android/updater-script (see the top for the assert) and finally re-zip. Note that I haven't tried this so be careful not to brick your phone...
Click to expand...
Click to collapse
There, fixed it for you
I have a huge problem. I have changed the original recovery.img of my phone(u8860) and using an android application I have started the phone in recovery mode manually. So, at startup there is an error screen says that signature verification error, change the recovery with official one. The firmware version of the phone is U8860V112R001C121B943 and I don't have the original stock rom. When, I try to install other Huawei roms like b919, b930 etc. I take an error message says "update failed" So I can't install any software and I can't turn on the phone. I need the stock rom or I need a firmware downgrade patch (I tried b929_rus patch it didn't solve my problem). Please please help me I'm in very big trouble. I have no idea to solve this problem. Thank you for all your answers.
This problem ruined my week
Please help. I have read all the forum about my device and I did not find any solution.
I have tried to create a downgrade patch but I couldn't because of the signature problem
I need support, please help.
goktahan said:
I need support, please help.
Click to expand...
Click to collapse
you cant install other roms
try google and find your stock rom there will be one and flash
go thru big GLORY thread.. m sure u will the find the solution
http://forum.xda-developers.com/showthread.php?t=1552038
Hi there,
I am currently running the Mokee OS 4.4.3 enrc2b 140610 on my HOX+. All works fine until I try to update.
No matter to what version I try to update, it always tells me: "/system/framework/core.odex has unexpected contents" when checking system files.
After that:
"E: Error in /data/media/0/mkupdater/OTA-MK(version).zip
(Status 7)
Installtion aborted."
So what can I do? I have Xposed framework installed, disabling it won't help. I didn't mess around with the core.odex myself and I can't think of any app that could be the reason for it. Downloading the OTA updates again didn't help either.
I am open for any help and advices!
Installing the whole OS completly new is the last thing I want to try.
mpmarth said:
Hi there,
I am currently running the Mokee OS 4.4.3 enrc2b 140610 on my HOX+. All works fine until I try to update.
No matter to what version I try to update, it always tells me: "/system/framework/core.odex has unexpected contents" when checking system files.
After that:
"E: Error in /data/media/0/mkupdater/OTA-MK(version).zip
(Status 7)
Installtion aborted."
So what can I do? I have Xposed framework installed, disabling it won't help. I didn't mess around with the core.odex myself and I can't think of any app that could be the reason for it. Downloading the OTA updates again didn't help either.
I am open for any help and advices!
Installing the whole OS completly new is the last thing I want to try.
Click to expand...
Click to collapse
I am also facing same issue.
Download the full ROM,install it without wiping .which helps u to upgrade to new version without losing data
Siddhareddy said:
Download the full ROM,install it without wiping .which helps u to upgrade to new version without losing data
Click to expand...
Click to collapse
I gonna try that, thank you man!
For Everyone who are unable to use OTA, Just do this, mount and format /system of Mokee from latest CWM, Later flash the Release ROM you have, don't flash gapps ( The release versions consist gapps, don't know about nightly/experimental), Next go to mokee center, download OTA and flash it. It will be successful, now after booting don't remove any system apps, If you don't need just go to TB and Frost them, also don't make any changes to build.prop, Don't flash gapps too
Hi developers. ^^ hey just wanna ask if there is anyone who is willing to make a custom rom for my zte blade s7... I prefer resurrection remix or cyanogenmod because of the veriety of customizing.. . Could anyone help? Or maybe some tutorials on how to create my own custom rom.. . I'm just a basic android customizer. I already know how to root, install xposed, reflash, backup, and such... But wanna kick it up a notch and make a custom rom.. . Hehe..
Jo_bell said:
Hi developers. ^^ hey just wanna ask if there is anyone who is willing to make a custom rom for my zte blade s7... I prefer resurrection remix or cyanogenmod because of the veriety of customizing.. . Could anyone help? Or maybe some tutorials on how to create my own custom rom.. . I'm just a basic android customizer. I already know how to root, install xposed, reflash, backup, and such... But wanna kick it up a notch and make a custom rom.. . Hehe..
Click to expand...
Click to collapse
My ports for S7
NFound said:
My ports for S7
Click to expand...
Click to collapse
Hey, you've made ports. Do you know what the difference is between twrp ports? For instance what makes a recovery.img different between phones? Does recovery.img have its own kernel? A rootfilesystem?
peterius said:
Hey, you've made ports. Do you know what the difference is between twrp ports? For instance what makes a recovery.img different between phones? Does recovery.img have its own kernel? A rootfilesystem?
Click to expand...
Click to collapse
Yes. To install TWRP use Google Translator: https://4pda.ru/forum/index.php?s=&showtopic=697227&view=findpost&p=64637653
Preview Oreo: https://4pda.ru/forum/index.php?s=&showtopic=697227&view=findpost&p=64948575
Yes to which? "Translation to secure pages is not supported". I was asking about phones in general, not just the ZTE. I asked in a different thread but there was no response. So I thought you might know, maybe PM would be better, or maybe it's inconvenient for you?
NFound said:
My ports for S7
Click to expand...
Click to collapse
hi i downloaded ur custom roms both cm12.1 and lineage...
but non of them were flashable.. it said tht the rom was for s7.. #something like tht# lucikly i have a backup of my rom to reflash. i researched some threads and found out tht i can flash the rom without the verification by deleting some symbols and words in updater script located inside google folder... but before I do tht.. i just want to make sure.. is the custom rom actually for "ZTE BLADE S7 T920" or is it for the "samsung s7"
http://m.gsmarena.com/zte_blade_s7-7670.php
here are the specs and such about the phone for reference
Jo_bell said:
hi i downloaded ur custom roms both cm12.1 and lineage...
but non of them were flashable.. it said tht the rom was for s7.. #something like tht# lucikly i have a backup of my rom to reflash. i researched some threads and found out tht i can flash the rom without the verification by deleting some symbols and words in updater script located inside google folder... but before I do tht.. i just want to make sure.. is the custom rom actually for "ZTE BLADE S7 T920" or is it for the "samsung s7"
http://m.gsmarena.com/zte_blade_s7-7670.php
here are the specs and such about the phone for reference
Click to expand...
Click to collapse
Yes, ZTE BLADE S7 T920. so you have an old TWRP therefore swearing. establish this TWRP 3.1.1-1 or delete first 2 lines in updater-script
NFound said:
Yes, ZTE BLADE S7 T920. so you have an old TWRP therefore swearing. establish this TWRP 3.1.1-1 or delete first 2 lines in updater-script
Click to expand...
Click to collapse
hi sorry for not replying... i was finding ways to flash the rom with my friend...
i think my phone is outta luck... already flsh the recovery you suggested but still can't install any of the roms... tried editing ro.product.device as s7... still the same with either error 6/7 if i use the edited updater script rom it will show up
Updater Process ended with error : 6
if i use the unedited rom it will show up error : 7
bummer for my phone... is there anymore that i can do?.. hehe.. i really want to experience android nougat and oreo..
but if its a dead end.. bummer...
maybe this could help?
i remember over the days.. i changed the build.prop and edit the model as my name..XD to fool my friends tht i made the device(trick failed.. they saw the logo at the back)XD... but i did'nt change it back.. because.. there was no harm. no error seem to pop up.. so... yeah... busted build.prop
i followed the custom rom... because i saw in some lines in updater script that wrote ro.product.device= s7
still the same with errors... below are the errors..
https://ibb.co/iRpA65
pictures of the log is in this link or in the attachment below... the picture is quite blurry because i used a java phone to snap a photo... hehe
inside the log is
''white colour'' regular process
installing zip file 'filename'
bla bla bla .etc
red colour... first red colour... was when i flash the edited rom(deleted some keywords in updater.script)
red 1
Updater process ended with ERROR : 6
Error installing zip file '/ filename'
the second red colour is flashing with the unedited rom
red 2
Updater process ended with ERROR : 7
Error installing zip file '/ filename'
if nothing can be done.. its okay ill just go with the stock then...
Jo_bell said:
hi sorry for not replying... i was finding ways to flash the rom with my friend...
i think my phone is outta luck... already flsh the recovery you suggested but still can't install any of the roms... tried editing ro.product.device as s7... still the same with either error 6/7 if i use the edited updater script rom it will show up
Updater Process ended with error : 6
if i use the unedited rom it will show up error : 7
bummer for my phone... is there anymore that i can do?.. hehe.. i really want to experience android nougat and oreo..
but if its a dead end.. bummer...
maybe this could help?
i remember over the days.. i changed the build.prop and edit the model as my name..XD to fool my friends tht i made the device(trick failed.. they saw the logo at the back)XD... but i did'nt change it back.. because.. there was no harm. no error seem to pop up.. so... yeah... busted build.prop
i followed the custom rom... because i saw in some lines in updater script that wrote ro.product.device= s7
still the same with errors... below are the errors..
https://ibb.co/iRpA65
pictures of the log is in this link or in the attachment below... the picture is quite blurry because i used a java phone to snap a photo... hehe
inside the log is
''white colour'' regular process
installing zip file 'filename'
bla bla bla .etc
red colour... first red colour... was when i flash the edited rom(deleted some keywords in updater.script)
red 1
Updater process ended with ERROR : 6
Error installing zip file '/ filename'
the second red colour is flashing with the unedited rom
red 2
Updater process ended with ERROR : 7
Error installing zip file '/ filename'
if nothing can be done.. its okay ill just go with the stock then...
Click to expand...
Click to collapse
i just tried the lineageOS 15 rom, and got an error 7, before that there was a line saying "this rom is for "s7" this is a "".
so how can i flash this rom?
Scepterus said:
i just tried the lineageOS 15 rom, and got an error 7, before that there was a line saying "this rom is for "s7" this is a "".
so how can i flash this rom?
Click to expand...
Click to collapse
Hi, I want to share a solution for this as user of ZTE Blade S7 too:
If you want to install any rom via TWRP 3.1.1 you will have to edit updater_script with Notepad ++ because probably these errors are caused by trying to edit with any other Windows text editer.
Please confirm two options in Notepad ++: "Edit/EOL Conversion/Convert to UNIX Format" and "Encoding/Encode in ANSI".
I recommend to erase the first two lines in the script, use "update archive" via WinZip, WinRAR, 7ZIP (not to rezip the files, only update updater_script with the modified one) and you will not encounter the ERROR:7.
This way I manage to install custom roms because the problem is that TWRP 3.1.1 do not recognize our ZTE Blade S7 as "ZTE_T920" so the best solution is to erase this lines of code in all roms that include "ro.product.device" and things like that but in the correct way, just erase correctly and if rom is correct it will install without a problem.
For error:6 if you do this correctly maybe it can be caused by not erasing system. Do not forget to wipe system in advanced settings.
Additionally, I have the latest B20 version from Malaysia in TWRP zip, but I cannot share links so if you want it please message me.
Still unable to flash the lineage 15 Rom and somebody please assist by posting a link for a flashable file. Thanks
Hey Guys,
i got the same Problem here.
I´ve rooted with Kingroot posted by NFound and flashed the TWRP 3.1.1-1.img with Rashr ony my ZTE Blade S7 (T920)
After that i switched into TWRP and wiped everything.
Next i tried to install the lineage os but get error 7, after deleting those 2 lines i still get the error 7 just the "this rom is for "s7" this is a ""." message is missing now.
So i tried the cm-rom, install works like a charm but google play freezes and i cant delete cache of apps because the settings window freezes too when i want to click on apps.... (used open gapps arm 5.1 nano)
So both dont work very well 4 me, maybe u got an idea.
Right now i´m downloading lineage os another time to make sure the rom is not bricked or sth.
Lg Seg
Thanks for updating, i was having problems with the stock rom after installing xposed and magisk and was considering trying the fix for the lineage rom.
I do wonder if anyone here actually managed to get that rom to work. Please update us if you succeed.
4pda
Scepterus said:
Thanks for updating, i was having problems with the stock rom after installing xposed and magisk and was considering trying the fix for the lineage rom.
I do wonder if anyone here actually managed to get that rom to work. Please update us if you succeed.
Click to expand...
Click to collapse
4pda android 8 lineageos 15.0 post 445 theme zte blade s 7
If this is in the wrong place I apologise and please move.
So i have been installing roms for a long time, I know how its done and what i need to avoid. Recently though, every rom i try to install fails with error 7, Even the same zip file i've already installed before so i know it should work fine. I've looked on google but all that comes up is this updater script that should fix it, but i have tried that to no avail.
Anybody had this problem and fixed it?
Thanks
beedle90 said:
If this is in the wrong place I apologise and please move.
So i have been installing roms for a long time, I know how its done and what i need to avoid. Recently though, every rom i try to install fails with error 7, Even the same zip file i've already installed before so i know it should work fine. I've looked on google but all that comes up is this updater script that should fix it, but i have tried that to no avail.
Anybody had this problem and fixed it?
Thanks
Click to expand...
Click to collapse
What's your variant, last firmware, twrp version ?
tech_infinity said:
What's your variant, last firmware, twrp version ?
Click to expand...
Click to collapse
Ah sorry about that forget to mention.
Anyway I figured it out, I had installed a vendor zip and forgot, turns out that was causing the problem.