• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root OFFICIAL ZTE OTA B07 to B09 update

Yeah how does this work i tried to use stock recovery i unrooted and went to bo7 and downloaded the update right on my phone but then every time it goes to install it gives me the status 7 error? can someone help me?
 
ok so this WILL NOT EVER work with stock, sad, but true. ive done some research and figured out that status 7 is apparently an assert failure. which means this zip can be repaired to work with cwm, but never to work with stock recovery because any modification will require recoding of the signature which we just cant do
 
unfortunately for you guys, i cant really access the thing all that well with my internet connection, so its on you.
inside the zip, there will be a folder called META-INF, inside that, a folder called com, then google, then android
so thats
/META-INF/com/google/android/

inside there youll find a file called updater-script, you will need to text edit that, preferably not with built in windows utilities...
i prefer notepad++
it will have lines that say something slightly similar to

assert(getprop("ro.device.slut") == "yourmom" || getprop("ro.product.zte") == "sucks");

obviously not going to be the exact words lol, but you get the idea
by removing those it will in fact fix the error in cwm but id like to see what they are first
i would prefer it, as im sure we all would, if someone could post that entire assert section, plus i may have been wrong about my previous statement, there may be a way to save things yet... we cant modify the zip and have it still work on stock recovery, but we can modify the rom settings
anyway here is a better tutorial lol
Fix Custom ROM Installation " Status 7 ","error, assert failed: getprop (?ro.product.dervice?) ,"Installation aborted" Recovery Error Easily - Android Gadgematic
but make sure you get me those asserts so i can look them over
 
basically, there is a chance that we could either A force the phones to use the right properties, B force a phone to make one so generic that it will work on any phone, or C make changes slight enough so as not to change the signature required to work
 
for instance, we figure out it takes the phone number property to make sure its right, we change that property to * which is a wildcard meaning it can be anything and let it download the file like that... boom, we now have a universally usable file. not that i recommend anyone doing this without me looking into it first or knowing what youre doing but i just wanted to put it out there kuz im forgetful lol
 
Junkie,

How about the first 8 lines? That thing's a monster.

if is_mounted("/system") then unmount("/system") endif;
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/system");
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20120728.133625:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20121128.160026.30230:user/release-keys");
assert(getprop("ro.product.device") == "warp2" ||
getprop("ro.build.product") == "warp2");
assert(getprop("ro.product.name") == "ZTE_Warp_Sequent");
ui_print("Verifying current system...");
show_progress(0.100000, 0);
assert(apply_patch_check("/system/app/ApplicationsProvider.apk", "0ec1c9527caa996b9a281602e67a8af8c94f600f", "623e012967cde722759f8d00a5828d0c57c97853"));
set_progress(0.000021);
 
wow, we are gonna have alot of asserts to go through... ill take a look at things and see what i can work out for non cwm users, cwm users tho should just be able to remove every line that starts with "assert" all the way till the
;
which ends it

example
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20120728.133625:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20121128.160026.30230:user/release-keys");

multiple lines, but its all one command basically so it all needs to be removed, a line only truly ends when you see a ;
 
ok... well zte made this as patches, not actual whole files
so in other words its risky to even try but here is what you would most likely need to remove to get it to work with a stock rom bo7 and a stock kernel

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20120728.133625:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20121128.160026.30230:user/release-keys");
assert(getprop("ro.product.device") == "warp2" ||
getprop("ro.build.product") == "warp2");
assert(getprop("ro.product.name") == "ZTE_Warp_Sequent");

all other asserts must stay, otherwise it cant make sure the patches will work, and if it doesnt verify that, then goes into trying to patch, and it turns out the files dont match right, well, you got yourself a bricked phone
 
junkie2100 said:
wow, we are gonna have alot of asserts to go through... ill take a look at things and see what i can work out for non cwm users, cwm users tho should just be able to remove every line that starts with "assert" all the way till the
;
which ends it

example
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20120728.133625:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "ZTE/ZTE_Warp_Sequent/warp2:4.0.4/IMM76D/20121128.160026.30230:user/release-keys");

multiple lines, but its all one command basically so it all needs to be removed, a line only truly ends when you see a ;
Click to expand...

ok i deleted all the assert lines...and the installation went a little further....but at the end still gave me status 7 after syscheck permissions then i deleted stuff afer that and it installed successfully but got a bootloop....i am on cwm i was just saying before i went back to b07 and unrooted with your tool and installed stock recovery and downloaed the update right from the phone menu and still got status 7 error.....

I just wish someone could upload the backup from the official bo9 from zte bc this is a pain in the a** for me lol thanks for your help junkie
 
well i mean people have posted what is basically the same thing, only in already patched form, thats what i was saying it has to have those other asserts, all the ones that say something about apply_patch_check are checking to make sure it wont break something
if anything on your rom has been modified, anything at all other than rooting and installing things, or is even just a little off, it will not install correctly and you will get stuck in a boot loop
no custom kernels, no modified themes, no nothing except the original stock b07 rom or it WILL fail and cause the boot loop. this patch of theirs is basically not usable, it relies on the exact right files to be modified instead of just installing new files over them. just stick to repackaged ones from now on, its much safer
 
Yeah I kind of figured it had to be bone stock....I'm on b09 deodexed works great....just wanted the newest thing I guess the only benefit is factory reset.....but once I try to do something I can't stop if it doesn't work for some reason I can usually work something out but this got me by the balls and I f##ked around for hours or maybe days!!! Lol

I won't fix what's not broken I guess this time....and stick with what I got.....thanks junkie I learned a little about updater scripts but not enough I guess lol
 
lol, hey, it takes time, at least you learned something. and generally updater scripts are much simpler, thats just a stock update one, its massive compared to say the one for the rom youre using or any cwm flashable around here really
 
You must log in or register to reply here.
Back
Top Bottom