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.
Related
Hi im new on this forum and I would like to have some tricks and tips cause I just rooted my phone yesterday and it seems more difficult to find information for my phone I have a galaxy s3 on 4.3 sgh i747m with Rogers .... Is it me or there is just a lot more stuff made for the i9300... I have tried to find ROM'S and tricks to put CWM recovery but it's harder to find information !!
to put CWM recovery I saw a lot of stuff saying download rom manager and install CWM recovery with this app but they offer me a version of CWM recovery for a galaxy s3 (metro cps) they doesn't say if it's made for a sgh i747 so im really scared to do something wrong if I install this version of CWM recovery ..
Could some one help me maybe with website limks or a guide for beginers noob like me or this forum seem's to be really good with some people with knowledge
Before my galaxy s3 I had a Jailbreak Iphone 3gs a year ago but Rooting an Android and putting stuff on it is not really the same thing it's far away from it!
And does it matter if put some stuff on my phone made for at&t sprint etc.... even if those are sgh i747
Hey,
I am running CM11 d2att and CWM d2att on my i747m and it works perfectly. It has been so long since I did it that I can't remember the exact steps that I took, so I would do some more research. Everything I needed to know was on these forums somewhere.
I believe the rough steps I took were:
- Root
- Install CWM (d2att)
- Update bootloaders (i747m)
- Flash d2att rom
But I can't remember exactly, so do some research before you go ahead!
You can install pretty much whatever you'll find in these forums except for bootloaders and modems.
There are specific bootloaders/modem for the i747m vs. i747.
The rest, unless explicitely specified otherwise, is 100% compatible between i747 and i747m.
As for your recovery script, I would suggest installing TWRP instead of CWM.
TWRP is more user friendly for people that are new to Android and both are usually supported.
For this, go to the Play Store, download and install the "Goo manager" application.
Once installed, open up the app, hit the menu button and select the "install recovery script" option.
It will automatically select/download/install the correct recovery for your phone and ask you to confirm before doing so.
HiKsFiles said:
You can install pretty much whatever you'll find in these forums except for bootloaders and modems.
There are specific bootloaders/modem for the i747m vs. i747.
The rest, unless explicitely specified otherwise, is 100% compatible between i747 and i747m.
As for your recovery script, I would suggest installing TWRP instead of CWM.
TWRP is more user friendly for people that are new to Android and both are usually supported.
For this, go to the Play Store, download and install the "Goo manager" application.
Once installed, open up the app, hit the menu button and select the "install recovery script" option.
It will automatically select/download/install the correct recovery for your phone and ask you to confirm before doing so.
Click to expand...
Click to collapse
Ok thank you thats what I was wondering it doesn't matter if it's an at&t, bell or rogers... but it have to be the right model !!
Your talking about bootloader ... when I rooted my phone I have unlock my bootloader right ?? What is the advantage of changing your bootloader ....do you have to change it when you put a custom rom's?? Maybe my question have no sense at all because im new to this but I keep reading a lot of stuff on android !
carlosQC said:
Ok thank you thats what I was wondering it doesn't matter if it's an at&t, bell or rogers... but it have to be the right model !!
Your talking about bootloader ... when I rooted my phone I have unlock my bootloader right ?? What is the advantage of changing your bootloader ....do you have to change it when you put a custom rom's?? Maybe my question have no sense at all because im new to this but I keep reading a lot of stuff on android !
Click to expand...
Click to collapse
I recommend not updating your phone to any stock 4.3 ROM. A stock 4.3 ROM will install a 4.3 bootloader which cannot be downgraded and may cause problems when trying to root or get back to stock.
Some newer ROMs require an updated bootloader in order to install and boot. I am running a 4.1.2 bootloader on my i747m and don't have any problems installing 4.4.2 ROMs.
Rooting gives you access to the system files and does not unlock you bootloader.
For installing custom ROMs, I use Philz Touch which is based on CWM. I have tried TWRP and I was getting errors when flashing custom ROMs. I was able to flash the same ROM using Philz Touch without a problem. TWRP is more user friendly but doesn't work as well for me.
audit13 said:
I recommend not updating your phone to any stock 4.3 ROM. A stock 4.3 ROM will install a 4.3 bootloader which cannot be downgraded and may cause problems when trying to root or get back to stock.
Some newer ROMs require an updated bootloader in order to install and boot. I am running a 4.1.2 bootloader on my i747m and don't have any problems installing 4.4.2 ROMs.
Rooting gives you access to the system files and does not unlock you bootloader.
For installing custom ROMs, I use Philz Touch which is based on CWM. I have tried TWRP and I was getting errors when flashing custom ROMs. I was able to flash the same ROM using Philz Touch without a problem. TWRP is more user friendly but doesn't work as well for me.
Click to expand...
Click to collapse
what do you mean when you say I recommend not updating your phone to any stock 4.3 ROM (when a custom rom is based on 4.3?) and can you explain me the bootloader thing in details how can I fix that or how can I unlock it ?
what is d2att ?
carlosQC said:
what do you mean when you say I recommend not updating your phone to any stock 4.3 ROM (when a custom rom is based on 4.3?) and can you explain me the bootloader thing in details how can I fix that or how can I unlock it ?
what is d2att ?
Click to expand...
Click to collapse
Your post says youhave 4.3 on your phone. Is it a stock 4.3 ROM?
d2att (i747) is the AT&T version of the s3. Canada has the i747m.
The bootloader does not need to be unlocked in order to install a custom recovery or to root like Motorola phones.
The bootloader is software that an OS works with in order to function as a phone.
audit13 said:
Your post says youhave 4.3 on your phone. Is it a stock 4.3 ROM?
d2att (i747) is the AT&T version of the s3. Canada has the i747m.
The bootloader does not need to be unlocked in order to install a custom recovery or to root like Motorola phones.
The bootloader is software that an OS works with in order to function as a phone.
Click to expand...
Click to collapse
yes its the 4.3 jelly bean stock rom
but can I put any custom rom for my model the i747 or 747m ? The carrier doesn't have any importance ?
Any warranty left on your phone? Installing a custom ROM will void your warranty.
If you want to install a custom rom, copy the ROM you want to the internal or external SD card, install Philz Touch recovery, boot into recovery, wipe cache, Dalvik, install the ROM, and reboot.
You can install any ROM for the d2att as long as the ROM supports the phone's bootloader.
How I know which bootloader I got? If I have the 4.3 jelly bean I have a 4.3 boot loader?
Sent from my SGH-I747M using xda app-developers app
audit13 said:
Any warranty left on your phone? Installing a custom ROM will void your warranty.
If you want to install a custom rom, copy the ROM you want to the internal or external SD card, install Philz Touch recovery, boot into recovery, wipe cache, Dalvik, install the ROM, and reboot.
You can install any ROM for the d2att as long as the ROM supports the phone's bootloader.
Click to expand...
Click to collapse
How I know which bootloader I got? If I have the 4.3 jelly bean I have a 4.3 boot loader?
carlosQC said:
How I know which bootloader I got? If I have the 4.3 jelly bean I have a 4.3 boot loader?
Click to expand...
Click to collapse
Of you loaded a stock 4.3 ROM, you'll have the 4.3 bootloader.
audit13 said:
Of you loaded a stock 4.3 ROM, you'll have the 4.3 bootloader.
Click to expand...
Click to collapse
thank you for your help
Since you have TWRP installed, you not flash custom ROMs. Look around for a ROM you like, download it to your phone's SD card, boot into recovery, wipe cache, Dalvik, flash ROM, reboot.
audit13 said:
Since you have TWRP installed, you can not flash custom ROMs. Look around for a ROM you like, download it to your phone's SD card, boot into recovery, wipe cache, Dalvik, flash ROM, reboot.
Click to expand...
Click to collapse
He meant you CAN flash custom roms.
As long as the rom isn't packaged with a modem or bootloader you can flash any AT&T rom as you please.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
He meant you CAN flash custom roms.
As long as the rom isn't packaged with a modem or bootloader you can flash any AT&T rom as you please.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for catching my error. I edited my original post.
audit13 said:
Thanks for catching my error. I edited my original post.
Click to expand...
Click to collapse
No problem hope you would do the same for me.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it possible to install a stock ROM once 4.3 and a locked bootloader is in place. I've looked all over and I seem to read conflicting stories. So...
I have a Samsung S3 Telus (AT&T) version running the latest 4.3 as of May1st, my bootloader is locked and I have a tripped flash counter.
If someone actually posts a I747MVLUEND2 rooted image can I flash it?
Can I flash an older version I747MVLUEM series?
Oh yeah my phone is NOT rooted.
Check post #5, 11, 27 here Guide: How I unlocked my ATT S3 [ 1 2 3 ... Last ]
Thread By: Jasonator
I think you didn't understand the question. You pointed me to a thread about unlocking.
With a 4.3 bootloader, you will need to install a custom recovery to flash ROMs. If you want to restore a stock 4.3 ROM, try this: http://forum.xda-developers.com/showthread.php?t=2658486
With a 4.3 bootloader, you cannot use Odin to flash a stock ROM unless that ROM was specifically compiled for flashing via Odin.
No this is not possible. I have a LOCKED boot loader. I can't flash a custom recovery as far as I know.
Also how would one know a ROM is made to be flashed by Odin even if it was possible? Maybe I missed something here.
I re-read your original post and I'm a bit confused. You have a Telus s3 (i747m) or AT&T s3 (i747)?
I have never heard of an s3 having a locked bootloader. All of the phones with a stock 4.3 ROM have a bootloader that cannot be downgraded.
audit13 said:
I re-read your original post and I'm a bit confused. You have a Telus s3 (i747m) or AT&T s3 (i747)?
I have never heard of an s3 having a locked bootloader. All of the phones with a stock 4.3 ROM have a bootloader that cannot be downgraded.
Click to expand...
Click to collapse
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
horga_83 said:
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
Click to expand...
Click to collapse
sir, the one who got the wrong idea is you
the only S3 with locked bootloader is the verizon version
i747/M doesn't regardless of which version
which occurs to me that you might have done something wrong trying to root your device
though i've never tried this tool to root but many people succeeded rooting their phone with this http://forum.xda-developers.com/showthread.php?t=1963790
so try it out
but again, you said to flash a stock rom... you can do it via Kies(is that how it is called? it had been so long since i last used it) or you can just use ODIN to flash it
Regardless of the subject of that thread, the posts I indicated directly speak to your 747m downgrade question.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
horga_83 said:
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
Click to expand...
Click to collapse
Can understand why some may be confused about the question. If you have stock 4.3 already (which is the latest version available), why would you want to flash another stock ROM? If you are talking about flashing an older stock ROM, yes it is possible, and there have been several posts on how you can successfully downgrade the system only without altering the bootloader. Attempting to downgrade the bootloader will, of course, cause a brick so downgrading ROM only is a rather complicated process that should be attempted only if there is a very worthwhile reason for this. So far, there are very few arguments, if any, for downgrading from 4.3 to any older stock ROM version. If you are trying to flash a rooted version of the same stock, you need to be sure it's one with the same bootloader. You may, however, find it easier simply keeping the current system and rooting via Safe Root. You can, however, flash a custom ROM if it won't attempt to mess with your bootloader . As far as recovery goes, even if you have stock 4.3, you can still flash custom recovery via Odin or other prescribed installation route. I'm not aware of 4.3 preventing the flashing of a custom recovery. I have an AT&T i747 with stock 4.3 and I've flashed custom recovery several times.
pcshano said:
sir, the one who got the wrong idea is you
the only S3 with locked bootloader is the verizon version
i747/M doesn't regardless of which version
which occurs to me that you might have done something wrong trying to root your device
though i've never tried this tool to root but many people succeeded rooting their phone with this http://forum.xda-developers.com/showthread.php?t=1963790
so try it out
but again, you said to flash a stock rom... you can do it via Kies(is that how it is called? it had been so long since i last used it) or you can just use ODIN to flash it
Click to expand...
Click to collapse
So when my bootloader says Qualcomm secure boot = 1, that means what exactly?
I haven't tried to root my phone yet.
Well actually it's a stock ROM that has been rooted. As per this page:
http://forum.xda-developers.com/showthread.php?t=1739426&__utma=248941774.1179961654.1399404439.1400082744.1400099749.11&__utmb=248941774.1.10.1400099749&__utmc=248941774&__utmx=-&__utmz=248941774.1400099749.11.3.utmcsr=forum.xda-developers.com|utmccn=%28referral%29|utmcmd=referral|utmcct=/galaxy-s3-att/&__utmv=-&__utmk=261245838
horga_83 said:
So when my bootloader says Qualcomm secure boot = 1, that means what exactly?
I haven't tried to root my phone yet.
Well actually it's a stock ROM that has been rooted. As per this page:
http://forum.xda-developers.com/showthread.php?t=1739426&__utma=248941774.1179961654.1399404439.1400082744.1400099749.11&__utmb=248941774.1.10.1400099749&__utmc=248941774&__utmx=-&__utmz=248941774.1400099749.11.3.utmcsr=forum.xda-developers.com|utmccn=%28referral%29|utmcmd=referral|utmcct=/galaxy-s3-att/&__utmv=-&__utmk=261245838
Click to expand...
Click to collapse
I think that means secure booting has been enabled. Secure booting has nothing to do with having a locked bootloader. From what I have read in other forums, a locked bootload would not allow you to load a custom kernel.
So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.
I know there are a few threads regarding this issue but I can't seem to find a definitive answer.
I am currently running stock 4.3 jellybean (rooted). My phone hasn't received the 4.4 KitKat update yet, so I wanted to install CM11 in order to get KitKat on my s3. However, I heard CM11 can be buggy on the s3, so in case things go south, I want to be able to revert back to the stock 4.3 rom. Some people have said that you can easily flash the stock ROM via ODIN. However, others said that downgrading from 4.4.2 to 4.3 will hard brick the device since installing CM11 updates the boot loader. So downgrading to 4.3 stock with a 4.4.2 boot loader will cause a hard brick according to other threads I've seen. My question is, how can I downgrade from CM11 to stock 4.3 safely without bricking? Thanks in advance.
If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).
audit13 said:
If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).
Click to expand...
Click to collapse
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.
Mzrz said:
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.
Click to expand...
Click to collapse
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?
audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!
Mzrz said:
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?
Click to expand...
Click to collapse
Philz is based on the latest release of CWM and I prefer CWM over TWRP because I had problems flashing ROMs. Once I switched to Philz/CWM, no more problems.
Mzrz said:
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!
Click to expand...
Click to collapse
The unlock should be permanent. I unlocked it using the free method when on 4.1.1 and no ROM has ever caused it to re-lock. Reflashing a completely stock ROM, including the bootloader, did not relock the phone.
Please remember that flashing and changing ROMs will always carry a risk of soft bricking or hard bricking your phone. Make sure you read all of the guides and be prepared for disaster.
Good read here: http://forum.xda-developers.com/showthread.php?t=2201860
Hi, I'm currently using this method to flash roms, and I've flashed OctOS M a total of 3 times using this method, but for some reason, after a bit of time the ROM gets really buggy.
Is there a better way of flashing this ROM, or is it the ROM itself causing these issues.
Thanks,
Which phone do you have? For the i747 and i747m can be flashed with TWRP from Odin. The custom ROM and Gapps and then flashed from TWRP.
audit13 said:
Which phone do you have? For the i747 and i747m can be flashed with TWRP from Odin. The custom ROM and Gapps and then flashed from TWRP.
Click to expand...
Click to collapse
Currently have an i747m
its just that for some reason, at first OctOS M works perfect, and then starts to have tons of issues overtime, which other people dont seem to have.
I remember somebody telling me to wipe data and cache about 3 times before installing the ROM in TWRP, even tho i usually just do it once. Is that the proper way to do it?
Thanks,
The phone is running the latest KK bootloader and modem/baseband?
Did you use TWRP to wipe system as well before installing the custom ROM?
audit13 said:
The phone is running the latest KK bootloader and modem/baseband?
Did you use TWRP to wipe system as well before installing the custom ROM?
Click to expand...
Click to collapse
Not sure how i can check if im running the latest bootloader or modem/baseband.
Yea, I had also wiped system, and delvik cache.
You can install the Samsung Phone Info App from the play store which will tell you the bootloader and modem/baseband version in the phone. I think FOB3 is the latest.
audit13 said:
You can install the Samsung Phone Info App from the play store which will tell you the bootloader and modem/baseband version in the phone. I think FOB3 is the latest.
Click to expand...
Click to collapse
My bootloader and modem/baseband end in FOB3.
Okay, then that's not causing the problem. It may be a bug that's unique to your particular phone. The only way to tell for sure may be to install a different ROM to see what happens.