So, my issues just started today. I was rooted but went back to the MC2 rooted restore. After the successful restore I made a mistake and clicked yes for the System Update. Then the problems came. The phone was stuck in factory mode. I researched and it told me to go to efs under Root Explorer. I did that but it said the phone wasnt rooted. Tried to restore it again. Now I'm getting the Kies firmware upgrade encountered. Did my research and fixed that. How do I get back to a rooted phone?????? I still get the black box with yellow writing saying factory mode. Please help!!!!!!!!!!!!!!!!!!!!!
Need more info:
1. MC2 rooted restore?
2. What is factory mode?
3. Are you on 4.3?
You could try this......ODIN TWRP and follow @billard412 guide to getting back to stock unrooted. Then ODIN TWRP again and flash a custom ROM of your liking. Hope this helps in getting back to a rooted phone!
92bubble said:
So, my issues just started today. I was rooted but went back to the MC2 rooted restore. After the successful restore I made a mistake and clicked yes for the System Update. Then the problems came. The phone was stuck in factory mode. I researched and it told me to go to efs under Root Explorer. I did that but it said the phone wasnt rooted. Tried to restore it again. Now I'm getting the Kies firmware upgrade encountered. Did my research and fixed that. How do I get back to a rooted phone?????? I still get the black box with yellow writing saying factory mode. Please help!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Agreed with flynhawn2002 Where are you coming from with your phone setup. Did you just wanted to root the stock? Or what ROM did you wanted to flash? We need the specific so we know exactly what you were attempting to accomplish. Hang in there!
Sorry about that. Yes its now on 4.3 MK4 after I clicked yes for the system update by mistake. Yes Id like to go to the MC2 rooted restore. But Ive tried and it wont work. 20% into the download mode it'll say failed on the odin and back to the Kies firmware encountered bull****. Then I have to go to Kies and restore the firmware all over again.
I just want to go back to a rooted restore. After that Im good to go. Oh yea. I put TWRP recovery on it through ODIN successfully.
ok....if you had issues following my above recommendation then you can follow lorjay589's guide to get stock rooted. FYI, you need to remove KNOX before installing SuperSU or youll have issues.
fixed...thanks alot people!!!
Rooted/Flashed my phone a long time. Constant bugs and errors. I really don't remember what all I did but I think I almost have it completely unrooted and back to stock. However, I can't update OTA. I've reflashed using this file, http://forum.xda-developers.com/showthread.php?t=2658486. Fixed just about all my issues and I actually have a lot of space on my phone. When I try to do the OTA Update, it doesn't install the update. Once it boots into recovery mode to install the update it gives an error. Can someone help my to 100% fully get my phone back to stock and be able to install OTA updates? I'm clueless.
First, did the 4.4.2 ota fail after a certain percentage? If so you may actually be partially updated already. If so, flashing MJB firmware/bootloader will hard brick.
Install and open Terminal Emulator and enter this:
getprop ro.bootloader
If it says MJB, you are still on 4.3 and can refresh that. If it says NE4, do not flash MJB!
If you can still flash MJB, there is a thread in General (I think that's where) that has the Odin flashable firmware package. Flash that with Odin and factory reset. Then try the OTA.
Factory resetting with stock recovery installed will wipe internal sd card, so back up first!
There are also a few threads in General that can help you update if the OTA continues to fail.
I'm unrooted. At least im pretty sure of that. I cant run superu anumore and root checker says im not rooted. Can I still access the terminal without being rooted. I know I had clockeork mod recovery. I also had used cyanogen mod at one point. Now I have the stock recovery but when I boot into recovery I get an error. I will post the error and install percentage as soon as the ota update downloads.
Yes, you can still run getprop w/o root. Just install terminal emulator by jackpal from the play store.
Yeah it said I747UCUEMJB. Like I said my recovery gives me an error. When I try flashing at all with odin it fails. Trying to install the ota update now. After it fails ill give the error recovery gives me. OTA update fails at 24%
Ok, booting into Android system recovery gives me a no command error than it shows the list of options. When I go to reboot system now, it gives me a no command error as well. Download mode used to give me an error, might only show up when attempting to flash something. However, these are the details of my ODIN Mode right now.
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary Custom
System Status: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
When you try to flash the firmware with Odin, what does it say in the message box?
Have you tried flashing TWRP via Odin?
A lot of people seem to be having issues with the OTA failing at 20-something percent. No idea why though. I know some found that their firmware was partially updated afterwards though, which is why they couldn't flash with Odin. Need to know what odin says about the failure to know for sure though.
You might need to factory reset btw.
I've already did a factory reset when I flashed this latest rom from that thread I posted.
Point me in the right direction of the firmware I need. I've got AT&T btw.
Try MJB firmware again. Im assuming that's what you tried to flash with odin earlier right? When/if it fails again, copy the text from the message box and paste it here.
So you want me to try flashing using Odin with that firmware I provided in that link? Like I said, ODIN on the pc gives me an error. I'll provide the error later when I get off work. Before I just put the firmware on my sd card, went into refovery mode and installed it from there.
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
I'll try ut as soon as I get home from work and posy my results. Thanks for the help so far!
Wow I think one of the reasons I couldn't use ODIN after trying to unroot, is because I never had turned on USB Debugging mode. You wanted me to just go through Step 4 for right now right? Just to get back to stock 4.3 AT&T S3 like right out the box?
Thanks so much Doc. After following step 4 on that thread I was able to Ota update!
DocHoliday77 said:
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
Click to expand...
Click to collapse
Been using my newly updated S3 and now the Touchwiz Home stops on startup and resets my default app settings repeatedly. Not sure what's the deal, tried suggestions on diff sites and am trying a factory restore, wipe date, and wipe cache partition. Any clue how to fix this?
PS: Seen in Android System Recovery it says KOT49H.I747UFNE4. Should that be I747UCEMJB since that's what mine is and recovery still gives me no command when I start it up?
You said you had updated with the OTA so NE4 would be correct.
As for recovery, if you want to keep stock recovery, enewman17 has it available in one of his threads (in development section I think). Redland that by itself and it ought to be good to go.
Otherwise, use Odin to flash TWRP recovery.
Factory reset should take care of the launcher/home issue you mentioned. You may not be able to though since it sounds like recovery is corrupted. Fix recovery as I said above and then try the reset.
If you factory reset with stock recovery installed, it will wipe your internal sd card. With custom recovery it will not.
You could also try clearing data for Touchwiz Home in application management.
I am having issues updating OTA too. It gets to 100% and then says my phone will reboot in 5 seconds, then it reboots and some at&t logo with a % counter comes up, that gets to 100% then it reboots into Android and it still says 4.3...what am I doing wrong? Anyone have any advice? Many thanks if so.
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
DocHoliday77 said:
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
Click to expand...
Click to collapse
I am trying to update by going to settings --> more --> about device --> software update. Not using a thread, no. I was rooted and uninstalled google books and newsstand then unrooted and did a factory reset in stock recovery because I found out that if you are rooted the OTA update won't take. I am 100% bone stock now except for the 2 bloatware apps I uninstalled. I have since reinstalled them via the play store , but I hear they need to be system apps?
They do, but they also need to be the same versions that were originally included. If you get them from the store they'll be updated and will cause the ota to fail.
OK. Long story of how I got here but I have CWM 6.04.7.
I had been running CM11 with UCUEMJB radio and whatever bootloader was on it initially.
I need Airwatch for work. On CM11 Airwatch with xPosed/Rootcloak would still detect root. So I went stock. My intention was to test the rooted stock rom to see if it would work with Rootcloak and Airwatch. After two OTAs to get to KK, I made a backup in CWM.
Rooted. Installed xPosed, Rootcloack and Airwatch. Airwatch saw that I have root so I went back to CWM to flash my backup.
Backup 'works'. I now have no phone functions nor IMEI. I spent a few hours trying to fix that with NV Tools and EFS Professional to no avail. 'SPC check failed' or something to that effect with NV Tools. EFS Professional requires a rooted phone. Circular issue here. alright. Flash CM11 back on. Everything works.
Great, right? Well, I still need to get back to stock and I have no image that I can flash to my knowledge. My backup has something broken/missing and everyone says that once you go UCUEMJB+ OTA a downgrade will brick.
TLDR - I need someone to tell me that it is ok to flash the factory image again. If that is not ok, I need a clean, unrooted UCUFNE4 full image to flash.
Thanks in advance!
I have been reading through many threads last night and today trying to figure out the best way to get rooted stock back on my AT&T S3 i747. I had hoped to figure it out myself, but have come to the realization that I need a little guidance.
In light of that, I'll try to give concise information. First of all, I am simply looking to end up with stock.
Series of events:
*Have had stock since given this phone in August; it was kept up to date with OTA and it was current (4.4.2) as of yesterday morning when att pushed the newest update to the phone.
*I rooted the phone in September using CF root and Supersu to both root and block Knox and it had been working very well until the attempted update yesterday.
*I no longer have a custom recovery backup
*yesterday my phone went through the update (download and install), but when it rebooted, it only made it through the Samsung splash screen and then went black.
*I am able to boot up both stock recovery and into download mode
*Using the stock recovery to reset the phone has not fixed the problem
Having never used Odin or installed a custom ROM, I am hesitant to flash anything to the phone until I verify that the new bootloader (that is now possibly there due to the OTA update) and anything I try to install won't conflict and make my problem worse.
It seems to me that I should use Odin to load a custom recovery, make a backup, and then flash a ROM. If that is correct, would the recovery ROM found in this thread be the correct one: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
If it is not the correct ROM, what would be the correct one?
Thank you,
M
For a custom recovery, flash the most recent tar.md5 file from here using Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Boot into recovery, create a backup, and flash a custom ROM. I recommend the most recent CM10.2 so you can determine the bootloader currently installed on your phone. Once you determine the bootloader, you can decide how you want to proceed.
Thank you so much for your response.
I did as you suggested and I do indeed have the UCUFNJ1 bootloader. That does help me determine which direction I can take. Although, now having tried out a non-Samsung ROM, I may have changed my mind about keeping stock on the phone. If I decide to go back to stock, I'll just keep my eyes open for a stock ROM that states it requires that bootloader, correct?
Again, thank you so much for your help!
Was trying to get the phone back to stock so I can upgrade. I followed the instructions on the How to Return a Device Back to Stock thread, downloaded the stock TAR, rebooted and tried to boot into recovery but it would not let me. I then tried to boot into the device as normal and now I have a screen with the message Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again. Any suggestions? I downloaded and tried but cannot connect via Kies 2.6.. I can still get into the device via ODIN. Suggestions?
What firmware did you use to flash? Flash NH7 if you haven't
A little back-story and a possible solution.
demonr6 said:
Was trying to get the phone back to stock so I can upgrade. I followed the instructions on the How to Return a Device Back to Stock thread, downloaded the stock TAR, rebooted and tried to boot into recovery but it would not let me. I then tried to boot into the device as normal and now I have a screen with the message Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again. Any suggestions? I downloaded and tried but cannot connect via Kies 2.6.. I can still get into the device via ODIN. Suggestions?
Click to expand...
Click to collapse
I've never updated my S4 past the MDL firmware. I encountered this problem a few months back when I wanted to revert back to 100% stock MDL. I had updated my baseband/modem though to NB4, yet still obviously had the MDL bootloader. I was scared to death that I had bricked my phone because nothing I did would let me boot past that screen. I couldn't get to recovery, normal boot, nothing... the phone would just automatically go to that screen: Firmware upgrade encountered an issue.
What I did was simply revert my baseband/modem back to MDL. Once that was done successfully I was able to flash the MDL firmware again and booted right up. If this might be your issue, you will have to know which baseband/modem you were using and which bootloader version you were running before you attempted to flash stock. It should go without saying that the main idea here is to have your baseband and bootloader versions match before flashing the firmware in Odin.
Seems a little odd to me as the stock Odin-flashable firmware includes the modems and all... I'm just passing along what worked for me when I had that problem.
lordcheeto03 said:
I've never updated my S4 past the MDL firmware. I encountered this problem a few months back when I wanted to revert back to 100% stock MDL. I had updated my baseband/modem though to NB4, yet still obviously had the MDL bootloader. I was scared to death that I had bricked my phone because nothing I did would let me boot past that screen. I couldn't get to recovery, normal boot, nothing... the phone would just automatically go to that screen: Firmware upgrade encountered an issue.
What I did was simply revert my baseband/modem back to MDL. Once that was done successfully I was able to flash the MDL firmware again and booted right up. If this might be your issue, you will have to know which baseband/modem you were using and which bootloader version you were running before you attempted to flash stock. It should go without saying that the main idea here is to have your baseband and bootloader versions match before flashing the firmware in Odin.
Seems a little odd to me as the stock Odin-flashable firmware includes the modems and all... I'm just passing along what worked for me when I had that problem.
Click to expand...
Click to collapse
I'll repost from another hoping this explains it as it is the only thing I can think of.. but it worked.
TLDR: installed stock TAR not stock TMO TAR, updated (stupid me) to 4.3, wrong baseband and recovery did not go back to stock using the stock TAR and the Philz Touch recovery would not have flown to return the phone. I figured it out with some help though!
Thank you, that was it. I returned it to stock after following the instructions in the how-to thread but something happened and it boned the recovery where it would reboot into the device every time. Being they need to inspect the phone and in my case they wiped it in front of me when I turned it in it had to be fixed. The device received the updates from TMO and stupid of me I installed them so it was now 4.3 hence the reason I could not install the stock 4.2 anymore. I found the stock firmware you mentioned above and installed it and it fixed it but tripped the counter. I installed the updates from TMO and it was enough to pass inspection. I was able to go into recovery at the store, show the clerk while he was dicking around with the paperwork for the Note I was about to buy. I reached over, showed him "look here it is in recovery and here is wipe data factory reset okay?" and wiped it. He muttered okay thanks or something like that and we were golden. Heck if he could have read the counter anyways it is so flipping tiny.
Thanks for the suggestions!