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.

Looking for a wind 4.3 modem

I have a wind t889v, I am stuck on stock after taking a 4.3 OTA update, i rooted and flashed the 4.1.1 modem from here http://forum.xda-developers.com/showthread.php?t=2061031 so that i could unlock my phone, but now I am stuck with this old modem since there is no link there for the 4.3 version. Does anyone have a link to the wind t889v 4.3 modem?
EDIT: I am going to try flashing a stock 4.3 wind rom for now, but how can i upload files to my phone? I have installed kies and kies3 but neither seem to detect it, and windows explorer does not show my phones storage. I have had to transfer files through my mega cloud folder in order to get them on my phone, but that is going to be a pain in the ass for a 907mb rom...
And my next question: How do I know what roms are flashable for the t889v after taking that stupid 4.3 update? I found this guide but its for a verizon note 2. I am rooted and I am hoping there is some customized odin flashable firmware for me

nodyarg said:
I have a wind t889v, I am stuck on stock after taking a 4.3 OTA update, i rooted and flashed the 4.1.1 modem from here http://forum.xda-developers.com/showthread.php?t=2061031 so that i could unlock my phone, but now I am stuck with this old modem since there is no link there for the 4.3 version. Does anyone have a link to the wind t889v 4.3 modem?
EDIT: I am going to try flashing a stock 4.3 wind rom for now, but how can i upload files to my phone? I have installed kies and kies3 but neither seem to detect it, and windows explorer does not show my phones storage. I have had to transfer files through my mega cloud folder in order to get them on my phone, but that is going to be a pain in the ass for a 907mb rom...
And my next question: How do I know what roms are flashable for the t889v after taking that stupid 4.3 update? I found this guide but its for a verizon note 2. I am rooted and I am hoping there is some customized odin flashable firmware for me
Click to expand...
Click to collapse
all roms are flashable while on the 4.3 bootloader. you will need to install a custom recovery (CWM, TWRP, etc). here is a link to the modem: http://forum.xda-developers.com/showthread.php?t=2554226 you can flash this in said recovery

mattlowry said:
all roms are flashable while on the 4.3 bootloader. you will need to install a custom recovery (CWM, TWRP, etc). here is a link to the modem: http://forum.xda-developers.com/showthread.php?t=2554226 you can flash this in said recovery
Click to expand...
Click to collapse
Oh alright, I suppose I can give it a shot. But I have been told its not possible to flash anything other than stock factory 4.3, for example here:
Baenwort said:
If your phone has factory 4.3 you can not downgrade to a lower version as the KNOX functionality that is built into the 4.3 bootloader will prevent the flashing of a prior version.
You can still root with stock factory 4.3 but you'll need to either trip the KNOX counter or use one of the more involved methods. Is there a reason you are trying to flash such an early version?
Click to expand...
Click to collapse
I have already rooted with saferoot, can i just flash the recovery and then custom images as normal?

nodyarg said:
Oh alright, I suppose I can give it a shot. But I have been told its not possible to flash anything other than stock factory 4.3, for example here:
I have already rooted with saferoot, can i just flash the recovery and then custom images as normal?
Click to expand...
Click to collapse
what that is referring to is the bootloader. which currently can not be downgraded. install a custom recovery and you can flash rom zips not images. most roms do not have a bootloader in the zip so there will be no conflict

mattlowry said:
what that is referring to is the bootloader. which currently can not be downgraded. install a custom recovery and you can flash rom zips not images. most roms do not have a bootloader in the zip so there will be no conflict
Click to expand...
Click to collapse
thanks you were right, i used the unified android toolkit to install twrp and it worked. so can i just flash any rom for the t889? because i believe i read that only touchwiz roms work. if thats true i havent seen many roms that i can use.

nodyarg said:
thanks you were right, i used the unified android toolkit to install twrp and it worked. so can i just flash any rom for the t889? because i believe i read that only touchwiz roms work. if thats true i havent seen many roms that i can use.
Click to expand...
Click to collapse
N7105, i317, and SGH-T889 ROMs are usually OK. Don't flash another device's modem. There is a whole mess of ROM options out there.
Make certain your APN is correct in other carrier designated ROMs. Don't flash recovery from automated recovery installers as they will not put the correct version in unless you are on a ROM with the correct build prop settings for the SGH-T889 (if your using a Tmo US device).
Hastily spouted for your befuddlement

Coug76 said:
N7105, i317, and SGH-T889 ROMs are usually OK. Don't flash another device's modem. There is a whole mess of ROM options out there.
Make certain your APN is correct in other carrier designated ROMs. Don't flash recovery from automated recovery installers as they will not put the correct version in unless you are on a ROM with the correct build prop settings for the SGH-T889 (if your using a Tmo US device).
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
So I flashed DN3, it was for n7105, its an AROMA installer. I jsut realized that thats what you meant when you said dont flash automated installers. It required that i flash an n7105 modem to complete the installation. Can i fix my build.prop after? How do i flash this rom without using AROMA? aaah
EDIT: I am going to try to flash the wind 4.1.1 t889v over top of this using mobile odin since my modem doesnt work now.

nodyarg said:
So I flashed DN3, it was for n7105, its an AROMA installer. I jsut realized that thats what you meant when you said dont flash automated installers. It required that i flash an n7105 modem to complete the installation. Can i fix my build.prop after? How do i flash this rom without using AROMA? aaah
EDIT: I am going to try to flash the wind 4.1.1 t889v over top of this using mobile odin since my modem doesnt work now.
Click to expand...
Click to collapse
I was more referring to ROM Manager and Goo Manager. ROMs that flash modems are atypical. Usually they leave you with a choice to install one of a couple choices or leave it as is. Sometimes they don't.
You may be able to find the 4.3 modem appropriate to your device around here somewhere. That will work much better than the 4.1.1 if you can get it to stick.
Hastily spouted for your befuddlement

Coug76 said:
I was more referring to ROM Manager and Goo Manager. ROMs that flash modems are atypical. Usually they leave you with a choice to install one of a couple choices or leave it as is. Sometimes they don't.
You may be able to find the 4.3 modem appropriate to your device around here somewhere. That will work much better than the 4.1.1 if you can get it to stick.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I flashed the wind 4.1.1 modem with mobile odin but i still have a "no network" icon. ill try to find a 4.3 wind modem and flash that. hopefully i havent bricked my modem, i thought this rom would be cross compatible. damn...
EDIT: I used mattlowry's 4.3 wind modem above, but still "no network" icon (the one that looks like a no smoking sign. not really sure what to do now. i was told this rom would work but i guess not. hopefully if i flash back to a t889v firmware i can get my modem working again....
any advice?

nodyarg said:
I flashed the wind 4.1.1 modem with mobile odin but i still have a "no network" icon. ill try to find a 4.3 wind modem and flash that. hopefully i havent bricked my modem, i thought this rom would be cross compatible. damn...
EDIT: I used mattlowry's 4.3 wind modem above, but still "no network" icon (the one that looks like a no smoking sign. not really sure what to do now. i was told this rom would work but i guess not. hopefully if i flash back to a t889v firmware i can get my modem working again....
any advice?
Click to expand...
Click to collapse
You could mobile Odin the stock image from sammobile or the root66 to flash everything but the bootloader. Kies recovery could maybe work. T889V is stubborn with modems IIRC. Teshx had problems with this very problem quite sometime ago IIRC.
This fits in my "this is a problem" category, backup and save your data.
Hastily spouted for your befuddlement

Coug76 said:
You could mobile Odin the stock image from sammobile or the root66 to flash everything but the bootloader. Kies recovery could maybe work. T889V is stubborn with modems IIRC. Teshx had problems with this very problem quite sometime ago IIRC.
This fits in my "this is a problem" category, backup and save your data.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
yeah i did some wiping in recovery and managed to soft brick my phone, then using pc odin to flahs a stock image got my phone back to life and showed signal bars again, then i flashed the custom recovery back on. so at least i know i can save my modem when i do this again. i then tried replacing the modem.bin files in the dn3 istall zip with t889v modem.bin files, tried reflashing it with the new modem.bins but it still gives me the no network symbol instead of signal bars.

[SOLVED] I think my i747M may be soft bricked?

Hey all. I am fairly inexperienced when it comes to rooting, though I have done a few succesfully in the past. I currently have the newest version of TWRP installed on my Samsung I747M. The I747M I have is not from one of the major carriers, but as far as I am aware, the phone is factory network unlocked. Carrier is GCI, in Alaska.
I currently have a 4.4.2 Touchwiz Rom installed and started having problems after I attempted to flash the ROM Dandroid, which is 4.3 (http://forum.xda-developers.com/showthread.php?t=2121506). I had created a backup using TWRP before flashing the ROM and reverted back once I noticed the problem.
The main issue I am experiencing at this time is the Baseband Version, IMEI, and other information related to the modem is showing "Unknown" and features such as wifi will not toggle on.
I had also attempted to flash the most current version of the modem that I was able to find thru Odin. Odin showed the flash as successful. The version I flashed to the phone was I747MUMUEND3: modem_CWM_I747MUMUEND3.zip - 18.80 MB - April 3rd, 2014 (http://forum.xda-developers.com/showthread.php?t=1831898)
At this point, I can still get into recovery, download modem and I am able to boot up the phone and access most all functions. The next step I was going to try was going to be to flash back to stock firmware from sammobile's website (Was using to use the Roger's version of 4.4.2), though I don't want to cause more issues than I can handle or resolve thru software.
Any advice on how to proceed would be greatly appreciated or even just how to get the modem/wifi features functional again would be helpful. I'm just as happy staying on my current ROM at this point if I can get the phone fully functional again.

It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.

audit13 said:
It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.
Click to expand...
Click to collapse
Forgot to mention, this is something I did try. I attempted to flash Cyanogen Mod 12.1 (Download: cm-12.1-20151017-NIGHTLY-d2att.zip (286.76 MB) ) and most recent nightly build & the most recent stable release (CM11) (Download: cm-11-20140210-SNAPSHOT-M3-d2att.zip (194.37 MB) ). When flashing these, I transferred the downloaded ZIP file to the internal storage of the phone in the root directory and attempted to run an install from TWRP. Both installs failed.

Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: http://www.sammobile.com/firmwares/database/SGH-I747M/
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar
Create a nandroid backup using TWRP and then try to flash a custom ROM again.

audit13 said:
Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
Create a nandroid backup using TWRP and then try to flash a custom ROM again.
Click to expand...
Click to collapse
I'll give that a shot when I get home. Stock firmware was one of my next thoughts. I have it downloading at the measly 15 Kbps offered for free from sammobile so hopefully should be done by the time I get home & update this thread with any progress.

Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in TMS3KK thread. The ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)

dawgdoc said:
Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the "http://forum.xda-developers.com/showthread.php?t=2725192"Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in http://forum.xda-developers.com/showthread.php?t=2725750" TMS3KK thread. The http://forum.xda-developers.com/showthread.php?t=1756776" ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)
Click to expand...
Click to collapse
I'm not opposed to any of this. Mostly just trying to slim down this phone to the basics as much as I can and am quite open to any recommendations. Main thing I want to maximize is battery life & simplicity since this is for my wife and those are her major wants in a phone. I figure any kind of ROM that just covers the basics should cover my bases & would prefer one with a darker/black skin to maximize battery life w/ the OLED screen. I am in the process of flashing to the Roger's stock ROM as I type this w/ my fingers crossed.
Just to add, no over clocking or anything of that nature is desired. If I remember correctly I ended up putting the ktoonsez kernel on one of my handsets, either this Galaxy S3 or my Galaxy S5, though I can't recall which since it was so long ago.

Alright! So progress! Wifi, Baseband version, IMEI and all other missing information restored & now works w/ stock rom flash. In process of reflashing TWRP now.

Let us know what happens.

Still all good with TWRP installed. Have not flashed back on a custom ROM yet. After reviewing some of the above recommendations, I am kind of liking the looks & features of TMS3KK (http://forum.xda-developers.com/showthread.php?t=2725750) and feel it would suit my needs.
I factory reset, cleared cache, and cleared Dalvik thru TWRP & then made a back up. Prior to this, I confirmed everything was still working normally w/ phone fully loaded after TWRP was installed.
One of the things mentioned on the installation instructions for that ROM is the following:
---
Do not mix and match 4.3 firmware (bootloaders/modem) with the new 4.4.2 ones. You will hard brick and I warned you. This works the same as any 4.3 or ND8port ROM with 4.3 firmware and it can use the new 4.4.2 ones also.
Link to recovery flashable i747 and i747M 4.4.2 bootloader and modem packages: http://forum.xda-developers.com/gala...hable-t2856914
---
How would I go about confirming my current bootloader/modem versions to make sure they are both 4.4.2 before flashing this ROM? At the link provided, those files/links to the files were removed because they were causing some bricked devices per a note at the top of that thread. Here's a link to the thread I am referencing since the above link looks to be broken. (http://forum.xda-developers.com/gal...mware-ne4-ne6-nf2-recovery-flashable-t2856914)

If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.

audit13 said:
If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.
Click to expand...
Click to collapse
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.

fodor362 said:
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.
Click to expand...
Click to collapse
Glad to hear the phone is running well.
I've heard it said "Happy wife, Happy life."

sound problem

Good Morning
passage through the forum to see if someone can help me with a problem I have since I started with custom roms. My problem is that the cell is left without sound when I have headphones on and the cell is hot. the strange thing is that the sound is full, even if I unplug the headphones. I have to reboot the phone and wait for the temperature to normalize again to plug headphones and the sound is heard.
Another fact is that my cell phone can be on fire and the sound will be perfect as long as you do not have headphones plugged
Does anyone know why this happens and how to fix it?:crying:

Unfortunately it sounds like you have a rather unique problem there. I've never encountered it anyway.
Have you tried other roms or kernels? If not, I think that would be the first thing to try. What rom and kernel are you currently using? Try flashing a stock based rom, factory reset, and see if it still occurs.
If the problem persists on different roms and kernels, it will likely be a hardware issue.
Have you also tried different headphones?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Unfortunately it sounds like you have a rather unique problem there. I've never encountered it anyway.
Have you tried other roms or kernels? If not, I think that would be the first thing to try. What rom and kernel are you currently using? Try flashing a stock based rom, factory reset, and see if it still occurs.
If the problem persists on different roms and kernels, it will likely be a hardware issue.
Have you also tried different headphones?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
ow it is the cyanogenmod 12.1, before used the slimkat and both have had that problem. I have not tried with stock rom because when I try to flash it with Odin leaves me in soft brick. and I find the rom that works. and hardware problem not think it's, as you never give me problems, unless the cell phone is hot

frank461 said:
ow it is the cyanogenmod 12.1, before used the slimkat and both have had that problem. I have not tried with stock rom because when I try to flash it with Odin leaves me in soft brick. and I find the rom that works. and hardware problem not think it's, as you never give me problems, unless the cell phone is hot
Click to expand...
Click to collapse
One reason Odin could be causing problems is if you are attempting to flash software with bootloader and modem that is older than what is on the phone. You have had CM12.1 on the phone, but what is your current bootloader and modem? You can use these commands in Terminal Emulator to find out:
Code:
getprop ro.bootloader
getprop | grep version.baseband
I may have missed it, but do you have the i747 or the i747M? Both will work with the same roms, however they use different bootloaders and modems. Odin should stop you from loading ROMs from the wrong device, most times anyway.

dawgdoc said:
One reason Odin could be causing problems is if you are attempting to flash software with bootloader and modem that is older than what is on the phone. You have had CM12.1 on the phone, but what is your current bootloader and modem? You can use these commands in Terminal Emulator to find out:
Code:
getprop ro.bootloader
getprop | grep version.baseband
I may have missed it, but do you have the i747 or the i747M? Both will work with the same roms, however they use different bootloaders and modems. Odin should stop you from loading ROMs from the wrong device, most times anyway.
Click to expand...
Click to collapse
Well my baseband AMD modem is I747mvlufne6 I for this model as I was going down the roms

frank461 said:
Well my baseband AMD modem is I747mvlufne6 I for this model as I was going down the roms
Click to expand...
Click to collapse
NE6 would indicate the i747M. The soft brick could be a factor of returning to stock KitKat after having been on Lollipop, either CM or AOSP and their derivatives. If you want to try a stock 4.4.2 ROM, the fix for the soft brick is either:
1) Flash the stock ROM from your custom recovery, then flash the stock recovery before rebooting, boot into the stock recovery and do a factory reset. OR -
2) Place the stock ROM on an external sdcard, boot into your custom recovery, format the internal sdcard, flash the stock ROM, reboot.
Needless to say, you will lose everything you have not backed up. Of course, I don't know that the stock ROM will fix your sound and overheating issues.

Ok i trying this and leter i tell you what happen
Thanks

If I'm not mistaken, the i747m firmware is available from http://sammobile.com/firmwares
So you can just flash NE6 full firmware (or newer), boot recovery and factory reset.
(Might be a little more straightforward that way...eliminates some extra steps)
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
If I'm not mistaken, the i747m firmware is available from http://sammobile.com/firmwares
So you can just flash NE6 full firmware (or newer), boot recovery and factory reset.
(Might be a little more straightforward that way...eliminates some extra steps)
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
You are correct, it is on sammobile and it would eliminate some steps. I think he would lose root, but it would be easy enough to afterwards flash a custom recovery and then root with the supersu.zip.
I probably suggest the two steps I do because they are the same for the i747M and the i747. With the i747 there is no 4.4.2 stock from sammobile to flash, so that third option isn't present.

good to fix the sound problem may work because i was investigated and found that the kernel could be problems because it was not compatible with Android 4.4 or newer. So I wanted to try to return to rom stock and see if it is true.
Now I'm downloading the rom is SamMobile (after a few problems of my own) and later, say if the sound repair

dawgdoc said:
You are correct, it is on sammobile and it would eliminate some steps. I think he would lose root, but it would be easy enough to afterwards flash a custom recovery and then root with the supersu.zip.
I probably suggest the two steps I do because they are the same for the i747M and the i747. With the i747 there is no 4.4.2 stock from sammobile to flash, so that third option isn't present.
Click to expand...
Click to collapse
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?

frank461 said:
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
Click to expand...
Click to collapse
@DocHoliday77 would it be safe for him to flash one of the At&T stock 4.4.2 ROMs made available by @enewman17 as long as he was very careful to not flash the bootloader and modem? I'm thinking it would, but I prefer hearing another voice confirm this.

frank461 said:
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
Click to expand...
Click to collapse
You have to be in Download Mode to flash with Odin, not recovery. (Same buttons but volume down instead of up.)
dawgdoc said:
@DocHoliday77 would it be safe for him to flash one of the At&T stock 4.4.2 ROMs made available by @enewman17 as long as he was very careful to not flash the bootloader and modem? I'm thinking it would, but I prefer hearing another voice confirm this.
Click to expand...
Click to collapse
That would be safe to do. The main reason I still suggest flashing the full official firmware though is in case something currently on the device got corrupted somehow. Plus if he flashes the NE4 system and it still isn't fixed, the next step would be to flash full official stock anyway. Imo, it's the only true way to know if you have a hardware or a software issue.
That said though, I have a feeling things would end up working with either one of those solutions.
Sent from my SGH-T999 using Tapatalk

Sorry for the delay, I have already flashed the official ROM and as the sound problem is arrangement. however I have one more question, I'm from mexico but to flash the rom NE6 cell did not recognize the Spanish language. it is the only detail, as I pass the phone to Spanish without rooting the phone
As I said everything works fine, signal, wifi, everything. I guess because it is released. But I would like this in Spanish.
for now thank everyone who attended my problem.

[Q] Help with going back to stock (from CM11)

Hey, sup?
I need your help, I'm trying to go back to stock firmware on my i747, currently I'm running CM11 latest snapshot.
Background: Some time ago, I accidently erased my imei. Took the phone to a guy who restored it but the phone doesn't work with 3G now, only 2G. So I wanted to try going back to stock firmware to see if that fixes the issue.
I tried downloading the CUEMJB file from here, but it doesn't work (keeps looping the same page) http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Can you help me? Also, it is safe what I'm trying to do?
Thank you!

Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes the IMEI matches.
I was able to download the file.
Unfortunately, the thing didn't went ok. After flashing my phone is unresponsive, black screen, no more boot
If I connect it to the computer at this point, it tries to search for a QHSUSB_DLOAD driver. Not sure what is that, I think I bricked my phone.
I've seen some guides for unbricking by placing a sd card in the phone at boot but so far it haven't worked

Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.

dawgdoc said:
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
Click to expand...
Click to collapse
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back

Alright! I just tried the SD card method w/ one of the files in the threads linked. Phone boots!
So it seems my bootloader is bad right?

japi2000 said:
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Click to expand...
Click to collapse
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.

dawgdoc said:
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
Click to expand...
Click to collapse
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?

japi2000 said:
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
Click to expand...
Click to collapse
That is the stock recovery. If you were successfully running one of the latest CM11 snapshots, you were probably on one of the three 4.4.2 bootloaders ( and modems ), they are NE4, NJ1, and NJ2. This would explain why the MJB (4.3) image you downloaded and flashed would soft brick your phone. It looks like that flash may be responsible for you being back on stock recovery, at best guess. Before anything else, do a factory reset from the stock recovery. This is frequently necessary to boot when going from a CM/AOSP LP rom back to stock.
Since you can get to download mode, I think the best bet would be to install a custom recovery. TWRP for the i747 is here, the top image is flashable with Odin while in download mode. Remember not to reboot from Odin. Instead remove the cable, pull the battery, then boot straight to recovery. Once you have TWRP loaded, boot into recovery and use the terminal emulator in it to determine bootloader and modem with these commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Once you know the version of bootloader and modem you had been on, reflash that version from TWRP you will probably need the file on an external sdcard to do so. After this you can flash your rom of choice from TWRP, stock or otherwise. Since you were having imei issues go with one of enewman's stock roms, as @DocHoliday77 suggested. He can then help you with the imei issues if still necessary. Any other ideas Doc?

Ok, so
Bootloader = I747UCUEMJB
I don't get anything when running getprop | grep version.baseband in the recovery.
This is what I've done so far.
Booted w/ the sdcard trick (bootloader in the sdcard).
Installed twrp
Installed the following files:
AT&T_I747UCUEMJB.zip
d2att_I747UCUEMJB_bootloader.zip
d2att_I747UCUEMJB_modem.zip
d2att_Kernel_Stock_init.d_4_3_MJB_v1.0.zip
That brought the phone to life again (w/ stock 4.3). Then I flashed CM12 from the recovery. All went ok.
Problem is, I still don't have 3G connectivity, only edge.
What would you recommend try next?
Thank you

Alright, I was able to upgrade to UCUFNJ1 for both the bootloader and baseband. Still no 3G. Ideas?

Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Alright thank you

Alright, I'm happy to say that with the help of our fellow DocHoliday77 I was able to solve the issue !
Thanks everyone!

Glad you have it working.
Way to go Doc.

Damn japi2000. You did that quick good job.

Thank you!
I can't believe I went from a almost dead phone to a fully working one in only a few days, even with the 3G/4G working again !
This forum and people are amazing! Thank you!