I got an S5 and want to sell my S3 that I've been running CM12.1 nightlies on now for the past year.
I'm having issues though just getting it back to complete stock through various stock TARs I've downloaded. I've soft bricked it a few times but it has bounced back after installing a recovery again in Odin. They're all on the front page of the Sprint S3 Android XDA forum, so it's not like I'm flashing something non-Sprint.
Here's what I've been doing:
I wiped and factory reset within TWRP recovery.
Then I flashed the stock recovery in Odin. That worked just fine.
Go into download mode, tried to flash the Stock NJ2 tar and it fails at aboot. Phone then says: SW REV CHECK FAIL: Fused 2 > Binary 1
I get the 'connect to Kies' error both when powering up and in recovery. Throw it back into download mode, flash stock recovery again. Works fine -- boots in CM12.1 again with no data fresh.
I then tried to flash stock MK3 and it failed too.
I've tried the latest Odin and 3.07 but both give me the same results.
Re-flashing any recovery (I've used stock and TWRP) both get it back to where it boots into CM12.1.
Any guidance on how I can get this thing back to a stock Touchwiz ROM with OTA updates so I can sell it on Craigslist or Swappa or something? I'd appreciate anything, I'm a loss here!
Nevermind! Thank goodness I found an old nandroid backup on an HD and it worked.
numero9 said:
Nevermind! Thank goodness I found an old nandroid backup on an HD and it worked.
Click to expand...
Click to collapse
Any chance you could share your nandroid backup with me? I'm having the same problem getting my S3 back to stock.
numero9 said:
I got an S5 and want to sell my S3 that I've been running CM12.1 nightlies on now for the past year.
I'm having issues though just getting it back to complete stock through various stock TARs I've downloaded. I've soft bricked it a few times but it has bounced back after installing a recovery again in Odin. They're all on the front page of the Sprint S3 Android XDA forum, so it's not like I'm flashing something non-Sprint.
Here's what I've been doing:
I wiped and factory reset within TWRP recovery.
Then I flashed the stock recovery in Odin. That worked just fine.
Go into download mode, tried to flash the Stock NJ2 tar and it fails at aboot. Phone then says: SW REV CHECK FAIL: Fused 2 > Binary 1
I get the 'connect to Kies' error both when powering up and in recovery. Throw it back into download mode, flash stock recovery again. Works fine -- boots in CM12.1 again with no data fresh.
I then tried to flash stock MK3 and it failed too.
I've tried the latest Odin and 3.07 but both give me the same results.
Re-flashing any recovery (I've used stock and TWRP) both get it back to where it boots into CM12.1.
Any guidance on how I can get this thing back to a stock Touchwiz ROM with OTA updates so I can sell it on Craigslist or Swappa or something? I'd appreciate anything, I'm a loss here!
Click to expand...
Click to collapse
Don't try to flash mk3, you will hard brick if you've updated to nd8 or newer. You don't flash stock recovery at all. Just the stock tar in odin. Have you flashed the stock nd8 or nj2 .tar? Those are the ones you should be flashing. Just the stock .tar, nothing else. It has the right recovery in it. You may be messing up flashing stock recovery. Every build has a different version of recovery ,( like nd8 or nj2).
Yeah I flashed both and they didn't work from Odin. I was on NJ2. MK3 just soft bricked me only. Anyway it's a moot point now that I got it working.
Related
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
hunter99507 said:
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
Click to expand...
Click to collapse
You might want to try flashing the "UCALH9 Kernel, Modem and TWRP Recovery Tar" from here with Odin. Make sure the "Auto Reboot" switch is not checked in Odin. When the flash is done, disconnect from the computer, pull the battery, then boot into recovery by holding Home and Vol Up and then pressing Power. Hold Home and Vol Up until you see the Samsung logo and some little blue text, then release. If you can get there, do a factory reset, then you should be able to flash the rooted LG1 image with Odin. Or, you can flash LH9 from the same thread or from here by flashing the Bootloader, ROM and Kernel files from the PIECES section (in that order) before rebooting.
Wipe cache and devlik and it will fix your issue. I had the same problem before.
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
I had the same issue a few days ago and ultimately fixed it by doing factory reset, wipe cache, dalvik, etc.. I had forgotten to do it after flashing back to stock. You were probably smarter than me and did those things BUT if you didn't it's usually something simple like I did to fix the problem.
\Hey hunter you prolly figured it out already but I was in the same situation today going from AOKP to stock rooted.. what fixed it for me was after flashing, booting into the stock recovery (HOME + VOL UP + POWER) and doing a wipe data and wipe cache. Then going back to download mode and reflashing the stock rooted tar. not sure if reflashing was necessary but it worked like a charm after that.
well as i wasnt in clockwork i was pushing a stock rom through odin i don't beleive i iclearly the cache that could of helped but nonetheless im stuck and i can't get into cwm or regular recovery etc
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
My suggestions including flashing a bunch of stuff. Which one caused the error? The flash of the modem/kernel/recovery tar file in Odin or the subsequent flashing of the zips in recovery? What was the exact error you received?
It's pretty hard to help you if you don't provide all the details.
I've flashed plenty of custom ROMs on this phone and my old Captivate so I'm not new to the process, but I have come across an interesting issue. At first, I had a version of RootBox (4.2.2) on my phone. I don't remember exactly what it was and I can't go check anymore. When I tried to install a new custom ROM, any, it said that my phone was d2spr even though it should be d2att and promptly failed. Never had the happen before so I thought I might need to go back to a stock ROM. Used Odin to flash a stock ROM, tried I747UCDLK3 first. Flashed successfully, but now it won't boot. So I'm stuck with a non-booting ROM and stock recovery. I tried flashing CWM using Odin. Flashed successful. When I try to boot into CWM it just shows a blank screen. Phone is still on since holding the power button doesn't attempt to start it. And that's where I'm now stuck. I'm attempting to get a Sprint ROM for this phone, figured it couldn't hurt at this point. I've tried TWRP and some other stock AT&T ROMs, but same things happens. I'm not really sure where to go from here since it seems to be unusual circumstances.
Does anyone know what's going on or what I should try?
Did you run an OTA update to take your d2att to 4.3? If you did, you cannot flash anything that is lower than 4.3 because the 4.3 update upgrades the bootloader.
I am assuming from your post you are not on the 4.3 mjb boot loaders.
Can you get into download mode. If so you could try the Odin back to stock again. Once complete you may need to boot into factory recovery and perform a full reset to clear the boot loop.
Did you root before flashing CWM?
Sent from my I-747 using xda app-developers app
Trying to figure this out. Browsed forums for the last 24 hours, unable to come up with a way to figure it out. I was running Effortless rom, and older version that I can't remember, but it was on NF6 firmware. I wanted to play around with cm11 so I decided to flash back to stock NF6 then update to NF9 for the VOLTE update just to have it. So I triangled away, wiped then rooted and installed TWRP via ODIN, made a backup, everything went fine. Then I downloaded cm11 and gapps 4.4.4 and put them on my internal sd and went to flash in TWRP but cm11 was giving me errors. I figured it may have been TWRP so i decided to flash CWM but no go. It wouldn't stick. Tried again, no luck. Downloaded ROM Manager and this time I installed CWM through there. Tried rebooting in to recovery and ended up getting stuck in the "recovery booting" bootloop, so I flashed stock NF9(since I was on this firmware now) and tried installing CWM again, no luck. When I tried booting to recovery, it was stock NB4 recovery. I'm thinking that I'm stuck on an old bootloader and the recovery isn't NF9, which is the current stock recovery. I'm thinking that the reason why I'm unable to flash anything in TWRP/unable to install CWM at all is because of the stock recovery and possibly bootloader being NB4 for some reason while my baseband and build are both NF9. Any ideas/help would be appreciated. Thanks guys.
re: custom recovery
pyr0path said:
Trying to figure this out. Browsed forums for the last 24 hours, unable to come up with a way to figure it out. I was running Effortless rom, and older version that I can't remember, but it was on NF6 firmware. I wanted to play around with cm11 so I decided to flash back to stock NF6 then update to NF9 for the VOLTE update just to have it. So I triangled away, wiped then rooted and installed TWRP via ODIN, made a backup, everything went fine. Then I downloaded cm11 and gapps 4.4.4 and put them on my internal sd and went to flash in TWRP but cm11 was giving me errors. I figured it may have been TWRP so i decided to flash CWM but no go. It wouldn't stick. Tried again, no luck. Downloaded ROM Manager and this time I installed CWM through there. Tried rebooting in to recovery and ended up getting stuck in the "recovery booting" bootloop, so I flashed stock NF9(since I was on this firmware now) and tried installing CWM again, no luck. When I tried booting to recovery, it was stock NB4 recovery. I'm thinking that I'm stuck on an old bootloader and the recovery isn't NF9, which is the current stock recovery. I'm thinking that the reason why I'm unable to flash anything in TWRP/unable to install CWM at all is because of the stock recovery and possibly bootloader being NB4 for some reason while my baseband and build are both NF9. Any ideas/help would be appreciated. Thanks guys.
Click to expand...
Click to collapse
If I were you the first thing I would do is to ODIN flash TWRP recovery
and go from there.
Here is a direct download link for the latest odin flash twrp
custom recovery for the N900T Note 3:
https://app.box.com/AndroidShare
Once you get into twrp recovery do a complete wipe
which includes wipe data, system, cache, dalvik and
last but not least do a factory reset in twrp.
When that's done odin flash the official stock N900T NF9
firmware which can be found at http://SamMobile.com
After that's done you will need to odin flash cf-autoroot
and then odin flash twrp recovery again.
Here is the download link for cf-autoroot:
https://app.box.com/s/rgovggya5gkc51lc1uax
Then simply copy your favorite N900T zip file rom into
your internal sd and flash the N900T rom of your choice.
Be sure to do a full and complete wipe again before
flashing any custom roms.
Good luck!
Hello,
Im having a problem using ODIN to return to stock. It is going through the entire step of flashing the stock image and it reboots successfully but it doesn't work and my old ROM is still there. Any idea why?
After successfully flashed .tar via odin, restart to recovery and do a full wipe/factory reset.
It will return you back to full stock
I am am trying to take my Samsung i317 AT&T Note 2 back to stock.
Installed 4.4.2 NJ1 stock rom using ODIN. Reset/ cleared and started phone and went to OTA upgrade the latest patch from AT&T to make it to NJ2. However, when the phone reboots, the Samsung Note II logo shows up and the screen does dark. When I try to enter recovery, it starts to reinstall the OTA patch all over again and says updated. Tried turning the phone back on and the same thing happens again.
I was able to get the phone to work by reflashing the NJ1 stock rom and installed the ZIP stock recovery file using CWM. However, I am trying to get back to the original stock configuration as possible without having CWM installed on the phone and was hoping I can install the stock recovery so that when I go to download mode, everything shows Samsung Official. Knox Warranty Void is at 1, so I guess there is nothing I can do to fix that at this point.
Would installing this be the simple fix by downloading 4.3 Param.bin and Tz.img
Another would be to install the stock recovery ZIP file using CWM as I have already successfully done and maybe someone can point me to find a way to uninstall the CWM afterwards. I've searched online to remove CWM but couldn't find the md5.tar file that would do that from ODIN.