Hi All,
So 2 years ago I went to cyanogenmod 10.2, twas great, but I am looking to return to a stock phone. I was able to reset the binary counter, but I can not seem to be able to flash any of the stock t-mobile s3 roms or recovery roms i have found, I just get failed errors. I was able to restore my phone to the original cyanogenmod upgrade I made using a nandroid backup, but I have not clue how to step back to stock samsumg s3 t-mobile.
Any help would be greatly appreciated, especially as I managed to temporarily softbrick my phone last night, I was finally able to fix that by re-flashing CWM Recovery using Odin.
Thanks
PS: on this current backup I am on, I am not getting any network access, just wifi.
You can use ODIN and follow the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=1771687
The stock recovery image is listed as well. You may have also lost your imei.
mycomputerisjunk said:
You can use ODIN and follow the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=1771687
The stock recovery image is listed as well. You may have also lost your imei.
Click to expand...
Click to collapse
Thanks, phone works like a phone again!!!
Related
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.
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks
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!