Develop Bugs

[Q] update of stock rom led to recovery failure

Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:

rezaasl2000 said:
Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
Click to expand...
Click to collapse
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage

hednik said:
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
Click to expand...
Click to collapse
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?

rezaasl2000 said:
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
Click to expand...
Click to collapse
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426

hednik said:
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.

rezaasl2000 said:
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
Click to expand...
Click to collapse
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.

rezaasl2000 said:
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
Click to expand...
Click to collapse
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?

hednik said:
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
Click to expand...
Click to collapse
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?

rezaasl2000 said:
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
Click to expand...
Click to collapse
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium

hednik said:
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So, I finally figured it out. I used the samsung galaxy s3 toolkit to install the stock firmware and then I updated it on the phone. Next, I went back to the toolkit and installed the most recent version of CWM on it and everything just worked beautifully. I have LiquidSmooth installed and it works just great.
thank you for the help hendik.
:good:

[Q] Official 4.3 Upgrade Issues

I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!

phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...

Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.

As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2

I had the same problem
I just had this same problem and was lucky enough to fix it!!!!

vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l

I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you

vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it

Have you tried the auto root course??
Sent from behind you

Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.

Co-author root didn't work, and nor did Root66

I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!

This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.

DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?

You can try first wiping just dalvik and cache, then try factory reset.

Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.

I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.

I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?

DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?

bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk

[Q] Plz Help 4.3 down to 4.1.2. rooted tried a few

So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon

mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.

eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.

mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.

eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery

this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones

smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.

[Q] Trying to downgrade from 4.4.2 (Cyanagenmod 11) to 4.1.2 stock (T999UVDMD5)

As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?

huz666 said:
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
Click to expand...
Click to collapse
If you are getting errors in both odin and cwm, it sounds like it is a root issue. In other words, it sounds like the apps are being denied access to root and therefor cannot flash. Both odin and cwm are able to generate logs so you can tell the reason for the fail. Personally, I would recommend flasing twrp recovery instead of cwm since it seems to simplify alot and is a little better for our device. Without knowing exactly why the flash is failing, i would just recommend to try and re-root the phone again.

Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.

Perseus71 said:
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Click to expand...
Click to collapse
Yes the phone was in downloading mode. I couldn't find any posts that thought that I would brick my phone for sure by downgrading so I thought I would try. Could I go back to the 4.3 Stock ROM with some degree of confidence?

Yes you can go back to 4.3 Stock.

Perseus71 said:
Yes you can go back to 4.3 Stock.
Click to expand...
Click to collapse
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.

huz666 said:
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
Click to expand...
Click to collapse
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk

serio22 said:
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
.
Thanks for the advice. I think I'll just quit while I'm only slightly behind now and remain on 4.3 Stock. I appreciate everyone's help and suggestions.

Downgrade from CM11 4.4.2 to 4.3 on I747
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747

You seriously need to do some reading
Sent from my SGH-T999 using Tapatalk

nitagro said:
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
Click to expand...
Click to collapse
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.

Perseus71 said:
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Click to expand...
Click to collapse
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.

nitagro said:
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
Click to expand...
Click to collapse
Please Read through this Thread. For Future Reference, all Odin Files for S3 in general are looked up by unique Keyword Root66. That thread is the right place for you to post errors or issues. If there's no 4.3 image for your phone there, you can post a request as well.
For your immediate Problem, there is a an alternate ATT StockMod Rom by @saranhai Please see this thread. Pay particular attention to the mandatory requirement of flashing a particular modem beforehand.

Bricked my S4 SGH-M919 :( Please help?

Hi all,
I've kind of backed myself into a corner here after a bit of "experimenting"
I just purchased an S4 SGH-M919, came with stock 4.2.2 Jellybean.
- Opened it up and rooted it via auto-root + Odin.
No issues.
Then instead of manually flashing a rom, I downloaded a play store app called 'Recovery Tools', and tried to flash TWRP onto the phone.
-Stuck at Samsung screen with blue 'booting recovery...' forever.
I then (stupidly?) tried to flash 4.4.2 onto the phone. *not sure if this is stupid because I read T-Mobile has an unlocked bootloader?
So flashing 4.4 T-Mobile Galaxy S4 Stock Firmware (4.4.2 - M919UVUFNB4) PASSES with odin, but the phone is still 'messed up'.
I can access recovery mode, but the phone will not boot past the 'Samsung' logo, and even after a factory data reset and deleting users.
I've also tried flashing back to 4.2.2, and odin fails.
Please help I can't afford another device and I'm now phoneless. Not sure where to go from here and could really use some direction..

Just adding that I think this happened because I accidentally flashed the most recent version of TWRP which doesn't work on the s4.
At this point I can't get any stock ROM to load.
Any idea folks? Any guidance greatly appreciated here..

You might want to try installing one of the cm or aosp based jflte roms. they seem to load easier. After that you can try another rom if you need to. Make sure you are giving it enough time to boot up the first time after a flash. It can commonly take 10 minutes for a stock touchwiz rom to load first time around. Edit: or just odin the stock nk2 firmware from here and start over. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508

ultrafta said:
You might want to try installing one of the jflte roms. they seem to load easier. After that you can try another rom i you need to. Make sure you are giving it enough time to boot up the first time after a flash. It can commonly take 10 minutes for a stock touchwiz rom to load first time around.
Click to expand...
Click to collapse
Screen just goes black, IF it gets past 'Samsung' logo, depending on what build I'm flashing. I was once able to get all the way into setup, then the phone completely went black again. Pretty sure it's not a hw issue because the phone was working fine until I started all of this.
Can I just load a jflte rom via Odin? That's about all I'm able to do currently.

At this point I would odin nk2 firmware. after that odin twrp.

ultrafta said:
At this point I would odin nk2 firmware. after that odin twrp.
Click to expand...
Click to collapse
Okay Ultra, appreciate your advice - I'll try this now.
To confirm - after flashing nk2, should the phone be able to fully boot? Or will I have to twrp first before I can expect it to fully boot?
Thanks again

It will boot without twrp
---------- Post added at 11:06 PM ---------- Previous post was at 11:02 PM ----------
Make sure you are using a very good condition usb cable. I've had some serious odin frustrations due to a poor usb cable

ultrafta said:
It will boot without twrp
Click to expand...
Click to collapse
That worked. Thanks so much!
Now I've already rooted with cf-auto once again, I shouldn't have any problem loading TWRP now right?

Right. Should be good to go

Stay away from twerp, use CWM it's more reliable and it won't brick phones. Those extras cooked into twrp make it flaky.
Pp.

VeryHappySlug said:
Hi all,
I just purchased an S4 SGH-M919, came with stock 4.2.2 Jellybean.
...[...]...
So flashing 4.4 T-Mobile Galaxy S4 Stock Firmware (4.4.2 - M919UVUFNB4) PASSES with odin, but the phone is still 'messed up'.
I can access recovery mode, but the phone will not boot past the 'Samsung' logo, and even after a factory data reset and deleting users.
I've also tried flashing back to 4.2.2, and odin fails.
Click to expand...
Click to collapse
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?

XDAUserWork said:
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?
Click to expand...
Click to collapse
Guys.. my battery was dead the entire time.
All is resolved.
*Slithers away*

XDAUserWork said:
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?
Click to expand...
Click to collapse
No. That is not how it works

ultrafta said:
No. That is not how it works
Click to expand...
Click to collapse
Would you please elaborate on the reason for how it does not work that way?
Specifically, would you recommend what way you would go about it?

XDAUserWork said:
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?
Click to expand...
Click to collapse
XDAUserWork said:
Would you please elaborate on the reason for how it does not work that way?
Specifically, would you recommend what way you would go about it?
Click to expand...
Click to collapse
Read the first post. He odined 442 to it. You cant go backwards. After that point it is best to just update to the latest complete firmware bootloader and all, just as he did and succeeded.
---------- Post added at 02:26 PM ---------- Previous post was at 01:45 PM ----------
Everthing over 4.3 has knox bootloader. and prevents downgrading. However i don't know why anyone would want to run 422 these days. The phones run smoothest with the latest nk2. And everyone overreacts about the m919 knox bootloader.

ultrafta said:
Everthing over 4.3 has knox bootloader. and prevents downgrading. However i don't know why anyone would want to run 422 these days. The phones run smoothest with the latest nk2. And everyone overreacts about the m919 knox bootloader.
Click to expand...
Click to collapse
Indeed, however if someone strongly preferred to downgrade from 4.4.2 (M919UVUFNB4) to 4.2.2 (M919UVUAMDL) would they need to first flash the 4.4.2 bootloader with the 4.2.2 bootloader, thereby replacing the 4.4.2 bootloader with the 4.2.2. bootloader, in order to then allow Odin to successfully flash from 4.4.2 (M919UVUFNB4) to 4.2.2 (M919UVUAMDL) - is that correct?