Database Users

How to Unbrick SGS4

I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!

Did you try and reflash recovery ? Does the phone boot up once you restore via Odin ?

Have you tried flashing twrp via Odin?

I have not tried flashing TWRP with Odin... is there a Odin version of TWRP?
It did not boot after flashing stock. I'd like to Odin TWRP if it's available.
I found an Odin TWRP.tar for SGS3, but nothing for S4, yet. Need a little more help.

Did you try rooting and flashing twrp via goomanager? I had something similar happen to me on my skyrocket and that's how I fixed it.

Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium

TheAxman said:
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This version of CWM claims to work with Aroma on the S4...
http://forum.xda-developers.com/showthread.php?t=2322682

scott14719 said:
This version of CWM claims to work with Aroma on the S4...
well lets take a look see...shall we. thanks
Click to expand...
Click to collapse

came across this thread: http://forum.xda-developers.com/showthread.php?t=2281287
it converts an img to an odin-flashable tar.
i went ahead and converted the latest twrp img for the at&t S4 and have attached it. i have not tested it as i am not near my device at the moment. if you decide to try it, unzip the tar.md5 and flash at your own risk as i have not tested this method by @cabloomi.

False aroma works fine with twrp on a gs4.
Sent from my SGH-I337 using Tapatalk 4 Beta

This happened to me. Use odin to put TWRP back on. You'll be fine.
Sent from my SGH-I337 using Tapatalk 2

Yeah I had this a couple different times trying to get rid of the custom/lock icon boot up. Flash fresh stock rom, root it and install recovery with "Root and Recovery for ATT-TMO GS4-CASUAL-R527b" --> http://forum.xda-developers.com/showthread.php?t=2297900 then flash the recovery you want etc, and restore Nandroid of backed up rom. Worked for me!

Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you

JJ5150 said:
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Click to expand...
Click to collapse
I had a similar issue. When you hold the key combination to boot into recovery, do it for more than one cycle. Sometime for some reason it doesn't take the first time so keep holding the buttons. After getting into android recovery, clear cache and reset the phone.

JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
Click to expand...
Click to collapse
When I had the problem is sounds like your having I Odined the Stock image back to the phone and then cleared the dalvik and cache with the stock recovery menu, then I was able to boot, I then rooted and used the debloater program found here on the forums and then just downloaded goomanager and installed TWRP, the one it pushes is LOKIed for you.
This is also the only .img file I can find for the our version of TWRP. IIRC you can use Odin to flash it
EDIT: Like trublu said, you may have to do it several times (clearing the caches in the stock recovery after ODIN)

JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing.
Click to expand...
Click to collapse
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
JJ5150 said:
I have yet to find a Odin version of TWRP that's loki'd for the S4.
Click to expand...
Click to collapse
i believe that all s4 recoveries are "loki'd", if you will.

xBeerdroiDx said:
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
i believe that all s4 recoveries are "loki'd", if you will.
Click to expand...
Click to collapse
The Tmo and Sprint variants do not require Loki'd recoveries, as their bootloaders are not locked.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands

JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
They do great work..used them 2 years ago. With a mytouch..ouch..
Sent from my SAMSUNG-SGH-I337 using xda premium

JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
It's called Jtag repair. And the guys you mentioned have saved many a ass with it. I've seen several good results. Unless something else is found, it is the only way I know of to fix a truly bricked phone. Some people (those who flash a lot and Dev a lot) have their own Jtag boxes.
BTW, which tool / method did you use to convert the .img to a TAR? I've seen a couple of methods and a tool or two but I was wondering if you used something I don't know about? TIA.

[Q] S4 Bell 1337m wont boot after flash.

Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced

BurnAll said:
Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced
Click to expand...
Click to collapse
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?

agent929 said:
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?
Click to expand...
Click to collapse
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142

BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
heck at this point i'd be happy just to get it back to normal as its late and i need to sleep and work tomorrow

BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)

agent929 said:
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)
Click to expand...
Click to collapse
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen

BurnAll said:
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen
Click to expand...
Click to collapse
It says page not found...get the dots out of your link

Did you use your carriers Kernel?

Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.

agent929 said:
Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.
Click to expand...
Click to collapse
i have the m

BurnAll said:
i have the m
Click to expand...
Click to collapse
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.

agent929 said:
It says page not found...get the dots out of your link
Click to expand...
Click to collapse
sorry here it is.
another fella on bell said this one worked for him
http://forum.xda-developers.com/showthread.php?p=41675354

lgsshedden said:
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.
Click to expand...
Click to collapse
okay thanks i'll try to restore it using odin with the MG1 and then give the philz a shot. i'll update u once i've done so.

CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304

lgsshedden said:
CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304
Click to expand...
Click to collapse
okay got it back to stock, now quick question for the philz do i flash the .tar with odin? or do something else with the .zip?

Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

agent929 said:
Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.

BurnAll said:
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.
Click to expand...
Click to collapse
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz

BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
READ THIS FIRST:
MAKE SURE YOU DO NOT HAVE THE MF3 FIRMWARE ON YOUR S4. THAT IS THE MOST IMPORTANT THING TO DO RIGHT NOW. IF YOU DO, DO NOT ATTEMPT TO INSTALL A CUSTOM RECOVERY.
You don't have a custom recovery already that's why. Did casual not install TWRP for you? If not try installing Goo Manager from the app market and try installing TWRP that way. MAKE SURE THAT WHEN YOU INSTALL IT, IT SAYS YOUR MODEL NUMBER EXACTLY! I CAN NOT STRESS THIS ENOUGH! When you have TWRP installed, then flash philz with TWRP and you'll have that custom recovery instead.

BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
do not use the zip you quoted it is not for your phone
use odin flash the tar philz_touch_5.15.0-jfltecan.tar.md5
now you have stock updated MG1 firmware with the latest baseband
root by CF root
Philz Recovery
Now follow the next steps:
1. set up your google account play store etc.
2.next, go into the recovery and do a full nandroid backup -- this gives you a stable base you can restore when needed
3. go flash a custom rom, I highly recommend the latest version of Goldeneye -- updated, well maintained, great developer, clear install instructions
4. try itt then again, use recovery to make a 2nd nandroid, this one of your custom rom install -- try different kernels, every phone is different and someone's favorite kernel just may not like your phone -- doesn't make it a bad kernel just makes it the wrong one for your phone, flash a different one
5. theme if you want -- this is where your recoveries become important as themes are notorious for not always sitting well and all is ok if you have a backup you can return to
6. NEVER flash a baseband from another variant -- stick with your MG1 from your carrier until your carrier updates stock firmware

[Q] Cant flash Recovery

i installed safestrap and tried updating to oudhs recovery through recovery.
it says it installs but when i reboot its still safestrap.
also tried installing twrp thorugh android emulator still have safestrap.
any suggestions?

You can't flash a recovery. You're going to have to return to stock
Edit how can someone with so many posts know so little about their device. If you're on ss you have to use the recovery that comes with it. Read the stickies

but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea

bstylz911 said:
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
Click to expand...
Click to collapse
So if you are on MDB or MDL (You must have been if you have the AT&T S4 and custom recovery) just Odin back to stock firmware and re-install whichever custom recovery you want (as long as it is for this phone and LOKId). Make sure you get the custom recovery on the phone before it tries to update to a firmware that you can't do anything (other then Safestrap) with. Search and read to find the information you need if you don't understand what I am telling you. And don't do anything to your phone until you do. Good luck.

[Q] Flashed new TWRP now no recovery.

I installed the KOT49H GE ROM on my AT&T SGH-I337 and it runs great. I then decided to see if there was an update to TWRP and I found an updated one and flashed it via goo.im. I later read that this is not the way to do it. Anyway, when I boot into recovery a big yella triangle appears and at&t scolds me for running in authorized firmware. I can boot into download, cancel it and the ROM boots and runs fine.
Under the "about device" page on settings it says the baseband is MK2 (because I flashed that modem). If I look at the boot loader version via android terminal emulator it shows I'm still on MDL.
Any ideas how to get recovery working again?

I am trying to understand the reason why you flashed a recovery.
From your post, it looks like you are using safestrap and deadly venom tool to run GE.
You can flash the MLD files from the tool to get the recovery back.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader

insaneretard said:
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
Click to expand...
Click to collapse
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.

jmjoyas said:
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
Click to expand...
Click to collapse
Thanks for helping me out. I tried this yesterday and today with the link you provided. When I try to flash it via odin, it comes up as failed. On my phone, it says "SECURE CHECK FAIL: recovery" in red letters on the download page. Any other ideas?

You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Red_81 said:
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Do i need root to do this? I don't think I even have root any more. I'm running a custom ROM without root access. I tried to use CASUAL to root and install the recovery but it couldn't root it.

You will only need to root again if you go all the way back to stock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Problems with ODIN'ing stock recovery

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 =)