Database Users

[Q] CM11 Problem.. Help Needed

Hi all,
I am interested in the CM11 ROM. Last night I spent 6hrs trying and failed, epically.
Here is what I did already:
1. Downgraded from 4.4.2 back to factory
2. Successfully rooted
3. Installed ROM Manager
4. Successfully downloaded CM11 and latest GApps
Then when I tried to boot into recovery it kept going to a screen with a little android guy lying on his back with a red triangle!!! I tried six times.
I got frustrated and just updated back to 4.4.2 and have been dealing with it. I am still rooted and have been able to remove my bloatware and other things you need root access for.
Any thoughts or help as to how I can install the CM11 rom?? I am happy running NovaLauncher and using DynamicNotifications to approximate it but really want to try out CM11.
Cheers and thanks!

Lucky there is no way to root on 4.4.2 yet or atleast no Recovery's yet it could be worse you're atleast rooted and it didn't brick your phone
Sent from my VS980 4G using Tapatalk

Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.

JRJ442 said:
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
Click to expand...
Click to collapse
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!

follow this step..
http://forum.xda-developers.com/showthread.php?t=2681205

android_nashville said:
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
Click to expand...
Click to collapse
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.

My first guess was that you missed the flashing the custom recovery step, which people above me have already helped ya out on. For being new to Android you did fairly well, you just missed that one step.
Good luck!

JRJ442 said:
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
Click to expand...
Click to collapse
thanks, forgot to mention it was only for D802 :good:

zekurosu said:
thanks, forgot to mention it was only for D802 :good:
Click to expand...
Click to collapse
I have an ATT D800 running 4.4.2. I can't decide whether its worth it to flash back to 4.2.2 to try again. Pretty happy with NovaLauncher + widgetlocke and fairly closely approximates what I am looking for.
For what its worth, I was in 4.2.2 when I tried the first time and failed. I think mackster is right, I didn't flash the custom recovery. I basically flashed back to 4.2.2->rooted->tried to boot into recovery (OVER and OVER) then gave up and upgraded back to 4.4.2.
Thanks for all the help. At least I now have a rooted phone and have been able to do some cool stuff with that. My goal is to get nexus 5 software in an LG G2 body (battery, camera, etc)

@android_nashville There's a way to have the best of both worlds. You can flash back to 4.2.2 (10d preferably) root, flash a custom recovery with Flashify or FreeGee. Both available on the play store. Then actually update to 4.4.2 following this thread http://forum.xda-developers.com/showthread.php?t=2483043. Eventually, if you want to flash custom ROMs you're going to have flash back to 4.2.2 and do this process regardless. The 4.4 aboot image (bootloader) can't be bypassed with Loki. Its been blocked. But some brilliant devs basically found out they can make a hybrid setup, with the 4.2.2 aboot, and everything else 4.4.2. This way you can have the ability to flash custom recovery, kernels and ROMs.

[Q] What is best way to get back to complete stock?

Hello,
What is the best way to get back to complete stock (including locked bootloader). I'm done with playing with custom ROMs (running CM11 right now). I want stock and guaranteed stability then nightmare dealing with nightlies etc.

artisticcheese said:
Hello,
What is the best way to get back to complete stock (including locked bootloader). I'm done with playing with custom ROMs (running CM11 right now). I want stock and guaranteed stability then nightmare dealing with nightlies etc.
Click to expand...
Click to collapse
I'm guessing you're on an I337 since you mentioned locked bootloader. If I were you I'd just flash a 4.4.2 stock ROM so that you can keep the possibility to use AOSP ROMs like the Google Edition ROMs and others. You can flash the ROM from HERE, use the version that doesn't say wBL at the end. Then just flash one of the 4.4.2 modems in RockRatt's I337 modem thread and it should work just fine. You could even reflash the MDL firmware before all of this to make it clean, or even just freeze the updater and stay on MDL.
If you really want to get rid of all possibility of running more than themed and modded TouchWiz ROMs, you can simply go to the General section, find the NB1 ODIN files, and flash them. If you want root after that, take the OTA to NC1 or sideload it and then use towelroot.

DeadlySin9 said:
I'm guessing you're on an I337 since you mentioned locked bootloader. If I were you I'd just flash a 4.4.2 stock ROM so that you can keep the possibility to use AOSP ROMs like the Google Edition ROMs and others. You can flash the ROM from HERE, use the version that doesn't say wBL at the end. Then just flash one of the 4.4.2 modems in RockRatt's I337 modem thread and it should work just fine. You could even reflash the MDL firmware before all of this to make it clean, or even just freeze the updater and stay on MDL.
If you really want to get rid of all possibility of running more than themed and modded TouchWiz ROMs, you can simply go to the General section, find the NB1 ODIN files, and flash them. If you want root after that, take the OTA to NC1 or sideload it and then use towelroot.
Click to expand...
Click to collapse
So if I flash one of NB1 ODIN files my phone will looks like something I get from ATT store if I walk in there today, right? That's what I want to achieve, completely something unadultered.

artisticcheese said:
So if I flash one of NB1 ODIN files my phone will looks like something I get from ATT store if I walk in there today, right? That's what I want to achieve, completely something unadultered.
Click to expand...
Click to collapse
Yes, it will be just like the others in every way, knox bootloader and settings and all, no custom flags or anything.

Softbrick/other questions

Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix

nola mike said:
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
Click to expand...
Click to collapse
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.

nola mike said:
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
Click to expand...
Click to collapse
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.

jmjoyas said:
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
Click to expand...
Click to collapse
Thanks for that, very enlightening.

nola mike said:
Thanks for that, very enlightening.
Click to expand...
Click to collapse
Just as an update, seems there's a workaround for Odin called heimdall, which is cross platform. . Haven't tried it, but looks like it should work.

I don't even know lol

Its been a very long time since I've had to dig this deep into flashing and I've always been a Samsung user so I'm somewhat use to the less difficult route. I'm running the 4.4.4 mokee ROM with the kitkat boot loader. Im trying to get miui running on my phone. The miui ROM is on 4.2.2 and I'm guessing requires a JB bootloader to flash. So my question is, is there a pre-rooted rsd package to get back to 4.2.2 so I can flash miui or do I have to flash back to stock, re-root and re-flash a custom recovery? Honestly I'm trying to get back for stability also. Unless someone knows where a KitKat miui ROM is for our phone? Other than the "V6" tablet ui ROM. It isn't no where stable enough.

brd912 said:
Its been a very long time since I've had to dig this deep into flashing and I've always been a Samsung user so I'm somewhat use to the less difficult route. I'm running the 4.4.4 mokee ROM with the kitkat boot loader. Im trying to get miui running on my phone. The miui ROM is on 4.2.2 and I'm guessing requires a JB bootloader to flash. So my question is, is there a pre-rooted rsd package to get back to 4.2.2 so I can flash miui or do I have to flash back to stock, re-root and re-flash a custom recovery? Honestly I'm trying to get back for stability also. Unless someone knows where a KitKat miui ROM is for our phone? Other than the "V6" tablet ui ROM. It isn't no where stable enough.
Click to expand...
Click to collapse
simplest route for you: install rsdlite, flash stock 4.4.2 which will upgrade you to kk bootloader. then install supersu from play store, then towelroot and root your phone. thereafter, use motocalypse to unlock bootloader.
after that you are free to pick and choose which rom you want to install. if you wish to install a jb rom, you will have to downgrade to jb bootloader. otherwise, you're free to install your favorite recovery followed by your favorite kk rom while still on the kk bootloader

brd912 said:
So my question is, is there a pre-rooted rsd package to get back to 4.2.2 so I can flash miui or do I have to flash back to stock, re-root and re-flash a custom recovery?
Click to expand...
Click to collapse
You don't have to be rooted to flash custom recoveries, so just downgrade to stock 4.1.2 (there was no 4.2) and then flash a custom recovery for the old bootloader.

You could also try this
http://www.droidrzr.com/index.php?/topic/50096-[How-To][Mobile-Downgrader]-Flash-Back-1.0-(07-15-14)#entry448942

thewraith420 said:
You could also try this
http://www.droidrzr.com/index.php?/topic/50096-[How-To][Mobile-Downgrader]-Flash-Back-1.0-(07-15-14)#entry448942
Click to expand...
Click to collapse
I flashed the JB file but it failed to flash a 4.2.2 ROM...since it flashes back to 4.1.2 would I have to flash a 4.1.2 based ROM and then flash a 4.2.2 rom?

brd912 said:
I flashed the JB file but it failed to flash a 4.2.2 ROM...since it flashes back to 4.1.2 would I have to flash a 4.1.2 based ROM and then flash a 4.2.2 rom?
Click to expand...
Click to collapse
If meant for 4.1.2 kernel then use flash back 4.1.2 then when recovery reboots flash the 4.1.2bl rom. Which 4.2.2 ROM are you trying?
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
If meant for 4.1.2 kernel then use flash back 4.1.2 then when recovery reboots flash the 4.1.2bl rom. Which 4.2.2 ROM are you trying?
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Miui. I'm gonna try the 4.1.2 miui and then after it boots see if it will flash the 4.2.2 ROM.

I can't get any jb ROM to flash using the flashback zip... I guess rsd it is

Sprint Galaxy S4 Rooting

I've spent hours searching and I know this is an old phone. Is ther anyway to root the Lollipop and download Jelly Bean (custom or stock) to it? I'm not worried about Warranties. I'm not exactly a newb and I don't like Lollipop at all. I don't mind KitKat, but what I hate is the front facing camera can't be flipped. Dumbest thing ever.

http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.

Strephon Alkhalikoi said:
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Click to expand...
Click to collapse
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.

BikerSk8rKid said:
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
Click to expand...
Click to collapse
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?

Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?

GDReaper said:
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Click to expand...
Click to collapse
I was half asleep and stressed out when I posted this. It's been a couple weeks or longer since I messed with the phone. Damn forums weren't resetting my password. When I mean I'm not a newb I mean I'm not like brand new to this and I know how to research. I guess you could say I'm not THAT stupid. haha
I'mma have to try this again and figure out what path's I kept trying. I'm so spaced out I can't remember hard any of it. Just that I tried to flash a stock and rooted rom with old odin and new odin. Spent 2 days straight messing with it and trying to get around it. But I kept getting blocked. I didn't come across CF-Autoroot. So I'll try that.
Strephon Alkhalikoi said:
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
Click to expand...
Click to collapse
Of all the researching I've done (I couldn't login) that one never showed up in my searchs. haha I'll have to give that one a try. It's been a couple weeks or longer. SPH-L720. I had a few Tri-Bands, but it seemed those were limited compared to the standard model.

Update: I went the CF-AutoRoot route and then tried to use Odin to flash stock mk2 rom. Now that I remember it kept failing everytime and then it would corrupt the current rom. I also tried using TWRP and couldn't get it to work properly.

That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.

GDReaper said:
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
Click to expand...
Click to collapse
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1

BikerSk8rKid said:
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
Click to expand...
Click to collapse
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.

GDReaper said:
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
Click to expand...
Click to collapse
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL

BikerSk8rKid said:
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
Click to expand...
Click to collapse
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.

GDReaper said:
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
Click to expand...
Click to collapse
I'll look into that and give it a shot. Thank you! I knew it wasn't THAT easy. LOL