Related
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!
This is my 2nd s3 and for some reason im having a lot of problems installing any rom om this one.
I rooted using this method [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel].
I installed twrp v2.3.3.0 through goomanager.
When I try to intall any rom I get this error.
checking for md5 file....
skipping md5 check: no md5 file found
assert failed: getprop("ro.product. device") == "
(status 7 )
So Im not sure what Im doing wrong. I have tried to search but vant seem to find exact what my issue is. Any help would be appreciated.
ottawadad34 said:
This is my 2nd s3 and for some reason im having a lot of problems installing any rom om this one.
I rooted using this method [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel].
I installed twrp v2.3.3.0 through goomanager.
When I try to intall any rom I get this error.
checking for md5 file....
skipping md5 check: no md5 file found
assert failed: getprop("ro.product. device") == "
(status 7 )
So Im not sure what Im doing wrong. I have tried to search but vant seem to find exact what my issue is. Any help would be appreciated.
Click to expand...
Click to collapse
Im pretty new to all this but Ive already read a lot of people having problems with that version of TWRP. I used 2.2.2.1 (i believe) on my other devices. i don;t know that this will fix your specific problem, but I think it's worth a shot.
Strange also cause even when i try to re install twrp through goomanager I get an invalid md5 sum
Try goo manager again. They have 2.3.3.1 out now. That might fix your issue.
Sent from my SGH-I747 using xda premium
Its still only showing 2.3.3.0
Sent from my SGH-I747M using Tapatalk 2
I noticed that goomanager is downloading d2can.img and not d2att.img. how can I get the right one?
Sent from my SGH-I747M using Tapatalk 2
Google for TWRP and download the image from there. You will have to manually install it with dd from terminal.
Sent from my SGH-I747 using xda premium
ottawadad34 said:
I noticed that goomanager is downloading d2can.img and not d2att.img. how can I get the right one?
Click to expand...
Click to collapse
If your device is SGH-I747M (a Canadian model), then GooManager is right when it downloads the d2can recovery image. This is the right one.
Now, if you try to flash a ROM but get stuck at an error 7 because your phone model isn't "d2att": you can change your device's model name in the build.prop file. This can be done manually, or you can use some other specialized build.prop editors. For example, I just did it right now in my SGS3 using Rom ToolBox Lite; under the "Performance" tab is listed a build.prop editor.
The keys you have to change are ro.build.product and ro.product.device -- change the value d2can to d2att, and reboot your device.
Thanks. I manually installed the d2att one and now I can flash any roms
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
disengage said:
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
Click to expand...
Click to collapse
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy cm10.1
http://d-h.st/8qP cwm
http://d-h.st/qft cwm touch
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
sending onalond
KorGuy123 said:
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
disengage said:
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
Click to expand...
Click to collapse
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay thanks, I will try later and reply with results.
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Also should I flash with ODIN?
disengage said:
Also should I flash with ODIN?
Click to expand...
Click to collapse
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hi there, I tried flashing from recovery, choosing zip from sdcard, and I got the same exact error assert failed: getprop(" ro.product.device") == "d2att" || getprop( " ro.build.product " ) == "d2att" E:Error in /sdcard/CWM-recovery_ATT-6.0.2.3_2.zip
(status 7)
Installation aborted.
I tried exactly what you said, still nothing.
Bump.
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think so. i have no idea how to check, forgive the noobness plz. My stock firmware is 4.1.1
Bump? Does anyone know how I can flash an updated recovery?
disengage said:
Bump? Does anyone know how I can flash an updated recovery?
Click to expand...
Click to collapse
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but I cannot flash the updated CWM. What am I doing wrong?
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
So my question stands: I flashed an outdated recovery by accident, and I want to flash a new, UPDATED recovery. KorGuy provided me with instructions and a link to a new, updated recovery, however I cannot flash that from my current recovery.
What can I do to flash an updated CWM?
Can someone give me a hand?
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
disengage said:
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
Can someone give me a hand?
Click to expand...
Click to collapse
If you can't follow a guide like this and figure things out, maybe flashing ROMs just isn't for you. I'm not trying to offend, but this isn't for everyone.
danieljordanmaddux said:
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I understand that I need to flash with ODIN. However, don't I need a .TAR recovery? I can't flash .img through ODIN...
Correct. Find the .tar of the recovery. I think you can find the TWRP .tar on their website
Sent from my SGH-T999 using Tapatalk 2
Root your phone and install a custom recovery. Most root guides will include instructions for flashing a custom recovery. Next buy "ROM toolbox" form android market, I say by because you will love this app so much you will want to buy it eventually anyway.
Open ROM toolbox and select cyanogen mod. ROM toolbox will flash your phone for you! It can also flash the custom recovery if you did not do this when you rooted your phone.
Annnother must have root app is titanium backup.
Hope this helps.
Sent from my Nexus 4 using xda app-developers app
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.
im trying to get cm11 on my phone and im coming from 4.2.2. flashed both rom and gapps and its still a no go...?...thanks in advance.
Please boot to recovery and do a factory Reset. If that too didn't help, please wipe data partition.
Are you trying to dirty flash CM11 over CM10.1? or over TW 4.2.2?
I did all that...i wiped EVERYTHING...I keep getting some type of error whenever I try to fkash a 4.4 rom...and I also noticed my phone keeps turning off but if I dont sign into google it wont just turn off...VERY WEIRD and annoying...i did all the wipes...flashed the right files everything...just cant figure this out for the life of me...i even used both cwm and twrp and both were tbe newest versions...
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
What bootloader? You might need to update it before moving on.
Maybe i just explained it wrong...i mean i can't get 4.4 to even flash...keep getting some type of build.prop error file not being found then there is a couple other Rom that won't even boot (meaning 4.3) also...I've noticed that my phone will just turn off on its own when starting random apps and if i don't sign into my gmail account then it won't turn off as fast or often. I have tried all different downloads with both newest cwm and trwp...and some of the Rom errors say (bad) and also even tried downloading from other sites and multiple times...I'll try to flash another 4.4 Rom and tell you the exect error i get...ill be back in a couple mins...thanks in advance...
Sent from my SAMSUNG-SGH-I997 using xda app-qdevelopers app
pcrack05 said:
Maybe i just explained it wrong...i mean i can't get 4.4 to even flash...keep getting some type of build.prop error file not being found then there is a couple other Rom that won't even boot (meaning 4.3) also...I've noticed that my phone will just turn off on its own when starting random apps and if i don't sign into my gmail account then it won't turn off as fast or often. I have tried all different downloads with both newest cwm and trwp...and some of the Rom errors say (bad) and also even tried downloading from other sites and multiple times...I'll try to flash another 4.4 Rom and tell you the exect error i get...ill be back in a couple mins...thanks in advance...
Sent from my SAMSUNG-SGH-I997 using xda app-qdevelopers app
Click to expand...
Click to collapse
It sounds to me like your either using a rom that wasnt made for your device.. Running a T999l on a T999v rom or a T999 for example..
that or you need to upgrade your firmware/modem/bootloader.. Not all roms will work on the same bootloader..
If you flashed the wrong bootloader you will HARD BRICK your phone..
and once you flash the new bootloader you CAN NOT flash back to the old..
Please be VERY specific..
What is,
Your Phone Model:?
Your Cellular provider:?
Your Bootloader:?
Your Modem:?
Your recovery:?
If you skipped any steps while installing a Rom, it will either not work, Soft or Hard BRICK your device, or cause insatiability..
Zaphodspeaks said:
It sounds to me like your either using a rom that wasnt made for your device.. Running a T999l on a T999v rom or a T999 for example..
that or you need to upgrade your firmware/modem/bootloader.. Not all roms will work on the same bootloader..
If you flashed the wrong bootloader you will HARD BRICK your phone..
and once you flash the new bootloader you CAN NOT flash back to the old..
Please be VERY specific..
What is,
Your Phone Model:?
Your Cellular provider:?
Your Bootloader:?
Your Modem:?
Your recovery:?
If you skipped any steps while installing a Rom, it will either not work, Soft or Hard BRICK your device, or cause insatiability..
Click to expand...
Click to collapse
+1 to all that. Without that information, it is very difficult to tell what the issue is and what the resolution could be.
What I'd like to add is that, if there are Assert Errors while flashing, then you are flashing Rom not meant for your phone. It won't boot even if you flash fine.
Now if you had Code 7 Errors with Kitkat Roms then you need to update your recovery.
Whenever I try to flash a 4.4 rom I get this error message... failed: getprop (ro.bootloader) what's that mean... and when I try to wipe the dalvic cache it says... E:unknown volume for path [C/sd-ext] ... but then says after that... dalvic cache wiped.... ?...I don't get it, PLEASE HELP... thanks in advance... "
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
I have had some code 7 errorsand I didn't mean my phone want boot up like what you guys are saying I ment it will get stuck on the samsung logo and that on most. Not all 4.3 roms...I also tried the newest trwp and cwm...to no advail. But I do I see what bootloader I have. Maybe I'm just thinking of the wrong definition for the word bootloader. Thanks guys I feel like I'm getting close oh and if this helps ill post the errors in getting.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app