Database Users

Every custom ROM restart issues, eventually bootloops

over the last few days I've flashed a number of ROMs, mostly the Google Edition 4.2.2 and 4.3 ones and every single one of them eventually fails to boot hanging on the Samsung bootloader screen. and i say eventually because the first boot is almost always flawless, but then each time i reboot or power down, its almost guaranteed to loop.
I've tried so many different combinations that there's really not a single path I've taken every time, but the general steps are:
-root original firmware using motochopper
-install TWRP via GooManager
-reboot recovery and wipe everything, typically I do Advanced and select everything, then format Data
-then flash through ADB sideload, I do this since I wipe everything before flashing and I don't have an external SD card
-immediately after flashing ROM, I flash loki-doki also through ADB sideload. some of the ROMs I tried said they were lokied, but I still got the ATT invalid ROM message, so I reflashed with loki and it worked.
-then reboot system and the first time it comes up and works fine on every ROM I've tried
But if I power down or restart, on a very rare occasion it'll come up, but almost every time it hangs on bootloader screen. I also noticed once it's stuck on bootloader, power button becomes unresponsive, sometimes holding it powers down device, sometimes does nothing (have to press and hold twice)
If I flash back to stock using Odin, it works, boots, reboots, powers down just fine.
I've also tried flashing with a ROM and then immediately after with the stock ATT kernel, also booted up fine, but looped on restart.
Could this be hardware issue?
I'm about to give up on this and go back to stock for good, which would be really disappointing, can anyone help?

Flash a KT kernel and see what happens, I suppose you know which one correct?

TheAxman said:
Flash a KT kernel and see what happens, I suppose you know which one correct?
Click to expand...
Click to collapse
I assume KT means http://forum.xda-developers.com/showthread.php?t=2292341 ?
I've tried that too with jamal2367's 4.2.2 GE ROM (http://forum.xda-developers.com/showthread.php?t=2341794). It refused to boot all together.
First time I flashed with AOSP version since I thought that was an AOSP ROM, then reading more comments in the other thread it said I needed the TW version for GE ROMs, so I tried that too. Either way, neither of them booted at all, even the first time, so I gave up on KT and only used either ROMs' included kernels or ATT stock.

It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.

TheAxman said:
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
Click to expand...
Click to collapse
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?

collegebored said:
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
Click to expand...
Click to collapse
You know, I don't even look at anything that says loki anymore, I flash the rom I want and use MY carriers kernel, bootloops and hangs are just not there, I do not see these issues everyone has, because, I have this procedure everytime. So...
Btw, your good on your files you want to flash, but, if this does not work ie, GE and that kernel, try a TW rom with the kernel, bet it boots properly. I do not give a rats
a$$ about goole roms. They are not worth it. Btw, I use this procedure on TW and aosp roms, no issues. Just because it says it loki'ed, flash the kernel you know works, loki just confuses people.
The Ax says again an again..My opinion only!
Good luck sir.
BTW, I ran that rom with the kernel you chose, it should work just fine. Remember, flash the TW version.
Thanks Ax for your help here, your welcome.

Stuck on GS4 bootscreen

So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.

amishbobinc said:
So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.
Click to expand...
Click to collapse
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.

Cytality said:
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.
Click to expand...
Click to collapse
I think I did....is that bad?

amishbobinc said:
I think I did....is that bad?
Click to expand...
Click to collapse
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.

Cytality said:
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.
Click to expand...
Click to collapse
What about the stock MDL, if I flash that rom it should work - right?

amishbobinc said:
What about the stock MDL, if I flash that rom it should work - right?
Click to expand...
Click to collapse
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.

Cytality said:
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.
Click to expand...
Click to collapse
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?

amishbobinc said:
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?
Click to expand...
Click to collapse
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.

Cytality said:
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.
Click to expand...
Click to collapse
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.

amishbobinc said:
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.
Click to expand...
Click to collapse
Whats the rom you are using?

Cytality said:
Whats the rom you are using?
Click to expand...
Click to collapse
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.

amishbobinc said:
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.
Click to expand...
Click to collapse
While you have the phone turned on, go in settings and see what your baseband version is. If it ends in MDL then you're good.
After that, I don't know. I've never used that rom personally, it could be an issue with the rom itself, nothing really wrong with your phone. You can try to wipe and reinstall, or just try a different ROM.

Ok got it!!
TWRP and clockworkmod were both NOT formatting like they said they where. I had to manually go in and erase everything except the external SD. Then I did a clean install and everything works great.
Thank you for your help!

[Q] Need help finding a certain pacman ROM nexus 4

I need help finding a pacman ROM for the nexus 4 that is JB 4.2.2 NOT 4.3. I don't have a computer to re root. Preferably that has halo included. I have pacman 22.2 right now, and I lost root access for certain apps, my VPN won't connect anymore etc. Just random problems, and it seems most roms were upgraded to 4.3. Thanks.

You don't need a computer to upgrade to 4.3.
Since your bootloader is unlocked and you have a custom recovery, you can update your baseband to one compatible with 4.3 via recovery.
Then you could upgrade to the 4.3 rom of your choice. It'd be a good idea to also have the supersu 1.65 zip handy to flash as well, although most custom roms come with one form of su or another.
Update twrp/cwm to newest version first. Grab updated radio of your choosing (hybrids if you care about LTE or 5ghz wifi, etc). Grab rom + 4.3 gapps. Flash away.
You may to wipe data (but you don't have to clear "sdcard"). Be careful which you choose so you don't accidentally do so...

I don't have a computer. As far as I know, there's no way to keep root when updating from 4.2 to 4.3. That's my main reason. I don't have a computer to re root. I have superSU pro, but survival mode is apparently hit and miss with OTA updates, unless there's a way to keep root without having to use a computer?

False. No need to use factory images to upgrade to 4.3. Doesn't look like you bothered to read my post.
Easiest way for you is to download Goo Manager. Use that to download and install the latest TWRP (2.6.3.0 currently). Download a new radio in flashable zip: http://forum.xda-developers.com/showthread.php?t=2087227 for .84 stock.
Download latest pacman rom. Download 4.3 gapps. Backup /data if necessary to /sdcard. Wipe data without wiping "sdcard" (recommended but may/may not be required. If you get a bunch of FCs, you'll need to wipe). Flash rom. Flash gapps. Done.
If you're downloading anything else or doing whatever else, you're on your ****ing own if you **** **** up.
I suppose it's worth noting that this won't update your bootloader, but the old one works just fine.

Ok. I followed your direction's, and have pacman 4.3 build 1. Normally on any other ROM performance is great, but on this one out of the 1.8GB of RAM I have, almost all of it is used up, and my phone is extremely slow. I've never had this issue before so I don't know what to do, any way to fix this, or is it the ROM itself?
Sent from my Nexus 4 using XDA Premium 4 mobile app

sinndissension said:
I need help finding a pacman ROM for the nexus 4 that is JB 4.2.2 NOT 4.3. I don't have a computer to re root. Preferably that has halo included. I have pacman 22.2 right now, and I lost root access for certain apps, my VPN won't connect anymore etc. Just random problems, and it seems most roms were upgraded to 4.3. Thanks.
Click to expand...
Click to collapse
Here you go.
https://copy.com/qgIs9ghyJ6E8

Thank you VERY much. I really appreciate it.

sinndissension said:
Thank you VERY much. I really appreciate it.
Click to expand...
Click to collapse
You're welcome.
Sent from my Nexus 4 using xda app-developers app

[Q] sgh i337m can't install any custom rom

Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.

wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!

wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
First off I am hoping you are flashing from recovery and not trying something through goo manager. Second, it sounds as though you are skipping the wiping step before installing a new rom, you absolutly have to wipe cache/dalvik/ and factory reset all before flashing any rom.... also I wipe the system too to make it a clean install, make sure you put the rom of choice on the external sd and make sure you have a nanroid backup with your installed recovery twrp or cwm.....
PS lokidokie and saftey starp only apply to US versions (I337) not the Canadian I337M use only the roms build of this model.... I haven't had very good luck with cm based roms in the past so I tend not to flash those... I flashed one rom and the phone got super hot ... not sure what the issue was ... nand back to stock starter over with a differnet rom

Adizzzle said:
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!
Click to expand...
Click to collapse
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?

wondakson said:
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?
Click to expand...
Click to collapse
Please... you need to provide some more info for people to help you..... rom you tried to install and the steps.. not tryin to be mean just hard to help without details....

Ahh I know the problem if your flashing all of them from the att section. It could be that all of those roms you tried have loki built into the kernel and is stopping you from booting. Are u choosing ones that say they are specifically for the Canadian model or the ones for att?

I would also suggest booting once first before flashing gapps. I am using this Carbon rom http://forum.xda-developers.com/showthread.php?t=2568699 and it's universal, for US or CA models. I highly recommend it.

Stuck looking for all the advice I can get

Ok, started a new post so that I can put everything in one place. Dev's please feel free to delete other one.
I have one of the first gs4's, it was rooted with TWRP installed. I was running Liquidsmooth rom when I founf the GPS to not be functional.
I trying flashing some different modems, none of them fixed that. (Mk2, Nb1)
Tried multiple different ROMS, also did not fix the problem. Ended up CM 11, liked the rom so I left it on. Everything working fine.
This morning I rebooted the phone and it hung on the SAMSUNG GALAXY S4 screen. Won't go past it. Booted into recovery. Tried to restore a backup, but after it too hung at SGS4 screen. Went back in, reflashed, wiped, still stuck.
Tried flashing the uvamdl.tar in odin, and that failed every time saying secure check fail SB12 on the phone.
Went back to playing with TWRP, because I am stuck. Found that if If I do a full wipe, including data (where you have to type yes), then flash CM11 I can get it to boot into the phone, but only once. If I reboot, it hangs again, and I have to go in, wipe, and start all over.
Here is what is weird, it only works with CM11, not any other ROM.
Obviously I can't format every time I want to reboot the phone, so I am looking for a way to get this back to normal.
attached current specs with screenshot
I am using a win 8.1 laptop right now, but when I get home I would have access to a windows 7 machine.
I am currently traveling and desperately need the phone, so any help you could offer would be most appreciated.

is there anyone who can help me decipher this issue?

There was a bug a while back where CM11 would hang sometimes on reboots, but you could always just reboot a couple more times and get it to boot. Why are you having to reboot? Just get CM on there, get it booted, and leave it be until you get back. You could try a newer nightly, but I'm not sure it would fix your problem.

im actually veery very suprised u got a cw rom to work period on a nb1 device...
Sent from my Venomous Droid Blue Chrome Edition S4 (team: @Venom0642 @ted77usa @rebel1699) ~ 20GB free cloud https://copy.com?r=vtiraF

Your android version 4.4.2. It appears you are leaving some information out of your post. If you have an AT&T phone you must be using Safestrap? MF3, MK2, etc.. can only use Safestrap as a recovery. I am also assuming your baseband...NB1 is due to the modem flashing, but that really won't make a difference because CMxx will not run on Safestrap. Your best option now is to Odin back to your original firmware version, re-install Safestrap, and stick with the compatible TW ROMs listed in the safestrap thread. If you don't understand what I am saying you will need to search and read about it all. You really should have known all of this before attempting to do anything to your phone. Good luck.

kevp75 said:
im actually veery very suprised u got a cw rom to work period on a nb1 device...[/url]
Click to expand...
Click to collapse
scott14719 said:
Your android version 4.4.2. It appears you are leaving some information out of your post. If you have an AT&T phone you must be using Safestrap? MF3, MK2, etc.. can only use Safestrap as a recovery. I am also assuming your baseband...NB1 is due to the modem flashing, but that really won't make a difference because CMxx will not run on Safestrap. Your best option now is to Odin back to your original firmware version, re-install Safestrap, and stick with the compatible TW ROMs listed in the safestrap thread. If you don't understand what I am saying you will need to search and read about it all. You really should have known all of this before attempting to do anything to your phone. Good luck.
Click to expand...
Click to collapse
I would venture that he still has MDB or MDL bootloader as to HOW and WHY he can run CM11.
To OP I also would suggest flashing the STOCK firmware that MATCHES what bootloader you have and start fresh. Just MAKE SURE to reinstall TWRP immediately, then flash CM11 or whatever ROM you want. This IS ASSUMING you still have the MDB or MDL bootloaders.
To check/verify which bootloader you have installed.
1. Download Terminal Emulator
2. Open Terminal Emulator app and hit OKAY to give it Root Rights.
3. Close Terminal Emulator
4. Re-Open Terminal Emulator and type "su" Enter (WITHOUT THE QUOTATION MARKS)
5. Type "getprop to.bootloader" (WITHOUT the quotation marks).
6. See the screenshot where mine shows I337---MDB as that is where your phone will show which bootloader you have installed.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

RockRatt said:
I would venture that he still has MDB or MDL bootloader as to HOW and WHY he can run CM11.
To OP I also would suggest flashing the STOCK firmware that MATCHES what bootloader you have and start fresh. Just MAKE SURE to reinstall TWRP immediately, then flash CM11 or whatever ROM you want. This IS ASSUMING you still have the MDB or MDL bootloaders.
To check/verify which bootloader you have installed.
1. Download Terminal Emulator
2. Open Terminal Emulator app and hit OKAY to give it Root Rights.
3. Close Terminal Emulator
4. Re-Open Terminal Emulator and type "su" Enter (WITHOUT THE QUOTATION MARKS)
5. Type "getprop to.bootloader" (WITHOUT the quotation marks).
6. See the screenshot where mine shows I337---MDB as that is where your phone will show which bootloader you have installed.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
thanks to all, i am on mdb bootloader, sorry, thought i put that in the text, i am not safe strap.
when i try to odin the original file image i get the error message, any ideas why i cannot odin?

Don't select "YES" in TWRP before rebooting--:good:
If you can't solve anything reformat your cards--backup first
Doesn't OP have to be on MDL "not MDB" to flash some roms?

aawshads said:
thanks to all, i am on mdb bootloader, sorry, thought i put that in the text, i am not safe strap.
when i try to odin the original file image i get the error message, any ideas why i cannot odin?
Click to expand...
Click to collapse
Did you try redownloading it? Otherwise make sure your phone cable is good and try different USB ports, maybe a different version of ODIN if you want
Sent from my SGH-I337 running Blackbox 3.0

rugmankc said:
Don't select "YES" in TWRP before rebooting--:good:
If you can't solve anything reformat your cards--backup first
Doesn't OP have to be on MDL "not MDB" to flash some roms?
Click to expand...
Click to collapse
I am not positive as I haven't flashed any aosp based Roms, I am still on MDB bootloaders as well. So far never needed to flash the MDL bootloaders though for any Roms I have run. It is possible that CM needs the MDL bootloader though.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

RockRatt said:
I am not positive as I haven't flashed any aosp based Roms, I am still on MDB bootloaders as well. So far never needed to flash the MDL bootloaders though for any Roms I have run. It is possible that CM needs the MDL bootloader though.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
Yeah Rock, I forget--too many roms that I flash. I do remember a dev saying that you must be on mdl for something. But, it was way back early on. I did a lot of CM when I started flashing years ago. But, started with mostly TW when I got the s4. So, seems it would have been TW. My "old" brain don't remember as good as it use too-- Oh well, hope the OP gets it sorted--

i wanted to thank everyone. after multiple attempts, downloads, etc, I finally got odin to work. so I flashed an original image, rooted, installed flash and then cm11, and everything (including GPS!) seems to be working. I appreciate all of the help and advice that was given.

aawshads said:
i wanted to thank everyone. after multiple attempts, downloads, etc, I finally got odin to work. so I flashed an original image, rooted, installed flash and then cm11, and everything (including GPS!) seems to be working. I appreciate all of the help and advice that was given.
Click to expand...
Click to collapse
Glad you got it
Sent from my SGH-I337 using Tapatalk