Develop Bugs

Rooted 4.1.2 what's the best way to update to 4.2

What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!

Not sure if your talking about 4.2 which is to my knowledge only with cm 10 or liquidsmooth or aokp most likely or 4.1.2 md4 either case download the appropriate file of your choice and flash from recovery do make sure backup amyways hope that answers your question
Sent from my SPH-L710 using XDA Premium HD app

six3onei said:
What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!
Click to expand...
Click to collapse
I think you mean update to 4.1.2. Check your version in settings about device. If it's 4.1.1 go here :
http://forum.xda-developers.com/showthread.php?p=586
Sent from my SPH-L710

Cm10.1
Sent from my SPH-L710 using xda app-developers app

Deviant Xone (linked in my sig). Awesome 4.2.2 ROM.

If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.

Overstew said:
If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.
Click to expand...
Click to collapse
Apparently you can avoid this by updating your recovery....the emulated 0 folder, I mean
Sent from my SPH-L710

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!

six3onei said:
I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!
Click to expand...
Click to collapse
Hey six3onei,
I'm assuming you just got the notification for the OTA (Over-The-Air) update. The newest version of the Stock Rom is MD4 which is still 4.1.2. Android version 4.2.x probably won't come out for your phone for a couple of months (that's my guess with no data to back it up other than my own intuition).
As far as upadating, you actually don't have to apply the OTA to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
The rom you want to download off of Freeza's page is:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4 | Mirror
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse

[Q] Stock update.zip L710

Hello all,
A little info before the question:
I recently flashed clockwork and switched my ROM to CM10. I have a 16GB MD4 SPH-L710. The flash went swimmingly and I love the rom. however, I've been looking for a way to flash a custom PRL to my phone and I've been trying various methods listed in several topics to no avail, so I'm ready to do a NAND backup, flash to stock to update it, and then restore the NAND.
If I understand my readings correctly, this will keep the PRL?
The root (hah) of my problem is this.. I forgot to make a NAND of my stock rom before I flashed CM10.
so I've been searching for a stock update.zip I can flash in clockwork. Alternatively, I need to make sure I can use an ODIN image and be fine. I don't want to lose CWM and SU unless I have to.
http://forum.xda-developers.com/showthread.php?t=1904099
If I read this right, I can use the image found here to flash stock image, then flash clockwork, then boot to OS, reboot to recovery and create NAND backup for future use, boot into OS to flash my custom PRL, then restore my CWM NAND backup.
Will this process keep the PRL?
Thanks in advance!

No just find Freezas stock rom, it's a pre rooted stock md4 rom. You can find it in the Sprint S3 development section.
Sent from the future via Tapatalk 4

edfunkycold said:
No just find Freezas stock rom, it's a pre rooted stock md4 rom. You can find it in the Sprint S3 development section.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Yeah, but he wants to flash a custom rom. With the stock rom you have to flash the prl write mod. He should just do the following:
1. Read this: http://forum.xda-developers.com/showthread.php?t=1880781
2. Probably easier to download a rom with it built in...this is just one example: http://forum.xda-developers.com/showthread.php?t=2116531
3. Boot into recovery
4. Make a backup (nandroid of your current CM setup)
5. After the backup, wipe cache, dalvik, system, data
6. Install the zip you downloaded in step 2
7. Update PRL normally or custom PRL with the instructions in step 1
8. After phone has rebooted, make sure the correct PRL is present
9. Reboot back into CWM
10. Wipe cache, dalvik, system, data
11. Restore the nandroid you just made
12. Reboot
13. Phone should be how it was
14. Read and search the forums!!!!
15. Read and youtube to make sure you know how to nandroid properly
16. Teach me how to place items in correct numerical sequence
17. No need to flash the return to stock/reset counter if you just want to update your PRL

he can do that with Freezas rom or any MD4 based rom. MOAR is a an MD4 based stock rom as well with customized theming. Makes no difference. He could flash MOAR, he could flash TPR it doesn't make one iota of a difference.
He stated he wanted the stock rom and was trying to flash via CWM so he doesn't have to flash stock image via odin and loose root. My intent was to explain that is not necessary, he could use any of the stock based roms in development and flash via recovery. I suggested Freezas rom because it is stock rooted and he could create a nandroid of that and have his stock nandroid.
Which is his Intent to have a nandroid of stock which he forgot to do when he rooted. His intent is not to flash a custom rom. He's already accomplished that a while back.
Sent from the future via Tapatalk 4

edfunkycold said:
he can do that with Freezas rom or any MD4 based rom. MOAR is a an MD4 based stock rom as well with customized theming. Makes no difference. He could flash MOAR, he could flash TPR it doesn't make one iota of a difference.
He stated he wanted the stock rom and was trying to flash via CWM so he doesn't have to flash stock image via odin and loose root. My intent was to explain that is not necessary, he could use any of the stock based roms in development and flash via recovery. I suggested Freezas rom because it is stock rooted and he could create a nandroid of that and have his stock nandroid.
Which is his Intent to have a nandroid of stock which he forgot to do when he rooted. His intent is not to flash a custom rom. He's already accomplished that a while back.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
But he sounds like he wants to flash a custom PRL. Not just update the Sprint PRL. You can't flash a custom PRL on the stock rom without the PRL write mod. I just suggested MOAR so he wouldn't have to dig around for the PRL write mod. Just based on his comments, it seems like step-by-step instructions would help him more. I mean, he was ready to flash a zip to take his phone back to out of the box stock in order to try this. Yes, Freeza's rom will work, but he probably wants to flash a modified PRL, which you also need the PRL write mod in order to do with that rom. If you want, I can edit my message to say download Freeza's stock and boot, then go back into CWM and flash the PRL Write mod. I was just saving him a few steps. That's why I said there are many roms with this built in, here is one example.

No its cool, just didn't want him to think he had to go back to stock unrooted. Hopefully he gets it done with yours and my advise:thumbup::thumbup:
Sent from the future via Tapatalk 4

edfunkycold said:
No its cool, just didn't want him to think he had to go back to stock unrooted. Hopefully he gets it done with yours and my advise:thumbup::thumbup:
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Cool. You said my laundry list of steps in one sentence.

thanks!
I looked at http://forum.xda-developers.com/showthread.php?t=1880781 and some other threads and tried these methods, the scripts too enable diag modem mode do not work for CM10.1 anymore.
Thanks for the other advice!! I'll try one of these roms. Anything to save me a few steps is awesome. Plust I can NAND go back and forth whenever I want
Why doesn't the PRL write mod work with CM, does it only support MD4/stock-based roms?
I'm very familiar with NAND backups/restores and custom rom flashing.. I'll make a new backup and try flashing MOAR on my lucnch today if I can.
lvpre said:
Yeah, but he wants to flash a custom rom. With the stock rom you have to flash the prl write mod. He should just do the following:
1. Read this: http://forum.xda-developers.com/showthread.php?t=1880781
2. Probably easier to download a rom with it built in...this is just one example: http://forum.xda-developers.com/showthread.php?t=2116531
3. Boot into recovery
4. Make a backup (nandroid of your current CM setup)
5. After the backup, wipe cache, dalvik, system, data
6. Install the zip you downloaded in step 2
7. Update PRL normally or custom PRL with the instructions in step 1
8. After phone has rebooted, make sure the correct PRL is present
9. Reboot back into CWM
10. Wipe cache, dalvik, system, data
11. Restore the nandroid you just made
12. Reboot
13. Phone should be how it was
14. Read and search the forums!!!!
15. Read and youtube to make sure you know how to nandroid properly
16. Teach me how to place items in correct numerical sequence
17. No need to flash the return to stock/reset counter if you just want to update your PRL
Click to expand...
Click to collapse

j0hnnyboy said:
I looked at http://forum.xda-developers.com/showthread.php?t=1880781 and some other threads and tried these methods, the scripts too enable diag modem mode do not work for CM10.1 anymore.
Thanks for the other advice!! I'll try one of these roms. Anything to save me a few steps is awesome. Plust I can NAND go back and forth whenever I want
Why doesn't the PRL write mod work with CM, does it only support MD4/stock-based roms?
I'm very familiar with NAND backups/restores and custom rom flashing.. I'll make a new backup and try flashing MOAR on my lucnch today if I can.
Click to expand...
Click to collapse
Cm just doesn't support it. You can do it, but it is an involved process and just easier to flash touchwiz rom. You'll find some custom touchwiz roms here don't support prl update either. Yeah, but just make a nand and go to town. I had the best luck finding a custom prl when I turned data off. It wouldn't stick otherwise

I went through this process twice and the PRL would not stick, even in the MOAR rom. That rom is sweet though, and it had the most beautiful setup I've seen lol.
I just might be giving up on this PRL stuff at this point unless someone has some tips.
Thanks for the help!
lvpre said:
Yeah, but he wants to flash a custom rom. With the stock rom you have to flash the prl write mod. He should just do the following:
1. Read this: http://forum.xda-developers.com/showthread.php?t=1880781
2. Probably easier to download a rom with it built in...this is just one example: http://forum.xda-developers.com/showthread.php?t=2116531
3. Boot into recovery
4. Make a backup (nandroid of your current CM setup)
5. After the backup, wipe cache, dalvik, system, data
6. Install the zip you downloaded in step 2
7. Update PRL normally or custom PRL with the instructions in step 1
8. After phone has rebooted, make sure the correct PRL is present
9. Reboot back into CWM
10. Wipe cache, dalvik, system, data
11. Restore the nandroid you just made
12. Reboot
13. Phone should be how it was
14. Read and search the forums!!!!
15. Read and youtube to make sure you know how to nandroid properly
16. Teach me how to place items in correct numerical sequence
17. No need to flash the return to stock/reset counter if you just want to update your PRL
Click to expand...
Click to collapse

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.

You need to give more info on the error
Sent from my SGH-M919 using Tapatalk

serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.

Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app

spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.

Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?

Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.

Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.

Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?

So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.

Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.

To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.

Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.

Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3

I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?

Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something

Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement

GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)

My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.

You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.

[Q] TWRp can't restore backup/wipe cache.dalvik.etc

I am trying to restore a backup made with TWRP. Here's what has happened so far:
Flashed TWRP several weeks ago. I've made several backups with no problems.
Flashed NK2 radio with no apparent problems.
Full wipe of phone. Phone was not rooted at this point.
Flashed 5.01 GPE ROM.
Phone boots and I get the "Kernal not SELinux enforcing" message (ugh...KNOX). Phone won't boot to new rom. I can only get to TWRP.
Try to restore backup. TWRP checks MD5 on backup-it passes and then screen blanks and TWRP reboots. It does this several times.
After research I restore phone to stock MB4 through Odin.
Phone boots into Android and is indeed 4.4.2 MB4.
Using Unified Toolkit re-flash TWRP and then proceed to root phone. After procedure SuperSU gives me "SuperSU has stopped" msg. Follow toolkit procedure to get around KNOX. SuperSU runs and I also install Busybox. Reboot phone. Root not held. Redo toolkit procedures to attain root. Still lose it upon reboot.
TWRP still reboots when trying to do anything involved with the filesystem (restore backup--wipe cache and dalvik--none works. TWRP blanks and reboots.) . At this point I'm scratching my head. I'd like to restore the backup and also root and change to GPE. I'm thinking this comes down to not being able to do anything in the filesystem due to root not being held. Any suggestions as to how to get root to stick so I can do the restore and change ROMS? Thanks folks.
Steve KS4KJ

If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.

PanchoPlanet said:
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
Click to expand...
Click to collapse
In flashing the stock 4.4.2 rom (which is where my phone was when I started this journey) I have done a reset haven't I? That is what I did when the 5.0 GPE rom wouldn't boot. I can certainly try loading the 4.4.4 NK2 rom and seeing what that will do. Pretty sure I did not root before using the toolkit to replace the stock recovery with (originally) CWM and then later with TWRP. I remember wanting to do a Nandroid backup before installing the 4.4.4 OTA (which then didn't work because I had changed the stock recovery). I keep thinking that KNOX is involved with this but not sure what to try to remedy it (other than the 4.4.4 suggestion which I will try). Thanks for the reply.
Steve

The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.

PanchoPlanet said:
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
Click to expand...
Click to collapse
I'll try that. Thanks again.

[Q] new CWM version to install via recovery or ODIN?

SGH-1747 (att)
Been running CM rom for years and love it. Yesterday my power button broke and I could not fix it. Swapped in a spare motherboard that had stock rom (4.3). Figured I would root and restore a backup from my SD card and be on my merry way.
Rooted via ODIN and ended up with CWM v5.5.0.4.
Verified I had a good root and failed to update to a newer CWM version before rebooting to CWM recovery to backup the existing stock image and restore my old backup.
The restore failed with status 7 which I know is potentially a CWM version issue. The partial restore killed my existing image so I went to retore it and it is hanging at the white att logo screen. I wiped the cache and dalvik and did a factory reset with no joy.
I see a bunch of stuff out there how to update CWM via the ROM manager but that is not an option for me since I can't get the OS to function. If I can get a newer version of CWM I think I can get my old backup running.
Where can I get a newer CWM version that is capable of being loaded via zip in recovery or via ODIN?
Thx

I took a quick look at the CW site and I didn't see any odin flashable tars. You could probably find some if you search around xda, but you run the risk of them being outdated.
I'd recommend TWRP or Philz. They both have odin tars posted for their up to date versions. I've always had good luck with TWRP, but it really comes down to personal preference.
http://teamw.in/project/twrp2/104
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Sent from my LG-V410 using XDA Free mobile app

You can flash the latest zip (tar.md5 for Odin, zip for cwm) from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/

Issue resolved.
Thanks for the info y'all but here is what I did...
Reverted to the android recovery using the info on this page. http://honai-android.blogspot.com/2014/02/how-to-root-galaxy-s3-at-sgh-i747-on.html
then re-rooted using odin and an newer CWM from this page http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/
Now I need to backup everything, revert to the stock OS so I can unlock it and then bring my usual CM rom online. Hope this helps any other folks that make the same goof.

chuzie said:
Issue resolved.
Thanks for the info y'all but here is what I did...
Reverted to the android recovery using the info on this page. http://honai-android.blogspot.com/2014/02/how-to-root-galaxy-s3-at-sgh-i747-on.html
then re-rooted using odin and an newer CWM from this page http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/
Now I need to backup everything, revert to the stock OS so I can unlock it and then bring my usual CM rom online. Hope this helps any other folks that make the same goof.
Click to expand...
Click to collapse
Do not downgrade from the 4.3 firmware and modem. Odds are you will hardbrick your device if you do. I mention this because the free sim unlock requires the 4.1.1 modem in order to have the proper hidden menus. These are now unaccessable to you.

Thanks for the heads up. So I really have no choice but to dish out some cash to unlock the sim at this point, correct?
Sent from my GS3 on Cyanogenmod with the older / better version of Tapatalk!

chuzie said:
Thanks for the heads up. So I really have no choice but to dish out some cash to unlock the sim at this point, correct?
Sent from my GS3 on Cyanogenmod with the older / better version of Tapatalk!
Click to expand...
Click to collapse
From all that I have read that is the way of it.