I recently installed CyanogenMod 11 on my S3 about a month ago. Yesterday, I got a notification on my phone stating that an update was available for CyanogenMod. I let it install and when the phone rebooted, it was stuck on the bootloader for at least an hour or two. I figured that I must've bricked the phone. I can still get into recovery mode and download mode.
So, I tried to reinstall the stock AT&T GS3 ROM as I had never particularly liked CyanogenMod. I thought this would be a great time to reinstall the stock ROM. I factory reset the phone and flashed the stock ROM (which I downloaded from another thread) using Odin. It automatically rebooted, the Samsung logo flashed for a second and the CyanogenMod bootloader showed up and it has not gone away since. So, what have I done wrong here and is there a way to save my phone? Any help would be greatly appreciated.
Where did you get the ROM you flashed? Did your phone have the 4.3 bootloader? What about Knox?
If your phone has the 4.3 bootloader, you cannot flash the 4.3 ROM via Odin as it was never released as a complete ROM, only as an update. THis might help: http://forum.xda-developers.com/showthread.php?t=2658486
Related
Recenttly i got a note 2 sch-i317 phone. It was runing the stock 4.3 update from att.
I am on tmobile, so i downgraded the phone to 4.1.1 and unlocked it.
Life is good and the phone is working fine.
then i get the great idea of upgrading back to 4.3 via the OTA update. And there starts all of my issues.
Orignaly i was under the impression i had used a stock att 4.1.1 to downgrade. now looking back i used a rooted version. i dont remember where i found it but here is the name of the file: root66_ATT_I317UCALJ2.tar.md5 (and i had to do a factory reset to get it to boot correctly)
Now here is the issue.
I can not get back into the recovery menu. However i can get into the Download mode.
Tried to flash TW recovery
Tried to flash CWM recovery
Tried to flash I317UCAMA4_I317ATTAMA4_ATT firmware
Tried to flash I317UCALJ2_I317ATTALJ2_ATT Firmware
i installed Kies and installed the usb driver it came with.
At first it did not detect my phone. now it detects my phone. but during the emergency repair, it downloads and extracts the new firmware but sits at 0% (and times out) when it pushes the firmware.
Im at a lost. i have spent 14+ hours in the past 2 days working on this, and i am burning out. help
re-flashed I317UCALJ2_I317ATTALJ2_ATT Firmware
and followed this
http://forum.xda-developers.com/showpost.php?p=49098941&postcount=2
and my phone works again
Woo Hoo !!!!
More goodness here.
http://forum.xda-developers.com/showthread.php?t=2618447
So This is my first time posting on any forum site for help, and i was refereed to XDA by my roommate. so what happened is a few months ago i asked my roommate to root my galaxy s3 SGH-I747, after he rooted it through odin and all seemed well, BUT we never could get the phone to recognize the root and was still unable to access any root functions. so after a few different attempts we gave up. i assumed that my roommate had removed the root (bad call) but never gave it any thought. a few days ago at&t started bugging me with a software update. i just hit ignore and it would pop up again in a few hours and the icon would never go away. so i gave in and started the update. i didnt pay the phone any attention while it "updated" but later that morning i went to turn it back on and it would get to the Samsung screen then the next screen but after that it goes black and vibrates. i showed it to my roommate and he informed me that it was never restored back to official frimware like i had previously assumed. and that it never should have received the update bc it was still on a custom frimware. we tried flashing the stock frimware back on the phone and every time it would fail the nand write. i believe it was updated to 4.4.2 before i received the update from AT&T and we tried many different ways too restore it i even tried the recovery in Kies 3 but all it says is "connecting" then connection failed. so far nothing has worked. i believe that the update contained android 5.0 and maybe that is the reason none of the other ways we tried worked. i have been researching for hours trying to find a similar case but nothing matches, and i cant find a single working solution that doesn't involve possible making it worse. i can access both the recovery and download modes. please any information or help would be greatly appreciated.
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
audit13 said:
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
Click to expand...
Click to collapse
firstly, thanks for the fast help. i did as you advised and flashed philz touch 6.15.4 which is the latest version from what i understand. that worked flawlessly. the problem now, is with cm10.2 every time ive tried to install it i get an error in /storage/sdcard1/cm-10.2.0-d2att.zip.
im sure im doing everything correctly. any ideas?
Try flashing an older CM11 ROM for the d2lte.
audit13 said:
Try flashing an older CM11 ROM for the d2lte.
Click to expand...
Click to collapse
thanks so much man youve been a big help that worked.
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
lsiravi said:
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Click to expand...
Click to collapse
lsiravi said:
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Click to expand...
Click to collapse
Nope! No go!!
Triangle away reset the counter.
The stock recovery works well. I was able to boot to recovery and wipe the data and all that.
Odin says "SW Revcheck Fail" when trying to download the stock rom.
I rebooted into Lollipop, downloaded Triangle away again and reset the counter. Still Odin fails with the same message.
I tried flashing ROM first then the recovery as it was suggested in that link. Nope. Again "SW Revcheck fail". For the record, my SWREV appears to be 3. It is supposed to be 0. Triangle Away does NOT reset this. It did reset another counter (as reported by Triangle away itself - was 5, got reset to 0).
I remember *this* was the problem previously as well, hence the original Q:
How *do* you get back to stock from Lollipop on the Galaxy S3/ATT?
Meanwhile, although Keis failed to recognize the device, I tried to run a firmware recovery manually. It took a long time and in the end failed. It also messed up the recovery, so I had to flash CW again to make it bootable. I'm still back up with Lollipop at this point, but I don't want Lollipop.
Anyone anything else I can do? Any other guide out there to downgrade?
Thanks again
L
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
audit13 said:
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
Click to expand...
Click to collapse
Right. I finally figured it out.
First the 4.1.1 FWs weren't flashing (in other words SW REV CHK FAIL) was basically indicating that my Bootloader was far ahead of the 4.1.1. I dropped 4.1 after I figured that part out.
Next, I tried to flash a 4.4 (UCUFNE-rooted-odex is available as a zip-flash) through CWR, which didn't work (no boot, stuck at splash).
Next I got hold of a 4.3 (UCUEMJB-2024954-REV04-user-low-ship), which successfully flashed through Odin (repartition checked), but there was no sound, IMEI indicated null. Service Mode yielded a blank screen.
I flashed TWRP through Odin (was working on CWR since the beginning) and then flashed the UCUFNE-rooted-odex above on top of 4.3 through TWRP, which was successful, still no sound/IMEI/service mode.
Finally I got hold of the UCUFNE-Modembaseband zip (a small one - 20MB) and flashed that through TWRP. Both sound and IMEI came back.
I'm at 4.4.2 now, but an OTA update from ATT failed (probably because it went through TWRP)
Now I'm back to stock, albeit rooted ROM (because of the Rooted-Odex 4.4 flash), but I am a happy camper.
Thanks to XDA for various bits of info here and there. But essentially *this* is how you go back to stock from Lollipop.
L
I had TWRP 2870
i was running cm 11 cough made
everything was fine for a few days then realized that i could only receive text messages and my lte was always dropping out. So I verified my APN setting with my wife's i317 and made all adjustments as needed but no help. so i just got fed up with it all and reinstalled from a backup that i made of stock 4.4.2 everything worked then last night my phone received an OTA from AT&T but because I had TWRP it would not install. I am assuming that it was the stage freight update so (all the trouble began) I used a back to stock recovery using a back to stock sticky that i found and it worked it took me all the way back to stock recovery and 4.1.2 I think and then after installing all necessary updates I went to about device and check for updates and it downloaded a update I don't remember the file size but under 500 megs. then it restarted and installed it then rebooted and it would not go past the samsung logo I have tried everything but a pit file or something like that the only thing i have access to is download mode. when I tried going back to stock 4.4.2 using odin3 v.1.85 and flashed I317-UCUCNE5-Stock.tar odin says all is good and I get very happy but the stupid phone wont boot it gets stuck at the same samgung logo for 30mins. help me. please! Im stuck using the captivate untill i get this fixed.
And you cannot boot into recovery using the 3 button combo ??
If yes ....wipe data...factory reset the device...and wipe the cache as well...g
Edit:
The Update will put the device to UCUCNJ1 official and will lock you into the Knox bootloader as well.
The only 4.1.2 reverts from this point forward cannot contain the bootloader image or softbrick will occur....g
Okay so i went through the bootloader unlock process on my Note 4 without any major hickups, was running on CM13 ever since until i wanted to play with Gear VR which from what i could find required me to be on a stock based/touchwiz rom, first up was Omega which installed fine but would boot loop at welcome screen, so then i went with Evolution and almost same story, just boot loop. Figured it had to be a problem with the firmware version on my phone and without thinking i downloaded the CPF1 firmware and flashed with Odin. Flash went fine with no problems, booted into marshmallow just fine, enabled usb debugging and rebooted to flash TWRP for recovery and i get zilch. Every single TWRP and CWM recovery file i try to flash end in a failure. Can't even get Kingroot to give me root in MM so I think i'm stuck...dont even see the Unlock logo and Custom on the main screen after i hit the power button to turn on.
SO.........
Big question is, did i just re-lock my bootloader when i flashed firmware CPF1?
I think I did this same thing a while ago, were you on an older version of CM13 from May or so? Anyway, what I had to do was flash stock 5.1 in Odin with the up to date kernel, modem, etc and follow the guide to re-unlock your bootloader
Well got it re-flashed and unlocked again, gotta give a shout out to the great guys here on XDA.
Next question is do i need to flash a new bootloader or modem in odin/twrp before moving to a MM rom or is that stuff usually included in the rom? My experience in roms and stuff is from my old Razr Maxx HD and never jumped operating system version with it so i'm not sure on this one.