Develop Bugs

[Q] Flash Failed: Status 7

I rooted my Bell Galaxy SIII this afternoon using Mr. Robinsons method.
All good. Have root. Installed CWM (LTE Variant and other newer listed on Mr. Robinsons thread. One at a time, same error)
Booted into recovery and tried to install CM10 after factory reset, dalvick wipe, yada, yada yada.
I get the error:
Assert Failed: getprop("ro.product.device*) =="E:Error in /SDCARD/cm-10-20120912-nightly-d2Att.zip (Status 7)
Might be some left out as not all of the error code is shown.
Tried multiple times to download CM using different browsers and directly on the phone.
I am able to restore factory rooted image no problem.
I then installed TWRP v2.2.2.0
Same error when trying to install CM10-current nightly
I'm assuming that this is related to device ID and I'm trying to install ROM's not suitable for it?
I've tried with AOKP version from Task and get same error.
http://forum.xda-developers.com/showthread.php?t=1766684
Pretty sure these are good for Bell version....
Any idea's or confirmation that these won't work with my phone.
Thanks
Mike

You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Not sure what the issue is but I can tell you that I have installed task aokp with twrp and cwm recovery versions back to 5.5.0.4 with no problems on my Bell phone.

liltitiz said:
You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
Just so I learn something out of this...Why do I need this? I understand that both versions of CWM and TWRP I installed are used by people with the same hardware?
Just want to understand what I am missing.
Thanks,
Mike
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.

If you go in the cm10 thread in original developpenent, they specify which recovery to install with a link to download it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

mikewestlake said:
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.
Click to expand...
Click to collapse
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.

task650 said:
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.
Click to expand...
Click to collapse
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike

mikewestlake said:
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike
Click to expand...
Click to collapse
Using ROM Manager helps you keep your CWM recovery up to date. You can find the app in the play store
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Sent from my SAMSUNG-SGH-I747 CM10 + KT747, 96-2106 MHz, noop, ktoonservative, undervolted, 3150mAh battery.
Thanks to: Ktoonsez, Task650 and Cyanogen for their amazing works!

CyanogenMod 10.1 Nightly Installation Error "Status 7"

Greetings! This is the first time I've felt compelled to post in the forums, so I apologize in advance if this happens to be in the wrong section. I've been running CyanogenMod 10.1 on my Samsung Galaxy S3 SGH-T999VVLLH2 (Mobilicity) for quite some time now, and have only recently been interested in downloading and installing the nightly installments that are released.
I haven't had any issues installing the new nightlies at all, until seemingly after revision 20130513. It seems that after this installment, I receive an "assert failed, get prop, status 7" error, upon the attempt at installing any newer nightly revisions. Now, I did a tremendous amount of digging around before I decided to make the post, and discovered that within the newer revisions, the updater-script now seems to flag certain Baseband versions of the phone, and prior to revision 20130513 (currently have), it didn't, and I had no issues installing.
When I go into the CyanogenMod settings, all of the nightly updates are available, as usual, up to the latest at the time of the post (20130524) but none will install. In the latest revisions the updater-script does show a similar version (T999VVLDLL1), which I've come to understand is an update for the software.
Am I required to do another update before installing the latest CyanogenMod 10.1 nightlies? Or is there another solution I haven't discovered yet? Any help regarding this would be greatly appreciated. Thanks!
On a side note, I am running the latest ClockWorkMod Recovery as well.

Im surprised that it happened to you on an AOSP recovery. Usually it happens when its a modded recovery with a kernel.
Try TWRP. Or check for an update.
Sent from my GT-I9505 using xda premium

You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2

TheLastSidekick said:
You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app

yanikd said:
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I have same problem and same phone t-online Firmware is up to date but i rooted for first time with no problem but cyanagon wont instal status 7 error. Please help

The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium

DocHoliday77 said:
The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?

yotaxd said:
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?
Click to expand...
Click to collapse
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
If yours is international, do not flash anything you find here!
Sent from my SGH-T999V using xda premium

DocHoliday77 said:
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
If yours is international, do not flash anything you find here!
i do not know if its internatianl oder t-mobile. but it should be t-mobile because starting the phone there is t-mobile logo and it is rent from t-mobile
anyway i installed new recovery 6. via google play but in recovery mode there is still Status 7. even its t-mobile. i can try every version because there is always status 7 so i can not damge phone installing wrong version i think. o the other hand i have always wipe chare/ factory before installing the cyanagenmod. i must restore data now and system setting by advanced backup thats kinda annoying. but next i should maybe try INT. now

If you don't know what model it is, don't flash anything!
Look under the battery.
Sent from my SGH-T999V using xda premium

They are adding the assert for T999VVLDMF2: http://review.cyanogenmod.org/#/c/45740/

[SOLVED!!]
i have this problem too when i want to install some roms like AOKP and JB 4.2.2 , i get same error !!
just go to recovery mode cwm then
go to mount and storage ---> unmount /system
now format /system and /data
try agian install cm rom , and it'l work :good:

HTC One
you guys got any ideas on the att M7 version of this problem. im almost positive i RUUd in order to flash CM but i couldnt get it to work. im on KitKat now cant get it to sideload or install from sd.
got any ideas?

CM thinks my device is sprint?

Somehow my Bell Canada Galaxy S3 i747 fails to install CM10.0 via CWM
I get this error
Code:
updating partition details...
installing /sdcard/roms/cm-10.1.0-d2att.zip
checking for md5 file...
skipping md5check: no md5 file found
assert failed: getprop("ro.product.device") == "
E: error executing updater binary in zip "/sdcard/roms...
error flasing zip "sdcard/roms/cm10.1.0-d2att...
It shows my device as d2spr instead of d2att
How can I make my phone go back to d2att?
Thanks
PS. I'm new to all this but is my device a d2can or d2att?

simon_66 said:
Somehow my Bell Canada Galaxy S3 i747 fails to install CM10.0 via CWM
I get this error
Code:
updating partition details...
installing /sdcard/roms/cm-10.1.0-d2att.zip
checking for md5 file...
skipping md5check: no md5 file found
assert failed: getprop("ro.product.device") == "
E: error executing updater binary in zip "/sdcard/roms...
error flasing zip "sdcard/roms/cm10.1.0-d2att...
It shows my device as d2spr instead of d2att
How can I make my phone go back to d2att?
Thanks
PS. I'm new to all this but is my device a d2can or d2att?
Click to expand...
Click to collapse
I'm interested to know where it shows your device as d2spr.
Regardless if you are a Bell customer [phone bought from bell] than you are a d2can. They are identical to the d2att except for the recoveries installed.
You have a couple options. You can download ROM manager and install cwm through there. It'll prompt you about which phone you have you want d2att.
Or you can flash twrp recovery for the d2att with this zip file.
http://forum.xda-developers.com/attachment.php?attachmentid=1879305&d=1365812877
Flash in recovery, reboot back into recovery and flash to your hearts content.
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
I'm interested to know where it shows your device as d2spr.
Regardless if you are a Bell customer [phone bought from bell] than you are a d2can. They are identical to the d2att except for the recoveries installed.
You have a couple options. You can download ROM manager and install cwm through there. It'll prompt you about which phone you have you want d2att.
Or you can flash twrp recovery for the d2att with this zip file.
http://forum.xda-developers.com/attachment.php?attachmentid=1879305&d=1365812877
Flash in recovery, reboot back into recovery and flash to your hearts content.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
When I install another ROM it accepts it and on installation screen it shows
"Your device: d2spr"

simon_66 said:
When I install another ROM it accepts it and on installation screen it shows
"Your device: d2spr"
Click to expand...
Click to collapse
Interesting.
My post above will remedy your issues.
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
Interesting.
My post above will remedy your issues.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did flash it but when I go to install a d2att rom it fails to install.
Is there any CM10.1 to works on a Bell Galaxy s3 phone?

simon_66 said:
I did flash it but when I go to install a d2att rom it fails to install.
Is there any CM10.1 to works on a Bell Galaxy s3 phone?
Click to expand...
Click to collapse
Either the d2att recovery I recommended didn't take or you need to also update your bootloader.
Sent from my SGH-I747 using xda app-developers app

[Q] Status 7 Error for Every Custom Rom (SGH-I747M)

Hello everyone,
This is my first post here so I hope I'm posting in the right section regarding to the issue I'm having. Be assured, I have searched DAYS for an answer and tried many ways that solve other member's problems but doesn't work for me.
Cannot seem to flash any custom ROM without STATUS 7 error (I have tried 4 different ones, all AOSP based, if that matters).
I receive the status 7 error on both CWM and TWRP, both on the latest versions. Says nothing about the "getprop" or anything like that, just says "Error flashing zip... (Status 7)" or something close to that.
I did notice that before the error it does say something about "set_perm:some changes failed" on the Zips I have tried to edit by taking out the assert lines in the updater script. Otherwise it shows the error after "Creating Symlinks..."
Phone Info:
-Canadian I747M on Rogers Network, but unlocked, running on chatr
-the stock rom I have is TW 4.1.2 OTA update for Rogers, which I had to flash manually through Odin.
-Stock Kernel
-Rooted
What I have already tried:
-wiping cache, factory reset, system, dalvik 3x before trying to install the zip
-have tried both the latest versions of CWM and TWRP, same error. And yes, I have tried both d2att and d2can recoveries for twrp.
-tried a few different roms
-have re-downloaded all of them to make sure download is not corrupt
-have tried to remove the assert lines within the "updater-script" file withing the ZIP, still get status 7
-Downgrading my bootloader from MVLDMF1 to MVLDLK4
-USB debugging is on
I could try and get a picture if anyone needed it of the error in recovery.
Any idea what could be causing this and how to overcome it? Thanks in advance.

GreenMean said:
Hello everyone,
This is my first post here so I hope I'm posting in the right section regarding to the issue I'm having. Be assured, I have searched DAYS for an answer and tried many ways that solve other member's problems but doesn't work for me.
Cannot seem to flash any custom ROM without STATUS 7 error (I have tried 4 different ones, all AOSP based, if that matters).
I receive the status 7 error on both CWM and TWRP, both on the latest versions. Says nothing about the "getprop" or anything like that, just says "Error flashing zip... (Status 7)" or something close to that.
I did notice that before the error it does say something about "set_perm:some changes failed" on the Zips I have tried to edit by taking out the assert lines in the updater script. Otherwise it shows the error after "Creating Symlinks..."
Phone Info:
-Canadian I747M on Rogers Network, but unlocked, running on chatr
-the stock rom I have is TW 4.1.2 OTA update for Rogers, which I had to flash manually through Odin.
-Stock Kernel
-Rooted
What I have already tried:
-wiping cache, factory reset, system, dalvik 3x before trying to install the zip
-have tried both the latest versions of CWM and TWRP, same error. And yes, I have tried both d2att and d2can recoveries for twrp.
-tried a few different roms
-have re-downloaded all of them to make sure download is not corrupt
-have tried to remove the assert lines within the "updater-script" file withing the ZIP, still get status 7
-Downgrading my bootloader from MVLDMF1 to MVLDLK4
-USB debugging is on
I could try and get a picture if anyone needed it of the error in recovery.
Any idea what could be causing this and how to overcome it? Thanks in advance.
Click to expand...
Click to collapse
Last time I helped someone with your issue everything was tried. Turned out he flashed the modem not the bootloader.
In terminal emulator type
su
getprop ro.bootloader
If its the same as the baseband I'm not sure what else to suggest. If it's different than make sure you're on the right bootloader.
Sent from my SGH-I747 using xda app-developers app

The terminal emulator confirmed that I have the I747MVLDLK4 bootloader...
Do you think maybe try a full internal storage wipe/factory reset and root again might do the trick?
Hopefully someone can figure this out... It's so frustrating.

GreenMean said:
The terminal emulator confirmed that I have the I747MVLDLK4 bootloader...
Do you think maybe try a full internal storage wipe/factory reset and root again might do the trick?
Hopefully someone can figure this out... It's so frustrating.
Click to expand...
Click to collapse
Sometimes a complete return to stock can solve many issues. Another guy had this same issue. I'm wondering if it has something to do with Canadian carriers and the boot loader. He removed the bootloader check from the install script for a couple months and that's the only way a non TW ROM would flash.
Sent from my SCH-I535 using xda premium

KorGuy123 said:
Last time I helped someone with your issue everything was tried. Turned out he flashed the modem not the bootloader.
In terminal emulator type
su
getprop ro.bootloader
If its the same as the baseband I'm not sure what else to suggest. If it's different than make sure you're on the right bootloader.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have tried BOOT LOADER UPDATE instructions from http://forum.xda-developers.com/showthread.php?t=2321310
Now, I have my baseband (from settings UI screen) and bootloader version (from terminal getprop ) both as I747UCDLK3 ; Still I get this Status 7 error while installing any CM ROM. Similar issue mentioned by OP (original post)

GreenMean said:
The terminal emulator confirmed that I have the I747MVLDLK4 bootloader...
Do you think maybe try a full internal storage wipe/factory reset and root again might do the trick?
Hopefully someone can figure this out... It's so frustrating.
Click to expand...
Click to collapse
You can always Odin to stock and flash the twrp.tar in odin while you're there. I've seen recoveries flashed with goo and ROM manager not stick.
I'm on Telus and have never had any issues since flashing the d2att recovery.
Wish I could be more help.
Let me know if going stock and re rooting helps.
If you rooted with a tool kit I'd recommend doing it manually.
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------
susram said:
I have tried BOOT LOADER UPDATE instructions from http://forum.xda-developers.com/showthread.php?t=2321310
Now, I have my baseband (from settings UI screen) and bootloader version (from terminal getprop ) both as I747UCDLK3 ; Still I get this Status 7 error while installing any CM ROM. Similar issue mentioned by OP (original post)
Click to expand...
Click to collapse
A) Thread jacking isn't really nice.
B) status 7 isn't just bootloader. You could have an out of date recovery or an incorrect recovery.
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
hednik said:
Sometimes a complete return to stock can solve many issues. Another guy had this same issue. I'm wondering if it has something to do with Canadian carriers and the boot loader. He removed the bootloader check from the install script for a couple months and that's the only way a non TW ROM would flash.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Removing the bootloader check can not only cause issues down the road (downloading the wrong ROM) but is also a bandaid fix.
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
You can always Odin to stock and flash the twrp.tar in odin while you're there. I've seen recoveries flashed with goo and ROM manager not stick.
I'm on Telus and have never had any issues since flashing the d2att recovery.
Wish I could be more help.
Let me know if going stock and re rooting helps.
If you rooted with a tool kit I'd recommend doing it manually.
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------
A) Thread jacking isn't really nice.
B) status 7 isn't just bootloader. You could have an out of date recovery or an incorrect recovery.
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
Removing the bootloader check can not only cause issues down the road (downloading the wrong ROM) but is also a bandaid fix.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I know haha. It was just a temp fix that of course one wouldn't do unless you knew what you were doing. Just wondering why Canadian guys are having this issue.
Sent from my SCH-I535 using xda premium

hednik said:
I know haha. It was just a temp fix that of course one wouldn't do unless you knew what you were doing. Just wondering why Canadian guys are having this issue.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
When most Canadians root their phones it loads d2can recoveries and the at&t Roms aren't "compatible" with our phones.
This usually comes up nightly.
Op's problem is odd though. I'm sure it's going to end up being something simple.
Sent from my SGH-I747 using xda app-developers app

I shall try and do a pre rooted firmware flash through odin and write everything back to stock tomorrow. I will post back and let everyone know how it goes after rooting again and trying to flash CM10.

Change the Recovery

Craptain Krunch said:
Change the Recovery
Click to expand...
Click to collapse
He stated in the op that he had.
Sent from my SGH-I747 using xda app-developers app

I fixed mine
Hey, I had the same issue when I just tried to flash a CM rom. I flashed the bootloader baseband update with no success. as someone has mentioned a few replys prior to this one I tried to change the recovery. I had the latest CWM downloaded from their site. Instead I installed TWRP and it now work I have successfully installed CM 10.1. I used ODIN to flash TWRP. For whatever reason it does not show the status 7 error anymore.

Now recieving new Error!
OK, so I went ahead a did a complete data wipe and flashed a stock ROM through ODIN once again leaving me completely stock except for installing root and custom recovery. What I notice now is that on the latest version of TWRP for d2att & d2can I get an error stating :
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/[ROM Name Here].zip
Updating partition details...
So I searched again and came along someone saying to try to use an older recovery, so I tried TWRP 2.3.3.1 for d2att and got:
set_perm: some changes failed
E:Error in /sdcard/[ROM Name Here].zip
(Status 7)
So the STATUS 7 is being resolved, but there is another error in the updater binary..!!!
I really need some help, hopefully someone can find a solution to this.

GreenMean said:
OK, so I went ahead a did a complete data wipe and flashed a stock ROM through ODIN once again leaving me completely stock except for installing root and custom recovery. What I notice now is that on the latest version of TWRP for d2att & d2can I get an error stating :
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/[ROM Name Here].zip
Updating partition details...
So I searched again and came along someone saying to try to use an older recovery, so I tried TWRP 2.3.3.1 for d2att and got:
set_perm: some changes failed
E:Error in /sdcard/[ROM Name Here].zip
(Status 7)
So the STATUS 7 is being resolved, but there is another error in the updater binary..!!!
I really need some help, hopefully someone can find a solution to this.
Click to expand...
Click to collapse
So @KorGuy123 this is third guy I've seen with this issue that seems to not make sense as to why he can't flash a rom. Status 7 makes sense with an older recovery but they use a newer one and it doesn't work at all. So if you knew you downloaded a ROM that was compatible for your phone, d2can and removed the bootloader check what harm could be done ? We know the bootloader is correct.
So honest question fmr ym own knowledge and his.

hednik said:
So @KorGuy123 this is third guy I've seen with this issue that seems to not make sense as to why he can't flash a rom. Status 7 makes sense with an older recovery but they use a newer one and it doesn't work at all. So if you knew you downloaded a ROM that was compatible for your phone, d2can and removed the bootloader check what harm could be done ? We know the bootloader is correct.
So honest question fmr ym own knowledge and his.
Click to expand...
Click to collapse
If you KNEW what ROM you downloaded and flashed nothing is wrong other than you'd have to do it to every ROM you download.
The problem is this is an open forum and someone who didn't know what they were doing is bound to flash something they shouldn't.
The other day there was a guy that admitted he "downloaded the first file that resembled a ROM" those are the people I / we don't need reading a suggestion like that.
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 04:47 PM ---------- Previous post was at 04:44 PM ----------
GreenMean said:
OK, so I went ahead a did a complete data wipe and flashed a stock ROM through ODIN once again leaving me completely stock except for installing root and custom recovery. What I notice now is that on the latest version of TWRP for d2att & d2can I get an error stating :
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/[ROM Name Here].zip
Updating partition details...
So I searched again and came along someone saying to try to use an older recovery, so I tried TWRP 2.3.3.1 for d2att and got:
set_perm: some changes failed
E:Error in /sdcard/[ROM Name Here].zip
(Status 7)
So the STATUS 7 is being resolved, but there is another error in the updater binary..!!!
I really need some help, hopefully someone can find a solution to this.
Click to expand...
Click to collapse
I wouldn't have gone so old. Latest is 2.6.0.0
2.3.3.1 is probably too old and can give status 7 try 2.5.0.0 or the one older than that 2.4.4.1 I think.
Also check under mount that "system" is unchecked. If it's checked it can prevent proper flashes.
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
If you KNEW what ROM you downloaded and flashed nothing is wrong other than you'd have to do it to every ROM you download.
The problem is this is an open forum and someone who didn't know what they were doing is bound to flash something they shouldn't.
The other day there was a guy that admitted he "downloaded the first file that resembled a ROM" those are the people I / we don't need reading a suggestion like that.
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 04:47 PM ---------- Previous post was at 04:44 PM ----------
I wouldn't have gone so old. Latest is 2.6.0.0
2.3.3.1 is probably too old and can give status 7 try 2.5.0.0 or the one older than that 2.4.4.1 I think.
Also check under mount that "system" is unchecked. If it's checked it can prevent proper flashes.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Good point
http://techerrata.com/browse/twrp2/d2att
Sent from my SAMSUNG-SGH-I747 using xda premium

I was going to chuck my S3 out the window just now.
Followed through with those suggestions also, tried latest 2.6.0.0 recovery and 2.5.0.0 and both still give me the error:
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/[ROM Name Here].zip
Updating partition details...
or something to do with symlinks... and the "system" under mount was not checked.
I am downloading a TouchWiz based ROM right now (Wicked v10) to see if its just AOSP based that are giving me problems.
Now I have to stay on laggy stock TW without everything that I had before because I wiped it.

GreenMean said:
I was going to chuck my S3 out the window just now.
Followed through with those suggestions also, tried latest 2.6.0.0 recovery and 2.5.0.0 and both still give me the error:
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/[ROM Name Here].zip
Updating partition details...
or something to do with symlinks... and the "system" under mount was not checked.
I am downloading a TouchWiz based ROM right now (Wicked v10) to see if its just AOSP based that are giving me problems.
Now I have to stay on laggy stock TW without everything that I had before because I wiped it.
Click to expand...
Click to collapse
Don't get too frustrated. We'll get this figured out. Wonder if @xBeerdroiDx has any ideas?
Sent from my SGH-I747 using xda app-developers app

Anything @xBeerdroiDx ?
Anyone know anything else I could try?

GreenMean said:
Anything @xBeerdroiDx ?
Anyone know anything else I could try?
Click to expand...
Click to collapse
So I've read up some and some people have issues flashing custom rom's on 2.5+. Have you tried to down grade to something like 2.4.1.0 and then wiping cache ? I know it was mentioned but I didn't see if you tried. It's an issue some HTC phones have so I'm not sur eif it applies to your situation.

Error installing pacman rom

I've been trying to flash the 4.3 pacman rom to my galaxy s3 and it refuses to work. I get the assert failed status 7 error. I've tried deleting the assert lines in the update file like a lot of people have recommended but then it just says "Error flashing zip" when I try again. I've also tried using different recoveries (twrp and cwm) still nothing. I've done all the wiping and stuff and any other rom seems to work just having trouble with this one for some reason. I looked around and it seems there were other people with issues just wasn't able to find a solution to it. Any ideas?

Are you on your carriers latest bootloader and modem?

Yup checked that too

dsljk2009 said:
Yup checked that too
Click to expand...
Click to collapse
What carrier are you on? If you're on a Canadian carrier make sure you've flashed a d2att recovery not a d2can
Sent from my SGH-I747 using xda app-developers app

Oh boy do I feel stupid but I figured out the problem. When I was rezipping the fiiles after deleting the assert lines I would rezip the the whole folder the files extracted to instead of just the files so I was creating an extra directory in my zip :silly: