Kitkat kernel help - G2 Q&A, Help & Troubleshooting

Why can't i install any kitkat kernel on any kitkat rom mainly AOKP and Paranoid.?Only thing i can guess is the fact that both roms will only install on a @blastagator modified jellybean boot-loader and not a kitkat boot-loader same with Paranoid lollipop.But back on subject i need some help ty.

Crumplet said:
Why can't i install any kitkat kernel on any kitkat rom mainly AOKP and Paranoid.?Only thing i can guess is the fact that both roms will only install on a @blastagator modified jellybean boot-loader and not a kitkat boot-loader same with Paranoid lollipop.But back on subject i need some help ty.
Click to expand...
Click to collapse
AOSP and Stock use different kernels, if that is what you are having an issue with. They are not interchangeable.

blastagator said:
AOSP and Stock use different kernels, if that is what you are having an issue with. They are not interchangeable.
Click to expand...
Click to collapse
So just to clarify in laymen terms,cause this is my first phone with an unlocked bootloader. In order to install a kernel, the kernel has to be compatible with the bootloader. This I already know. However my main problem is why AOKP and Paranoid KK roms won't install on using a KK bootloader. I can only install these two KK roms mentioned above with the JB bootloader only. This is what I don't understand.

Crumplet said:
So just to clarify in laymen terms,cause this is my first phone with an unlocked bootloader. In order to install a kernel, the kernel has to be compatible with the bootloader. This I already know. However my main problem is why AOKP and Paranoid KK roms won't install on using a KK bootloader. I can only install these two KK roms mentioned above with the JB bootloader only. This is what I don't understand.
Click to expand...
Click to collapse
Bootloader doesn't really matter as long as the hack you are using supports the bootloader. Our bootloader is locked, they just use bugs to get around the lock. Different BLs have different exploits available.
You could probably install those ROMs, you would just have to make sure the proper hack is applied first.

Related

Android 4.4.2 and MDL bootloader on I337

I have I337 with MDL bootloader. Omega 19 (4.3), MK2 GSM modem and MDL LTE modem.
New Omega 20 based on leaked 4.4.2 come.
I read Omega 20 installation notes than it works only with new 4.4.2 bootloder.
Does this means that the only way to install 4.4.2 is wait i337 4.4.2 stock, flash it and use safe strap.
PS
Is LOKI kernel for 4.4.2 TW available?
Was kinda wondering this myself.
I'm on 4.4.2 GE ROM, I assume just flashing a 4.4 ROM updates your bootloader but strangely I don't see any 4.4 TW ROMs in our Dev section yet?
Was hoping somebody has flashed an Intl 4.4 ROM with loki-doki and all was good.
seanpr123 said:
Was kinda wondering this myself.
I'm on 4.4.2 GE ROM, I assume just flashing a 4.4 ROM updates your bootloader but strangely I don't see any 4.4 TW ROMs in our Dev section yet?
Was hoping somebody has flashed an Intl 4.4 ROM with loki-doki and all was good.
Click to expand...
Click to collapse
Flashing a rom only updates the system and kernel. The modem, bootloader, and recovery stay intact. Odin packages contain the bootloader and modem. These are all on separate partitions.
The 4.4.2 released was a i9505 rom and only for them. You can be on an older bootloader and flash newer android version roms but you can't do the opposite and say flash a 2.3 rom while you on a 4.0 rom.
Also most people don't want the permanence of being stuck on a leak release and not being able to go back.
hednik said:
Flashing a rom only updates the system and kernel. The modem, bootloader, and recovery stay intact. Odin packages contain the bootloader and modem. These are all on separate partitions.
The 4.4.2 released was a i9505 rom and only for them. You can be on an older bootloader and flash newer android version roms but you can't do the opposite and say flash a 2.3 rom while you on a 4.0 rom.
Also most people don't want the permanence of being stuck on a leak release and not being able to go back.
Click to expand...
Click to collapse
Ahh ok, so I really do still have an MDL bootloader huh (even though I've flashed different modems).
But I can switch from a 4.4 GE/CM ROM to any 4.3 or 4.2.2 if I choose, so what do you mean not being able to go back?
seanpr123 said:
Ahh ok, so I really do still have an MDL bootloader huh (even though I've flashed different modems).
But I can switch from a 4.4 GE/CM ROM to any 4.3 or 4.2.2 if I choose, so what do you mean not being able to go back?
Click to expand...
Click to collapse
MDL was the second update I believe (right after release) for 4.2.2 before the the lock. Once you update the bootloader on these lock bootloaders (even MDL is locked, just has a loki work around) you can't go back. The bootloaders are going to be locked and you wont be able to flash a Odin .tar and go back. You are on there. YOu can flash 4.4 roms on a 4.2.2 bootloader but not a 4.2 rom on a 4.4 bootloader.
Alrighty, so to answer OP's question.
You should be fine to flash new Omega with a wipe of Cache/Davlik/System/Data followed by loki-doki.
seanpr123 said:
Alrighty, so to answer OP's question.
You should be fine to flash new Omega with a wipe of Cache/Davlik/System/Data followed by loki-doki.
Click to expand...
Click to collapse
not unless he is okay being stuck with a he new bootloader knowing he cant go to another rom unless its a 4.4
Omega (and all custom ROMs) wouldn't include the bootloader as you mentioned in your first reply...
seanpr123 said:
Omega (and all custom ROMs) wouldn't include the bootloader as you mentioned in your first reply...
Click to expand...
Click to collapse
It's true.
I am confused by what I read in the installation Instructions for Omega v20:
Installation:
1. Backup your device (nadroid backup, titanium backup, efs backup ... etc) and save the backup to a safe place.
2. Flash the new bootloder and modems with odin -> I9505XXUFNA1_Bootloader_Modems.tar
Click to expand...
Click to collapse

Any safestrap compatible for 4.4.2 roms now that official Kit Kat is out?

I've searched but haven't found anything other than jelly bean safestrap roms. is it safe to assume that at some point any safestrap compatible 4.4.2 roms might become available now that the M has a official kit kat?
Not sure what for as long as there's no root for locked phones.
No I meant any safestrap compatible 4.4.2 ROMS available now that official kitkat is out. Sorry should have been more clear.
I have a rooted but bootloader locked 4.1 razr m running Safestrap. As far as I know there have not been many options for ROMs being safestrap compatible for anything above 4.2
This would require KitKat with a 3.0 kernel, but KitKat on 3.0 just isn't KitKat.
iBolski said:
The issue with KitKat is it's a different kernel. In order to reap the benefits of KitKat, you need to run the latest kernel.
[...]
Therefore, don't expect to see a SS KitKat ROM.
Click to expand...
Click to collapse
dman9691 said:
No I meant any safestrap compatible 4.4.2 ROMS available now that official kitkat is out. Sorry should have been more clear.
I have a rooted but bootloader locked 4.1 razr m running Safestrap. As far as I know there have not been many options for ROMs being safestrap compatible for anything above 4.2
Click to expand...
Click to collapse
4.2 ROMs barely worked, I wouldn't even want to see a 4.4. Also, what version of 4.1 are you running? If you're still on one of the older versions, you might be able to to unlock the bootloader and get rid of SS.
RikRong said:
4.2 ROMs barely worked, I wouldn't even want to see a 4.4. Also, what version of 4.1 are you running? If you're still on one of the older versions, you might be able to to unlock the bootloader and get rid of SS.
Click to expand...
Click to collapse
Yes, it never hurts to try and see if the bootloader will unlock. Some people had to run the utility twice to get it to work. We had one individual on this forum that refused to listen to the benefits, until we badgered him enough (well, more like encouraged him) to really see the flaws in his logic. He wanted to keep root and be able to use TiBu to restore his apps, but then he stated he didn't care about root. But, I explained to him that going to KK will cause him to lose root and the ability to use TiBu, so he would have no way of restoring his apps and their related data since that required root.
We then explained that attempting to unlock the bootloader will NOT harm his phone. He tried it and after the second try, he had an unlocked phone. Now, he doesn't have to wait for an exploit (if it ever comes) to root KitKat. He can just sideload it now via ADB.
So, try to unlock it. Worse that can happen is, you'll find that an OTA was applied that fixed the exploit, or you could get lucky like the person I was just talking about and have an unlocked bootloader which will allow you to obtain root with KitKat.

From MDL 4.2.2 to CM11 (M3) and back

Hi. I'm not sure how to even ask this question. I've heard that the OTA 4.3 version of Android does something to the bootloader and disables loki patches or something like that. My question is... If I'm on MDL 4.2.2 now with Loki patch and TWRP recovery... if I use the CM11 web installer from CM and upgrade my custom rom to CM11 4.4.2... will CM11 mess with my bootloader to where I have to revert to SafeStrapper? or does CM11 not mess with the bootloader to which I can continue to install any rom I want? thanks
JJ5150 said:
Hi. I'm not sure how to even ask this question. I've heard that the OTA 4.3 version of Android does something to the bootloader and disables loki patches or something like that. My question is... If I'm on MDL 4.2.2 now with Loki patch and TWRP recovery... if I use the CM11 web installer from CM and upgrade my custom rom to CM11 4.4.2... will CM11 mess with my bootloader to where I have to revert to SafeStrapper? or does CM11 not mess with the bootloader to which I can continue to install any rom I want? thanks
Click to expand...
Click to collapse
No, it won't mess with your bootloader. If you update your firmware then your on trouble. But you're just flashing a custom rom so you're ok.
Sent from my Nexus 5 using XDA Free mobile app
Flashing ROMs is fine, but just so you know the CM Installer does not work on our device. You have to flash it in recovery.
Sent from my SGH-I337 running GPE

[Q] AT&T I337 MDL - Newest Firmware

Been trying to read and figure out as much as I can, but I'm lost. I rooted my phone right when I got it a few months after release. I have the MDL firmware and I'm running stock that I've modified to my liking. I rooted using motochopper, I have TB and SU and I have TWRP installed. I'm ready to take the jump and try to get an updated firmware, but don't know where to look. It seems a lot of the info in now for the newer firmwares.
I would like to run either Google edition or a modified TouchWiz I think. I like keeping things pretty clean and fast. I am currently running Aviate on top of TouchWiz and I like the clean organized feel of it, although a bit laggy.
Please help me XDA, sorry I know this is a newb post. I've been blocking the OTAs for over a year and I'm ready to move on.
First I would suggest NOT to use any STOCK firmware to update to 4.4.2
There are some newer Google Edition Roms I believe in the ATT original ANDROID SECTION. You can use them since you have twrp recovery. Those with newer firmware cannot use the latest google edition Roms unless they are made for safestrap.
Or if you want a modified stock Touchwiz with all the extra benefits you can flash directly to ShoStock-i 8.1 which is 4.4.2 based.
Keeping you MDL bootloader and the Loki bootloader bypass you have now let's you flash ANYTHING you want, including kernels.
If you update firmwares the bootloader becomes MORE LOCKED DOWN and you cannot flash any Roms that need a modified kernel like aosp based Roms, or any kernel other than stock.
Thank you ill check those roms out. I am aware that I DO NOT want to update my firmware, that's part of the reason I asked for advice, to see which roms work well with MDL. Most of what I found was all for newer FW versions.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Would I be better off upgrading to OUDHS Touch CWM-based Recovery 1.0.3.5 instead of TWRP so everything is auto Loki'd?
matchstick13 said:
Would I be better off upgrading to OUDHS Touch CWM-based Recovery 1.0.3.5 instead of TWRP so everything is auto Loki'd?
Click to expand...
Click to collapse
Sorry I haven't tried OUDHS so I cannot comment. But TWRP still works perfectly. For ShoStock you would NOT need to flash Loki-Doki patch or anything. The kernel in ShoStock-i is already Loki patched. If you plan on trying other Roms it is always best to keep the Loki-Doki flashable zip on your sdcard and flash it after flashing a ROM. Just extra insurance that won't hurt anything if the ROM is already lokified.
Ok going to try flashing this
http://forum.xda-developers.com/showthread.php?t=2537495
Followed by Loki Doki
Hope I'm doing this right.
matchstick13 said:
Ok going to try flashing this
http://forum.xda-developers.com/showthread.php?t=2537495
Followed by Loki Doki
Hope I'm doing this right.
Click to expand...
Click to collapse
Should work
Sent from my Nexus 5 using XDA Free mobile app

Can you downgrade to a custom ROM if you're rooted and already updated?

Hey guys, everything I've read has said once you update beyond 4.3 you can never go back down because of knox. I also saw someone mention you actually can downgrade to a custom ROM based on a previous build just not to stock. Can anyone clarify this for me? I'm not worried about breaking my warranty since it's long since expired. I'm on the rooted 5.01 Goldeneye ROM and want to go back to a 4.2 ROM. strictly for tethering purposes
What is the model # for the s4?
It's the AT&T sgh-i337
With a locked bootloader, the phone is limited to customs roms based off a stock Samsung rom. Aosp and cm will not install or run.
audit13 said:
With a locked bootloader, the phone is limited to customs roms based off a stock Samsung rom. Aosp and cm will not install or run.
Click to expand...
Click to collapse
Thanks for the reply! So if I stick to TouchWiz based custom roms I can downgrade without bricking my phone?
Yes, just don't touch the bootloader or modem.
audit13 said:
Yes, just don't touch the bootloader or modem.
Click to expand...
Click to collapse
Ok thanks. Can you suggest a good 4.2 ROM? Also, since I'm already rooted with safestrap, do I just wipe and flash the new ROM or do I need to install a different version of safestrap and kernal etc? I'm have trouble finding any instructions on how to downgrade. I appreciate all your help!
I can't recommend any 4.2 roms as I don't have the phone. Also, I don't think such an old rom will work on an lp modem and bootloader.
audit13 said:
I can't recommend any 4.2 roms as I don't have the phone. Also, I don't think such an old rom will work on an lp modem and bootloader.
Click to expand...
Click to collapse
Ok so based on your statement "I don't think such an old rom will work on a lp modem and bootloader," does that mean you actually don't think I can downgrade?
You can try but I don't think you will have a functioning phone in that the imei will not be properly displayed which means the phone wouldn't be able to connect to the carrier.
audit13 said:
You can try but I don't think you will have a functioning phone in that the imei will not be properly displayed which means the phone wouldn't be able to connect to the carrier.
Click to expand...
Click to collapse
I appreciate your help!

Categories

Resources