Related
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 bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Is it supposed to use T999 firmware?
Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium
re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.
tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!
How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done
Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app
You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium
Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app
No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium
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?/:
After ota 4.3 on stock att I747 Itried cf autroot and installed trp successfully. Somehow wiped the os off and now stuck n Samsung screen. I can get into download mode and recovery please help
You can load a custom recovery in Odin and flash a custom ROM.
Brandon136 said:
After ota 4.3 on stock att I747 Itried cf autroot and installed trp successfully. Somehow wiped the os off and now stuck n Samsung screen. I can get into download mode and recovery please help
Click to expand...
Click to collapse
Annoying, but not that hard to fix. You have two or three choices. If you made a backup, you can restore that from recovery mode.
You could go to download mode and flash a stock ROM onto the phone, then root it again.
Or you can go with a custom ROM as the poster above suggested. You generally need a custom recovery for that, so you'd go to download mode and install a custom recovery first. Followed by the custom ROM. If the custom ROM is a tar file, you'd also flash that with Odin in download mode. If it is a flashable zip file then the custom ROM would be flashed after you boot to the custom recovery mode first.
If flashing a stock image, ensure that it is a version 4.3 AT&T image. Trying to flash an earlier version will do bad things to your phone.
.
fffft said:
Annoying, but not that hard to fix. You have two choices.. you can go to download mode and flash a stock ROM onto the phone, then root it again.
Or you can go to download mode and install a custom recovery, followed by a custom ROM as the poster above suggested. If the custom ROM is a tar file, you'd also flash that with Odin in download mode. If it is a flashable zip file then the custom ROM would be flashed after you boot to the custom recovery mode first.
If flashing a stock image, ensure that it is a version 4.3 AT&T image. Trying to flash an earlier version will do bad things to your phone.
.
Click to expand...
Click to collapse
As far as I know, there is no stock 4.3 AT&T image available because one was never released by AT&T. However, I think there may be some 4.3 based ROMs that can be flashed.
Mobile Odin can also be used to flash an image since mobile Odin does not flash a bootloader or modem.
audit13 said:
As far as I know, there is no stock 4.3 AT&T image available because one was never released by AT&T. However, I think there may be some 4.3 based ROMs that can be flashed.
Mobile Odin can also be used to flash an image since mobile Odin does not flash a bootloader or modem.
Click to expand...
Click to collapse
It can be painful to be an AT&T customer at times. If a full factory 4.3 ROM wasn't released, the OP could still flash a properly formatted backup of someone's stock AT&T 4.3. But it would of course be easier to adopt a custom ROM as you suggested. One choice would be S3Rx 3.0.
.
Thanks for the help. However I tried to flash several 4.3 stock based roms and got nothing. I had an older s3 with a busted screen so I took the mother board out and put in this. I then flashed twrp and rooted. Im on the ota 4.3 and would really like a custom rom. Im currently on the hunt.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
Thanks for the help. However I tried to flash several 4.3 stock based roms and got nothing. I had an older s3 with a busted screen so I took the mother board out and put in this. I then flashed twrp and rooted. Im on the ota 4.3 and would really like a custom rom. Im currently on the hunt.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You didn't give us nearly enough details to really know what you tried, let alone why it might have failed. AT&T is much more restrictive than most carriers and is locking their bootloader, so you have to be careful not to flash someone else's bootloader or a pre 4.3 version.
But since you have a rooted phone again.. installing a custom ROM wouldn't be hard to do.. I gave you a link to decent custom ROM that would work for you. Or you can browse other custom ROMs if you prefer. There are detailed instructions in the thread to guide you. Basically confirm that you have one of the listed AT&T bootloaders and modems, download the custom ROM to your phone, boot to twrp, do a "factory wipe", then install the custom ROM (flashable zip file) from the twrp install menu.
.
Try Philz Touch recovery instead of TWRP. If it doesn't work with Philz, let us know the error messages you're getting.
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You can't find custom rooms cause you're blind or can't read. Backup out of the Q&A forum to the s3 page with all the forum listing then click on the forum that says AT&T galaxy s3 development. If you can't find one there you need to stop trying...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have had better luck flashing ROMs with CWM than TWRP.
There are lots of ROMs here: http://forum.xda-developers.com/galaxy-s3-att/development
Couldmyou point me in the direction to switch over. I have read alot on that same issue
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Download Philz Touch zip from here and flash in TWRP. Reboot into recovery and you should have CWM installed.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Sammobile.com has the stock images don"t they? Thats where i got my Fido factory image.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I know thats right. This is my first so needless to say its all new. I looked for just custom roms and not delelopment. Sorry, thanks for the help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
I know thats right. This is my first so needless to say its all new. I looked for just custom roms and not delelopment. Sorry, thanks for the help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Any luck?
Yes I have cwm and titanium back pro, busy box pro, and a few other goodies. So I made me a backup and flashed 4.4.2. I'm playing with it now. It seems really solid and way better customizations. I'm about to head over and give the developers thanks. Thank you as well for your advice.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I am trying to install the W03 Slim ROM V7 on my Tmobile Galaxy Note 3 through Philz recovery and I am getting stuck in a boot loop.
These are the steps I tried
1. Used Chainfire's root method to root Kitkat 4.4.2 (which was updated through kies). Used the N9005 and not N900T like the instructions asked me to
2. Flashed Philz Recovery through Odin
3. Copied the ROM and Gapps to my Phone.
4. Rebooted into recovery
5. Wiped Data/Factory reset, Install from Zip, wipe cache, wipe dalvik and reboot.
This is where I get stuck. The phone boots with these words on the top left, "Recovery not enforcing seandroid" or something along those lines and keeps booting. I booted back to Recovery and 'Re'wiped' the phone/did a factory reset, but nogo
So I downloaded the right stock firmware from Sammobile, installed through Odin and repeated the steps and still the same issue.
What am I doing wrong? I made sure I am flashing hltetmo (for TMo Note 3).
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
nikhilnagaraj24 said:
I am trying to install the W03 Slim ROM V7 on my Tmobile Galaxy Note 3 through Philz recovery and I am getting stuck in a boot loop.
These are the steps I tried
1. Used Chainfire's root method to root Kitkat 4.4.2 (which was updated through kies). Used the N9005 and not N900T like the instructions asked me to
2. Flashed Philz Recovery through Odin
3. Copied the ROM and Gapps to my Phone.
4. Rebooted into recovery
5. Wiped Data/Factory reset, Install from Zip, wipe cache, wipe dalvik and reboot.
This is where I get stuck. The phone boots with these words on the top left, "Recovery not enforcing seandroid" or something along those lines and keeps booting. I booted back to Recovery and 'Re'wiped' the phone/did a factory reset, but nogo
So I downloaded the right stock firmware from Sammobile, installed through Odin and repeated the steps and still the same issue.
What am I doing wrong? I made sure I am flashing hltetmo (for TMo Note 3).
Click to expand...
Click to collapse
Sounds like a Recovery issue to me. Please look one more time and make sure if you used PHILZ TOUCH that you did in fact flash 6.19.3 HLTE. and not HLTETMO. Im also using philz and no problems flashing. However before it was known that this was the version to use, I did loop at the same point when experimenting with other versoins. Also, check your MD5 and verify that it is a good download.... maybe re download just for gits and shiggles.
---------- Post added at 02:10 AM ---------- Previous post was at 02:07 AM ----------
willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think the new slimKat is 4.4?
willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Had the same bootloop issue when I just tried it out. I updated my bootloader when I updated to stock KK through odin. I am assuming by 4.3 you mean the bootloader on SlimRom is the 4.3 bootloader even though it is a 4.4.2 rom?
willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep.... you are correct sir. 4.3 bootloader. No el flashy 4.3 roms if you updated to 4.4 Bootloader.... im running Echoe rom. Maybe give that a try. Its an international.
Found this on page 78
Sent from my SM-N900T using XDA Premium 4 mobile app
willham said:
Found this on page 78
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks everyone. It does look like it is the bootloader issue.
How do we determine if a particular ROM supports a particular bootloader version? At least the ROMs I have sort of explored and wanted to try, dont mention that anywhere. Or maybe they use some geek term to reference that but I dont understand it. How do noobs like me determine the bootloader version and compatibility of a particular ROM (before flashing and finding out the hard way)???
nikhilnagaraj24 said:
Thanks everyone. It does look like it is the bootloader issue.
How do we determine if a particular ROM supports a particular bootloader version? At least the ROMs I have sort of explored and wanted to try, dont mention that anywhere. Or maybe they use some geek term to reference that but I dont understand it. How do noobs like me determine the bootloader version and compatibility of a particular ROM (before flashing and finding out the hard way)???
Click to expand...
Click to collapse
Not really an answer to your question but I did flash pac-rom without issue. So there is one safe one.
Sent from my SM-N900T using Tapatalk
I think w03 slim rom v4 works with 4.4 bootloader
Enviado desde mi SM-N900T mediante Tapatalk