Reverting to 4.3 from official 4.4.2 - T-Mobile Samsung Galaxy S 4

I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?

gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though

zz1049 said:
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though
Click to expand...
Click to collapse
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.

gaww said:
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.
Click to expand...
Click to collapse
Reason being is that the boot loader does not permit loading the old version of android onto it. If you update and then tried to flash the old Raum 4.3 it will cause errors and will ask you to reinstall the firmware, which is basically just the recovery part. 4.3 will flash this part of the image but then the rest of it will have problems. A lot of custom ROMs have been out there that run on 4.3 kernels but are running 4.4 ROMs and these are really actually 4.3. In those cases you can easily revert to stock 4.3. However, if you have updated then through Samsung software it will update the boot loader and you will no longer be able to revert.
For AT&T it is available to river, or at least reflash 4.4. I'm sure this will be fixed in time however at this point there is a lock or warning that has not been cracked basically. (Knox counter etc,)

gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
This is what I've read: if you update to official 4.4.2, you cannot flash back to official 4.3 in Odin. Likewise, if you updated to official 4.3, you cannot Odin back to official 4.2.2. If you try to, you'll soft brick. The Knox-secured bootloaders prevent Odin from successfully flashing a previous version.
Now, if you do this and therefore soft-brick, you need to pull the battery and re-enter Odin mode. Then you must Odin-flash a custom recovery (luckily there are some Odin-flashable recovery files out there). Then, after another battery pull, you need to manually boot into your custom recovery and flash a custom rom (or restore a Nandroid). This will save your soft brick.
What we don't know, because it hasn't been released yet, is if the official 4.4.2 tar file would successfully flash in Odin if you already have the 4.4.2 Knox bootloader.

Related

[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] going back to stock after the 4.3 OTA update

I'm currently running beanstalk 4.4.1 rooted with twrp installed. I did the 4.3 OTA update before I went with the custom roms.
what is my options as far as going back to stock 4.3? I've read several threads but non of them were the exact scenario that im in. Any help is appreciated.
Are you running an AT&T phone? If you are, you cannot flash any rom that tries to flash a bootloader that is older than 4.3. If you do, it will brick the phone.
audit13 said:
Are you running an AT&T phone? If you are, you cannot flash any rom that tries to flash a bootloader that is older than 4.3. If you do, it will brick the phone.
Click to expand...
Click to collapse
yes it is at&t. Also I do have my original backup but twrp doesn't recognize it
Why not load a 4.3-based ROM? If you want to go back to stock, you could try using mobile Odin to load a stock ROM.

[Q] 4.4.2 Cyanogenmod to 4.4.2 stock

Okay, so my phone is currently running 4.4.2 Cyanogenmod right now, I had to find out the hard way that I cant jump back to 4.3 due to the bootloader but will it be possible to install the stock 4.4.2 safely once its released? Or is there a way to go back down to 4.3 that I'm missing..
Shiro_Yuki said:
Okay, so my phone is currently running 4.4.2 Cyanogenmod right now, I had to find out the hard way that I cant jump back to 4.3 due to the bootloader but will it be possible to install the stock 4.4.2 safely once its released? Or is there a way to go back down to 4.3 that I'm missing..
Click to expand...
Click to collapse
Don't know how you got the impression you can't go back to 4.3 from Kit-Kat based CM. CM, like most stock ROMs, doesn't come with its own bootloaders but relies on manufacturer's bootloader to run. If you went to CM from stock 4.3, chances are your bootloader was unaffected and still remains at 4.3. You can check what bootloader your phone is on by going to settings and seeing what you have under baseband. If it's UCUEMJB then you have the 4.3 (MJB) bootloader and you should be able to use custom recovery to flash a stock 4.3 restore image.
If history is anything to go by, you would be unlikely to get the (newly released) 4.4.2 update OTA if you are not on a full stock (or stock-based) ROM. I would, however, not be in a rush for OTA as we can always trust the good guys in the development community to come up with a manual update process shortly. If you still want to revert to full stock 4.3, then you can follow the instructions in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
Your right!
Used the process you gave me and it worked, I had been trying to use odin but I supose a simpler solution was better. Thanks again!
I just switched from stable CM10.1 to stock 4.4.2 this week. It sucks. Performance and battery dropped drastically. Will be going back to CFW asap.

[Q] Rooted at Jellybean, no KitKat update from AT&T. How to get KitKat

My galaxy siii was rooted before kitkat was out, and I have been using it until now and have not yet update to KitKat yet because AT&T is not part of it any more.
How do I get KitKat on my phone? Do I have to unroot the phone and put it back into AT&T mode to download or what should I do?
this might help.
remember:READREADREAD
BACKUPBACKUPBACKUP
http://forum.xda-developers.com/showthread.php?t=1802160
good luck
err on the side of kindness
You will need to unroot your phone and have the stock recovery.
Thank you for both replies gentleman
audit13 said:
You will need to unroot your phone and have the stock recovery.
Click to expand...
Click to collapse
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Id recommend flashing the 4.3 firmware via Odin to begin with. Its starting to seem like a lot of people who even just have to unroot are having problems with the ota. I think Odin flashing stock 4.3 will give the best chance of a successful update.
mwrobe1 said:
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Click to expand...
Click to collapse
I am having this issue. I rooted on 4.3 and removed Google books and newsstand. I then uprooted and did a factory reset , so everything in download mode says "official" but the apps were still missing so I downloaded them from the play store. My question is will this let me get the OTA now or do I have to push the apps to the /system directory somehow? Also if I flash the 4.3 ODIN tar file, will it trip my warranty bit? It's at 0 right now and want to keep it that way until my warranty is up.
The firmware shouldn't trip the bit, but I can't promise that. Im sure its confirmed one way or the other in its thread though.
As for those apps, they'd have to be system apps, so just installing normally won't help. More importantly though, they would also need to be the same version that was originally built into the firmware. The apps you mentioned have seen many updates and using the current versions will not work.
I got the phone 2 weeks ago and it came with 4.3 installed on it. Would I be able to use the current version and just push them to /system/app with titanium backup? I am trying to get the OTA without tripping any warranty or security measures.

reverting to 4.1.1

i have the s3 att on a 4.4.4 CROM. the baseband says ...LK3. can i use any guide using odin to go back to 4.1.1 stock unrooted and then use OTA updates to get the latest baseband/bootloader/modem? just want to make sure before i do it. i hear this is the safest way and i want to make sure i have met the requirements before i do it so i dont end up having a brick! (not sure if it matters but i have never used OTA updates before)
thanks in advance.
Is your bootloader also the lk3? If the modem and bootloader are lk3, you can use Odin to flash back to stock using firmware from sammobile.com.
Ok, I'm on a similar boat. I tried several AOSP based ROMs, and while I like most of them a lot more than stock touchwiz, they all present the same problems:
- Camera stops working sometimes and I have to reboot device;
- Camera won't record videos in 1080p, even when it's selected in the settings;
- Cannot make video calls on Skype longer than 5 seconds before the call drops;
- Disconnecting a bluetooth media device while music is streaming causes sounds to stop working;
- Tap to pay doesn't work at all;
So because of these problems, I want to go back to stock . My phone is the AT&T version. Currently I'm running Carbon Rom with KitKat 444. The baseband version is I747UCUFNJ1. The latest version of the stock ROM available on sammobile is:
Version: Android 4.1.1
PDA: I747UCDLK3
CSC: I747ATTDLK3
MODEM: I747UCDLK3
Would I be able to revert my phone back to stock with Odin? If not, what would I have to do to revert? Am I stuck with custom ROMs?
I'm pretty new to this so I'd appreciate anybody's help.
If your bootloader and modem is the lk3, you should be able to Odin back to stock 4.1.1.
Ok, how do I find out if they are? And if they are not, do I have any other options?
Download and install the Samsung Info App from the Playstore. Report back here with your bootloader and modem.
audit13 said:
Download and install the Samsung Info App from the Playstore. Report back here with your bootloader and modem.
Click to expand...
Click to collapse
Ok, according to the Phone INFO *Samsung* app:
Baseband Version:
I747UCUFNJ1
Bootloader Version:
I747UCUFNJ1
There was no other modem info reported besides this
Modem Board:
MSM8960
someone correct me if i'm wrong.you cannot downgrade bootloader or it will brick. there is no stock rom for NJ1. this link will take you to a stock based 4.4.2 ROM which is safe to flash with the NJ1 bootloader/modem.
http://forum.xda-developers.com/showthread.php?t=2848080
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
someone correct me if i'm wrong.you cannot downgrade bootloader or it will brick. there is no stock rom for NJ1. this link will take you to a stock based 4.4.2 ROM which is safe to flash with the NJ1 bootloader/modem.
http://forum.xda-developers.com/showthread.php?t=2848080
Click to expand...
Click to collapse
Well, that's a bummer if I can't restore stock rom to the phone. So there is absolutely no way of safely downgrading the booatloader?
nope. it will brick your phone if you try to downgrade your bootloader.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Have you tried CM-11-based or TW-based ROMs?
mrrocketdog said:
someone correct me if i'm wrong.you cannot downgrade bootloader or it will brick. there is no stock rom for NJ1. this link will take you to a stock based 4.4.2 ROM which is safe to flash with the NJ1 bootloader/modem.
http://forum.xda-developers.com/showthread.php?t=2848080
Click to expand...
Click to collapse
I tried to push that ROM the phone using adb to flash it with ClockWorkMod, but the file is 1.7 GB and the phone always shuts itself down during the push process... So I wasn't able to try that. Also, the instructions say you're supposed to be on UCUFNE4. Are you sure it's safe to flash it on I747UCUFNJ1?
audit13 said:
Have you tried CM-11-based or TW-based ROMs?
Click to expand...
Click to collapse
I have tried CM11 and Carbon ROM, which is CM based, both have all the same problems. I haven't tried TW-based ROMS. Do you have any suggestions?
What do you mean by the phone shuts down? Did you try copying the ROM to a microSD card?
Did you notice any bootloader or modem files in the S3Rx 4.0 (11-9-14) ROM? It may not include a modem or bootloader. In step 1 of the flash process, it says "AT&T I747 users should update bootloaders and modem to NE4 http://forum.xda-developers.com/gala...pdate-t2808654 I747M and T999 users need to be on 4.3 firmware or ROM will not boot. "
the link i posted is TW. post #1306 claims is o.k. to flash with UFNJ1.
did not see any mention of bootloader or modem in changelog or in list of 'extra' features.
"all i can really do , is stay out of my own way and let the will of heaven be done"
audit13 said:
What do you mean by the phone shuts down? Did you try copying the ROM to a microSD card?
Did you notice any bootloader or modem files in the S3Rx 4.0 (11-9-14) ROM? It may not include a modem or bootloader. In step 1 of the flash process, it says "AT&T I747 users should update bootloaders and modem to NE4 http://forum.xda-developers.com/gala...pdate-t2808654 I747M and T999 users need to be on 4.3 firmware or ROM will not boot. "
Click to expand...
Click to collapse
I reboot the phone in ClockWorkMod recovery. Then I go to the command prompt and type:
Code:
adb push S3Rx_UCUFNE4_AROMA_11-9-14.zip /sdcard/
It starts pushing the file to the phone, but after a while, the phone screen goes black, and I get a "Protocol failure" on the command prompt. After this the power button no longer works, I have to do a battery pull for the phone to work again. The phone has 10 GB of storage left so it didn't run out of space. The USB chord is brand new so I don't think it's that either. It worked fine before when I pushed other smaller roms.
In another question, would this process allow me to downgrade the modem and restore stock rom?
http://forum.xda-developers.com/showthread.php?t=1831898
i am pretty sure that since youre on MJ1 , your bootloader and modem have to match.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Did you try flashing the card from an external microSD card?
AT&T never released a stock ROM for the i747 beyond 4.1.1 afaik; therefore, you cannot get back to stock unless you flash an OTA ROM that has been compiled for flashing in Odin.
I do not recommend mixing and matching bootloaders and modems as a mismatch may result in a hard brick.
Downgrading only the modem will not allow you to flash back to stock.
audit13 said:
Did you try flashing the card from an external microSD card?
Click to expand...
Click to collapse
I haven't tried flashing from external microSD card as I don't have one.
audit13 said:
AT&T never released a stock ROM for the i747 beyond 4.1.1 afaik; therefore, you cannot get back to stock unless you flash an OTA ROM that has been compiled for flashing in Odin.
I do not recommend mixing and matching bootloaders and modems as a mismatch may result in a hard brick.
Downgrading only the modem will not allow you to flash back to stock.
Click to expand...
Click to collapse
So you're basically telling me I'm stuck with custom roms unless I find a 4.4.2 OTA ROM I can flash with Odin (which doesn't appear to exist)?
---------- Post added at 05:24 PM ---------- Previous post was at 05:01 PM ----------
Would it be safe to try this:
http://forum.xda-developers.com/showthread.php?t=2788357
Even though I'm on I747UCUFNJ1 and not on I747UCUFNE4?
Once you upgrade to the 4.3 or newer bootloader on the i747, you are stuck with either custom ROMs or OTA ROMs that have been compiled for flashing in Odin or CWM/TWRP.
You can try flashing the NE4 ROM because it doesn't appear to include a bootloader or modem. The first post says "Prerequisites include a minimum of a 4.3 bootloader and modem.
If you are not on the official 4.4.2 bootloaders and modem then you will need to flash ktoonsez kernel."
Thanks audit13 and mrrocketdog for all the help. I was able to get the AROMA rom installed on the phone. All functionalities lost with AOSP ROMs are back working so that's a plus. Still can't get updates OTA updates but this phone is probably not gonna have any new ones. Still hopeful that lolipop based AOSP ROMs fix the problems I had, but I'm not holding my breath.

Categories

Resources