[SOLVED!] Unable to flash MIUI - Status 7 - Galaxy S 4 Q&A, Help & Troubleshooting

PROBLEM FOUND AND FIXED! Answer in Post #3
http://forum.xda-developers.com/showpost.php?p=53784248&postcount=3
Hey guys
I've been trying to install MIUI for hours, using both CWM or TWRP, and I'm always receiving the same error message:
Writing recovery
set-perm: some changes failed
E:Error in /sdcard/miui_i9500_4.6.20_27061504e7_4.2.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I've flashed CM without a problem, and an original stock ROM as well.
Why is MIUI giving me a hard time?
**I already followed this guide: http://en.miui.com/thread-13226-1-1.html**
Thank you!

Omga4000 said:
Hey guys
I've been trying to install MIUI for hours, using both CWM or TWRP, and I'm always receiving the same error message:
I've flashed CM without a problem, and an original stock ROM as well.
Why is MIUI giving me a hard time?
**I already followed this guide: http://en.miui.com/thread-13226-1-1.html**
Thank you!
Click to expand...
Click to collapse
Use Philz recovery (just flash zip attch in rec) it's something to do with the older binary code-that's why it's status 7 ?

Well, after deciding to fix this problem once and for all, I added a "ui_print" after
every (well not every) line, to see exactly where is the installation failing.
The discovery? It fails at:
set_perm(0, 0, 0555, "/data/local/tmp/relink");
Click to expand...
Click to collapse
The solution?
Change all "/data/local/tmp/relink" into "/tmp/relink" like so:
package_extract_file("META-INF/com/miui/relink", "/tmp/relink");
set_perm(0, 0, 0555, "/tmp/relink");
run_program("/tmp/relink");
delete("/tmp/relink");
Click to expand...
Click to collapse
Problem solved - clean installation with no errors

Hi Anyone having issue with offline charging in MIUI ROM ?
Sent from my GT-I9500 using XDA Premium 4 mobile app

Omga4000 said:
Well, after deciding to fix this problem once and for all, I added a "ui_print" after
every (well not every) line, to see exactly where is the installation failing.
The discovery? It fails at:
The solution?
Change all "/data/local/tmp/relink" into "/tmp/relink" like so:
Problem solved - clean installation with no errors
Click to expand...
Click to collapse
Hi! sorry
Please how can I clearly follow your guide I'm Noob and dont really know about this. So can you please guide me with a step by step.
Thanks for understanding

mckalyster said:
Hi! sorry
Please how can I clearly follow your guide I'm Noob and dont really know about this. So can you please guide me with a step by step.
Thanks for understanding
Click to expand...
Click to collapse
1) Extract "updater-script" from the ROM file (using winrar for example)
It's located in META_INF > COM > GOOGLE > ANDROID
2) Change the parts I wrote in the previous post
3) paste the "updater-script" file inside the rom
Good luck

i9500 MIUI Flashing Error
After downloading the MIUI ROM, open with winrar and locate the updater-script
\META-INF\com\google\android\updater-script
and remove the first line of code
getprop("ro.product.device") == "ja3g" || getprop("ro.product.device") == "ja3g" || abort("This package is for "ja3g" devices; this is a "" + getprop("ro.product.device") + "".");
save and update from the winrar app.
Try flashing again but disable the zip verification......Done
Big ups to Edwin270

i have installed cwm recovery in my mi4 and forgot which rom i have installd just to update the android version from kitkat to marshmallow(6.0)after installed it converted into completely android phone there is no sign of miui rom so plz tell me how to get it back. even i have tried to installed miui 8 rom bt it showing 'installation aborted' i have tried many times in a differnt way i have tried everything but still i am not able to install zip file that is miui 8 rom. please help anyone wht to do now?

Don't use cwm, use twrp to flash custom roms.

Related

What are the files to download and flash to get RCmixHD

HI all,
Ca you help me in flashing RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.0.1 ROM. I need to know which are the files I have to download and flash. Thanks in Advance.
With regards
<Manic>
There is a whole section titled ROM links, it shouldn't be that hard to work out :/
If you're generally referring to flashing a custom rom then have a good read at the Nexus One wiki, it'll help you understand a little more.
manicsen said:
HI all,
Ca you help me in flashing RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.0.1 ROM. I need to know which are the files I have to download and flash. Thanks in Advance.
With regards
<Manic>
Click to expand...
Click to collapse
ill upload it. the rom seems to be only showing up as 1.01mb on the OP thread. ill post link when im done
charlieb620 said:
ill upload it. the rom seems to be only showing up as 1.01mb on the OP thread. ill post link when im done
Click to expand...
Click to collapse
It might help if you read the posting fully. You need to download all three files.
1. RCmixHD 1.0
2. USB Fix
3. 1.0.1 Update
Install them in this order, reboot between each install. And make sure you fully wipe your device first.
What about for Version 1.1.. I think i can download that single file and flash the ROM..
hi,
i downloaded RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.1 ROM and flashed it after full wipe..
During the time of flashing i am getting this message.. Kindly help me in clearing this problem
E:Missing file:
ext/system-VR/0419/libCBLexMgr.0419.so
E: Verification failed
zip verification failed
zip isn't signed correctly.
Installation aborted..
manicsen said:
hi,
i downloaded RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.1 ROM and flashed it after full wipe..
During the time of flashing i am getting this message.. Kindly help me in clearing this problem
E:Missing file:
ext/system-VR/0419/libCBLexMgr.0419.so
E: Verification failed
zip verification failed
zip isn't signed correctly.
Installation aborted..
Click to expand...
Click to collapse
Disable signature verification(If you're using RA Recovery, you can see 'toggle signature...', and I think Clockwork also has such option) and try it again.
Hi,
Is it Safe to flash Unsigned ROM.. or i have to wait for Signature once full ROM is there..
<Manic>
manicsen said:
Hi,
Is it Safe to flash Unsigned ROM.. or i have to wait for Signature once full ROM is there..
<Manic>
Click to expand...
Click to collapse
Although it warns about unsigned ROM/updater, I think if it is from reliable developer, it's usually OK, though I feel developers should sign their .zip files after packing is done.
thanks.. i have flashed already

Error Update to _0089_US

My device is:
- 183825U
- ThinkPadTablet_A310_02_0039_0086_US I use ThinkPadTablet_A310_02_0039_0086_US_CWR_MOD.zip
- Root
- CWM-based Recovery v5.5.0.4
I download the ThinkPadTablet_A310_02_0039_0089_US.zip try install by CWM
Show this:
assert failed: getprop("ro.product.device") ++ "Indigo" || getprop("ro.bluid.product") == "Indigo"
E:Error in /sdcard/ThinkPadTablet_A310_02_0039_0089_US.zip
(Status 7)
Instalattion aborted
I think you have to edit the update script. There is a thread in the general section.
One question: are you US, WE, or ROW? You have to use Device specific rom.
Moved To General​
This is a development section, its not for questions​
why not just flash stock recovery to udpate?
rangercaptain said:
I think you have to edit the update script. There is a thread in the general section.
One question: are you US, WE, or ROW? You have to use Device specific rom.
Click to expand...
Click to collapse
Hi rangercaptain,
I've the same problem but I use ROW ROM. Could you please advise where can I find the mentioned update script?
emerson - you've updated to 0086 using a tweaked update that works with CWM Recovery as well as skips checking for a few specifics.
You can now use the next tweaked update to get you all the way to 0089/OTA2.5 - since you tried with the official Lenovo update, it failed. Use this one:
ThinkPadTablet_A310_02_0039_0089_US_CWR.zip
pwstein said:
emerson - you've updated to 0086 using a tweaked update that works with CWM Recovery as well as skips checking for a few specifics.
You can now use the next tweaked update to get you all the way to 0089/OTA2.5 - since you tried with the official Lenovo update, it failed. Use this one:
ThinkPadTablet_A310_02_0039_0089_US_CWR.zip
Click to expand...
Click to collapse
This work.

CM9 error while trying to install it

(First off, XDAFAIL. So if you have made 10 posts you instantly get smarter and get allowed to post in devolpment sub-forum section )
I edited the link (correct topic now):
[ROM][ICS 4.0.4][3G] CyanogenMod9 (29 Mar) (Cornerstone Available)
I have fully rooted transformer. At the moment I have the rooted latest official Asus version. I have cloackworkMod Recovery V.3.2.0.1 gee one-tf101-ww (is this outdated? I had the one that has the rebootloop issue).
When trying to install the zip after wiping cache (dalvik,...) it gives me the fallowing error:
Code:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "tf101" || getprop("ro.build.product") == "tf101"
E:Error in /sdcard/cmp9/update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip (status 7)
Installation aborted
(the .zip file is not corrupted... md5 result is the same)
So anyone know what the problem might be? I am gona look some more into this and try and install another clockwordMod.
Why are you linking [ROM][1.APR.2012][3G]AOKP (Android Open Kang Project) *OFFICIAL* [v1.8] Build 29! when you are trying to flash update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip?
The 10 post rule worked really well here since you would have posted in the wrong thread anyway.
Not sure if it has anything to do with your problem but you should update to CWM 5 by Roach.
When trying to install the zip after wiping cache (dalvik,...)
Click to expand...
Click to collapse
uh.. you are coming from stock ASUS rom. To avoid possible complications, you should wipe more than just dalvik cache. Do a full wipe.
horndroid said:
Why are you linking [ROM][1.APR.2012][3G]AOKP (Android Open Kang Project) *OFFICIAL* [v1.8] Build 29! when you are trying to flash update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip?
The 10 post rule worked really well here since you would have posted in the wrong thread anyway.
Not sure if it has anything to do with your problem but you should update to CWM 5 by Roach.
uh.. you are coming from stock ASUS rom. To avoid possible complications, you should wipe more than just dalvik cache. Do a full wipe.
Click to expand...
Click to collapse
Hmm, no I just made a error linking the wrong topic (I wouldn't have had to do that if I could just reply to the topic at hand). And yes, I am doing a full wipe (hence the "...").
The topic this relates to is:
[ROM][ICS 4.0.4][3G] CyanogenMod9 (29 Mar) (Cornerstone Available)
Btw, damm you reCaptcha! Its sometimes hard to read :S (i keep asking for new ones )
edit:
I found the problem! It was indeed because of the clockwork version (installed the team rogue version back again (wish is way better anyways!) and it works fine now).

Flashing ROM Fail HELP!!!

So I decided I'm tired of all the bugs in Android 4.4 and wanted to flash the PACMan ROM onto my 2012 Wifi only Nexus 7. So I have my nexus unlocked and rooted but when I go to install the ROM via TWRP V2.6.3.1 I get this error message:
Installing '/sdcard/pac_grouper-nightly-20140121.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" II getprop("ro.build.pr
E:Error executing updater binary in zip '/sdcard/pac_grouper-nightly-20140121.zip
Updating partition files..
Can anyone tell me whats going wrong? I'm terrible at the whole computer thing, unlocking and rooting was tough enough even with the Nexus Root Toolkit.
Thanks
ST2014 said:
So I decided I'm tired of all the bugs in Android 4.4 and wanted to flash the PACMan ROM onto my 2012 Wifi only Nexus 7. So I have my nexus unlocked and rooted but when I go to install the ROM via TWRP V2.6.3.1 I get this error message:
Installing '/sdcard/pac_grouper-nightly-20140121.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" II getprop("ro.build.pr
E:Error executing updater binary in zip '/sdcard/pac_grouper-nightly-20140121.zip
Updating partition files..
Can anyone tell me whats going wrong? I'm terrible at the whole computer thing, unlocking and rooting was tough enough even with the Nexus Root Toolkit.
Thanks
Click to expand...
Click to collapse
Transfer zip to a pc Open up the zip file with winrar or 7zip there is a meta inf folder find the updater script file open with notepad erase the first line it will say something like asset get prop ect...... save the file transfer back to tablet it will now flash. Or use cwm to flash. I can do it for you if u send me the updater script file.
Even I have the same problem and if you flash a modded zip, TWRP and CWM give an error with no specified status number. I even tried signing the zip
EDIT: Install CWM and toggle signature verification. Simple right?
Press thanks if I helped.?
b3ltazar said:
Transfer zip to a pc Open up the zip file with winrar or 7zip there is a meta inf folder find the updater script file open with notepad erase the first line it will say something like asset get prop ect...... save the file transfer back to tablet it will now flash. Or use cwm to flash. I can do it for you if u send me the updater script file.
Click to expand...
Click to collapse
Thanks for the help. Unfortunately I got a tad frustrated and accidentally deleted EVERYTHING!!! So I have blank tablet now. I'm trying to download the Google Factory Images from their site but it only downloads this .tgz file instead of a zip with 4 files. I even tried extracting the .tgz and it give me a single file. Anyone have any ideas as to why this is?
I'm trying to restore this tablet based on following this page (can't post outside links on this site until after 10 posts?.......really?)
But as you can imagine I'm stuck because I can't download the aforementioned zip file.
My tablet is soon becoming destined to be a rifle target.
BAM!!! Never mind got it all squared away. Now if we can get that ROM set up so that it will work properly.
Androlover98 said:
Even I have the same problem and if you flash a modded zip, TWRP and CWM give an error with no specified status number. I even tried signing the zip
EDIT: Install CWM and toggle signature verification. Simple right?
Press thanks if I helped.?
Click to expand...
Click to collapse
I used CWM to load the ROM no problem. Thanks for the heads up.
So far I''m loving this PACMan ROM, smooth and tons of options. For me KitKat ruined my tablet, completely breaking the auto-rotate (making is stick in portrait mode), chrome crashed all the time and it was just generally laggy and slow.
Thanks to all that replied.
ST2014 said:
I used CWM to load the ROM no problem. Thanks for the heads up.
So far I''m loving this PACMan ROM, smooth and tons of options. For me KitKat ruined my tablet, completely breaking the auto-rotate (making is stick in portrait mode), chrome crashed all the time and it was just generally laggy and slow.
Thanks to all that replied.
Click to expand...
Click to collapse
Kitkat should work with no issues. i use slimkat 4.4.2 and i love it. Just make sure you wipe before the kitkat install and your tablet will fly.
b3ltazar said:
Kitkat should work with no issues. i use slimkat 4.4.2 and i love it. Just make sure you wipe before the kitkat install and your tablet will fly.
Click to expand...
Click to collapse
Exactly. Nothing beats KitKat. PERIOD
Sent from my Nexus 7 using Tapatalk

[ROM][5.0.2][TEST][LOLLIPOP][n7000]RESURRECTION REMIX LP 5.2.5

I Have opened this thread for test purposes only
THIS is a thread of Ressurection Remix 5.2.5 android 5.0.2
LINK to rom here
LINK TO gapps Here
Link to raw kernel here
FIRST YOU NEED the compaitble recovery and kernel ,the same one that cm12 uses
Refer THIS Thread
installing:
copy Rom+Google Apps to sdcard
boot into recovery
(factory reset) (if you get fc's or bootloops after updating from an older rom)
flash the rom and gapps zip file
reboot
now remember always take a nadroid backup of previous rom
some users report this error
Code:
error status 7
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
somebody knows how to fix this error please feel free to share here and test the ROM
status 7 error as I have always seen is related to incompatible recovery.
People got it while trying to flash kk ROMs coming from JB using a non SE Linux recovery.
Maybe try raw kernel?
remember not to boot system after flashing that kernel but reboot to recovery.
REVENGE SOLVES EVERYTHING
Help needed
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
varund7726 said:
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
Click to expand...
Click to collapse
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
tysonraylee said:
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
unfortunately I can't this the only phone I had, my S plus are not with me currently,
anyway, I'm not sure any of this issue causing the error are appear to be mine only, but I'm sure it is
status 7 error failed to write..bla..bla "/tmp/boot.img.."
I already forgot how's the error,
I'll try again in some time, currently at work and kinda busy, :crying:
so sorry guys,
hopefully others help too, :highfive:
please :good:
varund7726 said:
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
Click to expand...
Click to collapse
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
tysonraylee said:
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
goodluck buddy! :highfive: :victory: :highfive:
I heard 4.2.2 is going to landed on our device by old sammy, seems nice for forest kernel development! :victory:
kazuna69 said:
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
Click to expand...
Click to collapse
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
TouchLeclouds said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
Click to expand...
Click to collapse
Status 7 here is due to se linux recovery
varund7726 said:
Status 7 here is due to se linux recovery
Click to expand...
Click to collapse
I had the same issue before, my problem was solved by changing the update script
TouchLeclouds said:
I had the same issue before, my problem was solved by changing the update script
Click to expand...
Click to collapse
So can we change bauner update script and check the possibility
mjrifath said:
So can we change bauner update script and check the possibility
Click to expand...
Click to collapse
you can try that, but also keep in mind that this issue could be caused anything else. i just gave the solution that worked for me
Ok i got it to boot.thanks for the help guys.ill open a thread in the dev section and close this one

Categories

Resources