Related
Just got my gs3 today and decided to root using this method http://forum.xda-developers.com/showthread.php?t=1746682
Not really so tech-savy with this yet and after the whole root process of odin3 i reboot into recovery, wipe/cache/dalvik then flash the new miui 2.10.19 http://miuiandroid.com/community/threads/2-10-19.18540/ one i hit flash it says installation failed blah blah blah (status 7) getprop. Yeah all that junk, so i searched up on the forums and the only solution i find is to update cwm and i have, to 6.0.1.4 and still same thing!! installation error, aborted. Can someone please help me out :crying: I'm sorry if im a noob, just trying to flash a rom here
Update CWM via ROM Manager.
Download again
Sent from my SGH-T999 using xda app-developers app
use twrp
theexel said:
Update CWM via ROM Manager.
Click to expand...
Click to collapse
i did, still no luck
mt3g said:
use twrp
Click to expand...
Click to collapse
and this was my last thing i tried before bed last night and still didnt work! should i just unroot then re-root all over again?
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Aerowinder said:
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Click to expand...
Click to collapse
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
How could cwm not be working if its updated to latest version? I dont think im downloading the wrong rom and its not a bad link. Even tried dragging it onto my internal sd wirh debugging off. Btw I have the 32 gb s3 with does not have an external sd.
The way I fix that was I rerootes my phone into latest clockwork recovery. I didn't remove the root I just rerootee it. Look for cwr 6 I think.
Sent from my SGH-T999 using xda app-developers app
From watching the video given for the toolkit, when in odin and have to open up pda then go to the toolkit files and then root all my files are in winRAR type and his are in tar archive type. Does that matter at all? And also when clicking on the pda then root you chose the file /boot-insecure-tmo-t99uvalem-cwm but when in odin and clicking this file on the little winrar icon to the left of the file name its the only one with a little like key lock, doesnt know if thats an issue or anything just something i noticed because when accessing the toolkit files on my c drive and going to the root folder, the key icon is no longer there.. Any ideas??
Reading about people flashing a kernal in recovery then flashing the rom and working but when you flash a rom isnt it flashing the kernal it comes with also? Or is this the problem
Well, I re ran the toolkit, re did the root and odin process same as i did the first time, downloaded rom straight from my phone flashed again still getting status 7 error/ installation aborted -______- ugh...
Brad4891 said:
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
Click to expand...
Click to collapse
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
I can't believe I didn't see this before....what is the exact file name of the rom you are flashing?
I looked and did not see our phone listed in the op. Looks like the international one is there (codename m0?). But no d2tmo, d2att, etc.
Unless I just missed it there, you do not want to even try flashing that anymore! If I'm right you just got very lucky dude!
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Brad4891 said:
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Click to expand...
Click to collapse
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
DocHoliday77 said:
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I was at first but then changed my mind, both werent working before hand though when i was getting the errors.
And im using hellfire and the rom is super smooth like butter. I have one problem though, its notifications. Whenever receiving texts i dont get a vibration or light pulse. Sometimes randomly i get a vibration. Anyone know how to fix?
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
Hey guys, right now im running CM 10 stable build, but when i flashed CM 10 i flashed the d2att, which worked fine for me. SO i decided to dirty flash CM 10.1 d2att since i flashed the att build last time, then i figured, maybe i got lucky last time, so i dirty flashed d2tmo and it still didnt work!
I dont wanna have to wipe everything and do a clean install all over again! SOMEONE PLEASE HELP!!!!!
Im with wind, so thats why the d2tmo made more sense, in case your wondering
Just to be sure, you do have the T999V model, correct?
If so, your answer is here:
http://forum.xda-developers.com/showthread.php?p=41701398
Sent from my SGH-T999L using xda premium
CM10 is 4.1.2 and CM10.1 is 4.2.2. You cannot dirty flash different Android versions, you have to wipe and start over, after backing up everything first of course.
Alright thanks!
Just a quick question before i flash, do i need to be on stock TW, cuz as i said im on CM10
And all i do is flash this, reboot and then flash CM 10.1 and gapps? right?
Nandroid backup first if you haven't. You will need to factory reset after flashing cm I'm pretty sure. Backup your internal sdcard too, just in case.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Nandroid backup first if you haven't. You will need to factory reset after flashing cm I'm pretty sure. Backup your internal sdcard too, just in case.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
You don't need to wipe data from CM 10 -> 10.1.
PSA: Upgrading from CM10 to CM10.1
As you may have noticed, we started updating some devices from cm10 (Android 4.1) to 10.1 (Android 4.2) during the weekend. The upgrade process has been tested extensively for the older devices (manta and mako didn't have that problem since they started out with 10.1), so you should be able to update directly without losing any data.
The single application known not to work is the Clock: Our changes to 4.1's clock to add the Stopwatch and Timer in CM10 aren't compatible with Google's own implementation of those features in 4.2 (which we're using in cm10.1); If your clock starts crashing after upgrading to 10.1, simply go into the Settings -> Apps menu, choose Clock from the All tab, and hit "Clear data".
Click to expand...
Click to collapse
Can somebody please tell me if it is safe to flash this http://forum.xda-developers.com/showthread.php?p=41701398 on CM10 or should i be on TW!?!? Pleaseeee, i wanna use CM 10.1 and this looks like it would help, im just afraid of bricking my phone
Jaz-Crahh said:
Can somebody please tell me if it is safe to flash this http://forum.xda-developers.com/showthread.php?p=41701398 on CM10 or should i be on TW!?!? Pleaseeee, i wanna use CM 10.1 and this looks like it would help, im just afraid of bricking my phone
Click to expand...
Click to collapse
Thats why I linked you to it. Just be sure you have a T999V and not a T999 model S3. Provided you do, it is safe to flash. many have already done so.
You can flash it while on TW or CM.
The assert is already there to include that bootloader in the latest CM10.1 Nightlies. I would suggest to flash CM10.1 & Gapps, then wipe cache & dalvik, then check your Baseband under Settings and About Phone, it may already be VLDLL1, because flashing a ROM shouldn't change those files (modem, etc.).
DJ_SpaRky said:
The assert is already there to include that bootloader in the latest CM10.1 Nightlies. I would suggest to flash CM10.1 & Gapps, then wipe cache & dalvik, then check your Baseband under Settings and About Phone, it may already be VLDLL1, because flashing a ROM shouldn't change those files (modem, etc.).
Click to expand...
Click to collapse
Cm won't flash, which is most likely because the phone isn't on LL1. Even if it is, its not going to hurt it to flash that firmware package.
If you want to be sure first though, what is your current baseband? Its under settings, about device.
Sent from my SGH-T999L using xda premium
yea, it is LL1 (T999VVLDLL1)
Did you ever flash just the modem?
Or have you ever updated via ota or by odin flashing the firmware?
Sent from my SGH-T999L using xda premium
The error msg i get is " E : Error in /sdcard/CM10/cm-10. 1. 0-RC5-d2att. zip (status 7) Installation aborted "
Same goes for when i flash d2tmo
I think ive heard of that status 7 error somewhere, could that be the reason?
ALSO, i can easily flash carbon rom 4.2.1
I just prefer CM and i like not losing my data, so yea, the fact that i can flash Carbon but not CM 10.1 shows that theres no problem with my version of CWM
Update your CWM if you are not using the latest version. Whether or not Carbon flashed is not relevant.
Also, don't flash AT&T ROMs. Just because you can doesn't mean you should. Flash T-Mobile ROMs. With d2tmo CWM. Link to the Odin .tar is in my signature. You flash the proper CWM, and CM will stop hassling you. When you attempt to flash CWM, it checks your bootloader version and recovery version. If either don't match what it's looking for - installation aborted.
Jaz-Crahh said:
ALSO, i can easily flash carbon rom 4.2.1
I just prefer CM and i like not losing my data, so yea, the fact that i can flash Carbon but not CM 10.1 shows that theres no problem with my version of CWM
Click to expand...
Click to collapse
First, I never said there was a problem with CWM, though if you aren't using the latest, I'd suggest updating it.
Second, you never answered my questions in my last post.
Third, I don't know how old Carbon 4.2.1 is but they are now on 4.2.2. When cm went to 4.2.2 is when they started checking your firmware, so just because you can flash that doesn't mean you can flash something newer.
So if you please, do the following and tell me what it says.
Open Terminal Emulator
Enter the following line:
getprop ro.bootloader
Let me know what it says please.
Also, everytime I've ever seen a Status 7 error, its been caused by the firmware not being up to date. So at this point I still believe flashing that firmware pkg I linked earlier will be your fix.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
First, I never said there was a problem with CWM, though if you aren't using the latest, I'd suggest updating it.
Second, you never answered my questions in my last post.
Third, I don't know how old Carbon 4.2.1 is but they are now on 4.2.2. When cm went to 4.2.2 is when they started checking your firmware, so just because you can flash that doesn't mean you can flash something newer.
So if you please, do the following and tell me what it says.
Open Terminal Emulator
Enter the following line:
getprop ro.bootloader
Let me know what it says please.
Also, everytime I've ever seen a Status 7 error, its been caused by the firmware not being up to date. So at this point I still believe flashing that firmware pkg I linked earlier will be your fix.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
When i did the terminal thing, i got
"T999VVLALE6"
Ok, that's the problem then. Its scropted to not flash unless that reads VLDLL1. hou can either flash the firmware pkg I linked to, or odin flash the correct firmware. After that you should be able to flash cm.
The pkg I linked to would be the easiest to use.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Ok, that's the problem then. Its scropted to not flash unless that reads VLDLL1. hou can either flash the firmware pkg I linked to, or odin flash the correct firmware. After that you should be able to flash cm.
The pkg I linked to would be the easiest to use.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Okay, will do, ill flash that pkg and get back to you when i attempt to flash CM 10.1 again
Jaz-Crahh said:
Okay, will do, ill flash that pkg and get back to you when i attempt to flash CM 10.1 again
Click to expand...
Click to collapse
Now this is gonna be awkward, but theres a couple of links there, which one exactly should i click?/:
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.
As much as I know, there are still setbacks with kernal installations...
The phone I bought from the store is a Samsung Galaxy s4 (SGH-M919. But low and behold, I unknowingly flashed a ROM for this phone which replaced my SGH-M919 kernal with a i9505 Kernal. Does this have any significance at all? Should I only flash zips that are built for i9505 kernal, or stick with flashing SGH-M919 kernal zips?
(I am INDEED a "flashaholic", and I don't know what to do, now that my kernal has changed (IE: I don't want to brick my phone)
Help? Advice?
androidiphonehacker said:
As much as I know, there are still setbacks with kernal installations...
The phone I bought from the store is a Samsung Galaxy s4 (SGH-M919. But low and behold, I unknowingly flashed a ROM for this phone which replaced my SGH-M919 kernal with a i9505 Kernal. Does this have any significance at all? Should I only flash zips that are built for i9505 kernal, or stick with flashing SGH-M919 kernal zips?
(I am INDEED a "flashaholic", and I don't know what to do, now that my kernal has changed (IE: I don't want to brick my phone)
Help? Advice?
Click to expand...
Click to collapse
If you are using T-Mobile then you have to flash a compatible kernel which you would normally do right after flashing the ROM.
Sent from my SGH-M919 using xda app-developers app
lalec said:
If you are using T-Mobile then you have to flash a compatible kernel which you would normally do right after flashing the ROM.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Not exactly.. i9505 kernels will boot and work just fine.
Only real setback is maybe some csc files mismatch and your build.prop will show you have a i9505.
As long as you don't flash any i9500 ROMs, you're okay.
in reply..
Exel said:
Not exactly.. i9505 kernels will boot and work just fine.
Only real setback is maybe some csc files mismatch and your build.prop will show you have a i9505.
As long as you don't flash any i9500 ROMs, you're okay.
Click to expand...
Click to collapse
BTW, I installed a cracked cwm Touch.zip, and it works great on i9505 kernal, except the main purpose of cwm is taken away (Installing zips)
Every time I attempt to flash zips on cwm touch, the terminal process always ends in "installation aborted". Should I revert back to the casual clockworkmod, or is there something I can do to fix the installation aborted error on cwm touch?
androidiphonehacker said:
BTW, I installed a cracked cwm Touch.zip, and it works great on i9505 kernal, except the main purpose of cwm is taken away (Installing zips)
Every time I attempt to flash zips on cwm touch, the terminal process always ends in "installation aborted". Should I revert back to the casual clockworkmod, or is there something I can do to fix the installation aborted error on cwm touch?
Click to expand...
Click to collapse
A cracked, what?
Also, what error do you get after the installation aborted? build.prop mismatch?
but...
Exel said:
A cracked, what?
Also, what error do you get after the installation aborted? build.prop mismatch?
Click to expand...
Click to collapse
Cracked, (pirated, I guess) version of it. I thought cwm touch was only available to donators o.o Guess I was wrong. Any who..
That's all I get as the error. "Installation aborted." And know that this is when using cwm. Not in terminal, if that's what you were thinking. cwm doesn't really inform you too much about the errors when aborting an installation, unless you take a look at the logs. (Where the logs are, I'm unsure of)
[GUIDE][ROMS]RUN OTHER CARRIER ROMs on AT&T/TMO/Canadian/Verizon S4 devices. Here's how!
thanks!
norml said:
[GUIDE][ROMS]RUN OTHER CARRIER ROMs on AT&T/TMO/Canadian/Verizon S4 devices. Here's how!
Click to expand...
Click to collapse
Thanks! I LOVE twrp! Omg, the interface and setup of it is so sexy (even though it's a recovery mode img) xD
Yes though, as for anyone who wants clockworkmod touch, go with TWRP! LIKE, NOW.
androidiphonehacker said:
Thanks! I LOVE twrp! Omg, the interface and setup of it is so sexy (even though it's a recovery mode img) xD
Yes though, as for anyone who wants clockworkmod touch, go with TWRP! LIKE, NOW.
Click to expand...
Click to collapse
Glad you like TWRP but there are CWM version that work just fine including the Philz CWM touch. You just need to be careful where you get your files from.
☞Sent from here☜
Exel said:
Not exactly.. i9505 kernels will boot and work just fine.
Only real setback is maybe some csc files mismatch and your build.prop will show you have a i9505.
As long as you don't flash any i9500 ROMs, you're okay.
Click to expand...
Click to collapse
+1