Develop Bugs

[Q] downgrading to cyanogenmod 10.2

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.

[Q] cant flash 4.4.2 rom

I attempted to flash a 4.4.2 rom yesterday but it couldnt and it gave me a status 7 error. I looked it up and people said that you have to update clockworkmod. Well i tried to through terminal but it couldn't. It said something like could not find directory. So if anyone has any idea what I can do pleast tell me.
Using Galaxy s3 sgh-i747 on PA 3.99.1 ROM

Flash Philz Touch from here via Odin (use the tar version in PDA): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att

alright i did it through odin and it worked..now im gonna make a backup again and try flashing a rom. hope it works. thanks for the help

If you can't flash a KK ROM, you may need to update your bootloader. If you're not on a 4.3 bootloader, try and avoid it for now.

audit13 said:
If you can't flash a KK ROM, you may need to update your bootloader. If you're not on a 4.3 bootloader, try and avoid it for now.
Click to expand...
Click to collapse
im on a 4.3 rom but if i get error status 7 again ill just restore my backup and avoid it...is there a 4.3 bootloader? Also i was about to wipe it but its asking me wipe data/factory reset or clean to install a new ROM. I suggest its the 2nd one but if i do it and it doesnt work can i still restore my backup?

orlans21 said:
im on a 4.3 rom but if i get error status 7 again ill just restore my backup and avoid it...is there a 4.3 bootloader? Also i was about to wipe it but its asking me wipe data/factory reset or clean to install a new ROM. I suggest its the 2nd one but if i do it and it doesnt work can i still restore my backup?
Click to expand...
Click to collapse
There is a 4.3 bootloader that would be installed if you ran an OTA update to 4.3 or you manually installed the 4.3 bootloader.
Did you make your backup using Philz? If not, make the backup using Philz, then wipe and install.

audit13 said:
There is a 4.3 bootloader that would be installed if you ran an OTA update to 4.3 or you manually installed the 4.3 bootloader.
Did you make your backup using Philz? If not, make the backup using Philz, then wipe and install.
Click to expand...
Click to collapse
I just made a backup on Philz and im not sure if i installed a 4.3 bootloader manually or OTA. Just to be clear im wiping to install ROM. so the 2nd option

orlans21 said:
I just made a backup on Philz and im not sure if i installed a 4.3 bootloader manually or OTA
Click to expand...
Click to collapse
Doesn't really matter but it's good to know that you need to stay away from any attempts to downgrade the bootloader.

hahah why would i want to downgrade?

orlans21 said:
hahah why would i want to downgrade?
Click to expand...
Click to collapse
I have seen posts where people bricked their phone when trying to return to a stock ROM using Odin.

well...im gonna have to put it back to a stock rom when i get a new phone and give this to my dad...i still have the 4.1 stock downloaded on my computer...i dont even remember how to put it back now lol. so i should try flashing a 4.4.2 rom? which rom do you prefer? i have carbon and liquidsmooth. i want halo like i do on PA and both have it i believe

orlans21 said:
well...im gonna have to put it back to a stock rom when i get a new phone and give this to my dad...i still have the 4.1 stock downloaded on my computer...i dont even remember how to put it back now lol
Click to expand...
Click to collapse
You can't restore to a completely stock ROM not that you have a 4.3 bootloader. AT&T never released a full 4.3 stock ROM, only an update to 4.3 from an earlier stock ROM.
If you did not have a 4.3 bootloader, you could install any stock AT&T ROM such as 4.1.1. Being able to restore to stock 4.1.1 would also allow you to sim unlock your phone for free, if necessary.

audit13 said:
You can't restore to a completely stock ROM not that you have a 4.3 bootloader. AT&T never released a full 4.3 stock ROM, only an update to 4.3 from an earlier stock ROM.
Click to expand...
Click to collapse
well im on rogers and its the same as att. i still have the original samsung touchwiz 4.1 rom just incase anything happens.

Your original post said you have an sgh-i747 which is an AT&T model. If you have a Rogers s3, it's an sgh-i747m.
Regardless of which model you have, you can't downgrade from any 4.3 bootloader which means you can't completely revert back to 4.1.1. The best you could do would be to run 4.1.1 on a 4.3 bootloader.

audit13 said:
Your original post said you have an sgh-i747 which is an AT&T model. If you have a Rogers s3, it's an sgh-i747m.
Regardless of which model you have, you can't downgrade from any 4.3 bootloader which means you can't completely revert back to 4.1.1. The best you could do would be to run 4.1.1 on a 4.3 bootloader.
Click to expand...
Click to collapse
sorry i should have included the m lol. i wont worry about going back to 4.1 until the galaxy s5 comes out and im ready to give it to my dad. but back to focusing on this. im about to attempt to flash a 4.4.2 rom. either liquidsmooth or carbon. what do you like?

I prefer Validus version 4.3 because it includes Nova Launcher and it has a dark UI theme.

but thats 4.3. i wanna be on 4.4 and im installing nova and making it the way i had it before.
wait a second is it a 4.4 rom?

orlans21 said:
but thats 4.3. i wanna be on 4.4 and im installing nova and making it the way i had it before.
wait a second is it a 4.4 rom?
Click to expand...
Click to collapse
It is a 4.4.2-based rom. The release is version 4.3.

hmm interesting...you do recommend it? what great features does it come with?

I like it because it's a very stripped-down ROM, has a dark UI, and is AOSP-based.
It's not radically different from other ROMs but has exactly what I want. I run the same ROM on a Nexus 4 and Motorola Atrix HD.

Help with reverting back to stock

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

[Q] AOKP KitKat SIM Unlock Clarification

Ok, I've read like 14 threads on this, but can't seem to verify an answer for my specific set up. So, sorry if this seems obvious to you guys. I def don't want to brick my phone.
I'm on AOKP Task650 4.4.3 (kitkat) ROM. Obviously the stock 4.1.1 SIM unlock method won't work on AOKP and I've read that the 4.3 version isn't able to downgrade and flash to a 4.1.1 ROM. What about 4.4.3? I also read that has to do with the bootloader and something about bootloaders with Knox on them won't work. I don't think that's my case.
When I go into my bootloader, I see:
ODIN MODE
Product Name: SGH-I747
Custom Binary Download: Yes (1 counts)
Current Binary: Custom
System Status: Custom
Qualcomm secureboot: Enable
So does that mean I can downgrade to 4.1.1 and unlock or am I SOL when it comes to unlocking?
Second part...if I can downgrade, do I have to do it via ODIN, or can I simply flask a ROM zip via TWRP?
If I have to do it via ODIN, can I perform a backup, flash 4.1.1, unlock, then go back into TWRP and restore to my 4.4.3 KitKat ROM?

What's your baseband version? this tells what modem/BL you have
Sent from my ATT Samsung Galaxy SIII using TapaTalk

crazymonkey05 said:
What's your baseband version? this tells what modem/BL you have
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
UCDLK3

Oki believe that's 4.1.1 so you can flash a 4.1.1 ROM and unlock....(I'm not a 100% so someone check me on that please)
Sent from my ATT Samsung Galaxy SIII using TapaTalk

Downgrading to the stock 4.1.1 ROM will erase all data so make sure you backup everything before using Odin to go back to stock.
Based on the information from the download screen and your baseband, you should be fine to downgrade.

audit13 said:
Downgrading to the stock 4.1.1 ROM will erase all data so make sure you backup everything before using Odin to go back to stock.
Based on the information from the download screen and your baseband, you should be fine to downgrade.
Click to expand...
Click to collapse
Awesome! Thanks, guys!

Just an update, I was able to flash a stock 4.1.1 via Odin and unlock my phone. Flashed TWRP and restored...back to right where I left of, but unlocked! Thanks again for the help, guys.

Charles: said:
Just an update, I was able to flash a stock 4.1.1 via Odin and unlock my phone. Flashed TWRP and restored...back to right where I left of, but unlocked! Thanks again for the help, guys.
Click to expand...
Click to collapse
Glad it worked for you. As a personal preference, I stayed away from the 4.3 bootloader.

audit13 said:
Glad it worked for you. As a personal preference, I stayed away from the 4.3 bootloader.
Click to expand...
Click to collapse
Evidently the Task560 AOKP ROM uses the 4.1.1 bootloader.

Charles: said:
Evidently the Task560 AOKP ROM uses the 4.1.1 bootloader.
Click to expand...
Click to collapse
If you want to see which bootloaders are supported by a particular custom ROM, have a look at the updater-script file in a text editor. The bootloader versions are contained in the first few get lines.

[Q] Likewise 4.4.2 ROM does not boot

Hi there, just registered to post this question regarding loading the Likewise 4.4.2 rom on tmobile galaxy s3. I cannot get it the rom to boot despite coming from android 4.3 and using TWRP. I have tried twice and both times the rom will not boot and I just get a black screen, forcing me to do another restore.
Does anyone have any advice? I will include a screenshot to show my current android version, which is what its supposed to be (4.3.) The only thing I've heard that causes problems with this rom is not being updated to 4.3, or not using TWRP. I don't know what is wrong here.

You need to update your firmware to 4.3. Your current rom has no bearing on this whatsoever.

DocHoliday77 said:
You need to update your fimware to 4.3. Your current rom has no bearing on this whatsoever.
Click to expand...
Click to collapse
Okay thanks. I feel like i may have done that already, back when i installed the unnofficial 4.3 software, but since the rom isnt booting maybe not.
On the xda page for the 4.3 firmware it says something about having to be stock/unmodified - is this true or can I flash the 4.3 firmware no matter what ROM I'm using.

Ypu can flash the firmware with odin regardless. You only have to be stock unmodified yo use the ota.

thanks got it working