Related
Hello.First post here.
I currently have been using CM11 for a few months now but miss some features on stock. (multiwindow, air view) so I installed Sacs ROM.
Everything was working great today except a known problem is wifi will not work due to radio opbstructions (i believe). So i attempted to change the baseband to MF9.
At first, Odin started then immidately it failed. The error read 'Fused 4 Binary 1'
So i assumed it was a connection error. I loaded back into download mode and tried again. Failed.
At this point i thought screw it, and took the battery out. tried to reboot and stuck at the soft brick "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I installed Kies. Plugged in my phone. Drivers installed but Kies will not connect. Try to do 'Firmware Upgrade and Initialization'
However Kies will NOT accpet my S/N number. i tried everything. writing it all out or with a space every 3 numbers or with 'DEC' at the front. nothing worked.
I even called sprint to double check S/N (ESN/DEC)
so basically I'm soft bricked and Kies is screwing me over. Any ideas?
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
ROMANTiC KiD said:
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
whatthe_fuzz said:
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
Click to expand...
Click to collapse
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
whatthe_fuzz said:
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
Click to expand...
Click to collapse
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i searched around and eventually found a working .md5 file. its apparently is stock. got my phone to start booting but it got stuck at the yellow sprint screen. im going to try to boot into safe mode. any ideas how to access my recovery file? i have one form CWM and one from Ti Backup
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
leaderbuilder said:
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
Click to expand...
Click to collapse
I think i fixed it.
Problems resolved.
The issue was i had Sacs v4 which didnt support wifi and i read that it needed MF9 firmware.
i had a lapse in judgement and without thinking tried to go back from MJA. didnt catch it until now.
I eventually found the correct stock file. eventually got into the phone. rerooted and in the process of install the proper sacs ROM (v5.6)
this was a simple error that i shouldve caught thanks guys!
hopefully this ROM will work with wifi...
BTW, all my backups were wiped
Your backups weren't on your external sd? Ooo, that sucks. Glad you got it.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Hey guys, I'm pretty new here and new to rooting devices. I recently just rooted my Samsung Galaxy S 4 SGH-1337 (At&t) with the new "TowelRoot" and then using Super SU to finish the root. I has a question when it came to installing the custom recovery Philz Touch. I have the 4 most recent versions of PT and using Odin v3.09 and v3.07 I am still unable to correctly install the recovery. When I try starting the process I get a "Leave CS" in the bottom left of the Odin window, and when I start the process fails? I've noticed when I go into download mode on my S 4 the phone tells me on the the official binary and official operating system. If I am rooted should that say something else? I have checked the Root Checker app and it says I am in fact rooted.
Other solutions I've already got advice and still unable:
- I'm using my out of box charging cable.
- I am pressing start after I ad the AP in Odin.
- The phone is in Download mode.
Can anyone help me out and assist me? This is super annoying and I would love to figure it out soon. Thank you in advance!
kelvin00 said:
Hey guys, I'm pretty new here and new to rooting devices. I recently just rooted my Samsung Galaxy S 4 SGH-1337 (At&t) with the new "TowelRoot" and then using Super SU to finish the root. I has a question when it came to installing the custom recovery Philz Touch. I have the 4 most recent versions of PT and using Odin v3.09 and v3.07 I am still unable to correctly install the recovery. When I try starting the process I get a "Leave CS" in the bottom left of the Odin window, and when I start the process fails? I've noticed when I go into download mode on my S 4 the phone tells me on the the official binary and official operating system. If I am rooted should that say something else? I have checked the Root Checker app and it says I am in fact rooted.
Other solutions I've already got advice and still unable:
- I'm using my out of box charging cable.
- I am pressing start after I ad the AP in Odin.
- The phone is in Download mode.
Can anyone help me out and assist me? This is super annoying and I would love to figure it out soon. Thank you in advance!
Click to expand...
Click to collapse
Since towel root worked in your phone I'm assuming you're on firmware nc1. This can not have a custom recovery installed. In fact you probably erased your stock recovery trying these other ones. I suggest using odin to flash nb1 then update back to nc1 and if you want a recovery yo install another rom (only touchwiz based roms) you'll to use safestrap. That is the only option at this time.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
Since towel root worked in your phone I'm assuming you're on firmware nc1. This can not have a custom recovery installed. In fact you probably erased your stock recovery trying these other ones. I suggest using odin to flash nb1 then update back to nc1 and if you want a recovery yo install another rom (only touchwiz based roms) you'll to use safestrap. That is the only option at this time.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the response. I am on firmware NC1. After posting I have read that there is a new bootlocker (?) that was pushed on the 4.4.2 update preventing people from actually installing custom recovery and other things. There is a workaround going to an older version to then root and get a custom recovery, but I definitely don't have the knowledge of what to do.
I'm not sure what you mean by me probably erasing my stock recovery? Are you saying if I try and restore my device it will not work?
kelvin00 said:
Thanks for the response. I am on firmware NC1. After posting I have read that there is a new bootlocker (?) that was pushed on the 4.4.2 update preventing people from actually installing custom recovery and other things. There is a workaround going to an older version to then root and get a custom recovery, but I definitely don't have the knowledge of what to do.
I'm not sure what you mean by me probably erasing my stock recovery? Are you saying if I try and restore my device it will not work?
Click to expand...
Click to collapse
When you tried to install the custom recovery it more than likely erased your stock recovery and the only way to get it back is to flash nb1. And going to an older version is no longer possible. Once you update and the bootloader is updated you're no longer able to revert to an older bootloader. Trying to do so could brick your phone
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
When you tried to install the custom recovery it more than likely erased your stock recovery and the only way to get it back is to flash nb1. And going to an older version is no longer possible. Once you update and the bootloader is updated you're no longer able to revert to an older bootloader. Trying to do so could brick your phone
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Again, thank you for responding to me. I understand what you are saying now about me possibly deleting my stock recovery. I didn't go very far i the process and I'm fairly sure I didn't for the simple reason that it did not work. I can definitely be wrong and you are probably more right on this situation than I am.
Thank you for the heads up with the older version not possibly anymore.
Do you know any confirmed ways of rooting and flashing a custom recovery since 4.4.2? If not I guess I'm just going to wait a bit for a confirmed method.
kelvin00 said:
Again, thank you for responding to me. I understand what you are saying now about me possibly deleting my stock recovery. I didn't go very far i the process and I'm fairly sure I didn't for the simple reason that it did not work. I can definitely be wrong and you are probably more right on this situation than I am.
Thank you for the heads up with the older version not possibly anymore.
Do you know any confirmed ways of rooting and flashing a custom recovery since 4.4.2? If not I guess I'm just going to wait a bit for a confirmed method.
Click to expand...
Click to collapse
Before proceeding check to make sure your stock recovery is still intact (power phone off, wait 10 seconds, power on while holding volume up/home button/power if you boot into recovery you're fine and can proceed with towel root (just Google it it'll come up right away) download and install the apk on your phone and it'll root your phone for you. Next go here
http://forum.xda-developers.com/showthread.php?t=2680868
Closest thing to custom recovery that will let you only flash touchwiz based roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hello everyone. I was trying to get Cyanogenmod 11 on my Galaxy S4. I read a guide and followed it to a T, but I guess it must have been a bad guide, and I can't find it now.
At any rate, I have 4.2.2 with NC1, and I used Geohot's TR to get root. I installed SU, and that's working. Then (because I used to use this on my GS3) I installed Rom Toolbox pro, chose to install CWM, and I kept getting errors. So I decided to use another, ROM installer, and flash TWRP.
So now, when I reboot my phone, I just get errors that say "Odin error".
What do I need to do in order to get a custom ROM? I've read in these forums that safestrap is the only way, but I don't want to do this until I know that I can move from what I'm currently at, to safestrap. I don't want to dig my hole any deeper.
Thank you so much.
ptizzl said:
Hello everyone. I was trying to get Cyanogenmod 11 on my Galaxy S4. I read a guide and followed it to a T, but I guess it must have been a bad guide, and I can't find it now.
At any rate, I have 4.2.2 with NC1, and I used Geohot's TR to get root. I installed SU, and that's working. Then (because I used to use this on my GS3) I installed Rom Toolbox pro, chose to install CWM, and I kept getting errors. So I decided to use another, ROM installer, and flash TWRP.
So now, when I reboot my phone, I just get errors that say "Odin error".
What do I need to do in order to get a custom ROM? I've read in these forums that safestrap is the only way, but I don't want to do this until I know that I can move from what I'm currently at, to safestrap. I don't want to dig my hole any deeper.
Thank you so much.
Click to expand...
Click to collapse
You can only use Safestrap. Boot into download mode and then exit from it (I forget which button you hold) to get back in to the system. Then install Safestrap after using SELinux Mode Changer. You'll probably also want to find the recovery image for NC1 and flash that. Check the NB1-NC1 keeproot ROM thread you can find in the index for that
If you need anything else, ask here, but next time you have a new question, start it in the q&a section please.
Sent from my SGH-I337 running GPE
DeadlySin9 said:
You can only use Safestrap. Boot into download mode and then exit from it (I forget which button you hold) to get back in to the system. Then install Safestrap after using SELinux Mode Changer. You'll probably also want to find the recovery image for NC1 and flash that. Check the NB1-NC1 keeproot ROM thread you can find in the index for that
If you need anything else, ask here, but next time you have a new question, start it in the q&a section please.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
First, thank you for taking the time to reply, and second, I'm sorry for posting in the wrong forum.
Plus, even with SafeStrap you can't run CM/aosp roms--
rugmankc said:
Plus, even with SafeStrap you can't run CM/aosp roms--
Click to expand...
Click to collapse
I have seen that everywhere. Out of desperation, is there ANY way I can get CyanogenMod on here?
Secondly, my phone is having issues and I want to restore it to factory settings. When I choose this, it reboots and I get the ODIN error. I then have to power down, then I have to hold down while restarting, then hit cancel, then it boots normally. How do I remedy this?
ptizzl said:
I have seen that everywhere. Out of desperation, is there ANY way I can get CyanogenMod on here?
Give up or get another phone-- NO CM at this time--there is a GE rom in General, I believe, for SafeStrap.
Not sure on other issue, maybe Odin back to stock--someone else may have suddestion--Read up on things in General and Q&A on SafeStrap. And a couple other threads like All Things MK2 etc--:good:
Click to expand...
Click to collapse
rugmankc said:
Plus, even with SafeStrap you can't run CM/aosp roms--
Click to expand...
Click to collapse
Has to be TouchWiz rom. To me it is not worth the effort. I just stay stock for now.
I was hoping to get some help.
I installed SafeStrap, used SELinux, and then installed GoldenEye Rom on slot 1 after taking a backup of my current rom to my external SD card. I then installed update-supersu and att_nc1_modules through safestrap.
I reboot into system and it just boots into the exact same rom as my stock rom... but the only difference is that my networks don't work. So I've booted back into safestrap and changed my boot device back to stock and all is well.
What step am I missing?
Edit: Yes, I've made sure that Rom Slot 1 is active before booting into it.
Don't use SS so not sure what you missed--
Did you follow this--
http://forum.xda-developers.com/showpost.php?p=53038182&postcount=13961
rugmankc said:
Don't use SS so not sure what you missed--
Did you follow this--
http://forum.xda-developers.com/showpost.php?p=53038182&postcount=13961
Click to expand...
Click to collapse
Yes, this is the guide I followed.
I've been looking into this a bit more, and it looks like I may need to just overwrite the stock rom slot.
ptizzl said:
I was hoping to get some help.
I installed SafeStrap, used SELinux, and then installed GoldenEye Rom on slot 1 after taking a backup of my current rom to my external SD card. I then installed update-supersu and att_nc1_modules through safestrap.
I reboot into system and it just boots into the exact same rom as my stock rom... but the only difference is that my networks don't work. So I've booted back into safestrap and changed my boot device back to stock and all is well.
What step am I missing?
Edit: Yes, I've made sure that Rom Slot 1 is active before booting into it.
Click to expand...
Click to collapse
Exact same thing it did with Me also. It was the same Stock rom with all the same programs.
tailgunner9 said:
Exact same thing it did with Me also. It was the same Stock rom with all the same programs.
Click to expand...
Click to collapse
I believe that the rom slots no longer work, I'm looking at this right now.
ptizzl said:
Yes, this is the guide I followed.
I've been looking into this a bit more, and it looks like I may need to just overwrite the stock rom slot.
Click to expand...
Click to collapse
You do. You can't use rom slots with ss on kit Kat.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You do. You can't use rom slots with ss on kit Kat.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I've done this, but now my phone is just sitting on the Samsung logo for the last 10 minutes or more.
From safestrap - did the factory reset, went through the GE install process. Went to restart the phone, hasn't come back on yet.
ptizzl said:
I've done this, but now my phone is just sitting on the Samsung logo for the last 10 minutes or more.
From safestrap - did the factory reset, went through the GE install process. Went to restart the phone, hasn't come back on yet.
Click to expand...
Click to collapse
You're probably going to have to flash the nb1 tar in Odin and start over again. After flashing in Odin ota to nc1 then towelroot, then safestrap.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're probably going to have to flash the nb1 tar in Odin and start over again. After flashing in Odin ota to nc1 then towelroot, then safestrap.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So my backup that I made with Satestrap won't work? I'm in the process of restoring that right now.
Do you have time to explain what all of this means?
flash the nb1 tar in Odin?
OTA to NC1?
Does this mean use Odin to get back to Nb1, then use the built in samsung updater to get to nc1, then start again with TR and SS?
I am a noob, so be detailed
Edit: I assume you mean this guide here: http://forum.xda-developers.com/showthread.php?p=49562527
another thing: restoring my phone within safestrap worked. I'm back on my stock rom. At least my phone's working again.
ptizzl said:
So my backup that I made with Satestrap won't work? I'm in the process of restoring that right now.
Do you have time to explain what all of this means?
flash the nb1 tar in Odin?
OTA to NC1?
Does this mean use Odin to get back to Nb1, then use the built in samsung updater to get to nc1, then start again with TR and SS?
I am a noob, so be detailed
Click to expand...
Click to collapse
Use this file in Odin, it's the nb1 tar file. After you download it you'll need to extract it using winrar or 7-zip. You'll get a .tar.md5 file http://forum.xda-developers.com/showthread.php?p=50912149
Use that in Odin pda/pa slot depending on what version of Odin you're using.
The either just ota, over the air, update to nc1 or there is a nb1 to nc1 zip file that can be side loaded in the stock recovery.
Once on nc1 you can use tr to root.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Use this file in Odin, it's the nb1 tar file. After you download it you'll need to extract it using winrar or 7-zip. You'll get a .tar.md5 file http://forum.xda-developers.com/showthread.php?p=50912149
Use that in Odin pda/pa slot depending on what version of Odin you're using.
The either just ota, over the air, update to nc1 or there is a nb1 to nc1 zip file that can be side loaded in the stock recovery.
Once on nc1 you can use tr to root.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the detail. I was able to restore my backup - do I still need to do all of this prior to trying again in safestrap?
I suppose it would increase my chances at success.
ptizzl said:
Thank you for the detail. I was able to restore my backup - do I still need to do all of this prior to trying again in safestrap?
I suppose it would increase my chances at success.
Click to expand...
Click to collapse
If you restored your backup I would try to flash your rom in the stock slot of safestrap first. Only do the Odin if you can't restore first.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you restored your backup I would try to flash your rom in the stock slot of safestrap first. Only do the Odin if you can't restore first.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So my first attempt, the one that left me in the boot loop, was from the stock slot. Try again?
I apologize in advance for my lack of knowledge and understanding. I recently flashed a custom rom on my Galaxy S4, and it worked but I noticed the Wifi wasn't working, so I attempted to get it to work by trying again. It ended up badly, and it's now been stuck on the boot screen for a while. I tried doing a factory reset and wiping the cache partition, but it was still stuck on the screen. I can also still get onto download mode, so I'm hoping that means I can still save my phone.. I'm also not worried if I lose my internal storage, considering I'm just desperate to get my phone working again. I have an SGH-I337 AT&T phone.
What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!
Daze_ said:
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!
Click to expand...
Click to collapse
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I'll try that. Also, this was the first time I've ever flashed a rom, and I'm unsure if you would consider it successful, since the wifi wasn't working, but besides that, I saw no issues.
I had to go this same route when I was messing around and soft bricked like you. It's not hard to recover following the instructions . Odin the NB1 stock tar, let phone boot to ensure it is alive again. Then use the built in recovery to install the NC1 update. Reboot and you are ready to towelroot/supersu/safestrap.
Don't worry. It will be ok!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I am currently on the unlocked MDL bootloader, and I am running KANGAKAT 7.0, which is a KitKat 4.4 ROM. My phone is also encrypted, which means that I cannot flash updates due to CWM/TWRP not supporting encryption.
The solution proposed by other users has been to ODIN the stock MK2 recovery onto my phone, use the stock recovery to factory reset my device, then re-flash TWRP and then my new ROM.
However I'm having a problem with these steps. I am able to successfully ODIN the stock MK2 recovery to my device, however whenever I try to boot into recovery, I get the yellow triangle screen stating that I'm running software that is not authorized by AT&T, and stating something to do with my kernel in the top left of the screen.
Is there a step that I am missing? I followed the instructions @ http://forum.xda-developers.com/showthread.php?t=1506697
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
ChrisG683 said:
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
Click to expand...
Click to collapse
Flashing the mdl firmware in Odin will still give you the mdl bootloader. But it'll want to update after you flash so flash another custom rom or freeze the update files before it does so.
Sent from my Nexus 5 using XDA Free mobile app
@ChrisG683 Be sure to turn your wi-fi off and remove your SIM card, that way it can't update. You can put any apps you think you might need on an SD card and install them without having to go to the play store. Once you get things frozen or removed then you'll be good to go. :good:
Thanks guys, I'll be sure to keep that in mind once I get things sorted out.
The newest thing I've figured out is that the MDL stock recovery does not give me the "yellow triangle" error, and it presents me with the option to wipe my device. (I grabbed it from here http://forum.xda-developers.com/showthread.php?t=2429406)
Now I'm just making sure I have a stock MDL ROM ready to ODIN in case I screw up my device =). Hopefully this all works out.
Edit:
Looks like everything went beautifully. The MDL stock recovery wiped my /data partition perfectly, and I was able to reboot into a fresh and clean copy of KANGAKAT 6.0. Then I was able to use a terminal to flash TWRP, did a factory reset, flashed KANGAPOP 1.4, and now you can add me to the list of proud Lollipop users =)