[Q] SONY XPERIA ARC LTi15 ASSERTS FAILED CWM FLASH PROBLEM - Xperia Arc General

I am unable to flash any new roms, be it CM or MIUI. This happens after i flashed the kernel through fastboot. I get the following error.
(STATUS 7) Asserts Failed. I disabled the certifications and tried all sorts of stuff. Right now, I have baseband 64, ROOTED on STOCK SE FIRMWARE.
I searched for this answer a long time but got nothing so I had to actually MAKE AN ACCOUNT just to ask this dumb question. I get this error.
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" || getprop("ro.product.board") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" || getprop("ro.product.board") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" || getprop("ro.product.board") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" || getprop("ro.product.board") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu" || getprop("ro.product.board") == "anzu");
package_extract_file
I tried many suggestions as deleting the lines of code from the actual ZIP FILE. That did not work. I want to ore specifically direct my question at DINESH, here
http://forum.xda-developers.com/showthread.php?t=1503527
as for some reason his MIUI ROM is more troublesome than others and SAOSIN'S MIUI GB ROM actually I can flash onto my phone. Please let me know what I can do guys. Thanks and sorry for yet another NOOB QUESTION.

uspeekchaineze said:
I am unable to flash any new roms, be it CM or MIUI. This happens after i flashed the kernel through fastboot. I get the following error.
(STATUS 7) Asserts Failed. I disabled the certifications and tried all sorts of stuff. Right now, I have baseband 64, ROOTED on STOCK SE FIRMWARE.
I searched for this answer a long time but got nothing so I had to actually MAKE AN ACCOUNT just to ask this dumb question. I get this error.
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" || getprop("ro.product.board") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" || getprop("ro.product.board") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" || getprop("ro.product.board") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" || getprop("ro.product.board") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu" || getprop("ro.product.board") == "anzu");
package_extract_file
I tried many suggestions as deleting the lines of code from the actual ZIP FILE. That did not work. I want to ore specifically direct my question at DINESH, here
http://forum.xda-developers.com/showthread.php?t=1503527
as for some reason his MIUI ROM is more troublesome than others and SAOSIN'S MIUI GB ROM actually I can flash onto my phone. Please let me know what I can do guys. Thanks and sorry for yet another NOOB QUESTION.
Click to expand...
Click to collapse
install via flashtool the original rom, reflash kernel and rom after. It will work. Try with another kernel if the last one doesn't work.

Wrong selection
From my sexy LT15i

You think if I just flash the kernels and do the roms it will work? Flashing the kernels through CWM though or using fastboot? Well, if you had any experience with them, please let me know. thanks.

u cannot flash kernel with cwm! The only way is via fastboot. I don't know if it works, but for resolve the topic problem u need to flash official rom, reflash a working kernel and after the rom.
in order to save time u should try first to flash a new kernel, with this try to install rom.zip from sd (wiping cache and system data). If it doesn't work, use the method explained above.

I flashed the miuiV4 from saossin and it worked. I think I know why. His rom is made only for the lt15i. The other rooms are made for both the arc and arc s. this is what screws up my phone. So the solution is to flash a rom made only for my phone. I had read somewhere that people had problems with partitions pertaining to this problem. Today I tried to download hosts for adfree and the program told me it could not find a partition to write to. Could this be a problem? Let me know what you think.

uspeekchaineze said:
I flashed the miuiV4 from saossin and it worked. I think I know why. His rom is made only for the lt15i. The other rooms are made for both the arc and arc s. this is what screws up my phone. So the solution is to flash a rom made only for my phone. I had read somewhere that people had problems with partitions pertaining to this problem. Today I tried to download hosts for adfree and the program told me it could not find a partition to write to. Could this be a problem? Let me know what you think.
Click to expand...
Click to collapse
i don't know but i don't think so, the roms designed for arc\arcs can work fully on both devices. I think that something can be corrupt in ur os, kernel or other, so my advice is the same yet. Use flashtool to return ur phone on the original factory rom, by this u can install all.

Related

KangXperiaProject Flashing or installation problem Resolved

open the downloaded rom zip file in computer.go to META-INF/com/google/android.
in that open updater-script in notepad.delete the below lines in ur notepad file.save it nd flash now.no installation errors.
assert(getprop("ro.product.device") == "X10i" || getprop("ro.build.product") == "X10i" ||
getprop("ro.product.device") == "X10a" || getprop("ro.build.product") == "X10a" ||
getprop("ro.product.device") == "es209ra" || getprop("ro.build.product") == "es209ra");
Click to expand...
Click to collapse
OK,I have solution
If your previous ROM is Feralab's ROM or orther,you will get the error during installation.
My solution is install other ROM like Achotjan's ROM before you install CM9 or AOKP ROM.You will have error free

KangXperiaProject error status 7 resolved

Open the downloaded rom zip file in computer.go to META-INF/com/google/android.
in that open updater-script in notepad.delete the below lines in ur notepad file.save it nd flash now.no installation errors.
assert(getprop("ro.product.device") == "X10i" || getprop("ro.build.product") == "X10i" ||
getprop("ro.product.device") == "X10a" || getprop("ro.build.product") == "X10a" ||
getprop("ro.product.device") == "es209ra" || getprop("ro.build.product") == "es209ra");
Click to expand...
Click to collapse

Impossible to flash latest MIUI 2.11.30

Hi All,
I'm trying to flash the latest MIUI 2.11.30 to my Galaxy SIII int without success.
I'd like to not install the chinese stock as requested on the MIUI site so I'm asking if someone was able to flash it from recovery on another rom.
Now I'm on Omega 3.33 with TWRP recovery but I also tried with Paranoid 2.54 and CWM touch without success.
I always get this error message:
Code:
assert failed: getprop("ro.product.device") == "~truncated
getprop("ro.build.product") == "m0" || ge~truncated
E:Error in "zip file path" (status 7)
Error flashing zip "zip file path"
Anyone knows a possible solution?
Thank you very much!
Bye.
Try altering the install script in the zip file to say "galaxys3" instead of "m0".
Sent from my GT-I9300 using Tapatalk 2
Theshawty said:
Try altering the install script in the zip file to say "galaxys3" instead of "m0".
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the advice, no luck with that but I solved it removing this assert statement:
Code:
assert(getprop("ro.product.device") == "m0" ||
getprop("ro.build.product") == "m0" || getprop("ro.product.device") == "m0" || getprop("ro.build.product") == "m0");
from this file inside the zip:
META-INF\com\google\android\updater-script
Thanks again for the advice, I took a look around and I saw that. :good:
Bye!
Now that it's solved, Thread closed.

help needed: install.zip for rom only

Hello,
ive made a custom kernel for Cyanogenmod 11 and Galaxy Note 3 to add drivedroid usbdrive mode and "usb keyboard" support. Now i want to give something back and want to share my kernel. The problem: i dont know how to build a install.zip for kernel only installation. Has anyone a template zipfile where i can add the kernel ? At the moment iam pushing the kernel with adb to my device, but i think its much easier for most to do this via recoveryimage.
Ive found some templates for other devices, but all contains some binaries from google and i dont know if this files are compatible with the SM-9005.
best regards and thank you for support.
EDIT: will this work ? I used the original fullversion auf cm11 install.zip and removed all other think i dont think i need for new kernel:
assert(getprop("ro.product.device") == "hltexx" || getprop("ro.build.product") == "hltexx" ||
getprop("ro.product.device") == "hltespr" || getprop("ro.build.product") == "hltespr" ||
getprop("ro.product.device") == "hltetmo" || getprop("ro.build.product") == "hltetmo" ||
getprop("ro.product.device") == "SM-N900T" || getprop("ro.build.product") == "SM-N900T" ||
getprop("ro.product.device") == "hltecan" || getprop("ro.build.product") == "hltecan" ||
getprop("ro.product.device") == "hlteatt" || getprop("ro.build.product") == "hlteatt" ||
getprop("ro.product.device") == "hltevzw" || getprop("ro.build.product") == "hltevzw" ||
getprop("ro.product.device") == "hlteusc" || getprop("ro.build.product") == "hlteusc" ||
getprop("ro.product.device") == "hlte" || getprop("ro.build.product") == "hlte" || abort("This package is for \"hltexx,hltespr,hltetmo,SM-N900T,hltecan,hlteatt,hltevzw,hlteusc,hlte\" devices; this is a \"" + getprop("ro.product.device") + "\".");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
Click to expand...
Click to collapse

your devise is wt88047 and this package is for HMxxxxx

recently i read it somewhere that flashing a custom rom over lollipop bootloader of R2P miui will give you voLTE in your custom rom
but there whenever i flash rom it gives status 7 error
it is recovery problem or rom problem?
using twrp recovery and mokee lollipop based rom
rajatchawla66 said:
recently i read it somewhere that flashing a custom rom over lollipop bootloader of R2P miui will give you voLTE in your custom rom
but there whenever i flash rom it gives status 7 error
it is recovery problem or rom problem?
using twrp recovery and mokee lollipop based rom
Click to expand...
Click to collapse
Do a clean flash[wipe data+cache+system] and install ROM.
Take a backup your current ROM first.
rajatchawla66 said:
recently i read it somewhere that flashing a custom rom over lollipop bootloader of R2P miui will give you voLTE in your custom rom
but there whenever i flash rom it gives status 7 error
it is recovery problem or rom problem?
using twrp recovery and mokee lollipop based rom
Click to expand...
Click to collapse
You are using wrong recovery. Download and use this one -
http://forum.xda-developers.com/redmi-2/development/recovery-recovery-built-source-inside-t3277621
Instructions for installing recovery can be found here -
http://forum.xda-developers.com/redmi-2/how-to/ultimate-guide-redmi-2-users-rooting-to-t3294212
Hope this helps :good:
Extract the Rom Zip file
Goto Meta-Inf/com/google/android/
Open updater script as a text file and add the following line just after this
assert(
Add this:
getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" ||
Or delete the following code from updater script:
assert(getprop("ro.product.device") == "HM2014811" || getprop("ro.build.product") == "HM2014811" || getprop("ro.product.device") == "HM2014812" || getprop("ro.build.product") == "HM2014812" || getprop("ro.product.device") == "HM2014813" || getprop("ro.build.product") == "HM2014813" || getprop("ro.product.device") == "HM2014814" || getprop("ro.build.product") == "HM2014814" || getprop("ro.product.device") == "HM2014815" || getprop("ro.build.product") == "HM2014815" || getprop("ro.product.device") == "HM2014816" || getprop("ro.build.product") == "HM2014816" || getprop("ro.product.device") == "HM2014817" || getprop("ro.build.product") == "HM2014817" || getprop("ro.product.device") == "HM2014818" || getprop("ro.build.product") == "HM2014818" || getprop("ro.product.device") == "HM2014819" || getprop("ro.build.product") == "HM2014819" || getprop("ro.product.device") == "HM2014820" || getprop("ro.build.product") == "HM2014820" || getprop("ro.product.device") == "HM2014821" || getprop("ro.build.product") == "HM2014821" || getprop("ro.product.device") == "HM2014112" || getprop("ro.build.product") == "HM2014112" || getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" || getprop("ro.product.device") == "wt86047" || getprop("ro.build.product") == "wt86047" || abort("This package is for device: HM2014811,HM2014812,HM2014813,HM2014814,HM2014815,HM2014816,HM2014817,HM2014818,HM2014819,HM2014820,HM2014821,HM2014112,wt88047,wt86047; this device is " + getprop("ro.product.device") + ".");
Only do this with the zip files which you know are for this device only. Doing this with zip files of other devices may damage your device beyond recovery...........
aashishdamrait said:
Extract the Rom Zip file
Goto Meta-Inf/com/google/android/
Open updater script as a text file and add the following line just after this
assert(
Add this:
getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" ||
Or delete the following code from updater script:
assert(getprop("ro.product.device") == "HM2014811" || getprop("ro.build.product") == "HM2014811" || getprop("ro.product.device") == "HM2014812" || getprop("ro.build.product") == "HM2014812" || getprop("ro.product.device") == "HM2014813" || getprop("ro.build.product") == "HM2014813" || getprop("ro.product.device") == "HM2014814" || getprop("ro.build.product") == "HM2014814" || getprop("ro.product.device") == "HM2014815" || getprop("ro.build.product") == "HM2014815" || getprop("ro.product.device") == "HM2014816" || getprop("ro.build.product") == "HM2014816" || getprop("ro.product.device") == "HM2014817" || getprop("ro.build.product") == "HM2014817" || getprop("ro.product.device") == "HM2014818" || getprop("ro.build.product") == "HM2014818" || getprop("ro.product.device") == "HM2014819" || getprop("ro.build.product") == "HM2014819" || getprop("ro.product.device") == "HM2014820" || getprop("ro.build.product") == "HM2014820" || getprop("ro.product.device") == "HM2014821" || getprop("ro.build.product") == "HM2014821" || getprop("ro.product.device") == "HM2014112" || getprop("ro.build.product") == "HM2014112" || getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" || getprop("ro.product.device") == "wt86047" || getprop("ro.build.product") == "wt86047" || abort("This package is for device: HM2014811,HM2014812,HM2014813,HM2014814,HM2014815,HM2014816,HM2014817,HM2014818,HM2014819,HM2014820,HM2014821,HM2014112,wt88047,wt86047; this device is " + getprop("ro.product.device") + ".");
Only do this with the zip files which you know are for this device only. Doing this with zip files of other devices may damage your device beyond recovery...........
Click to expand...
Click to collapse
i tried this earlier but i get "status 6" error
and i also checked the path,path of system is correct in updater script but still status 6 error
anandmore said:
You are using wrong recovery. Download and use this one -
http://forum.xda-developers.com/redmi-2/development/recovery-recovery-built-source-inside-t3277621
Instructions for installing recovery can be found here -
http://forum.xda-developers.com/redmi-2/how-to/ultimate-guide-redmi-2-users-rooting-to-t3294212
Hope this helps :good:
Click to expand...
Click to collapse
whenever i flash this recovery or boot this recovery by fastboot,it got stuck at mi logo .this is happening with me for a lot of recoveries
raymond_bqg said:
Do a clean flash[wipe data+cache+system] and install ROM.
Take a backup your current ROM first.
Click to expand...
Click to collapse
by this will i get voLTE in the new rom?
rajatchawla66 said:
by this will i get voLTE in the new rom?
Click to expand...
Click to collapse
If the ROM you are flashing supports volte,then YES.
damon_1991 said:
If the ROM you are flashing supports volte,then YES.
Click to expand...
Click to collapse
flashing a rom after a voLTE supported rom(miui 5.1.1 with voLTE) will give voLTE to the flashed custom rom
will it work after wiping system too?
rajatchawla66 said:
flashing a rom after a voLTE supported rom(miui 5.1.1 with voLTE) will give voLTE to the flashed custom rom
will it work after wiping system too?
Click to expand...
Click to collapse
Yes,as it is about bootloader not about system.
Always take backup of ur Current Rom by T.W.R.P before flashing any rom .
damon_1991 said:
Yes,as it is about bootloader not system.
Click to expand...
Click to collapse
flashing right now
hope for the best
thanks a lot for your help

Categories

Resources