(status 7) installion aborded in CWM while installing CM9 - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

Hey fellas recently Ive been trying to install a ROM (CM 9 to be precise) and when i install it shows,
STATUS 7
installation aborted
i have tried to formatted my SD card still in did not worked,
but i also know that it may work if i update the CWM to the latest version and i am using sk17i xperia mini pro so how to do so, can any one guide me please or if there is an other way to do so please tell me.
And I have rooted stock ROM (GB) & stock Kernel.

Yes. It happened to me many times. The problem is the package and model no. mismatch . Just as a != A .... Simply Install another kernel..
Sent from my WT19i using xda app-developers app

Disregard the comment above. All you need to do is flash the CM9 kernel (via fastboot), which is contained inside the flashable .zip (I assume it's FXP, right?).
Your phone will now show the FXP logo while booting up. Boot into recovery. You'll see it's CWM v6, and now you're free to install CM9. No more Status 7 errors
It happened to me on a cousin's XPlay.
Don't forget to flash CM9 baseband via FlashTool!

try this
Hameer123 said:
Hey fellas recently Ive been trying to install a ROM (CM 9 to be precise) and when i install it shows,
STATUS 7
installation abortedl.
Click to expand...
Click to collapse
First of all make sure you have the right version of CM9 for your device. Next, open the downloaded ZIP, edit the file updater-script in your CM9ZIP\META-INF\com\google\android\. Delete ONLYthe first line including and upto the first semicolon( which starts with:
assert(getprop("ro.product.device"...
Save the modifications made, re-copy the file to SD Card and try flashing it again.
Make sure you're using the CM9 kernel and baseband 72 too!

blackstallion1234 said:
First of all make sure you have the right version of CM9 for your device. Next, open the downloaded ZIP, edit the file updater-script in your CM9ZIP\META-INF\com\google\android\. Delete ONLYthe first line including and upto the first semicolon( which starts with:
assert(getprop("ro.product.device"...
Save the modifications made, re-copy the file to SD Card and try flashing it again.
Make sure you're using the CM9 kernel and baseband 72 too!
Click to expand...
Click to collapse
its not clear. which line? from where up to where?
please can you give us the exact line which needed ot be deleted?

Pixelado said:
Disregard the comment above. All you need to do is flash the CM9 kernel (via fastboot), which is contained inside the flashable .zip (I assume it's FXP, right?).
Your phone will now show the FXP logo while booting up. Boot into recovery. You'll see it's CWM v6, and now you're free to install CM9. No more Status 7 errors
It happened to me on a cousin's XPlay.
Don't forget to flash CM9 baseband via FlashTool!
Click to expand...
Click to collapse
could u give me the download link to the CM9 kernel for sk17i

The Kernel is included in the Download ZIP File. Just Download the ZIP file and extract it. Then you have 1 extracted and 1 packed. The packed you put on the sd card.
You take out of the extracted the Boot.img. Maybe it's got another Name, but it's an image File. Just Download flashtool (search in development Forum for Sony flashtool) and Flash via fastboot mode.
But remember: For all these steps, you MUST have an UNLOCKED BOOTLOADER!!!
Sent from my SK17i using xda app-developers app

static28 said:
its not clear. which line? from where up to where?
please can you give us the exact line which needed ot be deleted?
Click to expand...
Click to collapse
Thought that the "first semicolon" description would be enough, but anyway this is the line I'm talking about:
assert(getprop("ro.product.device") == "WT19a" || getprop("ro.build.product") == "WT19a" ||
getprop("ro.product.device") == "WT19i" || getprop("ro.build.product") == "WT19i" ||
getprop("ro.product.device") == "coconut" || getprop("ro.build.product") == "coconut");
"WT19{a/i}" will vary as per device codes. For instance, the OP will have"SK17{a/i}" (and "mango" instead of "coconut")
---------- Post added at 10:56 PM ---------- Previous post was at 10:52 PM ----------
Hameer123 said:
could u give me the download link to the CM9 kernel for sk17i
Click to expand...
Click to collapse
It's there on CyanogenMod's site but here's the link anyway! :angel:CM 9.1

Pixelado said:
Disregard the comment above. All you need to do is flash the CM9 kernel (via fastboot), which is contained inside the flashable .zip (I assume it's FXP, right?).
Your phone will now show the FXP logo while booting up. Boot into recovery. You'll see it's CWM v6, and now you're free to install CM9. No more Status 7 errors
It happened to me on a cousin's XPlay.
Don't forget to flash CM9 baseband via FlashTool!
Click to expand...
Click to collapse
i followed suggestion for status error7 .. of deleting first 3 lines
after placing that updated zip file in sd card .
i again got error
installation update
installation aborted ..
i tried searching ,many links didnt got it .. pls help as i have
xperia mini pro sk17i
unlocked bootloader
rooted
cmw 5.0.2
thanks in advance
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
static28 said:
its not clear. which line? from where up to where?
please can you give us the exact line which needed ot be deleted?
Click to expand...
Click to collapse
i followed suggestion for status error7 .. of deleting first 3 lines of updater script
after placing that updated zip file in sd card .
i again got error
installation update
installation aborted ..
i tried searching ,many links didnt got it .. pls help as i have
xperia mini pro sk17i
unlocked bootloader
rooted
cmw 5.0.2
thanks in advance

re install stock
flash cm9 kernel
wipe and factory reset
don't delete system or anything els
then install
good luck

I understand that you are new but please read the forum rules before posting.....Firstly many threads have been made on this issue so first check them out and then if none comes up to your expectation make a new thread and secondly these type of thread belong to the q/a thread and not the general thread.....so please moderators move this thread to q/a forum
Regards,
Abhinav

nick_pats said:
i followed suggestion for status error7 .. of deleting first 3 lines
after placing that updated zip file in sd card .
i again got error
installation update
installation aborted ..
i tried searching ,many links didnt got it .. pls help as i have
xperia mini pro sk17i
unlocked bootloader
rooted
cmw 5.0.2
thanks in advance
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
i followed suggestion for status error7 .. of deleting first 3 lines of updater script
after placing that updated zip file in sd card .
i again got error
installation update
installation aborted ..
i tried searching ,many links didnt got it .. pls help as i have
xperia mini pro sk17i
unlocked bootloader
rooted
cmw 5.0.2
thanks in advance
Click to expand...
Click to collapse
Your answer is in post #3. Flash the kernel for the ROM 1st, this will update your version of cwm and everything should be fine. You need to be careful when you delete the assert(getprop.... lines from the updater-script. First, these lines are there to protect you from flashing a ROM for a different device and this can really screw up your device, so you should only delete these if you are coming from a custom ROM that wasn't ported correctly (shows the wrong device in the build.prop) or if you have mangled your build.prop beyond belief. One way to tell is by connecting your device to the PC where you keep PC Companion, if it recognized as a different device then you may need to delete the assert(getprop....lines. Second, make sure you use a compatible text editor (in windows you probably want notepad++ ) to edit your updater-script. If you use plain old notepad, or wordpad, or word, you will probably mess up the updater-script and get install errors. The easiest way to fix this is to just redownload the ROM.
Edit: To be fair to nick_pats and to the OP, this is an old thread that was started before there was a Q&A section and probably nick_pats found it the way he was suppossed to...by using the search function!

Related

I can't flash any zip via xRecovery :-(

Hi sirs
I've tried to flash 3 zip files via xRec , it fails every time :-(
It says that there's something error or don't know what f**k it is
Then it says that the installtion of the zip file is aborted
So what can I do??
I trust that you can find me some solutions
You have BusyBox installed right?
Sent from my LT26i using xda premium
I had same problem, what flashtool version you using may I ask?
Sent from my flying X10 using xda premium
Make sure your not flashing unflashable zip. I made that mistake.
Sent from my flying X10 using xda premium
Surely I have BusyBox
And I'm sure that I haven't flashed unflashable zip , because I tried to flash the Xperia S music player zip downloaded from xda developpers
I had this before when I started out flashing roms, check to see if the zip file is flashed via xrec or cwm5 (if that's how its is or cmw5)
Sent from my Xperia X10 using XDA
The zip files uploaders says " flash with xRecovery " so I do & I fail
Is your super user and su binary up do date. I put mine up to date and it solved the issue of it being able to flash for some roms
TeraXimoS said:
Hi sirs
I've tried to flash 3 zip files via xRec , it fails every time :-(
It says that there's something error or don't know what f**k it is
Then it says that the installtion of the zip file is aborted
So what can I do??
I trust that you can find me some solutions
Click to expand...
Click to collapse
Are you download that file? Make sure your check md5sum
my superuser is up to date , but what is SU binary??
I found it , SU &it's binary is up to date , and the prob still appears :-(
TeraXimoS said:
I found it , SU &it's binary is up to date , and the prob still appears :-(
Click to expand...
Click to collapse
Maybe the zip you're trying to flash is a edify script? Try flash using CWM.
I remembered something , my version of BusyBox is not the latest , can it be a cause ??
I couldn't install the latest BusyBox version , it's really ****ing issue :-(
Please sirs , can you tell me how to flash via PC on Flashtool??
My device is Xperia X10 surely
My rom is the official GingerBread 2.3.3
Look here for flashtool help:
http://forum.xda-developers.com/showthread.php?p=10879507
Sent from my X10S using XDA
Hi, Did you try the search button before asking ?
To use Flashtool, you have an awesome guide by G-FACE (The link is in my signature)
If you are root and just want to install recovery with flashtool just go on post #6 of his thread HERE
Hope it helps...
---------- Post added at 07:56 PM ---------- Previous post was at 07:56 PM ----------
lol, too fast for me laneyofdeath ... ;-)
Mr. 9andar , I have already installed xRecovery , no problem with recovery mode , my problem is FLASHING ZIPs :-(
1: Download Rom of choice to pc/lappy 2:copy it to an easily found place on your sd card 3: boot into x recovery (mash back button upon boot) 4: goto install custom zip, select zip from sd card, and find the zip where u placed it on sd and select install. Thats it (u prob need to do factory reset before installing the zip)
Sent from my X10S using XDA
I'll try to install xRecovery GBReady with FlashTool, If it couldn't fix the prob, I'm gonna do a factory reset unfortunately :-(
Question :does the full backup of xRecovery creates a copy of messages and contacts??
Thank you all
Another question, will I be forced to re-root my device after factory reset??

4.0.4 rom installation help!!

Hi,
i've tried to install this rom on my x10i http://forum.xda-developers.com/showthread.php?t=1782771 but when i choose the file in cmw5 and hit install it says E:Error in /sdcard/XPERIA S ICS AOPK.zip (status 7) installation aborted.
before this ive unlocked the bootloader as this thread write: http://forum.xda-developers.com/showthread.php?t=1254087 and i think it was successful because i can flash this kernel http://forum.xda-developers.com/showpost.php?p=28126178&postcount=1566
and the SE logo disappeared.
what did i do wrong?? please help me! thanks!
qvasz said:
Hi,
i've tried to install this rom on my x10i http://forum.xda-developers.com/showthread.php?t=1782771 but when i choose the file in cmw5 and hit install it says E:Error in /sdcard/XPERIA S ICS AOPK.zip (status 7) installation aborted.
before this ive unlocked the bootloader as this thread write: http://forum.xda-developers.com/showthread.php?t=1254087 and i think it was successful because i can flash this kernel http://forum.xda-developers.com/showpost.php?p=28126178&postcount=1566
and the SE logo disappeared.
what did i do wrong?? please help me! thanks!
Click to expand...
Click to collapse
In the ZIP file (Meta-inf -> com -> Google -> Android) there is a file updater-script, you need to edit this file with notepad or similar. You need to get rid of the first line which has lots of "props" , so the first thing that stays there is : package_extract_file blabla
egerth said:
In the ZIP file (Meta-inf -> com -> Google -> Android) there is a file updater-script, you need to edit this file with notepad or similar. You need to get rid of the first line which has lots of "props" , so the first thing that stays there is : package_extract_file blabla
Click to expand...
Click to collapse
i did it but it says now E:Error in /sdcard/xperia s ics aokp.zip (status 6) installation aborted. :S
qvasz said:
i did it but it says now E:Error in /sdcard/xperia s ics aokp.zip (status 6) installation aborted. :S
Click to expand...
Click to collapse
Use different recovery, that might solve your problems.....
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
Use different recovery, that might solve your problems.....
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
ive tried the xrecovery but i got the same error message. but i cant install any rom with 4.0 :/
i write down what i already did, cuz i might forgot something,
first i unlocked the bootloader as i said then
i flashed the kernel with flashtool, then
i did a full wipe and then try to flash the rom.
Try this?
If you have unlocked Bootloader (Checked through S1tool that you have unlocked bootloader, and have such flashing errors, try this
1.Try flash KCernel V3 here via flashtool since got multiple recoveries. You will get KCernel Logo shows once powered on.
2.Got Backed Up Locked Bootloader stock ROM data? Restore it back from similar xrecovery you used, compared to Kcernel's
3.You will get bootanimation of your previous ROM, bootloop, so won't get homescreen reached.
4.Take Off battery for few seconds, and then power it on
5.Get back to CWM Recovery and make full wipe, clear dalvik cache:
6.Flash your 4.0 ROM zip
7.Should work normally...
I tried before and worked Just share my little past experience though I'm now in AOKP ICS. Hope helps
whitefang
Ok thanks for everybody now its working fine i flashed the stock 2.3.3 rom then root my phone again and then flash the kernel and the rom so its all good
Sent from my Xperia X10 using xda app-developers app

[Xperia P][4.4.2][CM 11][CWM] "Installation aborted"

Hi,
I've been trying to install CM 11 based on Kitkat 4.4.2 on my Xperia P. The following are the details / steps followed:
- The bootloader is unlocked
- The phone is rooted
- CWM 6.0.1.2 is installed ( I think this is the latest available for Xperia P)
1) Downloaded CM11-RC1 from the links in this thread http://forum.xda-developers.com/showthread.php?t=2626639
2) Modified 'updater-script' to get rid of Error 7
3) Extracted 'boot.img' and flashed it using FlashTool in fastboot mode.
After reboot, the phone stops at Sony logo and vibrates once.
4) Pressed the Power button to load CWM Recovery
5) Wiped Data, Cache/Partition, Dalvik Cache
6) Tried to install CM11-RC1 zip file using CWM
Now I get the message "Installation aborted", as soon as the installation begins, without any error code being displayed
I can't seem to get past this step, and don't know where I'm going wrong.
Can anyone please help me out?
Are you sure that your phone is unlocked bootloader ? Did you unlocked yourself ? And you should not change anything in update script because i had flash this rom without problem ...
Sent from my Xperia P using Tapatalk 2
-ss- said:
Are you sure that your phone is unlocked bootloader ? Did you unlocked yourself ? And you should not change anything in update script because i had flash this rom without problem ...
Sent from my Xperia P using Tapatalk 2
Click to expand...
Click to collapse
Yes. The bootloader is unlocked. I did it myself following the instructions on the Sony website.
The installation shows an error 7 if I don't modify the updater script.
Delete sorry
Sent from my Xperia P using Tapatalk
yomayne said:
Yes. The bootloader is unlocked. I did it myself following the instructions on the Sony website.
The installation shows an error 7 if I don't modify the updater script.
Click to expand...
Click to collapse
What i have done with flashing this rom was just followed the OP : format system, format data and format catch then flash ROM and gapps without problem ...
Sent from my Xperia P using Tapatalk 2
-ss- said:
What i have done with flashing this rom was just followed the OP : format system, format data and format catch then flash ROM and gapps without problem ...
Sent from my Xperia P using Tapatalk 2
Click to expand...
Click to collapse
Could it be a version issue? Which one did you flash? I did RC1
Hey I had exactly the same problem. What I did was this:
I used Sony Mobile EMMA to re-install latest stock firmware.
After that I rooted it and Installed CWM 1.0 Nypon, I believe this is CWM somewhere in V6.xxxx (other versions wouldn't work for me..)
I also edited the updater script because it wouldn't pass the assert section, so I deleted this.
After that Recompiled it, (Zip format ofcourse) and copied it to SD card.
Next, I flashed boot.img and rebooted the phone after that. Then access CWM.
Now what I did was userdata/factory reset after that I deleted cache, and last but not least dalvik cache.
After that I flashed the recompiled ROM file and then It passed the status 7 error.
When that was finished I flashed gapps
This was what I did, becuz' I had exactly the same problem. I don't know if this works for you but you might give it a try.
(Sorry for bad Englisch)
(Make sure that your bootloader is unlocked! (To verify, I did try to unlock it again. Then I got a message saying that it was allready unlocked)
ReplayMitta said:
Hey I had exactly the same problem. What I did was this:
I used Sony Mobile EMMA to re-install latest stock firmware.
After that I rooted it and Installed CWM 1.0 Nypon, I believe this is CWM somewhere in V6.xxxx (other versions wouldn't work for me..)
I also edited the updater script because it wouldn't pass the assert section, so I deleted this.
After that Recompiled it, (Zip format ofcourse) and copied it to SD card.
Next, I flashed boot.img and rebooted the phone after that. Then access CWM.
Now what I did was userdata/factory reset after that I deleted cache, and last but not least dalvik cache.
After that I flashed the recompiled ROM file and then It passed the status 7 error.
When that was finished I flashed gapps
This was what I did, becuz' I had exactly the same problem. I don't know if this works for you but you might give it a try.
(Sorry for bad Englisch)
(Make sure that your bootloader is unlocked! (To verify, I did try to unlock it again. Then I got a message saying that it was allready unlocked)
Click to expand...
Click to collapse
Thanks. I'll try doing that. Let's see if it works. Which CM11 build did you flash?
yomayne said:
Thanks. I'll try doing that. Let's see if it works. Which CM11 build did you flash?
Click to expand...
Click to collapse
I flashed RC1 also, I tried almost all nightly's and the RC1 lol but they all wouldn't work before I used this sort of 'method'
Yesterday RC1 workied succesfully for me, today I updated to nightly 25 and everything works fine. Note that once you get passed the installation of RC1, that you can only access the CWM recovery with holding the power button, when your phone vibrates when you see the sony logo.. The CW11 comes with CMW touchable. Goodluck
And did it work?
I've solved my status 7 problem with this video ;
http://www.youtube.com/watch?v=QW1znjDLe-k
gilgin said:
I've solved my status 7 problem with this video ;
http://www.youtube.com/watch?v=QW1znjDLe-k
Click to expand...
Click to collapse
Auful way way to "fix" things.
You can "fix" galaxy ROM to be installed on your phone and brick it permanently, it's already been done.
If you have flashed galaxy kernel you probably won't be able to boot but still able to recover.
Tha asserts are there for a reason.
ChikeD said:
Auful way way to "fix" things.
You can "fix" galaxy ROM to be installed on your phone and brick it permanently, it's already been done.
If you have flashed galaxy kernel you probably won't be able to boot but still able to recover.
Tha asserts are there for a reason.
Click to expand...
Click to collapse
I didn't flash a wrong kernel or rom. İf friend is sure of the right pack to flash, than he can use this method.
I wanted to flash cm nightly 25 (percy's rom) to my xperia p, and the cwm gave status 7 error. Then i have searched a solution for my problem, and i found this video and did what he shows in the video, and i have a cm11 flashed xperia p now. And i also flashed over cm11-weekly.
(sorry if i have a bad english)
gilgin said:
I didn't flash a wrong kernel or rom. İf friend is sure of the right pack to flash, than he can use this method.
I wanted to flash cm nightly 25 (percy's rom) to my xperia p, and the cwm gave status 7 error. Then i have searched a solution for my problem, and i found this video and did what he shows in the video, and i have a cm11 flashed xperia p now. And i also flashed over cm11-weekly.
(sorry if i have a bad english)
Click to expand...
Click to collapse
Sp they released a ROM that cannot be flushed, is that what you say? And no one else reporting it?
Somehow I find it difficult to believe.
If you have followed the instructions I'm sure there would be no problem, or the instructions are incomplete, or there is some issue, either way it's up to the developer to fix it.
Avoid "fixing" errors in this manner or one day you may regret it dearly.
ChikeD said:
Sp they released a ROM that cannot be flushed, is that what you say? And no one else reporting it?
Somehow I find it difficult to believe.
If you have followed the instructions I'm sure there would be no problem, or the instructions are incomplete, or there is some issue, either way it's up to the developer to fix it.
Avoid "fixing" errors in this manner or one day you may regret it dearly.
Click to expand...
Click to collapse
I have followed the instructions in a good way and this was the problem i have lived. Some of my friends lived this problem in a Turkish Forum and i recommended this way, they did it and flash the rom. I will give the link here; http://forum.donanimhaber.com/m_58138440/mpage_242/f_//tm.htm#87204228
My nick is ENG_civ on that forum. Everything is right about the rom but something goes in a wrong way, so this way makes the compiler not asking "is this right rom?", that's all. İn my opinion, if you are sure of the rom, there is no risk.
And i am new in this forum, and i couldn't write at development part, and this is the first time i am writing to a foreign language forum. So i couldn't reported them, and these rom's are not the final, so there could be faults on them i think.
gilgin said:
I've solved my status 7 problem with this video ;
(video)
Click to expand...
Click to collapse
I solved the problem with the CM11 this way too. But when I tried to install gapps after install cm11 appear the "status 7". What can I do?
Edit: I can flash the normal cm11 (without edit the .txt) but the problem with the gapps continues. I turned on my phone and then the cyanogenmod logo start running and don't leave this screen. Anyone can help me?
Error:
set_metadata_recursive: some changes failed
E:Error in /storage/sdcard0/gapps-kk-20140105.signed.zip (status 7)
Installation aborted.
nortonz said:
I solved the problem with the CM11 this way too. But when I tried to install gapps after install cm11 appear the "status 7". What can I do?
Edit: I can flash the normal cm11 (without edit the .txt) but the problem with the gapps continues. I turned on my phone and then the cyanogenmod logo start running and don't leave this screen. Anyone can help me?
Error:
set_metadata_recursive: some changes failed
E:Error in /storage/sdcard0/gapps-kk-20140105.signed.zip (status 7)
Installation aborted.
Click to expand...
Click to collapse
For gapps its normal. Its actually flashed
Sent from my Xperia P using Tapatalk
AndroidNoob69 said:
For gapps its normal. Its actually flashed
Sent from my Xperia P using Tapatalk
Click to expand...
Click to collapse
How "normal" ?
PS: now my celphone has cyanogenmod 11 ! I'm so glad and grateful for this post!
nortonz said:
How "normal" ?
Click to expand...
Click to collapse
'normal' as in everyone has it. The zip is actually flashed.
Sent from my Xperia P using Tapatalk
It worked!
Thanks so much ! I'm finally running 4.4.2

Error message while wiping and flashing CM 12.1

Hello guys,
I tried flashing cm 12.1 in oneplus x but faced a problem while doing the same.
Firstly i wiped my partitions which said-"Wipe complete" & "Failed" in new line bcos it couldn't wipe usb-otg,
i thought it was a minor problem & flashed CM 12.1 but it also gave some error as follows:
Installing '/sdcard/MA-12.1-20151223-onyx.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: ONE; this device is .
E:Error executing updater binary in zip '/sdcard/MA-12.1-20151223-onyx.zip'
Error flashing zip '/sdcard/MA-12.1-20151223-onyx.zip'
Updating partition details...
...done
I also flashed resurrection remix which gave exactly the same problem as above.
I repeated the same procedure twice & failed both the times and after that i restored my stock rom.
Can someone help me?
Delete the first line in updater.script and you will be fine.
Do u mean updater.script as in-
META-INF\com\google\android - updater-script of the rom zip file,
I tried this by deleting the first line which says-
assert(getprop("ro.product.device") == "ONE" ||
Got the same error again,what now?
R V said:
Do u mean updater.script as in-
META-INF\com\google\android - updater-script of the rom zip file,
I tried this by deleting the first line which says-
assert(getprop("ro.product.device") == "ONE" ||
Got the same error again,what now?
Click to expand...
Click to collapse
Or just flash blu spark recovery and flash cm12.1 from it, no need to delete any line.
You'll find the recovery in the blu spark kernel thread, download latest version from there.
R V said:
Hello guys,
I tried flashing cm 12.1 in oneplus x but faced a problem while doing the same.
Firstly i wiped my partitions which said-"Wipe complete" & "Failed" in new line bcos it couldn't wipe usb-otg,
i thought it was a minor problem & flashed CM 12.1 but it also gave some error as follows:
Installing '/sdcard/MA-12.1-20151223-onyx.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: ONE; this device is .
E:Error executing updater binary in zip '/sdcard/MA-12.1-20151223-onyx.zip'
Error flashing zip '/sdcard/MA-12.1-20151223-onyx.zip'
Updating partition details...
...done
I also flashed resurrection remix which gave exactly the same problem as above.
I repeated the same procedure twice & failed both the times and after that i restored my stock rom.
Can someone help me?
Click to expand...
Click to collapse
I hope you are using recovery from CM12.1, as MasterAwesome already mentioned in his OP that we have to use recovery which is provided by him. Or as someone else mentioned that you have to remove few lines of code to make it work.
I'm using twrp as given in cm12.1 thread by master awesome
parasthakur37 said:
Or just flash blu spark recovery and flash cm12.1 from it, no need to delete any line.
You'll find the recovery in the blu spark kernel thread, download latest version from there.
Click to expand...
Click to collapse
Can u paste the link here,it's nowhere to be found on blu spark's page
R V said:
Can u paste the link here,it's nowhere to be found on blu spark's page
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/dl/?id=15783
Quick suggestion : when you're finding something on a page and you've been told that it is on that page, try to exhaust all the links. I have given you the link which I got after clicking on DOWNLOAD.
parasthakur37 said:
http://forum.xda-developers.com/devdb/project/dl/?id=15783
Quick suggestion : when you're finding something on a page and you've been told that it is on that page, try to exhaust all the links. I have given you the link which I got after clicking on DOWNLOAD.
Click to expand...
Click to collapse
Man, i'm already using twrp.
Still i downloaded it again from ur link but the error while flashing cm12.1 or resurrection remix still persists.
And I will keep in mind your suggestion.
R V said:
Man, i'm already using twrp.
Still i downloaded it again from ur link but the error while flashing cm12.1 or resurrection remix still persists.
And I will keep in mind your suggestion.
Click to expand...
Click to collapse
Well that's very weird and shouldn't happen but okay no problem.
http://forum.xda-developers.com/devdb/project/dl/?id=15644
This is the link to twrp specifically for cm12.1 and I took it off the cm12.1 thread by MasterAwesome himself.
You can flash cm12.1 from this, don't know about RR or Mokee because the updater script might be changed.
1. Flash the recovery using flashify
2. Boot into recovery, flash cm12.1
parasthakur37 said:
Well that's very weird and shouldn't happen but okay no problem.
http://forum.xda-developers.com/devdb/project/dl/?id=15644
This is the link to twrp specifically for cm12.1 and I took it off the cm12.1 thread by MasterAwesome himself.
You can flash cm12.1 from this, don't know about RR or Mokee because the updater script might be changed.
1. Flash the recovery using flashify
2. Boot into recovery, flash cm12.1
Click to expand...
Click to collapse
Flashify served the purpose this time,
Thank u very much.
But the main problem due to which I flashed the ROM still persists i.e.many of my previous games give parse error problem while installing,can u please help me with this also.
R V said:
Flashify served the purpose this time,
Thank u very much.
But the main problem due to which I flashed the ROM still persists i.e.many of my previous games give parse error problem while installing,can u please help me with this also.
Click to expand...
Click to collapse
1. Be on stock where you have those apps running. (simply restore twrp backup)
2. Take a titanium backup (data+apk)
3. Flash cm12.1
4. Restore titanium backup
5. You're welcome
parasthakur37 said:
1. Be on stock where you have those apps running. (simply restore twrp backup)
2. Take a titanium backup (data+apk)
3. Flash cm12.1
4. Restore titanium backup
5. You're welcome
Click to expand...
Click to collapse
The problem is that they never ran on my stock ROM that's why I flashed custom rom moreover my titanium backup said that I was not rooted even when I was,what now?

[fix][guide]error_status_7 while flashing rom

Hi!
These is my first post?
If I made any mistake please help me to overcome☺
And if this guide helps u why not leave a thank you??
While flashing ROM we often find this error
Here is the all kinds of fix for this problem that I found in the INTERNET
Fix for that problem
#1
Check if you have changed the mount and format point correctly according to your device
Check this for details
http://www.mtkroms.com/2015/05/mtk-kitkat-porting-guide.html?m=1
#2
If you have done it
Check for this assert(
In your meta-inf/com/google/updater script
Search it using notepad++ and search assert
If you find a line started like this
assert(......
......)
Delete it from first to last bracket
Check this for details
http://forum.xda-developers.com/showthread.php?t=2302599
#3
If there is no assert lines
Then while flashing
First wipe(system+data+cache)
Reboot to recovery
Then try flashing
#4
If thats not working
Mount system in recovery
Then unmount it
Then try flashing
#5
If thats not working too
Did u copy replaced files you were asked to from stock to port?
Or u just deleted the files then copy paste in port?
If u deleted and then copy paste then try replacing files from stock to port
#6
U are using cwm/ctr recovery? Then try flashing using TWRP RECOVERY
U using Twrp recovery? Then try flashing using Phillz recovery
#7
If those fixs not working for u...
Use previous working meta-inf for your device that u have successfully ported
If are a newbie in porting and can't find a device specific cm ROM for your device then have a belief someone in this world have same device and ported a cm based ROM successfully and you if are lucky enough you may find him/her
Or just try another ROM to port and say to yourself that this ROM is full of bugs and ****s
IF I MISS ANYTHING DONT HESITATE TO MENTION

Categories

Resources