Hello,
I have been flashing some different roms lately, and I really wanted to stay on a 4.3 rom because 4.4 roms are having bluetooth issues, and I cannot connect it with my car.
When I flash a 4.3 rom like Slimbean or CM 10.2. I always get random reboots. It will happen if its just sitting there, or if I am doing something.
I've done a full reset, format, and flash, and I even let it just sit with nothing installed after the flash, but it still reboots randomly. I read a thread about the kernel being a problems. Can anyone shed some light on this?
Thank you,
- |-Goku-|
I have no issues with CM 10.2 and I am running the kernel that comes with it. What bootloader are you on?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
aybarrap1 said:
I have no issues with CM 10.2 and I am running the kernel that comes with it. What bootloader are you on?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I am on CWM Touch, latest version.
What about you?
|-Goku-| said:
I am on CWM Touch, latest version.
What about you?
Click to expand...
Click to collapse
CWM is the recovery. Which bootloader is on your phone?
audit13 said:
CWM is the recovery. Which bootloader is on your phone?
Click to expand...
Click to collapse
Gah, my bad. I've done some searches, and can't figure out how to check the bootloader. Can you point me to a thread?
audit13 said:
CWM is the recovery. Which bootloader is on your phone?
Click to expand...
Click to collapse
I did find something in the download mode that says Bootloader AP SWRev: 2
Got it, says I'm on I747UCUEMJB.
|-Goku-| said:
Got it, says I'm on I747UCUEMJB.
Click to expand...
Click to collapse
Okay, you're running a 4.3 bootloader which means you cannot downgrade the bootloader. Attempting to do so could brick your phone.
I recommend that you install the latest CWM and flash a ROM based on TW 4.3. I believe Slimbean is based on a CM.
audit13 said:
Okay, you're running a 4.3 bootloader which means you cannot downgrade the bootloader. Attempting to do so could brick your phone.
I recommend that you install the latest CWM and flash a ROM based on TW 4.3. I believe Slimbean is based on a CM.
Click to expand...
Click to collapse
Sounds good. Do you have any recommendations for a TW 4.3 rom? And would you have any guess as to why it would be randomly rebooting?
There are a few TW-based ROMs in the development section. I would start there.
http://forum.xda-developers.com/galaxy-s3-att/development
Related
So I need some advice on which ROM to flash back on my phone. I am new to custom ROMs and managed to hard brick my phone. I am going to try a Jig to see if I can get into download mode, however, if I do that I am not sure what ROM to flash back onto my phone. It's a galaxy S3 i747. When this all started I was running JB 4.1.1 on it. Then I flashed CM10 and that went great. After I flashed CM10 my phone said that I was on JB 4.3. Did CM update JB and the bootloader? I know that trying to flash an older bootloader can cause troubles. Afater I had CM running I tried to flash LeanKernel and this is when I bricked my phone. So my questions is, do I need to flash the ROM for JB4.1.1 or for JB 4.3? Any advice would be greatly appreciated.
loveforvdubs said:
So I need some advice on which ROM to flash back on my phone. I am new to custom ROMs and managed to hard brick my phone. I am going to try a Jig to see if I can get into download mode, however, if I do that I am not sure what ROM to flash back onto my phone. It's a galaxy S3 i747. When this all started I was running JB 4.1.1 on it. Then I flashed CM10 and that went great. After I flashed CM10 my phone said that I was on JB 4.3. Did CM update JB and the bootloader? I know that trying to flash an older bootloader can cause troubles. Afater I had CM running I tried to flash LeanKernel and this is when I bricked my phone. So my questions is, do I need to flash the ROM for JB4.1.1 or for JB 4.3? Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Look buddy, the first thing you want to do is flash the latest STOCK rom for you're model. After you've done that you can now backup you're stock rom via recovery (TWRP recommended), after that you now have a stable rom to return to just in case you fail to flash a custom rom. And I would recommend one of the stock mod roms to get the use of all of Samsung's exclusive features. Good luck, and feel free to ask any more questions.
Ali7000 said:
Look buddy, the first thing you want to do is flash the latest STOCK rom for you're model. After you've done that you can now backup you're stock rom via recovery (TWRP recommended), after that you now have a stable rom to return to just in case you fail to flash a custom rom. And I would recommend one of the stock mod roms to get the use of all of Samsung's exclusive features. Good luck, and feel free to ask any more questions.
Click to expand...
Click to collapse
Hey thanks. I really appreciate the help. I got in a little over my head so I'm just trying to get ahead of the learning curve as quick as possible. Now I've searched around for the stock 4.3 flash able ROM and am having trouble finding a clear cut download for it. Do you have a recommendation of where I can find the JB 4.3 stock to flash with ODIN?
loveforvdubs said:
Hey thanks. I really appreciate the help. I got in a little over my head so I'm just trying to get ahead of the learning curve as quick as possible. Now I've searched around for the stock 4.3 flash able ROM and am having trouble finding a clear cut download for it. Do you have a recommendation of where I can find the JB 4.3 stock to flash with ODIN?
Click to expand...
Click to collapse
There isn't an odin flashable 4.3 rom for i747. The last thing there is is 4.1.1 then the 4.3 you would take as an ota. I highly doubt cm updated your bootloader. Floating around the forums is an sd unbrick method. You could try that. I don't have experience with it, but quite a few people have. Good luck.
pre4speed said:
There isn't an odin flashable 4.3 rom for i747. The last thing there is is 4.1.1 then the 4.3 you would take as an ota. I highly doubt cm updated your bootloader. Floating around the forums is an sd unbrick method. You could try that. I don't have experience with it, but quite a few people have. Good luck.
Click to expand...
Click to collapse
Maybe this would work : http://forum.xda-developers.com/showthread.php?t=2498233 Do some research on it first then let me know. And if you want a good and stable custom rom I recommend using http://forum.xda-developers.com/showthread.php?t=2504903. Just don't choose the note 3 option, choose the stock.
Ali7000 said:
Maybe this would work : http://forum.xda-developers.com/showthread.php?t=2498233 Do some research on it first then let me know. And if you want a good and stable custom rom I recommend using http://forum.xda-developers.com/showthread.php?t=2504903. Just don't choose the note 3 option, choose the stock.
Click to expand...
Click to collapse
Thanks. That's helpful.
http://http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
This is the rom I used to root it a year ago when I got the phone. Would this be a suitable choice to un-brick my phone?
loveforvdubs said:
Thanks. That's helpful.
http://http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
This is the rom I used to root it a year ago when I got the phone. Would this be a suitable choice to un-brick my phone?
Click to expand...
Click to collapse
That is only a method used to root you're phone, not to unbrick it.
Ali7000 said:
That is only a method used to root you're phone, not to unbrick it.
Click to expand...
Click to collapse
But to root I flashed a ROM with Odin. The ROM is linked on that page. At least that is my understanding of how rooting works. Wouldn't that've a good ROM to use to un-brick?
Have you ever updated your phone to 4.3?
Sent from my SGH-I747M using XDA Premium 4 mobile app
Ali7000 said:
Have you ever updated your phone to 4.3?
Sent from my SGH-I747M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not entirely sure. Never updated to 4.3 on a stock ROM. It was on JB 4.1 before I flashed CM10. However once I flashed CM10 the settings page said my phone was on JB 4.3. So not sure if the bootloader got updated or not.
Thanks so much everyone for the help. I really appreciate it. Unfortunately the Jig did not work, so it is all a moot point in the end. Looks like the phone is going off to get JTAGed.
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.
So I updated to stock 4.3(I747M) via Odin, then flashed TWRP with Odin, then Flashed a 4.4 ROM with TWRP.
The Super SU app is failing to update the binary. And it's not giving root access to apps. Does this have anything to do with the MK5 bootloader?
I can't seem to find a fix? If someone could point me in the right direction, that'd be great.
Thanks!
Try flashing a another ROM such a Validus or CM11 as ROMs are pre-rooted.
Also, I prefer Philz Touch over TWRP. Maybe the recovery program makes a difference?
solaris11 said:
So I updated to stock 4.3(I747M) via Odin, then flashed TWRP with Odin, then Flashed a 4.4 ROM with TWRP.
The Super SU app is failing to update the binary. And it's not giving root access to apps. Does this have anything to do with the MK5 bootloader?
I can't seem to find a fix? If someone could point me in the right direction, that'd be great.
Thanks!
Click to expand...
Click to collapse
I did this procedure with the same bootloader on a Koodo phone, no problem. I I rooted and installed TWRP 2.6.3.1 and then I flashed Quantum ROM. Which ROM did you flash? (Oh, I see now you tried OmniRom.) Only difference with how I did it is I had already taken the stock OTA from Koodo.
jmppe3 said:
I did this procedure with the same bootloader on a Koodo phone, no problem. I I rooted and installed TWRP 2.6.3.1 and then I flashed Quantum ROM. Which ROM did you flash? (Oh, I see now you tried OmniRom.) Only difference with how I did it is I had already taken the stock OTA from Koodo.
Click to expand...
Click to collapse
Yeah I bricked my phone messing with bootloaders...used an SD boot image to get to download mode and odined stock 4.3. Odined twrp. Twrp flashed omni's latest build. Does omni not come prerooted? That doesn't make much sense. I'll try another ROM.
It should also be noted I tried rooting stock 4.3 but it really didn't like that at all.
Sent from my SGH-I747 using xda app-developers app
audit13 said:
Try flashing a another ROM such a Validus or CM11 as ROMs are pre-rooted.
Also, I prefer Philz Touch over TWRP. Maybe the recovery program makes a difference?
Click to expand...
Click to collapse
On validus now...same thing
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Weird that you don't have root. I have Validus and apps like root explorer ask for root access which I can grant.
Maybe the 4.3 bootloader is causing a problem?
audit13 said:
Weird that you don't have root. I have Validus and apps like root explorer ask for root access which I can grant.
Maybe the 4.3 bootloader is causing a problem?
Click to expand...
Click to collapse
Yeah, this whole thing is weird. I had the 4.3 bootloader (rooted at end of Dec 2013) and didn't have an issue. I went to Quantum ROM FWIW. Have you tried a full wipe (system, cache, dalvik, data) with a clean flash of the ROM?
so i have a rooted at&T galaxy s3 on the latest stock firmware which i guess is 4.3. i tried flashing resurrection rom which was kit kat and it failed. so i restored my back up and the phone would get stuck on the splash screen. so i formated the whole phone and forgot to save my backup to my sdcard. twrp now says that i have no OS installed and also says i am not rooted anymore. im scared and need a little assistance. i just want to get it going.
Just flash the latest TWRP, copy a custom ROM to your phone, boot into TWRP, and flash it.
audit13 said:
Just flash the latest TWRP, copy a custom ROM to your phone, boot into TWRP, and flash it.
Click to expand...
Click to collapse
i bought a micro sc card reader and transfered a superuser zip and an old 4.3 beanstalk rom. it flashed fine last night. i used my phone all day and downloaded the latest 4.3 beanstalk rom and just tried to flash it and it FAILED. This is the second time i had a flash fail. I tried flashing that old beanstalk rom again and it failed too! what the heck???? my battery is a little low.....does twrp have some kind of safety built in where it wont flash if bettery is low?
ok...so i flashed cwm because im more familiar it than twrp. then i flashed an old slimbean 4.3 rom i had. everything worked fine and the phone booted up perfectly. i dont want slim bean so i rebooted into cwm and tried to flash the newest 4.3 beanstalk rom and it failed.....why?
scorey03 said:
ok...so i flashed cwm because im more familiar it than twrp. then i flashed an old slimbean 4.3 rom i had. everything worked fine and the phone booted up perfectly. i dont want slim bean so i rebooted into cwm and tried to flash the newest 4.3 beanstalk rom and it failed.....why?
Click to expand...
Click to collapse
Did you install the latest CWM? Is the 4.3 Beanstalk based on Kit Kat?
audit13 said:
Did you install the latest CWM? Is the 4.3 Beanstalk based on Kit Kat?
Click to expand...
Click to collapse
no its not based on kitkat. i flashed an older version of cwm via odin. i figured i could just update it with rom manager. i tried to update cwm to the latest verion and it fails everytime. so...i downloaded root checker from the play store and it says im not rooted. i need to fix this lol
im running a custom rom but yet root checker says its not rooted...hmm
Flash the latest Philz and. Validus as I know that is a rooted ROM. Personally, I don't use ROM manager.
scorey03 said:
im running a custom rom but yet root checker says its not rooted...hmm
Click to expand...
Click to collapse
What custom Rom is this?
Sent from my HTC One using Tapatalk
I'm on slimbean 4.3 and I've lost root. I want root back so I can get rid of this ROM. Ive flashed supersu multiple times with cwm..but I still do not have root access.
So I guess my question now is.....how do I get back to stock rooted? Im on slimbean 4.3 without root access.
scorey03 said:
I'm on slimbean 4.3 and I've lost root. I want root back so I can get rid of this ROM. Ive flashed supersu multiple times with cwm..but I still do not have root access.
Click to expand...
Click to collapse
Rooting is not needed to flash another ROM. Just boot into recovery, wipe, and flash another ROM.
audit13 said:
Rooting is not needed to flash another ROM. Just boot into recovery, wipe, and flash another ROM.
Click to expand...
Click to collapse
I tried and it failed......
scorey03 said:
I tried and it failed......
Click to expand...
Click to collapse
What rom and which recovery did you try?
I suggest you Odin to stock and try all this again
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
I suggest you Odin to stock and try all this again
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I agree 100%. Can you tell me where I can get stock 4.3 firmware?
Here is a repository with a lot of stock firmwares http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my ATT Samsung Galaxy SIII using TapaTalk
scorey03 said:
I agree 100%. Can you tell me where I can get stock 4.3 firmware?
Click to expand...
Click to collapse
There is no stock ATT 4.3 ROM because ATT only released 4.3 as an OTA update. Do not flash any 4.3 firmware (even from sammmobile.com) unless it has been compiled for installation via Odin. Check the development threads for firmware that can be flashed via Odin.
crazymonkey05 said:
Here is a repository with a lot of stock firmwares http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ok. im going to flash I747UCUEMJ2.7z which came from that link/thread you posted via odin.
If you got the phone on 4.3 you need to flash mjb or else you will brick the device
Sent from my ATT Samsung Galaxy SIII using TapaTalk
I have a i747m with stock 4.4.2 and I was wondering if I could straight up downgrade odin to 4.3 or is there anyway I could?
Nope
DocHoliday77 said:
Nope
Click to expand...
Click to collapse
so it's impossible to downgrade without bricking my phone?
Yup. You can flash older roms, but thats it.
DocHoliday77 said:
Yup. You can flash older roms, but thats it.
Click to expand...
Click to collapse
am I able to flash cwm, then flash a custom rom such as quantum?
Yup. Should be just fine.
DocHoliday77 said:
Yup. You can flash older roms, but thats it.
Click to expand...
Click to collapse
does this mean that you can flash any other custom rom even if tis base on 4.3 and lower version?
Yes. Custom roms generally only include the system and kernel, so your base firmware would remain at 4.4.2.
If you go too old though, such as flashing 4.0.4 or 4.1.1 roms, theres no guarantee they wont be a bit buggy. But they should still run nonetheless.
The thing to keep in mind though, is it is ok to flash older roms, kernels and recoveries, but nothing else.