I have done some testing of ROM's and Radios and I am posting my results here. Sorry I am starting a new thread on this but the 4.3 is all over the place with what is said and what is not said.
First Just so it is known where I am testing From.
Samsung Galaxy III Rooted and Running DocHoliday 4.3 no KNOX and no CIQ, rooted. Warranty Bit not tripped.
Installed Official 4.3 ROM from Sam Mobile Warranty Bit Not Tripped
Went to root with Odin root66. Odin failed Warranty Bit tripped and has remain tripped.
So now as for the testing I have done with ROMs and Modems
ROM..................Modem.................Modem Working
MJC...................MJC ....................Yes
MD5...................MD5.....................No
MD5...................MJC.....................Yes
LJC....................LJC......................No
LJC....................MJC.....................Yes
I tried to one click ODIN LJA but would not Odin
So it appears Once you put in the Official 4.3 ROM from Samsung you cannot change the bootloader and the only radio that will work is the MJC. You cannot Odin any ROM besides the official 4.3 once you have already had the Offical 4.3 installed (this may not include future ROMS like the 4.4).
You can flash any ROM from a zip file but you will have to use the MJC modem.
You can Odin recoveries TWRP and CWM or use the TWRP and CWM Respective Managers. I have used both recovery managers and they both work for installing recoveries.
I hope this clears up some things for some people and helps some.
For people who are haveing a hard time with installing and reseting a counter I have a step by step below.
1. In Odin Flash (twrp 2.6.3.0)
2. Use adb to reboot recovery (adb reboot recovery)
3. Flash custom rom (T999_4.3_UVUEMJC_deodexed2.zip)
4. Flash custom Kernel (T999_AT&T_UCUEMJ2_Insecure_kernel.zip)
5. Installed and used 'Triangle Away' to reset Custom Binary Counter to 0 (Optional)
6. Use Odin to flash official MJC ROM (Grabbed from SAMMOBILE.COM)
Phone is back to stock and working, It still has the 'Warranty Bit 1' set though.
toeshot said:
I have done some testing of ROM's and Radios and I am posting my results here. Sorry I am starting a new thread on this but the 4.3 is all over the place with what is said and what is not said.
First Just so it is known where I am testing From.
Samsung Galaxy III Rooted and Running DocHoliday 4.3 no KNOX and no CIQ, rooted. Warranty Bit not tripped.
Installed Official 4.3 ROM from Sam Mobile Warranty Bit Not Tripped
Went to root with Odin root66. Odin failed Warranty Bit tripped and has remain tripped.
So now as for the testing I have done with ROMs and Modems
ROM..................Modem.................Modem Working
MJC...................MJC ....................Yes
MD5...................MD5.....................No
MD5...................MJC.....................Yes
LJC....................LJC......................No
LJC....................MJC.....................Yes
I tried to one click ODIN LJA but would not Odin
So it appears Once you put in the Official 4.3 ROM from Samsung you cannot change the bootloader and the only radio that will work is the MJC. You cannot Odin any ROM besides the official 4.3 once you have already had the Offical 4.3 installed (this may not include future ROMS like the 4.4).
You can flash any ROM from a zip file but you will have to use the MJC modem.
You can Odin recoveries TWRP and CWM or use the TWRP and CWM Respective Managers. I have used both recovery managers and they both work for installing recoveries.
I hope this clears up some things for some people and helps some.
For people who are haveing a hard time with installing and reseting a counter I have a step by step below.
1. In Odin Flash (twrp 2.6.3.0)
2. Use adb to reboot recovery (adb reboot recovery)
3. Flash custom rom (T999_4.3_UVUEMJC_deodexed2.zip)
4. Flash custom Kernel (T999_AT&T_UCUEMJ2_Insecure_kernel.zip)
5. Installed and used 'Triangle Away' to reset Custom Binary Counter to 0 (Optional)
6. Use Odin to flash official MJC ROM (Grabbed from SAMMOBILE.COM)
Phone is back to stock and working, It still has the 'Warranty Bit 1' set though.
Click to expand...
Click to collapse
With the S4 for Tmobile , Ive tried this method, Knox does not allow any kind of write to thhe phone using odin.
It says FAIL every time. Triangle gone also us useless.
WHat samsung has done is placed a set of rules in the bootloader which checks teh phone to see if it fits samsungs rules as a legitimate rom, modem and kernel.
If your phone doesnt have a match for any of these it wont let anything install.
For me, I cant install a 4.3 factory rom. Somehow knox knows Im nolonger factory and now will not let me go BACK to factory. It makes me stay out of warranty so I cant get a refund or any warranty work.
I can install some custom roms but some dont work. It has something to do with the kernels they use. It seems there must be certain requirements knox needs to allow installs and this also is dependent of whether your phone was rooted before or after knox was installed.
nickcaper said:
With the S4 for Tmobile , Ive tried this method, Knox does not allow any kind of write to thhe phone using odin.
It says FAIL every time. Triangle gone also us useless.
WHat samsung has done is placed a set of rules in the bootloader which checks teh phone to see if it fits samsungs rules as a legitimate rom, modem and kernel.
If your phone doesnt have a match for any of these it wont let anything install.
For me, I cant install a 4.3 factory rom. Somehow knox knows Im nolonger factory and now will not let me go BACK to factory. It makes me stay out of warranty so I cant get a refund or any warranty work.
I can install some custom roms but some dont work. It has something to do with the kernels they use. It seems there must be certain requirements knox needs to allow installs and this also is dependent of whether your phone was rooted before or after knox was installed.
Click to expand...
Click to collapse
When you say it fails, is it Odin that says fail or will the phone won't boot? when I odin the official 4.3 ROM it says it fails at the end but the ROM actually installs and runs.
Have you tried booting the ROM after a failed attempt? I would be curious to know if it works or not. Wish I had a S4 to test with
OK folks, in order to keep this thread as tidy as possible, going to link and close this one..
Please go here http://forum.xda-developers.com/showthread.php?t=2561670
galaxy s3 4.3 sgh i747m with Roger's on twrp recovery
Hi I have rooted my phone two days ago and im new to the rooting world of android there is soooo much stuff to learn !!!
I want to know what does it mean when im in odin mode and I see
qualcomm secureboot enable.... and bootloader rp swrev :1 what does it means actually ? I try to find information but it's not clear i dont want to install a custom rom and brick my phone ...
i have so many question ...
if I install a custom rom does my boot loader have to be unlock or i shouldn't care ?
I do i check if my bootloader is unlock ?
Is the carrier is important when you put a custom rom ?
where I can find the gapps file made for my phone ?
1 rom that interest me is wicked sensation rom http://forum.xda-developers.com/showthread.php?t=2286350 it look so sick but once again it says for at&t can I install it if im with rogers because they are the same model ?
it's some little tecnical question that I have can some one help me
Are you on stock Rogers 4.3? If you are, loading a custom recovery will void the warranty by tripping the Knox counter.
If you have no warranty and just want to install a custom ROM, you can install a custom recovery via Odin and flash the ROM you want.
audit13 said:
Are you on stock Rogers 4.3? If you are, loading a custom recovery will void the warranty by tripping the Knox counter.
If you have no warranty and just want to install a custom ROM, you can install a custom recovery via Odin and flash the ROM you want.
Click to expand...
Click to collapse
Yes im on stock 4.3 but my warranty is over so it doesn't really matter I have TWRP recovery so if I want to flash a rom there is no problem ?
I made a nandroid backup in case
carlosQC said:
Yes im on stock 4.3 but my warranty is over so it doesn't really matter I have TWRP recovery so if I want to flash a rom there is no problem ?
I made a nandroid backup in case
Click to expand...
Click to collapse
I prefer Philz Touch which is based on CWM because I had problems flashing with TWRP.
There should be no problem as long as the ROM is supported by TWRP.
carlosQC said:
Yes im on stock 4.3 but my warranty is over so it doesn't really matter I have TWRP recovery so if I want to flash a rom there is no problem ?
I made a nandroid backup in case
Click to expand...
Click to collapse
You shouldn't just go around flashing all the ROMs you think look or sound cool. I would suggest doing your research beforehand. For example, if you want to install the newer KitKat ROMs, you HAVE to be on a JellyBean bootloader. Click HERE for the bootloader guide if you need it.
Also, your TWRP should always be up to date. The link for the latest (may be outdated, idk...)TWRP is HERE
Lastly, if you ever run into any problems and want to go back to stock, or you just want to start fresh and start from scratch, then use this. This has never failed on me. Click HERE
Remember, YMMV.
Best of luck!
I don't think you need a 4.3 bootloader for all ROMs. I have loaded Cyanfox, CM11, and Vidalus which are all 4.4.2 ROMs without issue. I personally prefer to stay away from the 4.3 bootloader because I want the ability to return my phone to stock for warranty purposes.
The OP is running 4.3 stock and the link you provided could brick his phone.
audit13 said:
I don't think you need a 4.3 bootloader for all ROMs. I have loaded Cyanfox, CM11, and Vidalus which are all 4.4.2 ROMs without issue. I personally prefer to stay away from the 4.3 bootloader because I want the ability to return my phone to stock for warranty purposes.
The OP is running 4.3 stock and the link you provided could brick his phone.
Click to expand...
Click to collapse
I never said that the OP needed to update his bootloader, I was just mentioning as an example if he wanted to then he would probably need to if he wanted to flash a KitKat ROM.
But you are right, for him, I would stay away from 4.3 since you can't downgrade.
hey guys,
i recently rooted my galaxy s3 i747 and installed cm11 on it. the whole process was done automatically using one of those cm installers. however, i recently learned that cm11 is not stable yet. so i want to downgrade to 10.2 which is the most recent stable cm.
i did try that, using manual methods, such as flashing it via recovery, however a picture of a dead android with a red warning triangle popped up saying it couldn't be done.
my question is, why would this happen? i know official android doesn't allow downgrade, but rooted ones should allow installation of any custom rom no matter which verison, right?
another question, how do i downgrade to 10.2, or install any other stable custom rom? i am afraid that the phone might become bricked due to my inexperience, but i want stability in my phone.
also, if my phone is indeed hard bricked, would it be possible to get it fixed under $100?
P.S. i am quite new to xda, so sorry if i posted this in the wrong area.
Are you using the most up to date custom recovery for your phone? Are you wiping system, Dalvik, and cache before installting the new ROM?
audit13 said:
Are you using the most up to date custom recovery for your phone? Are you wiping system, Dalvik, and cache before installting the new ROM?
Click to expand...
Click to collapse
used goo manager to install recovery, and wiped system, dalvik cache and cache. you see, i was following a video tutorial, and the custom recovery on that one was an older version. so, although i wiped them all, it was a bit different. you think that might be the problem?
user9560 said:
used goo manager to install recovery, and wiped system, dalvik cache and cache. you see, i was following a video tutorial, and the custom recovery on that one was an older version. so, although i wiped them all, it was a bit different. you think that might be the problem?
Click to expand...
Click to collapse
I would start over by flashing the tar version of Philz Touch via Odin 3.07 from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att.
Copy CM10.2 to your phone or external SD card, boot into recovery, wipe cache, Dalvik, data, and system. Then install CM10.2, boot into the OS, set things up, boot into recovery, and flash Gapps.
I prefer doing everything via recovery mode.
thanks! aah i'm a little scared though. do you think if i follow the instructions correctly, there'll be little chance of a hard brick? i know nothing's full proof tho.... what do you think? is it worth it? is 10.2 better than cm11 nightly as of yet?
You're using an AT&T s3 i747? What ROM was on the phone before you installed a custom ROM?
If it was any stock 4.3, don't touch the bootloader.
audit13 said:
You're using an AT&T s3 i747? What ROM was on the phone before you installed a custom ROM?
If it was any stock 4.3, don't touch the bootloader.
Click to expand...
Click to collapse
yup s3 i747 with bell. i think its the same as att. the phone came with 4.2 then i updated to 4.3 jelly bean.
also, isn't odin like a software on the computer? could you perhaps point to a tutorial? sorry ^_^' i'm not so familiar with android and there r so many tutorials out there, i wouldnt know which one i should follow in this case.
user9560 said:
yup s3 i747 with bell. i think its the same as att. the phone came with 4.2 then i updated to 4.3 jelly bean.
also, isn't odin like a software on the computer? could you perhaps point to a tutorial? sorry ^_^' i'm not so familiar with android and there r so many tutorials out there, i wouldnt know which one i should follow in this case.
Click to expand...
Click to collapse
The model # for the Bell s3 is i747m. The AT&T version is an i747. Make note of the difference when posting and looking solutions.
Do you have any warranty left on your phone? If you do, installing the 4.3 update will install the 4.3 bootloader and Knox. Once you have upgraded to the 4.3 bootloader, any attempts to downgrade the bootloader will brick the phone. Any reason you updated to 4.3?
Since you have Knox on your phone, installing a custom recovery will trip the knox counter and void your warranty. If you have no warranty left, tripping the counter isn't a problem.
audit13 said:
The model # for the Bell s3 is i747m. The AT&T version is an i747. Make note of the difference when posting and looking solutions.
Do you have any warranty left on your phone? If you do, installing the 4.3 update will install the 4.3 bootloader and Knox. Once you have upgraded to the 4.3 bootloader, any attempts to downgrade the bootloader will brick the phone. Any reason you updated to 4.3?
Since you have Knox on your phone, installing a custom recovery will trip the knox counter and void your warranty. If you have no warranty left, tripping the counter isn't a problem.
Click to expand...
Click to collapse
hmm when i look at my about phone it just says SMASUNG-SGH-I747... so i'm not sure where i747m comes in... i assume there's no warranty for my phone anymore since it's been rooted already. i just updated to 4.3 because i assumed that a reputable company like samsung would give out a good and better performance update. after i updated however, the phone started going haywire. it became laggy and slow. not that noticable, but still bothered me. the main reason i ditched iphone was because of it's sluggy behavior. so i had nothing to do but root. cm11's great, but some features are unstable, like random reboots and stuff. so i wanted to try cm10.2 or miui v5. hmm. i'm still thinking about how to figure out odin..
user9560 said:
hmm when i look at my about phone it just says SMASUNG-SGH-I747... so i'm not sure where i747m comes in... i assume there's no warranty for my phone anymore since it's been rooted already. i just updated to 4.3 because i assumed that a reputable company like samsung would give out a good and better performance update. after i updated however, the phone started going haywire. it became laggy and slow. not that noticable, but still bothered me. the main reason i ditched iphone was because of it's sluggy behavior. so i had nothing to do but root. cm11's great, but some features are unstable, like random reboots and stuff. so i wanted to try cm10.2 or miui v5. hmm. i'm still thinking about how to figure out odin..
Click to expand...
Click to collapse
The Bell, Rogers, and Telus version of the s3 is sgh-i747m. The AT&T version is sgh-i747. Did you get the phone from one of the Canadian carriers?
If you're running a custom ROM, this may be the reason it just shows sgh-i747. Custom ROMs on XDA are designed for the d2att but are compatible with the Canadian version of the s3.
Updating to 4.3 would have loaded a 4.3 bootloader and Knox. Once your phone has the 4.3 bootloader, do not attempt to downgrade the bootloader as it will brick your phone.
Knox software can interfere when trying to root your device.
You updated to 4.3, then installed CM?
audit13 said:
The Bell, Rogers, and Telus version of the s3 is sgh-i747m. The AT&T version is sgh-i747. Did you get the phone from one of the Canadian carriers?
If you're running a custom ROM, this may be the reason it just shows sgh-i747. Custom ROMs on XDA are designed for the d2att but are compatible with the Canadian version of the s3.
Updating to 4.3 would have loaded a 4.3 bootloader and Knox. Once your phone has the 4.3 bootloader, do not attempt to downgrade the bootloader as it will brick your phone.
Knox software can interfere when trying to root your device.
You updated to 4.3, then installed CM?
Click to expand...
Click to collapse
ah i understand now. i got the phone from bell. thanks for clarifying that.
i installed cm after the update, unfortunately. but when i went into recovery mode, i did not see anything related to knox. does it show up on the phone or in recovery mode? as of this moment, i was not thinking about the bootloader. because we're just tyring to downgrade the os, right? or is it something like previous os would not run on an updated bootloader?
user9560 said:
ah i understand now. i got the phone from bell. thanks for clarifying that.
i installed cm after the update, unfortunately. but when i went into recovery mode, i did not see anything related to knox. does it show up on the phone or in recovery mode? as of this moment, i was not thinking about the bootloader. because we're just tyring to downgrade the os, right? or is it something like previous os would not run on an updated bootloader?
Click to expand...
Click to collapse
Go into download mode and look at the screen. What does it say? It will probably have the model #, warranty bit, and whether it is running custom or official software.
Are you running TWRP or CWM?
audit13 said:
Go into download mode and look at the screen. What does it say? It will probably have the model #, warranty bit, and whether it is running custom or official software.
Are you running TWRP or CWM?
Click to expand...
Click to collapse
ok sir, this is what it says:
-ODIN MODE
-PRODUCT NAME: SGH-I747M
-CUSTOM BINARY DOWNLOAD: Yes (2 counts)
-CURRENT BINARY: Custom
-SYSTEM STATUS: Official
-QUALCOMM SECUREBOOT: ENABLE
-Warranty Bit: 1
-BOOTLOADER RP SWERV: 1
This screen tells you that your phone is an i747m, you have knox installed, any warranty on your phone has been voided, and you're loaded 2 custom ROMs.
Since you have a custom recovery, you can wipe data, cache, Dalvik, and install cm10.2.
audit13 said:
This screen tells you that your phone is an i747m, you have knox installed, any warranty on your phone has been voided, and you're loaded 2 custom ROMs.
Since you have a custom recovery, you can wipe data, cache, Dalvik, and install cm10.2.
Click to expand...
Click to collapse
ok now that you mentioned cwm and twrp, i noticed my phone resembles cwm when i boot into recovery. the tutorial i followed was in what looked like twrp. but why would that happen? i followed his instructdions and updated the recovery the same way he did via goo manager. he is using twrp, i am using cwm. is that the problem?
user9560 said:
ok now that you mentioned cwm and twrp, i noticed my phone resembles cwm when i boot into recovery. the tutorial i followed was in what looked like twrp. but why would that happen? i followed his instructdions and updated the recovery the same way he did via goo manager. he is using twrp, i am using cwm. is that the problem?
Click to expand...
Click to collapse
As long as you have a custom recovery, you can try flashing cm10.2.
audit13 said:
As long as you have a custom recovery, you can try flashing cm10.2.
Click to expand...
Click to collapse
i did try it before. booted into recovery, tried to flash rom zip and gapps. but it failed to flash. are you suggesting i do it in DOWNLOAD MODE with the new tar file you have mentioned? would you be able to link me to a place which would give me instructions? i am quite new to this. thanks
user9560 said:
i did try it before. booted into recovery, tried to flash rom zip and gapps. but it failed to flash. are you suggesting i do it in DOWNLOAD MODE with the new tar file you have mentioned? would you be able to link me to a place which would give me instructions? i am quite new to this. thanks
Click to expand...
Click to collapse
What error are you getting when you try to flash a ROM?
audit13 said:
What error are you getting when you try to flash a ROM?
Click to expand...
Click to collapse
it gives me a dead android with a red warning triangle. the one that says rom cannot be flashed.
user9560 said:
it gives me a dead android with a red warning triangle. the one that says rom cannot be flashed.
Click to expand...
Click to collapse
Are there any RPM error messages? What custom recovery do you have on your phone? It should say at the very top.
Could someone please direct me to the latest AT&T stock image with root access? I flashed another one last night, and I'm not happy with the results. I can't flash CWM and SuperUser doesn't work, I will flash the latest AT&T stock with Odin. Thanks.
GAPY427 said:
Could someone please direct me to the latest AT&T stock image with root access? I flashed another one last night, and I'm not happy with the results. I can't flash CWM and SuperUser doesn't work, I will flash the latest AT&T stock with Odin. Thanks.
Click to expand...
Click to collapse
Not sure if this helps but, http://forum.xda-developers.com/showthread.php?t=2540998&page=1
If you have the 4.3 bootloader on your phone, you cannot use Odin to flash a stock AT&T phone as it may brick it.
What bootloader is on your phone? How did you try to flash CWM?
audit13 said:
If you have the 4.3 bootloader on your phone, you cannot use Odin to flash a stock AT&T phone as it may brick it.
What bootloader is on your phone? How did you try to flash CWM?
Click to expand...
Click to collapse
I'm not sure. When I'm in Download Mode, this is what I have:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL: Fused 2 > Binary 8
When I plug my phone to my PC, it doesn't recognize it. I can get into recovery (CWM) though. I flashed CWM with Odin.
You have the 4.3 bootloader; therefore, you cannot use Odin to flash a stock image because AT&T did not release a full 4.3 stock ROM. The 4.3 ROM was made available as an OTA update.
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
You have the 4.3 bootloader; therefore, you cannot use Odin to flash a stock image because AT&T did not release a full 4.3 stock ROM. The 4.3 ROM was made available as an OTA update.
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
I tried that but the installation aborted in CWM. When I plug my phone in to my PC it doesn't recognize it. I have to take out my SD card to load files into the phone, which obviously isn't working. In CWM, when I "choose zip from internal SD card" I see this:
- 0/
- legacy/
- obb/
When I select '0', I see all the menu choices. Did I eff up or lose my internal storage? I can't load files onto it. Can flash files to my internal via command prompt window?
Can you get into download mode? If you can, use Odin load the latest tar version of Philz Touch from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att