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!
Related
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.
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!!!
So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.
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.
Okay so have a I747 AT&T Galaxy S3. Had CM13 running fine on NE4 baseband. Decided to upgrade baseband and flashed NJ1 then NJ2, rebooted and everything was fine.
Well then I decided to check out a different ROM, and tried installing these via recovery and then I get stuck on that AT&T splash screen:
d2att_I747UCUFNJ2.zip (didn't work) so then d2att_I747UCUFNJ2_Deodex_Rooted_KnoxFree_Debloated.zip
I thought I was able to install those since I just upgraded my baseband, but my phone did not like it!
I also noticed that in download mode, in red there was a "warranty bit: 1", not sure if that's relevant?
So I can still get into download and recovery, but any restoring CM13 from backups or return to stock results in a bootloop. How can I get CM13 back?
Can I flash back to stock with Odin and start over to fix this? Is this the file I should use?= I747UCDLK3_I747ATTDLK3_ATT.zip or this one?= I747UCUEMJB.zip
Or will those brick my device since I'm quite certain I'm on NJ2 firmware?
OR should i try reinstalling a certain CM version with certain gapps?
What can I do? I'm really freaking out here, everything I have is on 2fa! Please help!
Was the bootloader updated when the baseband was updated?
turns out im just an idiot and installed the wrong gapps.