Related
When I flash the latest nightly it says installation aborted.
assert failed :get prop(''ro.product.device'')......
Help?
What version of cwm are you running ? Try to update it and redownload the rom
Sent from my SGH-I747M using xda app-developers app
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
offwiththeface said:
What version of cwm are you running ? Try to update it and redownload the rom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
I just re downloaded and installed. Same issue.
lol
outkast22 said:
I just re downloaded and installed. Same issue.
Click to expand...
Click to collapse
lol..you didn't answer his question. =P He asked you what version of Clockworkmod Recovery you are using when you try to flash the CM10 rom. For instance, CWM 6.0.1.2, is a version of cwm. Just for your information you cannot flash a new rom with an outdated CWM recovery or else you get the "get.prop" error. Try this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.2-d2att.img
This is a .img(image) file and cannot be flashed in odin or cwm. I'd suggest you type cwm 6.0.1.2 into the XDA forum search to find the file or you can follow these instructions: download the Galaxy S3 toolkit from Android development section and then select #1 for AT&T, and then #9 to convert .img file to a tar file. To convert the file you have to put the .img into the INPUT file inside the toolkit. To access the toolkit go to my computer and then click the hard rive and then search for the Galaxy S3 Toolkit and click on it, you will find INPUT in there.
After it converts the file you can rename it and then transfer it to you desired location for easy access.
Open up the Odin 3.07 program and then click PDA, make sure you chose PDA, and then navigate to the converted CWM 6.0.1.2 file and select it.
If you aren't in Download mode go to it now, Volume down + Power + the home button, and the top box should light up and say COMblahblah where the blahblah is a random number. and then press start and when it's finished you can try to flash the ROM again. Be sure to create a nandroid.
My guess is at least when it comes to this particular build prop error is that you may have an i747M and cm10 won't flash on that (its looking for i747) unless you update your recovery as mentioned above. That or use mobile Odin to flash the cm10 zip file.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
My fault. I read that in a rush, trying to get it fixed before flying out the door for work. Thanks I will try that! And Im on v 5.5.0.4. just flashed the touch version and it is still on v5.5.0.5.How do I flash a newer version?
This is cwm 6.0.1.4 http://db.tt/te3vInsu you can flash it from your recovery than reboot and flash cm10
When I try to go into recovery phone boots up. Is my recovery gone?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks
tonymtl said:
This is cwm 6.0.1.4 http://db.tt/te3vInsu you can flash it from your recovery than reboot and flash cm10
Click to expand...
Click to collapse
finally got the Mod 10 to work using this CWM. was pulling my hair out
it doesnt have play store? how do i add my google account to sync my contacts and download apps? sorry noob
Your going to have to install the gaaps rom after you install the cm10 one. Do a search for where to get the gaaps file.
how do I add more themes? like the blood red theme. I only have one option.
Download them here http://forum.xda-developers.com/showthread.php?t=1801752
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
I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!
OK, so I have been rooted almost a year, and have flashed several roms. I am currently on 4.1 of I believe Hybrid's rom. I believe I have had a 4.3 at one time but my last flash, whenever I started trying to flash a 4.4 version I started running into problems along the way. Is there anything special I need to do to upgrade to 4.4? Like besides flashing the rom, is there anything else I need to flash? Anyone have any recommendations?
Thanks!
Brandon.
wwe9112 said:
OK, so I have been rooted almost a year, and have flashed several roms. I am currently on 4.1 of I believe Hybrid's rom. I believe I have had a 4.3 at one time but my last flash, whenever I started trying to flash a 4.4 version I started running into problems along the way. Is there anything special I need to do to upgrade to 4.4? Like besides flashing the rom, is there anything else I need to flash? Anyone have any recommendations?
Thanks!
Brandon.
Click to expand...
Click to collapse
I have the same question here.... I just rooted my phone on 4.3 jelly bean stock but if one day a stock 4.4 is comming out do I need to unroot my phone to make the update ?
carlosQC said:
I have the same question here.... I just rooted my phone on 4.3 jelly bean stock but if one day a stock 4.4 is comming out do I need to unroot my phone to make the update ?
Click to expand...
Click to collapse
No one still has answered lol. I tried to flash a few different 4.3's and they kept failing. I'm using TWRP or whatever it's called 2.6.0.0 not sure what that's about. I had to flash an older rom I had on my computer to get it to allow my phone to work.
I prefer using CWM or Philz Touch which is based on CWM rather than TWRP. I tried TWRP with a few ROMs but they always failed to install. Once I switched to CWM, they installed without issue.You can flash the tar version of Philz using Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
To run 4.4.2 ROMs, you should update to the latest 4.1.2 bootloader, load a custom recovery, boot into recovery, wipe cache, Dalvik, data, system, and flash the new ROM.
audit13 said:
I prefer using CWM or Philz Touch which is based on CWM rather than TWRP. I tried TWRP with a few ROMs but they always failed to install. Once I switched to CWM, they installed without issue.You can flash the tar version of Philz using Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
To run 4.4.2 ROMs, you should update to the latest 4.1.2 bootloader, load a custom recovery, boot into recovery, wipe cache, Dalvik, data, system, and flash the new ROM.
Click to expand...
Click to collapse
I already updated my bootloader to the one that said "you cannot downgrade from this one or you will brick your device" I think that's the latest one I'm not sure lol.
By "Boot into recovery" are you meaning boot to the recovery screen? Sorry, I like to make sure of what I am doing so I don't brick anything lol. Although in a month I'm buying the Note 3 .
How do I go about switching back to CWM? Sorry to ask and sound dumb -- which I am not I have an associates of science in computer programming but just reciently switched to Mechatronic Engineering due to higher job growth in my area. I digress.
I could probably find dozens of articles on here how to go about it, but its generally quicker if someone just posts the link to the correct one to use for my device, every time I go searching these forms, I end up on every-which phone other than mine -- I do apologize.
You need the newest version of cwm to flash anything 4.4.
If you're rooted use goomanager from play store it will install cwm or look in the stickies there are files and instructions.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
audit13 said:
I prefer using CWM or Philz Touch which is based on CWM rather than TWRP. I tried TWRP with a few ROMs but they always failed to install. Once I switched to CWM, they installed without issue.You can flash the tar version of Philz using Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
To run 4.4.2 ROMs, you should update to the latest 4.1.2 bootloader, load a custom recovery, boot into recovery, wipe cache, Dalvik, data, system, and flash the new ROM.
Click to expand...
Click to collapse
If I have already TWRP installed can I install CWM over it ?
theramsey3 said:
You need the newest version of cwm to flash anything 4.4.
If you're rooted use goomanager from play store it will install cwm or look in the stickies there are files and instructions.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thats how I got TWRP I believe x). And ok thanks, I'll look around.
wwe9112 said:
Thats how I got TWRP I believe x). And ok thanks, I'll look around.
Click to expand...
Click to collapse
Sorry I confused the cwm and twrp install process. Goo manager will download the newest twrp which is 2.6.3.1 I don't know if it will flash 4.4 roms or not... And yes you can flash cwm directly over twrp. You will want to use rom manager from play store to flash cwm. Sorry for the confusion...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Sorry I confused the cwm and twrp install process. Goo manager will download the newest twrp which is 2.6.3.1 I don't know if it will flash 4.4 roms or not... And yes you can flash cwm directly over twrp. You will want to use rom manager from play store to flash cwm. Sorry for the confusion...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
IT WORKED! Thanks so much. I am using Liquid Kit-Kat lol. Thanks again!
theramsey3 said:
Sorry I confused the cwm and twrp install process. Goo manager will download the newest twrp which is 2.6.3.1 I don't know if it will flash 4.4 roms or not... And yes you can flash cwm directly over twrp. You will want to use rom manager from play store to flash cwm. Sorry for the confusion...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It does work. I have flashed every 4.4 rom there is with that version of TWRP. Which is way better than cwm for me. :silly:
theramsey3 said:
Sorry I confused the cwm and twrp install process. Goo manager will download the newest twrp which is 2.6.3.1 I don't know if it will flash 4.4 roms or not... And yes you can flash cwm directly over twrp. You will want to use rom manager from play store to flash cwm. Sorry for the confusion...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have checked in the rom manager app it will install a version for galaxy s3 (metroPCS) d2mtr .... Is it going to work ??
carlosQC said:
I have checked in the rom manager app it will install a version for galaxy s3 (metroPCS) d2mtr .... Is it going to work ??
Click to expand...
Click to collapse
I just downloaded rom manager today and it installed cwm for I747 D2ATT. Perhaps you need a newer version of rom manager?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
I just downloaded rom manager today and it installed cwm for I747 D2ATT. Perhaps you need a newer version of rom manager?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Rom manager by clockworkmod ?? Why the **** it says "sorry we do not have a version for i747m " I dont understand why haha
carlosQC said:
Rom manager by clockworkmod ?? Why the **** it says "sorry we do not have a version for i747m " I dont understand why haha
Click to expand...
Click to collapse
I can not verify anything about the I747M, I have the AT&T I747. However I have heard it is safe for you guys to use the I747 D2ATT version of cwm. I am trying out the philz touch cwm that audit13 keeps suggesting, it is highly modifiable. Thus far I am happy.
Can anyone on the I747M verify it is safe to flash the D2ATT recovery? I do know for a fact you guys can use any of our roms.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
I can not verify anything about the I747M, I have the AT&T I747. However I have heard it is safe for you guys to use the I747 D2ATT version of cwm. I am trying out the philz touch cwm that audit13 keeps suggesting, it is highly modifiable. Thus far I am happy.
Can anyone on the I747M verify it is safe to flash the D2ATT recovery? I do know for a fact you guys can use any of our roms.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
yeahh maybe it will find it for your phone but not for mine .....
carlosQC said:
yeahh maybe it will find it for your phone but not for mine .....
Click to expand...
Click to collapse
Go to the general section and read the stickies here is a quote from the recovery thread I have heavily clipped it you need to read the whole thing in its original form. From what I read it is safe for your phone to use the D2ATT recovery image, I however take no responsibility for any thing that happens successful or not if you you flash it you wear it...
dstruct2k said:
So you've got your device rooted, and you want to install a custom recovery? Great! Don't just follow any guide you stumble across though, as some of the early recovery packages for the "AT&T" model were actually just copies of the custom Sprint recovery, and then you'll have all sorts of fun trying to install ROMs. ("Status 7" errors anyone? )
While this may seem difficult, it's really not. Grab a recovery image (these files end in ".img") such as ClockWork Mod (CWM) or Team Win Recovery Project (TWRP) for your device. Most ROM developers say to use CWM, but they both work equally well.
In our case, we need an image for the Samsung Galaxy S3 AT&T. Telus, Rogers, Bell, and SaskTel phones are (almost*) the exact same phone as AT&T, if you have one of these devices, you will be installing the AT&T recovery.
*NOTE: While we're on the topic, let's take a second to talk about what makes the Canadian I747M different from the AT&T I747.
The short version is... The modem. AT&T is using completely different and incompatible modem firmware in their phones when compared with the Canadian models. Rogers, Bell, Telus, and any other Canadian I747M are the same device (Samsung worked some strange voodoo and got all the Canadian carriers to agree on the same hardware!) which means that if Rogers releases a new modem firmware update, a SaskTel user could install it without issue. AT&T modem updates will not work on Canadian models, nor will Canadian updates work on AT&T phones! I've tried it. Trust me. You don't want to deal with the hassle of fixing it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Go to the general section and read the stickies here is a quote from the recovery thread I have heavily clipped it you need to read the whole thing in its original form. From what I read it is safe for your phone...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
ok good thank you for your help !!!
carlosQC said:
ok good thank you for your help !!!
Click to expand...
Click to collapse
I edited the above post please reread it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
I edited the above post please reread it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
So in on word I can't really do anything with my rooted phone ?? When you flash a rom does it change anything to the modem file ?
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.
BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app
DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app
No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.
BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/