Hi,
I am new to this forum and android stuff.
Please forgive me if I asked noob question.
I tried to search but got no complete answer.
My condition:
Nexus 7
build number JRO03S
used Nexus root toolkit 1.5.3
to unlock and root
used TWRP to install poitee kernel for usb dac.
Then:
The 4.1.2 updates notification show up
I pressed yes ... accidentally.
Now:
The build number becomes JRO03S
but the Android version is still 4.1.1
Question:
a. How to update to 4.1.2?
b. How to update without wiping any data and apps?
c. Do I have to reinstall the pointee kernel?
d. Will flashing rom ( updating to newer version ) wipe all things?
Sorry for so many questions,
For my situation it is a mixed up that I can't find similar condition on the internet yet.
Please kindly help and advise.
Much Thanks!
Btw,
I done below, no success:
1. quickboot
2. TWRP recovery
3. install nakasi-JZO54K-from-JRO03S.zip (from /sdcard)
4. error --> "Status 7" shown.
Cannot update.
Please Please help....
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
Understood and Thanks a lot!!!:good:
that means all in all,
I still have to go through
the route of "Backup all --> Flash Stock & unroot --> Root --> Restore all".
However, considering the latest update seems don't have anything important or useful to me
So I just wait for the next more important update.
and save the drudgery next time.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
He doesn't need to lock his bootloader, and he'll still not be able to run the update the natural way as long as he's got twrp or cwm installed. He can flash the factory rom and push the update through using custom recovery though.
Visa Declined said:
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
Click to expand...
Click to collapse
Thanks for you advise,:highfive:
it is very kind of you to help.
I think may be the Status 7 error could be caused by the Custom Kernel Installed (poitee)
I better ask him in detail later on.
But mine is JRO03S,
May be it is safer to Return to Stock Rom completely and go for OTA later.
Sadly, This 4.1.2. seems got no very useful component to me,
I solely use it as a second PDA and Music Player with USB DAC.
I will have to wait for better solution then.....
pleaseabcd said:
However, considering the latest update seems don't have anything important or useful to me
Click to expand...
Click to collapse
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Visa Declined said:
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Click to expand...
Click to collapse
O'really.....em...then it is a different story..(Safer for the future...)
Perhaps, I just:
1. use Titanium Backup to back up everything --> copy the "Back up" to PC (just in case)
2. use Wugfresh Nexus Root Toolkit 1.5.4 to Flash Stock n Root
3. if can Flash to 4.1.2 stock rom directly, OK
4. if can't --> flash back to 4.1.1 stock rom (JRO03S) and then OTA
5. Finally, use Titanium backup to restore Everything.
Have to Thank You you guys again!
I know I am a newbie... but I am learning......
Hate to be limited to what I was given......while I can experiment and make mistake to grow up !:laugh:
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
mikeprius said:
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
Click to expand...
Click to collapse
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
cruise350 said:
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
Click to expand...
Click to collapse
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
mikeprius said:
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
Click to expand...
Click to collapse
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
cruise350 said:
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
Click to expand...
Click to collapse
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
mikeprius said:
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
Click to expand...
Click to collapse
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
cruise350 said:
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
Click to expand...
Click to collapse
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
mikeprius said:
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
Click to expand...
Click to collapse
Every thing in the data partition(titanium backup) will remain and everything in the system partition (SuperSU & stuff modified via xposed installer) will be gone and replaced with the bloatware.
Sent from my SPH-L720 using Tapatalk
Ok, so it appears to have worked. I flashed the 4.3 prior version however it was hooked up to wifi and automatically downloaded the new version and removed root (not a big deal). My status says custom still, but I am assuming that I can OTA after the flash b/c it updated to the most recent 4.3 in Dec 2013. I re-rooted so it is back to prior, but I know now how to do it.
Is there anything that I may delete or uninstall that cannot be replaced by flashing the stock firmware ? For example I was thinking about getting rid of the 'help' on the phone and Titanium Back up said it is odexed or something to that extent and can only be replaced by using Titanium Backup and the exact same copy ?
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Being able to flash the stock .tar through ODIN gives me peace of mind from screw ups, even if it removes root and takes time.
mikeprius said:
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Click to expand...
Click to collapse
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
nobody291 said:
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
Click to expand...
Click to collapse
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
mikeprius said:
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
Click to expand...
Click to collapse
To me, one of the hardest parts of this whole thing is getting to the point where the basic terms make sense. I've been at this for a couple of years with an HTC Evo and now the GS4 since October, and sometimes it still makes my head spin. Here is an attempt to explain my understanding of a few things:
1. Booting...you can boot into Download mode, recovery, or system. Download mode is what you use with ODIN, you need the correct drivers on your computer (which can be found lots of places), so that ODIN and your phone can communicate. In download mode, the phone just accepts whatever ODIN sends it, so it's the easiest way to totally brick your phone. Don't mess with partitions and follow the instructions for whatever you're doing very carefully, because I think this is the only way to "hard brick" your phone.
2. Recovery - something you use to create images of your phone's ROM (nandroids), flash ROMs and mods, and restore past nandroids. The stock recovery will only flash approved updates from the carrier, so to do any of the things I listed you need a custom recovery. Most people use Philz (which is based on the ClockworkMod recovery) or TWRP. To flash the custom recovery, use ODIN and follow the instructions in the thread exactly. There is a way to flash recoveries without ODIN, but I've never done it. I was using TWRP, and switched to Philz to flash the rooted stock 4.3 update because the thread suggested it. They both seem to do the same thing, and I have been happy with both. I'm sure there are technical differences, but I couldn't explain what they are. You can switch back and forth as much as you'd like between the recoveries with ODIN. Recoveries can flash a complete ROM or just partial changes (like the hotspot mod). In a custom recovery (or the stock) you can also do factory resets and cache cleaning (most ROMs suggest you do this before flashing). Factory reset doesn't return the ROM to the factory original, it just clears out all of the user data (including user apps). A nandroid is the fastest way to restore a phone if you screw it up...I always make one before making significant changes to the phone. It takes several minutes to do, but I think it's well worth it. The operating system can't be running when you make one, that's why you need to boot into recovery mode. You create a Nandroid in Philz by selecting "backup and restore" then "backup to" which will allow backup to the internal storage or external SD card.
3. ROM - the actual operating system used by the phone when you actually use it as a smartphone. There are 2 basic flavors for the GS4...touchwiz and AOSP (Android Open Source Project). Touchwiz is Samsung's "flavor" of Android, AOSP is the "pure Google" version of Android. A lot of the things the GS4 will do rely on touchwiz (multiwindow is one example...but there are several). Some people really like the AOSP ROMs (Cyanogen is AOSP), but make sure you understand their limitations. I've never used one on the GS4. There are several touchwiz custom ROMs which have various features. I've tried a few and just settled on the stock rooted touchwiz ROM, but there are lots of options from great developers. I think most custom ROMs require you to use a custom recovery to flash them, but there might be ways to do it using ODIN. I like having a custom recovery, so I've only used ODIN for flashing modems and recoveries.
4. Firmware - as far as I can tell, there are two important parts of the firmware...the modem (sometimes called "radios" or "baseband"...find your version by looking in "about device"->"Baseband version"...the different modems are described by the last 3 letters you see) and the bootloader. The modem and the version of the ROM you flash need to match or you'll have problems with the radios in the phone (wifi seems to be the biggest problem if you have a mismatch). MF9 was the last modem version based on 4.2.2, and 4.3 has had MJA and MK2 (MK2 is the latest). The bootloader is what the phone uses to initially decide how to boot up. If you have the 4.3 version of the bootloader it will include "Knox", which will prevent you from flashing older versions of the modem, so you'll have to use a 4.3 ROM. Knox also "trips" a counter if you flash a custom ROM and Samsung claims they won't honor the warranty on a phone with the "Knox flag" tripped. If you have the 4.3 bootloader you're stuck with it (for now at least). I still have the 4.2.2 bootloader, so I don't have much more to offer on this subject. There are ways to get the 4.3 modem and ROM without the 4.3 bootloader. There is a lot here (and lots on youtube) on how to navigate the Knox minefield if you care about it. If you still have the 4.2.2 bootloader you can flash older (and newer) modems as much as you'd like without getting the updated bootloader using ODIN.
Hopefully this helps...this is a great place with lots of great people. Sometimes the scale of the amount of information here is overwhelming. But, search is your friend along with lots of time! Feel free to keep asking questions.
thanks for explaining this nobody-
The information does help quite a bit and I am still learning, however; I do enjoy the process of messing with the phone. My GS4 now runs the RAM at 750-800mg instead of a bloated 1.2GB which was happening quite a bit. I had to originally not use a lot of apps I wanted to like Facebook bc the programs themselves bloated up to accomidate the existing bloatware which was also running. I did flash my phone back with the stock firmware today and it looks like it installed all the stock software. My status said 'custom' when I looked at it however I was already connected to wifi and it went from 4.3 (Oct 2013 version which I flashed) to Dec 2013 version automatically so it appears that the OTA feature works.
I assumed if I accidently delete something from the phone that I really need to affects the phone, I can always flash the stock ROM to fix it. Losing the root is not that big of an issue, but I did lose Superuser and had to re-root the phone. I suppose I do have a few more questions, one was when I was reading another carrier provider thread.
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
mikeprius said:
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
Click to expand...
Click to collapse
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
Click to expand...
Click to collapse
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
nobody291 said:
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
Click to expand...
Click to collapse
It was good that you mentioned the Knox bootloader issue with the 4.3 upgrade. When I purchased my cell phone back in Nov, I believe it had the 4.3 (1st) version loaded, but it already had Knox features as I do recall seeing them. If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ? This may have been the error I read about due to the new Knox feature.
I think since my phone is currently rooted and I altered some of the bloatware system files that the update if it were made available OTA should not update anyway due to the root. Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ? With that, if I were to load 4.4 and not like it, could I flash back 4.3 ? I am guessing this is the part where you mentioned that the carrier may decide differently later on.....I suppose I will just keep an eye out in the meantime.
Good good............, I'm picking up this pretty well so far.............
mikeprius said:
If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ?
Click to expand...
Click to collapse
I'm not sure what symptoms you'd see if you installed 4.2.2 with the 4.3 bootloader. Most likely the phone would fail to boot. ODIN will flash whatever you tell it to, I don't believe it does any compatibility checking on its own. You can still get the wifi hotspot feature to work even with Knox and the 4.3 bootloader, I don't think that was what they were trying to do with the update. There are threads discussing 4.3 and what changed, but there wasn't much obvious to the user. For now you can't go back if you're on 4.3, but there might be an exploit discovered down the road that lets you get the old bootloader and go back.
Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ?
Click to expand...
Click to collapse
Yes, they won't be available immediately though. It can take some time for the community to re-obtain root too, depending on how big the changes are.
With that, if I were to load 4.4 and not like it, could I flash back 4.3 ?
Click to expand...
Click to collapse
I think you alluded to the answer already, but it depends. It took a month or two before you could flash the stock 4.3 without the 4.3 bootloader. There were custom ROMs available that used custom kernels sooner, but there was a problem trying to use the stock kernel with the 4.2.2 bootloader. So, always read and read and read some more before flashing updates.
So far i think i got the hang of it. I have been modifying the phones original touchwhiz. I ended up freezing alot of files instead of deleting them so the ability to turn them back on is there. Some of the files while there are not meant to be frozen/disabled/turned off. I tried a few methods for keeping SuperSU over an ODIN with no luck. I do have a question though. If i turned off (but did not delete) alot of system files and were to run ODIN again will all of them including the bloatware be turned back on and restored? That would be bad if i flashed, lost root, then simultaneously had all the system files disabled with no way to turn them back on......
This also a dumb question but what exactly am i flashing with ODIN? Its a 1.5 GB file with Sprint and it is a tar that restores all bloatware and turns the phone status back to official so i can get OTA updates. Am i flashing the entire stock ROM or just the firmware? Its nice that i have not lost any existing apps or data. It just restores the bloatware and removes root
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
mikeprius said:
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
Click to expand...
Click to collapse
The .tar you are flashing from sprint is what we would call stock firmware image. This is the image that shipped on the phone from the factory. I'm an avid flasher and would highly recommend installing twrp or philz touch, creating a nandroid backup and giving some debloated touchwiz roms a shot. You'll see some significant improvement in battery life and performance and some really cool upstream features. I use odin as a last resort, when I need to go back to stock for whatever reason (ie domestic sim unlock) or have fubar'd my current setup past a point of no return.
Hello everyone. Just hoping to find some advice on how I should go about upgrading to Kitkat.
I'm currently running rooted (via de la vega, knox at 0x0 currently) stock 4.3 firmware on a T-mob Note 3, stock bootloader. For now, I'd like to keep the rom stock but get it up to 4.4.2. I've been digging around trying to find out what I should do and am coming up a bit short. Hopefully I can get pointed in the right direction.
One thing I noticed is that one needs a different bootloader for 4.4.2 than 4.3. I'm no longer concerned about keeping knox at 0x0, and would like to throw CWM Touch on. Should I be installing CWM for 4.3 before updating to 4.4.2, then updating CWM? Or should I be installing CWM for 4.4.2 right from the start?
Is there another root method I should use, perhaps something that will handle getting the custom bootloader on as part of the process?
Is it possible to update like this without a wipe?
Ultimately, I'd prefer to get a bootloader on first so I can make a backup, and then retain some way of being able to revert to the backup if needed. I understand that once knox is tripped, there's no getting that back. That is fine.
If I need to provide more information before assistance can be provided, please ask. Thanks in advance for your help/suggestions.
SM-N900T
Android v4.3
Baseband N900TUVUBMI7
dethzord said:
...
Is it possible to update like this without a wipe?
Ultimately, I'd prefer to get a bootloader on first so I can make a backup, and then retain some way of being able to revert to the backup if needed. I understand that once knox is tripped, there's no getting that back. That is fine.
...
Click to expand...
Click to collapse
It is possible to do the update without the wipe on N9005, but probably on N900T you should better ask for details in the specific forum.
You should also keep in mind that (AFAIK) at this point it is impossible to return on N9005 from 4.4.2 back to 4.3 (with or without wipe, no matter what kind of backup you have). Some things might be different on N900T - so again you should ask in the right forum for more details!
Historically the first method available was with Mobile Odin Pro - look around for the specific thread on that.
Another option is to manually select a specific stock ROM that uses a kernel BEFORE July 2014, write it with normal Odin and then use Towelroot to re-root.
If you somehow managed to get on a version AFTER July 2014 Towelroot will no longer work and in that case you will need to read and understand the method described in this thread:
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
dethzord said:
Hello everyone. Just hoping to find some advice on how I should go about upgrading to Kitkat.
I'm currently running rooted (via de la vega, knox at 0x0 currently) stock 4.3 firmware on a T-mob Note 3, stock bootloader. For now, I'd like to keep the rom stock but get it up to 4.4.2. I've been digging around trying to find out what I should do and am coming up a bit short. Hopefully I can get pointed in the right direction.
One thing I noticed is that one needs a different bootloader for 4.4.2 than 4.3. I'm no longer concerned about keeping knox at 0x0, and would like to throw CWM Touch on. Should I be installing CWM for 4.3 before updating to 4.4.2, then updating CWM? Or should I be installing CWM for 4.4.2 right from the start?
Is there another root method I should use, perhaps something that will handle getting the custom bootloader on as part of the process?
Is it possible to update like this without a wipe?
Ultimately, I'd prefer to get a bootloader on first so I can make a backup, and then retain some way of being able to revert to the backup if needed. I understand that once knox is tripped, there's no getting that back. That is fine.
If I need to provide more information before assistance can be provided, please ask. Thanks in advance for your help/suggestions.
SM-N900T
Android v4.3
Baseband N900TUVUBMI7
Click to expand...
Click to collapse
The following instruction is for N900V. Not sure if it is also useful for N900T.
Code:
1. Open SuperSU settings
2. Scroll down to the bottom, Enable Pro. Reboot. (you have to purchase SuperSU Pro)
3. Check Survival mode
4. Uncheck Enable Superuser
5. Install OTA update
6. After reboot, Enable Superuser
7. Disable Survival mode
vndnguyen said:
The following instruction is for N900V. Not sure if it is also useful for N900T.
Code:
1. Open SuperSU settings
2. Scroll down to the bottom, Enable Pro. Reboot. (you have to purchase SuperSU Pro)
3. Check Survival mode
4. Uncheck Enable Superuser
5. Install OTA update
6. After reboot, Enable Superuser
7. Disable Survival mode
Click to expand...
Click to collapse
I'll try that tonight. Would try it immediately if not for low battery. I had done the survival and the OTA failed to install, but I didn't think to disable SU. Thanks, will let you know if it works.
Looks like it's a no go. Still fails to update. I dunno if there's anything else I might need to ditch first like Xposed or the like. But essentially, I might as well wipe if I have to redo all my tweaks.
But if I can't get the OTA working, I have to figure out what the best way to go about it will be as far as getting the right bootloader and installing in the right order, and retaining root. If I have to go with a custom rom, I will.
Hi all,
I have a AT&T Galaxy S4 i337. The WIFI doesn't work. It seems to be a very common problem as there are many fixes on the internet. I have tried them all and I don't know what to do now. It is running V. 4.3 and my baseband version is i337ucugoc4.
- Rooted. Installed Rom Manager, Terminal Emulator, SuperSU, and Reverse Tether so I could use the internet (because no wifi).
- Tried to install a new modem but could not find the exact modem file. I saw a list at http://forum.xda-developers.com/showthread.php?t=2496517 but didn't know which was good for my phone. I saw I337_UCUGOC3_Modem_RockRatt.zip but it ends in a 3 not a 4 as required for my modem.
- tried to update using the AT&T Software update. It stayed at "Checking for software updates...." and then said "Software update interrupted. No updates available. Check back in 24 hours". Don't know if that would have solved the WIFI problem anyhow.
- Tried again to install to 5.0 thru USB. Downloaded and installed it but when I rebooted, it was still 4.3
- Downloaded FXR wifi and ran it - no luck there.
- downloaded the modem file ATT_OC4_modules.zip and flashed it to the phone. It said SUCCESSFUL but there was no wifi afterwards.
- Adjusted the source code with terminal emulator as I saw in a youtube video. No success and I changed it back to the original.
- Downloaded wifi manager and tried turned off-then-on wifi.
- probably more things I have forgotten in the last three days.
I have tried everything I can find to try. It has been 3 days of trying - very frustrated. I would very much appreciate direction on this. To recap, I need to get wifi working and want to upgrade to lolipop.
Thanks so much,
Amber
amberblossom said:
Hi all,
I have a AT&T Galaxy S4 i337. The WIFI doesn't work. It seems to be a very common problem as there are many fixes on the internet. I have tried them all and I don't know what to do now. It is running V. 4.3 and my baseband version is i337ucugoc4.
- Rooted. Installed Rom Manager, Terminal Emulator, SuperSU, and Reverse Tether so I could use the internet (because no wifi).
- Tried to install a new modem but could not find the exact modem file. I saw a list at http://forum.xda-developers.com/showthread.php?t=2496517 but didn't know which was good for my phone. I saw I337_UCUGOC3_Modem_RockRatt.zip but it ends in a 3 not a 4 as required for my modem.
- tried to update using the AT&T Software update. It stayed at "Checking for software updates...." and then said "Software update interrupted. No updates available. Check back in 24 hours". Don't know if that would have solved the WIFI problem anyhow.
- Tried again to install to 5.0 thru USB. Downloaded and installed it but when I rebooted, it was still 4.3
- Downloaded FXR wifi and ran it - no luck there.
- downloaded the modem file ATT_OC4_modules.zip and flashed it to the phone. It said SUCCESSFUL but there was no wifi afterwards.
- Adjusted the source code with terminal emulator as I saw in a youtube video. No success and I changed it back to the original.
- Downloaded wifi manager and tried turned off-then-on wifi.
- probably more things I have forgotten in the last three days.
I have tried everything I can find to try. It has been 3 days of trying - very frustrated. I would very much appreciate direction on this. To recap, I need to get wifi working and want to upgrade to lollipop.
Thanks so much,
Amber
Click to expand...
Click to collapse
May I ask why is your bootloader is lollipop but your OS rom is still Jelly bean ( you said 4.3). It appears that you might have jelly bean kernel which will not work with lollipop modem and bootloader. Majority of the wifi problem is caused by the kernel and bootloader mismatched, assuming that your radio (modem) has no physical damage. Try to flash the OC4 kernel and see you still have the wifi problem.
If you want to upgrade to lollipop from Jelly bean, there are several guides on this forum explaining step by step.
I flashed the OC4 kernal - no change in wifi
sway8966 said:
May I ask why is your bootloader is lollipop but your OS rom is still Jelly bean ( you said 4.3). It appears that you might have jelly bean kernel which will not work with lollipop modem and bootloader. Majority of the wifi problem is caused by the kernel and bootloader mismatched, assuming that your radio (modem) has no physical damage. Try to flash the OC4 kernel and see you still have the wifi problem.
If you want to upgrade to lollipop from Jelly bean, there are several guides on this forum explaining step by step.
Click to expand...
Click to collapse
Thanks sway8966,
I flashed the OC4_update_from_OC3.zip file but there was no change - still no wifi. I wonder if I were to upgrade to lollipop would it automatically fix the problem because it would have the matching bootloader and OS rom? Do you think this might solve the problem?
Thanks again.
amberblossom said:
Thanks sway8966,
I flashed the OC4_update_from_OC3.zip file but there was no change - still no wifi. I wonder if I were to upgrade to lollipop would it automatically fix the problem because it would have the matching bootloader and OS rom? Do you think this might solve the problem?
Thanks again.
Click to expand...
Click to collapse
I do not know what included in the oc4 update from oc3.zip file. As I said before you could try flashing the OC4 kernel file and see whether your wifi is working or not.
Here is the link for the OC4 kernel. You need to flash it via odin.
If you do not have any particular reason to stick with Jelly bean you should upgrade to Lollipop or at least to Kit-kat.
Hi! I had an s4 variant with your problem the same, the wifi nope in none routers.
I gave this device to trash , because i discovered what "happened"
Some stock app, from samsung, masked as anything that i skipped to search (i have much precious time to loose, instead loose really, lost time BRITISH DEVICES IN EXT4 filesystem) what app exactly, is receiving data from samsung server to delete the /system/etc/wifi/bcmdhd.cal
I was obligated to reinstall this file 4 times, changed permission to r--r--r--T untill resolve. But was not sufficient, after this, my wifi, fixed again, but the phone at 8ยบ reboot, after , received a remote conmand again to turn the phone ridiculously slower, i lost my head and crashed this device on the wall, and nevermore i will use this name. Sorry,
All this happened just exactly, after install cwm and root sucessfully, without touch anything on the firmware. Something from samsung inc, is programmed to "detect" these 2 events, and send a "tick" to begin the hell in fire on this devices GT S-Xx
Sent from my XT687 using xda premium
won't boot past the SAMSUNG screen
sway8966 said:
I do not know what included in the oc4 update from oc3.zip file. As I said before you could try flashing the OC4 kernel file and see whether your wifi is working or not.
Here is the link for the OC4 kernel. You need to flash it via odin.
If you do not have any particular reason to stick with Jelly bean you should upgrade to Lollipop or at least to Kit-kat.
Click to expand...
Click to collapse
I flashed the OC4 kernel and it won't boot past the SAMSUNG screen.
amberblossom said:
I flashed the OC4 kernel and it won't boot past the SAMSUNG screen.
Click to expand...
Click to collapse
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
IT WORKED!!!
sway8966 said:
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
Click to expand...
Click to collapse
Thank you so much. It worked. I got my phone back and the wifi is working. Pretty nice. Thanks again. Now to figure out towel root (is that the best for my phone?). You are awesome.
couple more questions
sway8966 said:
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
Click to expand...
Click to collapse
I rooted with towelroot (verified with root checker). I installed superuser but didn't see how to remove bloatware. There are no apps in the apps list. How do I do that? Also, now that it is rooted, is it possible to upgrade it to lollipop? Thanks again.
amberblossom said:
I rooted with towelroot (verified with root checker). I installed superuser but didn't see how to remove bloatware. There are no apps in the apps list. How do I do that? Also, now that it is rooted, is it possible to upgrade it to lollipop? Thanks again.
Click to expand...
Click to collapse
I am glad to hear that it fixes your problem. The NB1 firmware (cooked by muniz_ri) is a live saver. Keep that one. Down the line if your phone screwed up used that one to revive your phone.
Majority of bloatware are system app as such they will not show up in the app bar To remove those you need an admin rights (root) hence we need to root the phone.
To remove the bloatware there are many bloatware remove apps. However they are not written to the specific phone and OS version as such you need to be very careful when you are using them.
I use titanium backup pro to either freeze or remove the bloatware one by one. You can find the list of bloatware for each version on the net. Another way is to install the lean custom rom.
If you want to upgrade to Lollipop you can do it. If somethings screws up you can use that NB1 to come back to Kitkat.
The latest lollipop for the sgh-i337 is OK2 but OK2 gave me some problem that I could not live with it so I stay at OC4.
If you want to upgrade to OK2 or OC4 do let me know. I will point you the guide and necessary files.
CyanogenMod
sway8966 said:
I am glad to hear that it fixes your problem. The NB1 firmware (cooked by muniz_ri) is a live saver. Keep that one. Down the line if your phone screwed up used that one to revive your phone.
Majority of bloatware are system app as such they will not show up in the app bar To remove those you need an admin rights (root) hence we need to root the phone.
To remove the bloatware there are many bloatware remove apps. However they are not written to the specific phone and OS version as such you need to be very careful when you are using them.
I use titanium backup pro to either freeze or remove the bloatware one by one. You can find the list of bloatware for each version on the net. Another way is to install the lean custom rom.
If you want to upgrade to Lollipop you can do it. If somethings screws up you can use that NB1 to come back to Kitkat.
The latest lollipop for the sgh-i337 is OK2 but OK2 gave me some problem that I could not live with it so I stay at OC4.
If you want to upgrade to OK2 or OC4 do let me know. I will point you the guide and necessary files.
Click to expand...
Click to collapse
I guess I will pass on lollipop if there was a problem with it. I looked around for a rom and saw CyanogenMod. It looked pretty good but they discontinued the installer. Can I download it on my PC, move it to the ext card on the S4 and install it from there? Without any changes to my current configuration of the S4? Thanks again.
amberblossom said:
I guess I will pass on lollipop if there was a problem with it. I looked around for a rom and saw CyanogenMod. It looked pretty good but they discontinued the installer. Can I download it on my PC, move it to the ext card on the S4 and install it from there? Without any changes to my current configuration of the S4? Thanks again.
Click to expand...
Click to collapse
I did not say lollipop has a problem, what I meant was I had some problem with lollipop OK2 as such I stay with lollipop OC4.
I took it as you are talking about the CyanogenMoD for the locked bootloader .
You can install that one. You need to install the safestrap first to flash that rom, as mentioned on that link. However, the link also mentioned that you can not make a phone call with that rom as such they stop developing that rom.
sway8966 said:
I did not say lollipop has a problem, what I meant was I had some problem with lollipop OK2 as such I stay with lollipop OC4.
I took it as you are talking about the CyanogenMoD for the locked bootloader .
You can install that one. You need to install the safestrap first to flash that rom, as mentioned on that link. However, the link also mentioned that you can not make a phone call with that rom as such they stop developing that rom.
Click to expand...
Click to collapse
Oh, I didn't understand. I think I would like to try to get up to lollipop. Can you point me to the kernel for that? Also, I have been trying to install CyanogenMod but am running into roadblocks. I think I might have succeeded finally because I now have a yellow triangle and a notice about non-AT&T system software (with a tiny notice - secure fail: kernel). I also had a difficult time installing TWRP as the installer was asking for a file format that the installer didn't download. From what I gather, CyanogenMod looks like a good all around OS and was easy to install when the installer was in play. But if there is another that would suffice but is easier to install, I think that might be a better idea. Could you suggest one?
Sorry about all these questions. I don't know why this is so difficult for me. I feel like an idiot. Thanks again.
amberblossom said:
Oh, I didn't understand. I think I would like to try to get up to lollipop. Can you point me to the kernel for that? Also, I have been trying to install CyanogenMod but am running into roadblocks. I think I might have succeeded finally because I now have a yellow triangle and a notice about non-AT&T system software (with a tiny notice - secure fail: kernel). I also had a difficult time installing TWRP as the installer was asking for a file format that the installer didn't download. From what I gather, CyanogenMod looks like a good all around OS and was easy to install when the installer was in play. But if there is another that would suffice but is easier to install, I think that might be a better idea. Could you suggest one?
Sorry about all these questions. I don't know why this is so difficult for me. I feel like an idiot. Thanks again.
Click to expand...
Click to collapse
SGH-i377 has locked bootloader as such we can not install custom recovery like TWRP or CWM. The only installers we have are safestrap and flashfire. When I was in Kit-kat I used safestrap. It is very troublesome to work with safestrap in lollipop so when I upgrade to lollipop I use falshfire instead.
I have two devices that are on cyanogen mod. I like cyanogen mod but I prefer touch-wiz rom over AOSP though.
The only cyanogen mod you can install is the one that I mentioned in my previous message. You need to use safestrap to install it.
For SGH-I337 you can only install the touch-wiz rom which are written for either safestrap or flashfire. I do not see any AOSP rom written for safestrap or flashfire.
What I did was flash NB1 via odin. root with towl root and install the flashfire. Flash the OC4 rom via flashfire and flash the OC4 bootloader via odin. After my phone boot to lollipop OC4, Installed flashfire and flash the Albe95 S6 port rom. I like to use the S6 features and that custom rom is a stable one. Do you think the process is easy enough?
To upgrade to Lollipop,
I assumed that you are back on NB1 and rooted. If not do that process first. (you mentioned that you installed the cyanogenmode)
Here is the guide telling you step by step how to install lollipop from NB1.
The guide was originally written for OC4 but when OK2 came out it was updated with OK2. So if you want to go to OK2, use the files that mentioned on the guide. If you want to go to OC4 use the file I posted below instead.
I337_OC4_Stock_Rooted_ROM.zip
I337_OC4_Stock_Rooted_Deodexed_ROM
I337_OC4_Bootloader.tar.md5
The choice between using normal and deodexed_rom is your call.