Develop Bugs

[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.

[Q] Downgrading CM11 to stock 4.3 on i747M

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

[Q] Help!! ROM flashing problems

Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/

dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486

Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help

dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991

Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?

dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks

[Q] Questions about going back to stock.

Hey guys,
I was running Cyanogenmod 11 for a while which I installed using the automatic tool online. During the summer I flashed Dirty Unicorns but I have issues with the camera and random rebooting. I just got a Galaxy Gear for Christmas and I've read that its only compatible with touchwiz roms.
I'm trying to go back to stock and I am ok with losing my root access.
I have an SGH-1747m on Baseband I747MVLUEMK5 and my service provider is Bell. The android version is 4.4.4 currently. Whats the easiest method to do this? I've read some concerning information that going back to an earlier version of android will soft brick your phone, but I believe the most current Bell firmware is still in Jelly Bean.
Is it as easy as downloading the correct firmware and flashing it using Clockworkmod Recovery?
Thanks

You should download the stock ROM from sammobile.com and flash it in Odin to get back to stock.

audit13 said:
You should download the stock ROM from sammobile.com and flash it in Odin to get back to stock.
Click to expand...
Click to collapse
The latest version available for my baseband is 4.3. Will I run into problems going from 4.4.4 to 4.3?

Flashing in Odin will flash everything, including the bootloader and modem.

audit13 said:
Flashing in Odin will flash everything, including the bootloader and modem.
Click to expand...
Click to collapse
Thanks. So if I'm understanding correctly I just flash the latest firmware released by my carrier (4.4.2)? Is there anything else to watch out for when choosing the firmware?
Also, before flashing should I make a backup with Clockwork Recovery or any other program? Will Clockwork Recovery still be present after flashing with ODIN?

ZombieLee said:
Thanks. So if I'm understanding correctly I just flash the latest firmware released by my carrier (4.4.2)? Is there anything else to watch out for when choosing the firmware?
Also, before flashing should I make a backup with Clockwork Recovery or any other program? Will Clockwork Recovery still be present after flashing with ODIN?
Click to expand...
Click to collapse
Yes, flash the latest firmware for your phone. Be sure it's firmware for the i747m and not anything else. Always make a backup if you ever screw up or want to go back to where you are now. You will lose everything by flashing the stock firmware with ODIN, even clockwork mod recovery.

Thanks. When I made a backup before going to Dirty Unicorns I used Clockwork Recovery. If Clockwork will be deleted by flashing with ODIN, how would I utilize that backup if I needed it? Should I use another program to back up?
EDIT: I flashed it and everything went smoothly. Sincere thanks to everyone who gave me help!

How do you unlock an i747M locked to Fido? [OctOS L 5.1.1]

So I'm planning to switch carriers and I'm wondering how I can unlock my i747M locked to Fido that's running OctOS L 5.1.1. If I have to downgrade, how do I transfer all my current app data and pic's. Also, is it possible to keep the unlock if you were to update you phone to a higher version or install a custom ROM or install the nandroid backup you made before unlocking? Please leave me with some important things to know about while unlocking your phone if possible!

If the phone is running a 4.3 or newer bootloader, you'll have to buy an unlock code.
In order to enter the unlock code, the phone should be running a stock samsung ROM from sammobile.
I suggest creating a nandroid backup with TWRP, copy the backup to your computer, flash the stock ROM, perform a factory reset after flashing stock, unlock, flash TWRP, restore nandroid.

audit13 said:
If the phone is running a 4.3 or newer bootloader, you'll have to buy an unlock code.
In order to enter the unlock code, the phone should be running a stock samsung ROM from sammobile.
I suggest creating a nandroid backup with TWRP, copy the backup to your computer, flash the stock ROM, perform a factory reset after flashing stock, unlock, flash TWRP, restore nandroid.
Click to expand...
Click to collapse
so, in a nutshell, i just need to downgrade my phone to a stock rom of 4.3 or below and just search up a video of how to unlock it using the keypad method?
than if i wanted to, i could use the nandroid backup i did before and flash it and still have an unlocked phone?

You cannot use the free method once the phone is running a 4.3 or newer bootloader because you cannot properly run the 4.1.1 modem on a 4.3 or 4.4.2 bootloader and the 4.3 or 4.4.2 bootloader cannot be downgraded to a 4.1.1 bootloader.
Before flashing anything, which bootloader is on the phone?

audit13 said:
You cannot use the free method once the phone is running a 4.3 or newer bootloader because you cannot properly run the 4.1.1 modem on a 4.3 or 4.4.2 bootloader and the 4.3 or 4.4.2 bootloader cannot be downgraded to a 4.1.1 bootloader.
Before flashing anything, which bootloader is on the phone?
Click to expand...
Click to collapse
Sorry for the noob question, but how do i found out my bootloader?
If this helps, my baseband is I747MVLUFOB3

I actually just logged on to get similar clarification. I have an unlock code, but it does not work when I enter it using OctOS-M. Do I need to be on a stock rom to unlock? Can I easily jump back to a stock rom, then back again to a marshmallow rom?

JoshMcMadMac said:
I actually just logged on to get similar clarification. I have an unlock code, but it does not work when I enter it using OctOS-M. Do I need to be on a stock rom to unlock? Can I easily jump back to a stock rom, then back again to a marshmallow rom?
Click to expand...
Click to collapse
From what ive heard, you have to be on a stock rom. As of google, even then, some users have problems or cant, which from what ive heard, can be fixed by downgrading to 4.3 (make sure ur bootloader is the same or your phone WILL be bricked).
Please note that this is from what ive heard and may not be accurate.

Install the Samsung phone info app from the play store as it will tell you a lot.

audit13 said:
Install the Samsung phone info app from the play store as it will tell you a lot.
Click to expand...
Click to collapse
My boot loader seems to be the same as my baseband.

What is the bootloader version?

GamingDevilsCC said:
From what ive heard, you have to be on a stock rom. As of google, even then, some users have problems or cant, which from what ive heard, can be fixed by downgrading to 4.3 (make sure ur bootloader is the same or your phone WILL be bricked).
Click to expand...
Click to collapse
That sounds problematic...I am on NJ2. I am not having any luck finding anything about getting back to stock on the newest bootloader.

audit13 said:
If the phone is running a 4.3 or newer bootloader, you'll have to buy an unlock code.
In order to enter the unlock code, the phone should be running a stock samsung ROM from sammobile.
I suggest creating a nandroid backup with TWRP, copy the backup to your computer, flash the stock ROM, perform a factory reset after flashing stock, unlock, flash TWRP, restore nandroid.
Click to expand...
Click to collapse
Do you think this one would work?
https://z3x-team.com/forum/topic.php?id=9505
Whats a CWM anyways?

CWM is Clockworkmod with is a custom recovery. CWM is outdated as it has not been updated for quite some time. Many recent custom ROMs now require TWRP.
You may be able to software unlock the phone but you'll probaby need a UART cable and Samsung Pro tools. I don't believe Pro Tools is free.
The linked thread is from 2014 and, in 2014, many phones were running 4.1.2 which meant the phone could be downgraded to 4.1.1 using and sim unlocked using the dialler's menu options.