Database Info

[Q] Updating a Custom ROM

I recently flashed my Captivate with Cognition 4.2.2. I just noticed that 4.3 is out now with some desirable updates. Furthermore, I notice that there is a full ROM and a "Kernel only" version.
I have noticed that some people only talk about doing a full ODIN procedure back to stock is only necessary when flashing an entirely new ROM.
If I update to 4.3 :
Can I flash the kernel only? Or is there lot's of important things I will be missing. Is it only recommended to update kernel if I know that there have ONLY been updates to the kernel?
Is it important to flash back to Stock? Or can I just put the update in the root directory and use clockwork to boot after renaming the ROM to "update.zip"?
Any information on the way that these parts intertwine and what an update to one does to the others would be appreciated.
Thank you!

[Q] Can I update stock N5 BUT with Franco Kernel?

I've got a Nexus 5 on Lollipop that's completely stock except for running franco kernel. Haven't touched it for awhile. If I check and there are any OTA updates available, will they install successfully?

No, you must have stock kernel, stock recovery, and unroot

micens said:
No, you must have stock kernel, stock recovery, and unroot
Click to expand...
Click to collapse
Thanks.

Is there a way to manually flash the OTA, or to install it one way or another, without having to revert to stock kernel and unroot and then re-root and re-install franco again?

Edit flash-all file and remove "-w".
Save the file and flash it from fastboot

.psd said:
Is there a way to manually flash the OTA, or to install it one way or another, without having to revert to stock kernel and unroot and then re-root and re-install franco again?
Click to expand...
Click to collapse
As of Lollipop, the OTA method has changed and instead compares the checksum/hash of the entire /system partition, as well as the boot and recovery partitions. The "old" pre-Lollipop method was to check the specific files it cares about rather than sum of the entire partition.
The best way for you to update is download the factory image, extract it then flash the boot and system images using fastboot while your device is booted into the bootloader. You may also want to flash the new bootloader and/or radio. Don't flash the userdata image as it will wipe your /data partition (which the internal storage also resides in), unless that is something you want.
After that, boot into your custom recovery and simply flash the latest SuperSU and if you want to, a Lollipop version of the kernel you want. Files required by SuperSU/root access reside in the /system partition, which prevents an OTA update, and is overwritten when flashing a factory system image. A KitKat kernel won't boot on Lollipop, and a custom kernel also prevents OTA.
OTAs are really only for those who have absolutely no software modifications (and are not informed enough to be able to flash manually) and is honestly the worst way of updating.

What is the most stable stock OS? Kitkat or Lollipop?

What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?

GoodLooks550 said:
What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?
Click to expand...
Click to collapse
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.

painiac said:
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.
Click to expand...
Click to collapse
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?

GoodLooks550 said:
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Click to expand...
Click to collapse
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
GoodLooks550 said:
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?
Click to expand...
Click to collapse
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.

painiac said:
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
Click to expand...
Click to collapse
I was lucky to have my an S4 MDK (unlocked bl), so things were much simpler back then--had an S3, as well. In the process of getting my S5 running the way I wanted, the use of safestrap was completely new to me. Thankfully, some heavy browsing of the forums got me through. I did not use flashfire, which would have been something else to learn!
painiac said:
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.
Click to expand...
Click to collapse
Thank you--your replies and guide were gold in terms of figuring it all out.
For onlookers of this thread, once you get to lollipop, it's hard to go back to kitkat. A lot of the small details really add up to an improved user experience. Also, having an s7 edge, the PB1 build on the S5 has 90% of the same functionality of the S7e--excluding edge-related features, of course.
To summarize my upgrade experience:
Root from any kitkat rom: Flash the NCG kernel in odin (AP/PDA), reboot and root with towelroot apk, and then install and update supersu; and lastly re-flash the NE9 kernel.
Install Hashcode's version of Safestrap: Install busybox apk. Install safestrap apk (version 3.75). Make sure to use a microsd card for installation, as recommended.
Install PB1 rom: (source: http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029). Reboot into SS. Flash G900V_Fix Safestrap.zip. Reboot into SS. Flash:
VZW_BPB1_ODEX_DEODEX_V9.zip,
Extra_toggles.zip (optional),
BPB1_Firmware_No_Bootloaders.zip , and
G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip.
Flash all in a single queue. Reboot into download mode and flash G900V_OD5_Bootloader.tar.md5 in odin. Reboot. Wait. (NOTE: for more customization, before installing rom, unzip rom. Edit the options.prop in text editor to your likeing. Rezip original contents with updated options.prop. Flash this zip as the rom file)
To get back into safestrap/recovery: Make sure hashcode's version of safestrap is installed. A lollipop safestrap will be installed--don't use it. Also, install NI2Flasher.apk (this flashes a kitkat kernel, which will allow you to get back into the kitkat safestrap). Reboot into safestrap. IMPORTANT: When complete with whatever is being done in SS, flash G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip to get back into lollipop rom.
Install xpose modules: This allows the essential greenify app (HIGHLY RECOMMENDED) to run to maximum potential. Gather following files:
1. APK: Xposed Installer 3.0 alpha4 (comes with some roms)
2. Flash in SS: Framework: xposed-v75-sdk21-arm-arter97-snapdragon.zip
3. Flash in SS: Uninstaller: xposed-uninstaller-arter97.zip
Since the rom I installed did not come with xposed installed. I flashed the framework in SS (look above to properly access and leave SS). Reboot. Install the APK. Reboot. Highly recommend installing Wanam's modules for lollipop--tons of modifications.
Unbrick: Get into download mode and flash: Full Wipe G900V_Downgrade_to_NCG.tar . (This helped me a ton until I realized that safestrap for the S5 does not work with rom-slots. Use the stock slot to do all flashing)
I gathered all this information from various threads, and hope this helps (highly recommend reviewing painiac's guide before starting anything - http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848). I am no expert, but this is what worked for me--please correct me if I'm wrong at any step. I believe the way I set this up, I should be able to get back to a kitkat rom, if I ever wanted to (easiest way to do this would be to flash the unbrick file). I hope this can help at least one person, since I know I'm not the only person to recently get an S5 due to someone else in the family upgrading to the S7.

Need some guidance in setting up root and Rom on my s5. Never done this before on a Verizon phone so if anyone can help I'd appreciate it

Is there a way to revert custom ROM to stock and keep the phone rooted?

Also, how can I tell what were the previous versions of Android that my phone had (STOCK)?
For example: there were several 5.1.1 versions or 5.0. versions - how do I know which one do I need?
Thanks.

The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.

audit13 said:
The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.
Click to expand...
Click to collapse
Sorry if I didn't explain myself - my phone is rooted and I have a custom ROM. What I want to do is to go back to stock ROM but keep it rooted.
Thanks.

Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.

audit13 said:
Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.
Click to expand...
Click to collapse
So you can't keep it rooted while flashing stock?
And how do you know which versions are for your phone (if I don't want to go back to the latest Marshmallow for example)?

You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.

audit13 said:
You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.
Click to expand...
Click to collapse
Yes, I know that I need to Google for factory image, but there are several images with the same release. For example, there are three 5.1.1. (LMY48B, LMY48I and LMY48M). Same with 6.0.0. and 4 X 6.0.1 version. How do you know which one is for my device?
Thanks.

Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.

wangdaning said:
Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.
Click to expand...
Click to collapse
Thanks!
Just trying to understand that difference between the different versions, or are these simply system updates, from XXX29K to XXX29S for example?

Changes in the android version 5.0->5.1->6.0 are fairly large system updates. Within 5.1.1 they are security patches.

If you have a rooted phone and talk about flashing, you should know this. Else you are a menace to your phone...
Root is a system modification - if you delete or reinstall the System partition, you'll lose root. But re-root is easy.
I recommend to read tutorials and get some knowledge before trying to root, flash or before asking those questions, where Senior xda-members just shake their heads.

The simple way to do what you seem to want is to back up all your important stuff (photos, etc.), install MMB29V (the latest March 1st 6.0.1 security version), install TWRP 3.0.0.0, and from TWRP flash SuperSU v2.70. It will take slightly longer than it's taken me to type this, but not much...
After that, when a new monthly security version comes out, flash system.img, boot.img & radio.img, and repeat the TWRP & SuperSU steps. No data loss.

How to update OEM partitions?

How do you update oem/modem/other manufacturer specific partitions if you are on Lineage or another custom rom. Obviously OTA won't work and flashing the recent stock rom is not an option since you would (probably) lose all of your data.
Can you somehow extract those partitions from the stock rom and flash them separately?

mr_keule said:
How do you update oem/modem/other manufacturer specific partitions if you are on Lineage or another custom rom. Obviously OTA won't work and flashing the recent stock rom is not an option since you would (probably) lose all of your data.
Can you somehow extract those partitions from the stock rom and flash them separately?
Click to expand...
Click to collapse
I would leave those alone, unless you have many years of firmware hacking... Everytime I messed with them, they bricked my phone... Not worth it for what you get...