Where's the Kit Kat 24a VZW ROM thanks to xdabbeb.
WARNING.....This won't boot without a 24a custom recovery or a 12a patched kernel.
WARNING....
There currently is no 24a custom recovery.
Download. Do not flash till further testing...
.removed.....
24a modem:
https://mega.co.nz/#!Rd1VGJiB!3P-8GBSR-Dl4Fr-9Byu_UkIRWtOZQQKs9odehiVr4LI
KK kernel:
http://forum.xda-developers.com/showthread.php?t=2699123
Flashing scenarios:
On 12b with twrp, no kk ota done.
Flash ROM. Flash xdabbeb's kk kernel. If no radio flash 24a modem.
I havent had time to test this.
Sent from my VS980 4G using Tapatalk
MicroMod777 said:
Here's the Kit Kat 24a VZW ROM thanks to xdabbeb.
WARNING.....This won't boot without a 24a custom recovery or a 12a patched kernel.
WARNING....
Flash for testing.
https://mega.co.nz/#!9R9yHaCD!B6OG_eBdXPlUUbjIukYLg3H1ufiRZ7uUfQsWQ6yoKeg
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Will give this a flash tonight when I have access to real WiFi. Work WiFi got me downloading like I'm back on 56k
Sent from my LG-VS980
Lawlrus said:
Will give this a flash tonight when I have access to real WiFi. Work WiFi got me downloading like I'm back on 56k
Sent from my LG-VS980
Click to expand...
Click to collapse
Micromod...Do we need to have DD'ed the 12b aboot from JC's post? Or will any old loki'd aboot work as long as we flash XDABebb's stock kernel with this ROM? I take it we need to also flash the KK baseband. Should we flash the baseband first or make sure it boots. I know we will have to flash the 12b baseband to restore our old 12B rom such as Malladus 1.2.9.
Thanks to you and everyone else who havn't seen this allowing me to download @ 3MB p/sec
Thank you for this. I will download and test. Can't wait for your debloated version.
jrgilbert79 said:
Micromod...Do we need to have DD'ed the 12b aboot from JC's post? Or will any old loki'd aboot work as long as we flash XDABebb's stock kernel with this ROM? I take it we need to also flash the KK baseband. Should we flash the baseband first or make sure it boots. I know we will have to flash the 12b baseband to restore our old 12B rom such as Malladus 1.2.9.
Thanks to you and everyone else who havn't seen this allowing me to download @ 3MB p/sec
Click to expand...
Click to collapse
You need to have done everything needed to get on 24a plus everything needed to get the recovery on 24a. Older roms or backups will not work with 24a recoveries without old basebands.
Cannot wait for a debloated version of this!!
nrage23 said:
You need to have done everything needed to get on 24a plus everything needed to get the recovery on 24a. Older roms or backups will not work with 24a recoveries without old basebands.
Click to expand...
Click to collapse
I don't think this makes a whole lot of sense... If I currently have TWRP 2.7 and an old aboot. All thats required for this to flash is BB, ROM, and patched Kernel. Do we need to apply the recovery img from JC's thread or is the TWRP 2.7 we already have gonna work?
MicroMod777 said:
Here's the Kit Kat 24a VZW ROM thanks to xdabbeb.
WARNING.....This won't boot without a 24a custom recovery or a 12a patched kernel.
WARNING....
Flash for testing.
https://mega.co.nz/#!9R9yHaCD!B6OG_eBdXPlUUbjIukYLg3H1ufiRZ7uUfQsWQ6yoKeg
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
jrgilbert79 said:
I don't think this makes a whole lot of sense... If I currently have TWRP 2.7 and an old aboot. All thats required for this to flash is BB, ROM, and patched Kernel. Do we need to apply the recovery img from JC's thread or is the TWRP 2.7 we already have gonna work?
Click to expand...
Click to collapse
He states you need a 24a custom recovery. You could try just getting the 24a recovery.
nrage23 said:
He states you need a 24a custom recovery. You could try just getting the 24a recovery.
Click to expand...
Click to collapse
How do u go about getting a 24a recovery
Jduncan312 said:
How do u go about getting a 24a recovery
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2702958
I do not think it will work without getting to stock rooted 24a first. You can try it but I would not do it. I am on stock rooted 24a with the 24a version of TWRP. It is not terribly difficult to do.
Jduncan312 said:
How do u go about getting a 24a recovery
Click to expand...
Click to collapse
I agree with this. In order to avoid confusion and a million requests/doesn't work replies can MicroMod provide a guide to flashing this in the OP. Even if it is copied bits from JC and XDABebb's guide I think it will help quell the issues. Most people's eyes probably will light up thinking this is something most can flash in the current state to avoid the commands some feel are dangerous. I know quite quickly in the ATT and TMobile threads there was flashable content entitled KK the easy way which seemed much more straight forward than this does. To clarify I am not complaining I just wanted to get the real skinny and help others understand if this is not a KK the easy way type zip. :angel:
nrage23 said:
He states you need a 24a custom recovery. You could try just getting the 24a recovery.
Click to expand...
Click to collapse
Jduncan312 said:
How do u go about getting a 24a recovery
Click to expand...
Click to collapse
There is no 24a custom recovery, per se. I believe what he means is that you'll need a custom recovery so that you have the ability to flash this. In order to do so, your aboot/bootloader will need to be 12b as that is the last loki-exploitable version...which is therefore the only way you can have any custom recovery at this point.
I think it's an excellent idea for someone to make a flashable zip for those that just want to update in that way, but please keep in mind that there are a number of other partitions involved beyond system, boot, aboot, and modem that should also be updated properly. Improperly mixing/matching/flashing them can cause problems. I don't want to scare anyone off of doing this...just make them aware.
I posted this so we can find a working kernel.
Sent from my VS980 4G using Tapatalk
nrage23 said:
He states you need a 24a custom recovery. You could try just getting the 24a recovery.
Click to expand...
Click to collapse
You just quoted that you only read half of what he said. 24a OR KitKat kernal patched to work on 12b. The same way people are installing cloudypro 2. There are two possible ways for us to get a 4.4 stock ROM.
Sent from my LG-VS980
xdabbeb said:
There is no 24a custom recovery, per se. I believe what he means is that you'll need a custom recovery so that you have the ability to flash this. In order to do so, your aboot/bootloader will need to be 12b as that is the last loki-exploitable version...which is therefore the only way you can have any custom recovery at this point.
I think it's an excellent idea for someone to make a flashable zip for those that just want to update in that way, but please keep in mind that there are a number of other partitions involved beyond system, boot, aboot, and modem that should also be updated properly. Improperly mixing/matching/flashing them can cause problems. I don't want to scare anyone off of doing this...just make them aware.
Click to expand...
Click to collapse
So...I bit the bullet installed the KK BB first...:good: Flashed the Rom next :good:...error flashing both of XDABebb's vs980 KK kernels
Extracting Files
Loki Patch/Flash Kernel
assert failed: run_program( " /tmp/loki.sh") == 0
E: Error executing updater binary in zip '/sdcard/TWRP/Kernels/KK/xdabebb_vs98024a_kernel_linaro.zip'
Error flashing zip ' " BLAH BLAH"
Updating Partition Details...
Is this because my aboot is most likley still 10b from ancient times long forgotten. I have never OTA'd only flashed custom JB roms of AOSP and Stock currently Malladus 1.2.9 which is 12b?
Thanks to everyone so far and appreciate direction.
Edit: Scary restore...my restore backup window was empty...I played around with TWRP 2.7.0.0 after I flashed the 12b radio back. Had to wipe everything but internal again, Go into advanced...Unmount all parts...remount all partitions. Use file manager to search the backup directory to make TWRP self aware and then I could restore.
Restoring now to Malladus 1.2.9 (12b)
Edit 2: Restore completed...re-flashed 12b Radio and Furnace 1.7.1 kernel for good measure. Wiped cache and dalvik once more cause Ill wipe till I'm bloody successfully rebooted.
What we all learned: Restoring is not a big deal but I don't know what would happen if you flushed TWRP out of RAM by accidentally rebooting after any failure. I am assuming power+down vol would be fine but please don't make an ass-umer out of me
jrgilbert79 said:
So...I bit the bullet installed the KK BB first...:good: Flashed the Rom next :good:...error flashing both of XDABebb's vs980 KK kernels
Extracting Files
Loki Patch/Flash Kernel
assert failed: run_program( " /tmp/loki.sh") == 0
E: Error executing updater binary in zip '/sdcard/TWRP/Kernels/KK/xdabebb_vs98024a_kernel_linaro.zip'
Error flashing zip ' " BLAH BLAH"
Updating Partition Details...
Is this because my aboot is most likley still 10b from ancient times long forgotten. I have never OTA'd only flashed custom JB roms of AOSP and Stock currently Malladus 1.2.9 which is 12b?
Thanks to everyone so far and appreciate direction.
Edit: Scary restore...my restore backup window was empty...I played around with TWRP after I flashed the 12b radio back. Had to wipe everything but internal again, Go into advanced...Unmount all parts...remount all partitions. Use file manager to search the backup directory to make TWRP self aware and then I could restore.
Restoring now to Malladus 1.2.9 (12b)
Click to expand...
Click to collapse
Correct. There's a check in the script that verifies you have a 12b aboot. It's just for safety, so if you feel brazen you can change the "vs98012b" to "vs980" in the loki.sh script.
xdabbeb said:
Correct. There's a check in the script that verifies you have a 12b aboot. It's just for safety, so if you feel brazen you can change the "vs98012b" to "vs980" in the loki.sh script.
Click to expand...
Click to collapse
XDABebb before I go all Rambo has anyone tried any KK related installs with 10b/11a? I do not really think there is much of a diff and I would have thought that with all the weird security issues with 12b when it came out devs would just have tried the older less quirky aboots to begin with. But I can't make that call I am just a Lemming on these forums
Looking at it from the opposite perspective I have been using 12b JB kernels with whatever aboot I currently have for the last few months with 0 issues so in theory...who's up next LAWL
Anybody find a working kernel for 12a?
Sent from my VS980 4G using Tapatalk
MicroMod777 said:
Anybody find a working kernel for 12a?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
12a? isnt that older than 12B?
why wouldnt the kernels ie furnace, dr87, paek work?
steveo17 said:
12a? isnt that older than 12B?
why wouldnt the kernels ie furnace, dr87, paek work?
Click to expand...
Click to collapse
From what I have gathered the only important step is to DD the 12b aboot to your device and then everything should come easily once we have a solid kernel....I attempted it earlier and the kernel check failed because my aboot is 10a since I have never restored a tot/kdz or took an OTA. I haven't gotten a response back if we can DD the 12b safely while on a JB ROM in the interim so we have a backup that will work while we are testing kernels.
To answer your question though we need a new Kernel that works with KK 24a and has been patched to work with the 12b aboot and boot image.. We don't necessarily have to worry about hte boot image because that is included in the flashable ROM its just the specific aboot that is killing most of us. I also asked if it could be written to work with 10a and 11a aboots as well so it wouldn't matter since they are really the same except the revision number. I also haven't heard back on that subject either.
Related
Hi
I'm using a VZW G2 VS980, on 12B. I rooted it, install CWM with Simple tool V3.2
I installed Cloudyfa 's CloudyPro 2.2 (KK), all the steps are done correctly, it worked but a little buggy.
The stupid thing is I tried to restore the phone with CWM from the backup (of the 12B rom), and now it stucks in the boot LG logo. I can still access CWM though, works fine.
The question is: should I sideload another ROM (or recovery - KK based) and go from there to save time or go back to stock (11A)? And then how should I procceed to get a latest custom KK rom?
Thanks guys
Flash cloudyfa Rom again so u can boot up and download a jb baseband and flash that. Wipe as normal then restore your jb backup.
Sent from my VS980 4G using XDA Premium 4 mobile app
Esteway.619 said:
Flash cloudyfa Rom again so u can boot up and download a jb baseband and flash that. Wipe as normal then restore your jb backup.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi
Thanks but I tried that, stucked at LG logo too...
So when I restored from the backup, the baseband is still KK? (I flashed KK baseband before flashing cloudy)
trungbeo said:
Hi
Thanks but I tried that, stucked at LG logo too...
So when I restored from the backup, the baseband is still KK? (I flashed KK baseband before flashing cloudy)
Click to expand...
Click to collapse
You need both a JB backup and be running the JB baseband. If you did not explicitly install a JB baseband and restore a JB backup you have one or the other but not both.
A trouble I had was even though I restored the JB baseband and restored a JB backup it still didn't boot and that required dirty flashing my ROM over to get it to work.
The thing is I'm trying to get a custom KK rom that works, I don't want to go back to JB.
So should I go back completely to JB (like you said, falsh JB baseband and restore) or somehow flash another KK rom?
trungbeo said:
The thing is I'm trying to get a custom KK rom that works, I don't want to go back to JB.
So should I go back completely to JB (like you said, falsh JB baseband and restore) or somehow flash another KK rom?
Click to expand...
Click to collapse
from what is looks like reading the post is your still on the wrong radio
simple_fear85 said:
from what is looks like reading the post is your still on the wrong radio
Click to expand...
Click to collapse
Can you develop?
So should I sideload the KK bootstack 24A? Then flash another KK ROM?Or how can I fix the radio/baseband?
Yes flash the bootstack
Sent from my LG-VS980 using XDA Free mobile app
bootstack
Xdabbeb 24a 1.2.1 there is also his link for his bootstack zips
So I have a Verizon G2 with the 24A patch which doesn't allow me to install Cyanogenmod or any non stock based roms. When I try to install them they install fine but when I try to boot I get a bootloop and I have to reflash my backup file. Is there anyway to unpatch the 24A security? Thanks.
mkhan231 said:
So I have a Verizon G2 with the 24A patch which doesn't allow me to install Cyanogenmod or any non stock based roms. When I try to install them they install fine but when I try to boot I get a bootloop and I have to reflash my backup file. Is there anyway to unpatch the 24A security? Thanks.
Click to expand...
Click to collapse
There's plenty of AOSP roms that work with 24A now.
Use this for CM11 - http://forum.xda-developers.com/showthread.php?t=2702958
Personally I use Mahdi and it works fine on 24A, check the Verizon G2 Android Development section, most of the AOSP roms are using 24A drivers/files now.
Hello all,
Couldn't find a stock flashable kernel for in between kernel flashes, so I slapped this one together. I used an old kernel script I had from back in the day (see my thread history) and just put the boot.img inside and changed the UI text. Tested working. Enjoy!
Handy! Thanks for your efforts.
Thank you?
No problem! I made it for myself and realized nobody had one up here so I figured it could help at least one person.
Thanks, always handy when you've tried a kernel that is not good
Thank you very much for this man!
Thanks
First of all, thank you for sharing it with us.
Then, from my understanding since this is Google Stock Kernel that comes with Lollipop, I'm assuming it won't allow root even flashing SuperSU ? (Last time I've read the kernel needed to be somewhat compliant with root so you can use root), am I right?
Cheers!
MidnightDevil said:
First of all, thank you for sharing it with us.
Then, from my understanding since this is Google Stock Kernel that comes with Lollipop, I'm assuming it won't allow root even flashing SuperSU ? (Last time I've read the kernel needed to be somewhat compliant with root so you can use root), am I right?
Cheers!
Click to expand...
Click to collapse
You're correct. So basically what I do is flash this, then immediately flash the next kernel I want to use in the same TWRP session.
jlink38 said:
You're correct. So basically what I do is flash this, then immediately flash the next kernel I want to use in the same TWRP session.
Click to expand...
Click to collapse
Thanks, also, from my understanding, some users reporting broken scripts when switching from one custom kernel to another. The solution so far was to flash Stock kernel before flashing another custom kernel. This happene(d) betweeen Franco Kernel and ElementalX, where sweep2wake functions wouldn't work.
Thanks for clearing this up, a stock kernel is always handy whatever the reason
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Duilio Patiño said:
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Click to expand...
Click to collapse
Sure, flash away, as long as it is stock 5.0. Not sure how it would fare with AOSP. YMMV.
jlink38 said:
Sure, flash away, as long as it is stock 5.0. Not sure how it would fare with AOSP. YMMV.
Click to expand...
Click to collapse
Thanks
Duilio Patiño said:
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Click to expand...
Click to collapse
Not all kernels modify the devices system files.
I believe though that since Franco kernel modifies the system files and Since flashing just the stock recovery wouldn't alter or restore those modified system files back to normal otherwise it may/will cause conflicts and errors while running the new kernel.
You would need to (depending on your current setup)
1. Dirty flash the 5.0 ROM that your running to replace those system files back to normal and then flash the OP's stock recovery.
2. Fastboot flash the 5.0 Google Factory System.img (whick would reaplace the modified system files) and or the google factory boot.img or just flash the OP,s stock recovery and then any other compatible kernel in one setting.
3. Restore a stock nandroid backup that has the stock system.img and then flash any comparable kernel.
@jlink38
Thank you for this... Very Much appreciate and it will definitely come in very handy! :good:
I like to have a copy of evey stock recovery version for the N5 in a flashable.zip
xdrc45 said:
Not all kernels modify the devices system files.
I believe though that since Franco kernel modifies the system files and Since flashing just the stock recovery wouldn't alter or restore those modified system files back to normal otherwise it may/will cause conflicts and errors while running the new kernel.
You would need to (depending on your current setup)
1. Dirty flash the 5.0 ROM that your running to replace those system files back to normal and then flash the OP's stock recovery.
2. Fastboot flash the 5.0 Google Factory System.img (whick would reaplace the modified system files) and or the google factory boot.img or just flash the OP,s stock recovery and then any other compatible kernel in one setting.
3. Restore a stock nandroid backup that has the stock system.img and then flash any comparable kernel.
@jlink38
Thank you for this... Very Much appreciate and it will definitely come in very handy! :good:
I like to have a copy of evey stock recovery version for the N5 in a flashable.zip
Click to expand...
Click to collapse
No problem!
Thank you very much for the thoughtful upload, OP!!
Been meaning to try out Franco's latest nightly for LP to see if I get an improvement in battery life
I'm assuming if I don't like Franco's kernel, I just simply flash this zip in recovery (I use Philz CWM) to return back to the stock LP kernel?
RevoWution said:
Thank you very much for the thoughtful upload, OP!!
Been meaning to try out Franco's latest nightly for LP to see if I get an improvement in battery life
I'm assuming if I don't like Franco's kernel, I just simply flash this zip in recovery (I use Philz CWM) to return back to the stock LP kernel?
Click to expand...
Click to collapse
Pretty much, yeah
Sent from my Nexus 5
amir7777 said:
Pretty much, yeah
Sent from my Nexus 5
Click to expand...
Click to collapse
Cheers buddy
I'm in Elementalx kernel and Rom stock. To receive OTA, flash stock kernel is enough?
danifeb said:
I'm in Elementalx kernel and Rom stock. To receive OTA, flash stock kernel is enough?
Click to expand...
Click to collapse
You should be OK. I don't know what else you have tweaked.
I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
mnemonicj said:
I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
Click to expand...
Click to collapse
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
dirtydodge said:
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
Click to expand...
Click to collapse
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
mnemonicj said:
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
Click to expand...
Click to collapse
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
dirtydodge said:
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
Click to expand...
Click to collapse
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
mnemonicj said:
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
Click to expand...
Click to collapse
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
dirtydodge said:
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
Click to expand...
Click to collapse
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
mnemonicj said:
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
Click to expand...
Click to collapse
First off you can't flash cyanogenmod cause of the locked bootloader. We have to stick with TW base roms. I like the stability about TMS2.0 plus the fact that the dev is still working on it. Most all the other devs have went to other phones. TalkingMonkeys is a great dev and is constantly working on mods and features.
So I'm in nc2 and wanna jump up to a new rom. Thinking alliance, biggins or Arya mod. What all are you guys running and how'd you do it? I can seem. To find the thread on how to do it. Did you use safestrap or flashfire? If you used flashfire, how do you use that? I must have the stupid on the search here lately...
Sent from my SM-N900A using Tapatalk
You got it easy.
Root with towelroot, Install SuperSU, Install Busybox, Install Safestrap 3.75. Done.
Reboot to safestrap and flash what you need. Don't worry about flashfire, you probably won't ever need to use it. Or at least out of my experience I've not had to use it. (For the note 3 that is)
I'm much more versed in rooting and roms than you assume. I'm on dk7.1 and have odind many times. Just curious as to the actual process of switching to lp. And what would need done to go back to kk if necessary
Sent from my SM-N900A using Tapatalk
Before you flash, just back up your kk rom. And then when you flash the rom, make sure to flash the kk kernel so safestrap is still accessible
OMG_VTEC said:
I'm much more versed in rooting and roms than you assume. I'm on dk7.1 and have odind many times. Just curious as to the actual process of switching to lp. And what would need done to go back to kk if necessary
Sent from my SM-N900A using Tapatalk
Click to expand...
Click to collapse
It doesn't matter what ROM you are currently on you can always odin back to NC2 and then upgrade to NL1 or OC1/2.
Examples:
If you're on OC1/2 and want to go back to NL1, you would full odin back to NC2, re-root and such. Then flash a NL1 based ROM.
If you're on NL1 without root and want OC1/2, full odin back to NC2, re-root, etc. Then flash a OC1/2 based ROM.
I've never even head of nl1. And Don you need to flash the kernel and radio or is just the kernel necessary?
Sent from my SM-N900A using Tapatalk
It depends on the ROM you plan on going to.
AllianceROM v12 doesn't require a kernel flash
UrDroid Stock Deodexed requires an OC1 flash (optional OC2 patch available)
OC1 is 5.0
OC2 is a security patch for OC1
NL1 is 4.4.4
NJ2 is 4.2.2
Click to expand...
Click to collapse
Are you sure about alliance? I tried to flash that and got stuck on the Galaxy Note 3 screen
Sent from my SM-N900A using Tapatalk
I've ran Alliance v12 more than a few times on both my phone and my girlfriends phone, I've not once had to flash a kernel if you get stuck reboot into the stock recovery and look at the top, if it says OC1 then your on the right kernel. But flashing it definitely won't hurt anything.
This is taken out of the changelog for AllianceROM v12
ROM will automatically flash OC1 Kernel so after install, just hit reboot.
Click to expand...
Click to collapse
Also make sure you're on version 3.75 for Safestrap.
i have done this many times over within the past hour and safestrap wont install... i have used these exact steps b4 last year but it just wont work now....