Database Info

[GUIDE] painiac's Essential Guide to Galaxy S5 Flashing, Rooting, Fixing, Customizing

painiac's Essential Guide to Samsung Galaxy S5 (SM-G900V) Flashing, Rooting, Fixing, and Customizing
This is a distillation of everything I've learned about rooting, installing custom recovery, installing custom ROMs, and customizing the Verizon Galaxy S5 SM-G900V. I am NOT the creator of any of the hard work that has made all of this possible, I simply compiled it all in one place. I have done this for the convenience of newer people, and to hopefully decrease the need for the same questions coming up every time somebody discovers they can improve their phone but doesn't yet know how. The Galaxy S5 has a steeper learning curve because of its locked bootloader, hence the need for a guide. I know I had a LOT of questions and more than a little worry about accidentally screwing up my phone, so I did a lot of research and accumulated a lot of information in a short amount of time.
CAUTION: Some of the more general information here might apply equally to all variants of the Galaxy S5, but much of it is specific to the Verizon SM-G900V (and attempts to flash any G900V-specific files to a non-G900V variant will in all likelihood brick your phone. You have been warned.)
This is meant to be a general repository of information, but for projects in active development (such as the 5.0 root method, SafeStrap, custom ROMs, etc) I encourage you to ask questions in their respective threads where their developers (who are most knowledgable about their projects) are best able to see and answer your questions.
If a piece of information originated from you and I have failed to credit you properly, please say so and I will do so immediately.
I encourage you to share this information freely, and I encourage you to submit even minor corrections.
Table of Contents
Android Versions
Updates and Flashable Stock Files
Restoring, Upgrading, and Downgrading
Recovery Mode and Download Mode
Flashing Files with Odin
Custom Recovery Environment
Fixing a Bricked Phone
Rooting 4.4.x and 5.x
Custom ROMs
Debloating
Disabling Knox
Xposed Framework and Modules

Android Versions
First, a brief introduction of the Android versions available on this phone. You find your version number by opening "Settings" and scrolling down to "About Phone" The version numbers look like (for example) "G900VVRU1ANCG", and only the last three or four digits are what we refer to. In this example, we would abbreviate this as "ANCG" or "NCG". You'll note that the version numbers are roughly alphabetical.
KitKat 4.4.2 versions (root with TowelRoot, more on this later)
ANCG = 4.4.2
ANE9 = 4.4.2
KitKat 4.4.4 versions (downgrade kernel to root with TowelRoot, more on this later)
ANHA = 4.4.4
ANI2 = 4.4.4
ANK2 = 4.4.4
ANK7 = 4.4.4 (incremental update to prepare for 5.0; it is not available for download, nor is it necessary to do so)
Lollipop 5.0 versions (root with KingRoot, more on this later)
BOA8 = 5.0
BOC4 = 5.0
BOD5 = 5.0 (last version of the bootloader that can be downgraded)
BOE1 = 5.0 (prevents downgrading the bootloader)
BOG5 = 5.0 (prevents downgrading the bootloader)
BOK3 = 5.0 (prevents downgrading the bootloader)
BPB1 = 5.0 (security update. prevents downgrading the bootloader))
Marshmallow 6.0.1 versions (not rootable yet)
DPD1 = 6.0.1
DPF4 = 6.0.1 (minor bugfix)
Updates and Flashable Stock Files
If you accept an OTA (Over-the-Air) update from Verizon, it updates everything. The same thing happens when you manually flash a "firmware" or "factory restore image" file. Note: If you are still on BOD5 or earlier, do not accept an OTA update.
You can also selectively update certain components by flashing only those files. Most files are flashed with Odin, but some can be flashed in a custom Recovery if they were so prepared.
CAUTION: If you are on BOE1, BOG5, BOK3, or PB1, do not under any circumstances attempt to flash any older versions, or you will brick.
Firmware: Collectively refers to the Operating System and Applications that allow the phone to function. A "Retail" firmware file also contains all the components listed below, so be sure you know what you intend to accomplish by flashing one. You should stick with the latest safe firmwares provided by jrkruse.
CAUTION: If you have BOE1, BOG5, BOK3, or PB1, do not under any circumstances flash an older firmware file unless it specifically says it it is either "for BOE1 or later" or that it does not include a bootloader.
Bootloader: Performs basic checks and then instructs the kernel and the other essential software to boot. On this phone, the bootloader is locked: if it doesn't find the correct (TouchWiz-based) kernel, it will not allow the phone to boot. As of the BOE1 update, a hardware "qfuse" is tripped permanently, which prevents downgrading. In order for a 5.0 ROM to boot, you need a 5.0 bootloader: If you have not previously accepted an update to BOE1, BOG5, BOK3, or PB1, then the best thing to do is update the bootloader to BOD5, which is the last bootloader that can be downgraded later.
CAUTION: If you have BOE1, BOG5, BOK3, or PB1, do not under any circumstances flash an older firmware file unless it specifically says it it is either for BOE1 or later or that it does not include a bootloader.
Note that on the special "Developer Edition" S5, the bootloader is not locked, but the price is unreasonably high.
CAUTION: If you do have a "Developer Edition" phone, do not under any circumstances flash any file that has a retail bootloader, or your phone will have a permanently locked bootloader and will, practically speaking, no longer be a "Dev Edition" phone.
Kernel: Basically the layer that allows the operating system (Android) and the hardware to communicate with each other. You can flash a different kernel version independently, but the operating system will not actually be able to start with an incompatible version of the kernel and it will hang forever on the splash screen. Downgrading the kernel temporarily is necessary for obtaining root on later builds, because the root exploits always get patched in later versions. Simply flashing the compatible kernel will allow the phone to again boot normally. You should stick with the latest safe kernels provided by jrkruse.
CAUTION: Do not attempt to flash a custom (non TouchWiz-based) kernel, or you will brick.
Baseband: This is the Modem, sometimes called a Radio. This is what allows the phone to communicate with the cellular network. Modems can be flashed independently and without regard to the firmware version you're running. You can experiment with which modem gives your particular phone the best reception in your area (which may or may not be the most recent one). You can find flashable modems here.
Non-HLOS: This contains other radios such as Wifi and Bluetooth.
PIT file: Re-partitions the internal storage. You do not normally need to do this, but it can correct specific problems.

Restoring, Upgrading, and Downgrading
If you are on 4.4.x, you can update to 5.0 and keep root.
CAUTION: If you want to preserve your ability to downgrade to 4.4.x, never upgrade via an OTA or other official update; Only upgrade with flashable ROMS or modified Odin files that do not upgrade the bootloader past BOD5.
If you are on 5.0 BOD5 or earlier, you can freely downgrade to 4.4.x, but do not upgrade your bootloader to BOE1 or later if you want to be able to downgrade later
If you are on BOE1 or later, you can freely upgrade but you CANNOT downgrade.
If you need any restore files for NCG through OC4, Misterxtc has provided them here.
I advise you to download these files now if you need them, because I have noticed with previous phones that as people lose interest in particular models, files that are hosted in only one place tend to disappear.
If you need BOG5 and BOK3 restore files, jrkruse has provided them here
Note that he has provided a version that will update (lock) the bootloader, and a BOD5 bootloader version that will not lock the bootloader if it has not previously been locked. If you are on Lollipop there is no good reason to not update to the latest BOK3 firmware, but if you're still on a BOD5 or earlier bootloader then use the "BOK3 firmware with BOD5 bootloader" it in order to preserve your option to downgrade to KitKat.
Recovery Mode and Download Mode
Recovery Mode: This phone has a built-in recovery environment (typically referred to as "stock recovery"), which you access by first powering off the phone (and making sure it's not plugged in), then holding the Home + Volume UP + Power buttons at the same time. After a couple seconds, blue text will appear at the top of the screen which says "Recovery Booting..."
CAUTION: Never attempt to install a custom ROM or unofficial update file from the stock recovery mode: the phone will flip out and brick.
The stock recovery mode contains the following options:
1) reboot system now
2) apply update from ADB
3) apply update from external storage
4) wipe data/factory reset
5) wipe cache partition
6) apply update from cache
Wiping the cache is an easy and painless fix to a lot of vague problems and even solves some boot failures after installing a custom ROM. Doing a factory reset can solve a lot of things too, but be aware that you'll have to reinstall and reconfigure all of your apps unless you keep good backups.
Download Mode: The phone also has a mode where you connect to software on a computer and flash files to it, sometimes referred to as "Odin Mode". Access Download Mode by first powering off the phone (and making sure it's not plugged in), then holding the Home + Volume DOWN + Power buttons at the same time ("down" = "download"...get it?). After a few seconds, a screen will appear giving you a dire warning that installing a custom operating system is known to the Surgeon General of California to cause cancer, or...something....I don't know, I've never actually read the whole thing. Just press Vol-Up to acknowledge the warning. While in this mode, connect the phone via a microUSB cable to a Windows computer.
Flashing Files With Odin
The operations in Download Mode will be performed with a piece of Windows-based software called Odin. This tool is reported to be the actual software that Samsung uses to flash and repair phones, which has been leaked to the Android community. I caution you to only download this from XDA-provided sources. Odin is used to flash files to the various system partitions of the phone (firmware, kernels, modems, factory restore images, etc). Odin cannot be used to flash custom ROMs.
Odin 3.09: can be downloaded here.
Note that when you have the phone in Download mode, your computer won't show it as a device in "My Computer" because it's not connected as a media device., but Odin (or any other software that knows how to look for it) can see it. Odin will highlight blue in its first "ID:COM" box when it detects your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You'll see several boxes on the right side when you open Odin.
BL = Bootloader
AP = Your system, recovery, and boot.img (this was labelled "PDA" in older versions of Odin)
CP = Modem
CSC = Cache and Hidden CSC features
Everything on this phone is flashed using "AP" box (highlighted in blue in this picture), and you'll want to leave every option at the default setting unless specifically told otherwise.
When you click "AP", a file browser window will pop up, and you browse to and select the flashable file you've downloaded. The file needs to be one that ends with a file extension "tar.md5", or Odin can't see it. If what you've downloaded is a zip archive, the image is inside that and you need to extract it first.
Only extract a flashable file if the contents of the archive are "FILENAME.tar.md5", because that itself is the Odin-flashable archive. But do not attempt to extract the contents of the tar.md5, just flash it with Odin. If the file is a .zip that contains "META-INF" and/or other files and folders, it is to be flashed with SafeStrap or FlashFire rather than Odin.
MD5 Checksum: Before flashing ANY file, you need to verify that it downloaded fully and accurately. To do this, you use an md5 checksum tool (such as this one provided by Misterxtc), which generates a hash string based on the exact bit content of the file you've downloaded. You then compare that string of characters to the one provided along with the original. For example, AndroidFileHost.com will always list it here (as I've highlighted in red). You don't have to manually compare them, as most md5 tools have an input box where you can paste the string for comparison. If the file you've downloaded is even slightly corrupted or incomplete, the md5 checksum will not match and you'll know immediately that you need to re-download it. Obviously, attempting to flash a corrupted file will fail. You should check the md5 after you download a file, and again after moving it to your phone's storage. Here you see the md5 hash, which I have outlined in red.
After you select your file, Odin will verify its integrity. When that process is complete, click Odin's "Start" button. The file will flash to your phone, then when the flash is complete (unless you unchecked that option) the phone will be rebooted automatically. The text box on the bottom-left of the Odin window will report the results of the flash operation, including any errors.
CAUTION: Do not unplug your phone or allow your battery to die while a flash is in progress!
Odin troubleshooting (if your phone is not recognized by Odin, or a flash fails)
1) Verify the md5 checksum of the file you're trying to flash
2) Ensure the USB drivers for the phone are installed and up to date on the computer you're using. If you have problems, you may have to "uninstall" the phone from the computer's "Device Manager" and then reinstall it.
3) Check that your microUSB cable is fully seated in both the phone and the USB port on the computer.
4) Try a different microUSB cable and/or a different USB port on your computer (a bad cable or bad USB port are very common causes of a flash failure)
5) Examine the microUSB port on your phone to ensure it's not damaged, or plugged with pocket lint which may be preventing a complete connection
Samsung provides a free tool called "Kies", which allows you to do various things including installing drivers, transferring files to/from your phone, etc. You may find it useful if you are having difficulty connecting your phone to your computer. Just be aware that if you have Kies running, it will prevent Odin from functioning.
If Windows is not an option for you, you might try the open-source alternative to Odin known as "Heimdall Suite". I have no experience with Heimdall so will not try to comment on it further, but if anybody has any important info about it I would be happy to edit it into this guide.

Custom Recovery Environment
Due to the locked bootloader, the custom recovery environments such as TWRP (TeamWin Recovery Project) and ClockworkMod Recovery (CWM) cannot be used. However, hashcode created SafeStrap Recovery (a heavily modified TWRP recovery environment) that is safe to use on the S5.
A custom recovery is optional, but it's a powerful tool and safety net, allowing you to flash files (except Odin files), install ROMs, selectively wipe partitions, and create/restore full system backups (known as NANDroid Backups), among other things.
SafeStrap was originally conceived to allow ROMs to be installed in different "ROM Slots", allowing the stock OS to be untouched and easily swapped between. Unfortunately, hashcode abandoned SafeStrap development before the slots were ever made to work reliably. If you are still using the KitKat 4.4x version of SafeStrap, only flash ROMs to the "Stock" slot and pretend the other slots do not even exist.
hashcode's original SafeStrap thread - Use this if you are still on 4.4.x
If you are on Lollipop 5.x, hashcode's version of SafeStrap is functional, but requires a workaround so it is a bit of a hassle. SafeStrap will not function with a 5.0 kernel, so you most first either use Odin or the NI2Flasher.apk to flash an older 4.4.x kernel, then boot into SafeStrap. You must then flash your appropriate 5.0 kernel with Odin or from within SafeStrap BEFORE rebooting, or your phone will not be able to boot. Fortunately, jrkruse has modified SafeStrap Recovery to work smoothly on 5.0: it automates the process of the necessary kernel flashes ( and has several other small improvements, such as removing the non-functioning ROM slots).
jrkruse's updated SafeStrap for Lollipop - Use this if you are on 5.x
FlashFire: If you don't want to use SafeStrap for some reason, an alternative is Chainfire's "FlashFire" app. It is fully capable of doing most anything SafeStrap can do, without you having to boot into a custom recovery environment. The only real downside is that Flashfire is an app, so if your phone won't start up then you can't use it to restore a backup. You can selectively use both FlashFire and SafeStrap depending on the circumcstances.
Fixing a Bricked Phone
"Bricked" means a phone will not start and can no longer be used; in other words, it's as good as a brick. Fortunately, in almost every case the phone is not totally ("hard") bricked, but is only "soft" bricked and can be repaired fairly easily. If you are unable to load your operating system but you are seeing any kind of logo or splash screen, relax: you are only soft bricked, and the phone can be fixed bexcause you can still boot the phone into Download Mode and Recovery Mode.
If you've just flashed a file (such as a custom ROM) and the phone won't start, don't panic.
1) The first thing to try is to wait: if you've just flashed a deodexed ROM, it can take up to ten minutes to load and boot, and all you'll see is the splash screen. Let the phone sit for 10-15 minutes to see if it's just busy.
2) If the phone still won't boot, unplug the phone and pull out the battery, then re-insert it and try again.
3) If the phone STILL won't boot, pull the battery again, then reinsert it. Enter Recovery Mode by holding the Home + Volume UP + Power buttons at the same time until the phone says "Recovery Booting" at the top of the screen. From there, select "clear cache" and then reboot.
4) If the phone STILL won't boot, repeat step 3, but select "factory reset", then reboot. CAUTION: In case you're not clear on what "factory reset" means, you will lose all apps you have installed and all settings you have configured.
If you've flashed a kernel and the phone won't boot, you may have used a non-compatible kernel version. Flashing the same kernel version as your phone's firmware version will allow the phone to boot. After you boot into Recovery mode, you will see the firmware version listed at the top of the screen.
If all else fails, you can always boot into Download Mode by holding the Home + Volume DOWN + Power buttons, then use Odin to flash a Stock Restore image file. This will restore the phone to its factory state. CAUTION: To be clear: all of your apps and settings, and everything on the phone's internal storage will be deleted (but anything on your external SD card will not be affected).
Unbrick Image: If you are unable to get into Download Mode, there is one thing you can try. There was a method developed (I believe) for the Galaxy S3 that also works on the S5.
1) First, you must obtain an Unbrick Image that has been created with the Unbrick Image Creator on a phone with the same version of firmware and bootloader as the one you're trying to restore. Use the forum search function to find the image you'll need (unless someone is willing to provide a permanent repository of unbrick images).
2) Rename that file to "unbrick_IMG.img", and use Win32DiskImager to flash that image file to a "16gb Class 10" MicroSD card.
3) Insert the Unbrick MicroSD card into the phone, and power it off by unplugging it and removing the battery.
4) Re-insert the battery, then boot into download mode by holding the Home + Volume DOWN + Power buttons.
5) Now connect with Odin and flash a factory restore image.
JTAG: If your phone is truly bricked, you have one last possible recourse. There is a hardware tool called a JTAG that may be able to help you. It's a fairly expensive piece of hardware, but some repair places offer a one-time JTAG repair for a modest fee.
ROOTING 4.4.x and 5.x
As of mid-January 2016, root has now been achieved on every firmware version from NCG all the way to PB1.
Root access is simply a configuration within the operating system that allows one write access to protected system files. This is HUGELY powerful, allowing one to modify or delete system apps or alter how they function. If you are not very computer literate, you may want to pass on rooting until you've learned more. If you don't know what you are doing, it's possible to do some damage to your phone's configuration (possibly rendering it unusable to you, at least until you learn how to repair it). It can be dangerous to play outside the boundaries of User Space. Here there be monsters...
Note that although we have root access, the Bootloader is still locked and is extremely likely to remain so indefinitely. The bootloader is booby-trapped with a hardware "qfuse": attempts to alter the bootloader result in a hard-bricked phone, which effectively dissuades developers from messing with it. Fewer and fewer developers care about this phone, anyway, and have moved on to brands that are less hostile to power users.
Root Kitkat 4.4.2 or 4.4.4 (uses TowelRoot after temporarily downgrading kernel to NCG)
Update from rooted 4.4.x to 5.0 and Keep Root
Root Lollipop 5.0 (uses KingRoot)
Busybox: Android is a gutted variant of the Linux operating system, stripped down to only those functions needed to run a smartphone. Busybox adds back in a lot of the linux/unix functions and commands that were removed. You'll need this once you root if you want to be able to do anything really useful.
Custom ROMs
With a rooted phone, it is possible to install a customized version of the operating system, which is known as a "ROM". These range from rooted Stock ROM, mildly to heavily debloated versions of the Stock ROM, to more heavily customized and themed ROMs.
Unfortunately, because the bootloader on the Verizon S5 is locked, it is only possible to choose from a small selection of TouchWiz-based ROMS. Cyanogenmod (and all the various AOSP-based ROMs) require a different kernel: if you try to use a non-TouchWiz based kernel, the locked bootloader will not allow it to boot.
Only install ROMS found in the Verizon Galaxy S5 Android Development section of the forum.
The Verizon "Developer Edition" S5 comes with an unlocked bootloader, so on that device you CAN run non-TouchWiz ROMs.
As of March 2016 an unlock method for one of the two possible bootloaders has been discovered and exploited, essentially allowing you to turn your phone into a Dev Edition. To determine if your model is unlockable, you need to check the eMMC version. Do this by using a file explorer to browse to /sys/block/mmcblk0/device/cid. The CID file will contain a string of characters: if the first two digits are 15, your phone has the Samsung chip that is unlockable. If the first two digits are 11, your phone has the Toshiba chip and is NOT unlockable.
Odexed vs De-Odexed: You will also see in a ROM's description if it is "odexed" or "de-odexed". This is referring to how all of the applications on the phone are packaged.
An ODEXED application is one where parts of it have been "optimized" in a separate file (with the file extension .odex). This makes the application take up a little less storage apace and also load a little more quickly. However, because the parts of the app are packaged separately, it makes it harder to alter that application on-the-fly (such as theming or modifying the way it behaves).
A DEODEXED application is one where this optimization has been undone. This is necessary for theming or other modifications, and the space and speed difference is probably not really noticeable. If you plan to do any theming or on running Xposed framework, you should install the DEODEXED version of your chosen ROM.
The basic procedure for installing a custom ROM:
1) Boot into SafeStrap Recovery
2) Make a NANDroid backup of your current system, saved to the MicroSD card. If something goes wrong, you can easily restore to where you are now.
3) Wipe cache, dalvik cache, and system partitions.
4) Install your chosen ROM (which will be a .zip file)
5) Install any optional modification zips included and compatible with that particular ROM
6) Wipe cache
7) Reboot
jrkruse goes into much more detail for installing Lollipop ROMS here
Always do a full system wipe from SafeStrap before installing a ROM, or you will have many problems with conflicting settings and system files. Wiping first is known as a "clean flash". The only exception is if you are updating to a newer version of the same ROM, in which case it may be successful to do a "dirty flash", where settings files are unlikely to have changed enough to cause conflicts.
Likewise, never restore "system" apps with Titanium Backup or anything else unless you're on exactly the same version of the OS, because this is almost certain to try to configure those system apps in ways they can no longer function. Doing so will introduce strange problems that can be very difficult to troubleshoot.
If something goes catastrophically wrong, you can always get back to a factory state with Odin, root, install SafeStrap, and restore your NANDroid backup (provided you saved it to the external SDcard like I instructed you, rather than wiping it into oblivion with a ROM flash).
Debloating
Once rooted, you can remove a lot of the bloatware from your phone. It is possible to just uninstall or delete unwanted bloatware, but this can cause problems if you unknowingly remove something that was required for something else to work.
The safest option is to use Titanium Backup to "freeze" the undesirable apps. Then run your phone normally for a few days to make sure everything is functional. Once you're sure an app is safe to delete, you can then do so, or you can just leave it frozen. If it turns out you need to re-enable a frozen app, just "defrost" it in Titanium Backup.
Disabling KNOX
If you choose to use a Stock ROM after rooting, you will want to disable a few things: Knox, security update notifications, and the Verizon Over-the-Air updater.
Use Titanium Backup to freeze the following system apps:
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store
Security policy updates SPD_v2_1402_4_1 (Security update notification)
SDM 1.0 (Verizon OTA update)
Xposed Framework and Modules
I won't go into a lot of detail here at this point. Just a few notes. I'll probably flesh this out more later and list my favorite modules.
In order for Xposed to function, you must be using a DEODEXED version of your ROM.
Xposed is awesome, and you should look into using it. I've been using the GravityBox module, and it allows me to get most of the little features I've previously enjoyed in custom ROMs.
Xposed installer for Lollipop
The specific Xposed framework you need to use for S5 Lollipop
Xposed bootloop: If you install an incompatible Xposed module, the worst case is a bootloop. You fix that by getting into Safestrap, choosing file explorer, and creating a file called "disabled" in /data/data/de.robv.android.xposed.installer/conf/
Alternately, there's a flashable zip file somewhere that puts the "disabled" file where it needs to be.
Then you reboot, get into Xposed and turn off the offending module. Then use a file explorer to go delete that "disabled" file and reboot.

Awesome thread!! Thank you very much for spending the time and putting this all together!!
Sent from my still locked down SM-G900V ?

Lots of great info in here! I appreciate the time and effort.
Are there any roms beyond 5.0 for verizon? I'm still running 4.4.4 right now. I tried 5.0 and hated some of the changes with sounds settings (Normal/Vibrate/Silent). My understanding is that 5.1.1 replaces these with the older setup. If that's the case I'd love to move to 5.1 but haven't found any ROMs that do 5.1.x except for one in the Unified forum. But the links for that are dead.

RedRamage said:
Lots of great info in here! I appreciate the time and effort.
Are there any roms beyond 5.0 for verizon? I'm still running 4.4.4 right now. I tried 5.0 and hated some of the changes with sounds settings (Normal/Vibrate/Silent). My understanding is that 5.1.1 replaces these with the older setup. If that's the case I'd love to move to 5.1 but haven't found any ROMs that do 5.1.x except for one in the Unified forum. But the links for that are dead.
Click to expand...
Click to collapse
Not to my knowledge. The locked bootloader makes development very difficult. I think we will have to receive a stock 5.1 that functions with our locked bootloader before anybody can develop ROMs based on it.
I still prefer 4.4.4, too. However, if you want to give 5.0 another try, you may be able to use an Xposed module to restore the way you prefer the sound settings to work.

RedRamage said:
Are there any roms beyond 5.0 for verizon? I'm still running 4.4.4 right now. I tried 5.0 and hated some of the changes with sounds settings (Normal/Vibrate/Silent). My understanding is that 5.1.1 replaces these with the older setup. If that's the case I'd love to move to 5.1 but haven't found any ROMs that do 5.1.x except for one in the Unified forum. But the links for that are dead.
Click to expand...
Click to collapse
As of now, we are limited to 5.0. If you give 5.0 another shot, I'd suggest using Wanam Xposed and enabling expandable volume control. I couldn't stand the volume settings of Lollipop until I started using Wanam.
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Thank you, @painiac! Now I have a thread I can link every time someone asks how to do the basics. Having a device specific root/ROM thread makes things much easier.

I'm trying to help a fellow user who's trying to install the Optimal ROM and he keeps getting the OTA update message. I mentioned for him to try to freeze the SDM 1.0 but he said that it's not listed in TB. And to be honest, I don't see it listed anywhere in the MOAR ROM that I'm running. So if someone could point me in the right direction on how to freeze the OTA update. I/he would be greatly appreciated. He's posted the issue on the Optimal thread. Thank you in advance

al50 said:
I'm trying to help a fellow user who's trying to install the Optimal ROM and he keeps getting the OTA update message. I mentioned for him to try to freeze the SDM 1.0 but he said that it's not listed in TB. And to be honest, I don't see it listed anywhere in the MOAR ROM that I'm running. So if someone could point me in the right direction on how to freeze the OTA update. I/he would be greatly appreciated. He's posted the issue on the Optimal thread. Thank you in advance
Click to expand...
Click to collapse
It has been a long time since I've used MOAR, but I'm sure the OTA updater has been removed from it. The name of the app is SDM.apk. You should be able to find it in Titanium, but you can delete it manually if need be.

CVertigo1 said:
It has been a long time since I've used MOAR, but I'm sure the OTA updater has been removed from it. The name of the app is SDM.apk. You should be able to find it in Titanium, but you can delete it manually if need be.
Click to expand...
Click to collapse
Thank you for replying CVerigo1. That's what I was thinking about it may have been removed. We suggested that he wipe 2 timesbefore installing the ROM just in case he had some files lingering around. I'm hoping that will solve his issue. Thanks again and apologize for posting this in Painiac's thread.

Thanks for putting all of this together. I sent in a request for the thread to be stickied since we need an updated "How to" thread.

Dudash said:
Thanks for putting all of this together. I sent in a request for the thread to be stickied since we need an updated "How to" thread.
Click to expand...
Click to collapse
It appears your request has been approved. I appreciate everyone's kind words.

So, say I have a phone that is BOK3 rooted (sweet) and I want to go back to factory unrooted BPB1 (to sell it)... what steps do I follow?
Update (3/8): Found out one solution to going back to stock...
1.) (This Step Is Probably Optional) -- Flash the stock BOK3 Rom using Odin and the PA slot -- This clears the bulk of your custom/rooted files off the phone
2.) Check for system update, allow it to install (should be BPB1)
3.) Boot into recovery mode and clear the phone (WARNING: You will lose all data on your phone)
--- Turn the Galaxy S5 off.
--- Press and hold the Volume up button, the Home button, and the Power button together until you see the Android on screen.
--- Use Volume down to highlight the wipe data/factory reset option and press the Power button to select it.
--- Use Volume down again to highlight Yes – delete all user data and press Power to select it.
--- Wait until you see the reboot system now option and then use the Power button to select it.
--- When the S5 restarts it should be completely wiped and ready to set up again.
Thanks,
Wook

rxwookie said:
So, say I have a phone that is BOK3 rooted (sweet) and I want to go back to factory unrooted BPB1 (to sell it)... what steps do I follow?
Update (3/8): Found out one solution to going back to stock...
1.) (This Step Is Probably Optional) -- Flash the stock BOK3 Rom using Odin and the PA slot -- This clears the bulk of your custom/rooted files off the phone
2.) Check for system update, allow it to install (should be BPB1)
3.) Boot into recovery mode and clear the phone (WARNING: You will lose all data on your phone)
--- Turn the Galaxy S5 off.
--- Press and hold the Volume up button, the Home button, and the Power button together until you see the Android on screen.
--- Use Volume down to highlight the wipe data/factory reset option and press the Power button to select it.
--- Use Volume down again to highlight Yes – delete all user data and press Power to select it.
--- Wait until you see the reboot system now option and then use the Power button to select it.
--- When the S5 restarts it should be completely wiped and ready to set up again.
Thanks,
Wook
Click to expand...
Click to collapse
That works, but it has some extra steps. Just flash the PB1 factory image with Odin: there's no real reason to do BOK3 and then wait for an update to install. Flashing a factory image should have cleared all of your user data as well, but you can initiate a factory reset to be sure if you're selling it.

painiac said:
That works, but it has some extra steps. Just flash the PB1 factory image with Odin: there's no real reason to do BOK3 and then wait for an update to install. Flashing a factory image should have cleared all of your user data as well, but you can initiate a factory reset to be sure if you're selling it.
Click to expand...
Click to collapse
Thank you for clarifying that. I was afraid to just flash the PBP1 Rom without knowing how it would act.
When I flashed the stock OK3 Rom it took the OTA update just fine. Interestingly, flashing the stock Rom didn't clear anything off the phone, so a factory reset had to be performed in my case.
In all honesty, I love the phone overall... But I'm just really sick of the locked bootloader.
Thank you for the comprehensive thread (and response to my post above).
Thanks,
Wook

rxwookie said:
Thank you for clarifying that. I was afraid to just flash the PBP1 Rom without knowing how it would act.
When I flashed the stock OK3 Rom it took the OTA update just fine. Interestingly, flashing the stock Rom didn't clear anything off the phone, so a factory reset had to be performed in my case.
In all honesty, I love the phone overall... But I'm just really sick of the locked bootloader.
Thank you for the comprehensive thread (and response to my post above).
Thanks,
Wook
Click to expand...
Click to collapse
You're very welcome. I can't blame you... my next phone likely won't be a Samsung.

Thank you for putting all of this together. Does http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909 change any of the information regarding custom ROMs?

jokajak said:
Thank you for putting all of this together. Does http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909 change any of the information regarding custom ROMs?
Click to expand...
Click to collapse
It does, IF you have the specific chipset that can be unlocked. Thanks for mentioning that, I should add it to the guide.

This is a wonderful guide, thank you for putting it up. I'm a software engineer, but I rarely work with android code and have been using iPhones for awhile.
I used to root old droid phones back in the days of the Droid X2 and Droid 3, but I haven't done it in awhile. My girlfriend has an S5 that is causing her lots of problems, specifically terrible battery and no more space for adding apps because of the bloatware. When I used the older motorola droids, there was a process termed "sbf-ing" that would allow me to downgrade my phone to a different version. Is there any way I can do this with an s5 ? She has an S5 running 5.1.1, and I'm curious if I can bring it down to 5.0 or 4.xx to work with some of these roms.
Thanks!

Trying to do CM13 to CM12.1 downgrade on soft-bricked

So I decide to upgrade a a couple of weeks after OTA update to CM13 arrived. Turns out it was a massive mistake, especially since no backup, no ADB enabled, no root and nothing custom. This is the best I have so far: https://jira.cyanogenmod.org/browse/BACON-4808 (summary: System UI and com.android.phone both crash on startup). Sad thing is I can see phone working just fine behind the crashed UI (getting mail, notifications etc.) I know my data is in there but cannot get to it.
Anyway, customer support is responsive but I am not sure they will let me keep my data.
I am pretty much starting from scratch regarding flashing, and the first few hours was deciphering abbreviations and other bull. Other than that I am decently proficient with the tech stuff.
Would be grateful if you guys can help point me in the right direction. The info I currently have:
* I want to keep my data
* images here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
* I know that my phone is recognized by PC if I put it into ADB sideload mode (didn't yet try whether it works though)
* phone is also recognized when in fastboot
* possibly downgrade might work, but I am trying to find a method that will let me keep the data, if I get glitches I don't care for now
What I am not so sure about:
* flashing for example cm-12.1-YOG7DAS2K1-bacon-signed.zip in full should let me keep the data, true?
* taking fastboot image and just flashing boot&system should also let me keep the data, true? Did I miss anything?
What do you guys suggest I do? I know that in the end I might crash everything anyway, but at least I want to do the best I can (And make that backup soon after). Thanks for all and any help!
edit: Did the sideload flashing, that went fine, is easy. Problem is those images seem not to work for me anyway (bootloop). Probably because I didn't wipe userdata.

maybe try to use the restore tool (http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851) its pretty old (CM11s) but if it workd then refalsh the TWRP and update your phone to cm12.1 (with the required firmware)

A good question after all I did: Did anyone ever successfully downgrade from 13 to 12.1 without full data wipe?
p.s. it is very very easy to downgrade, it just doesn't work since OS upgrade makes changes to local data making it incompatible. This is what I did:
1) down+power on
2) chose upgrade and sideload upgrade from adb
3) while in that menu phone will wait for the update, just connect it to pc and do adb sideload image.zip (image needs to be signed ordinary image not the fastboot one)
4) wait until it completes and reboot phone
Tried all 4 CM12.1 images to no avail.

Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.

skundurthy said:
Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.
Click to expand...
Click to collapse
Take a backup of your internal storage
Flash factory images of CM13 using Index #8 http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
After flashing factory images, flash TWRP (Index #8)
After flashing TWRP, flash SuperSu from TWRP http://download.chainfire.eu/supersu-stable

Completely Eliminated Static Boot on Rooted V20 with My Stock Kernel!!!

Alright guys, so this happened 100% ON ACCIDENT but it actually worked! I wanted to let you guys know because maybe it will help some of the devs figure out how to eliminate the static boot for good.
I have the H910 ATT V20. I initially rooted it using Dirty Santa but, at the time, nobody had made a custom ROM for the ATT variant yet. I flashed the Konverged Kernel and from then on, I had the dreaded static screen on boot. @Tilde88 was extremely generous in offering to make a custom ROM if I provided some files for him and he made the first excellent NotSoStock ROM for the ATT V20. However, I had some issues installing it on the first try. When I tried to flash his ROM, TWRP gave me an error telling me I had a US996. I patched the zip with a file from Tilde88 and it worked like magic!
Since then, there has been a lot of progress in ROMs and kernels for all the variants. For the sake of experimentation, I have tried different ROMs and kernels to see how they affect the phone. Since my phone is registering as a US996, I flashed that variant of the NotSoStock ROM. The Werewolf Kernel from @USA-RedDragon is the only one I know of so far that does not have the static on boot. I have been flashing Werewolf and Konverged along with different ROMs to see the difference in performance and battery.
The ROM I am on right now is Extreme Syndicate from @elliwigy. Since it is based off of the stock deodexed US996 firmware, I thought it sounded great to try since it has NONE of the bloat from any of the various carriers. I read in a post by @AlkaliV2 here about flashing the stock kernel located on my computer from the original Dirty Santa root method:
https://forum.xda-developers.com/v2...-nrd90m-modded-notsostock-rom-t3525344/page21
That gave me an idea to download and flash the stock unlocked US996 kernel since Extreme Syndicate is based off of that. I had Konverged Kernel at the time. I flashed the US996 kernel, but forgot to flash SuperSU before boot... Woops lol. So I went back to TWRP and formatted my phone to start from a fresh flash, but realized I also deleted my ROM backup when I formatted my phone. So I decided to install a ROM and kernel fresh.
HERE IS HOW I FIXED THE STATIC BOOT
After formatting my phone, I flashed the Extreme Syndicate ROM with the Werewolf Kernel. I chose this kernel so there would not be any static on boot.
Then
I booted back to TWRP, made a backup just in case, and flashed my stock H910 ATT kernel from the file named bootbackup.img. After that, I flashed SuperSU, wiped Cache and Dalvik, rebooted... and BAM, just like that, no static! It says under software information that I am on kernel version 3.18.31. 3C Toolbox shows the kernel as Linux 3.18.31g12e8957
It is still fresh so I have to see how it goes with battery and performance. Initially, it was noticeably slower. I completely fixed this by:
1. Implementing all options under "One Click -> Performance Optimizations" in the app 3C Toolbox
2. Selecting "Performance" under Profiles in the app L Speed
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!

Yes, there is an updated driver branch using CAF sources that fixes static boot. I'm far too busy in life to get anything done, and before anything else, I have to get v6.0 for the H918 going. Once that is up (using the latest build and soruces from LG), I can move forward for 6.0 for the other devices.

nikktrikk said:
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!
Click to expand...
Click to collapse
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb

AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Hmmm interesting. Mine returned with:
Code:
3.18.31-g12e8957
[/QUOTE]
Do you have any idea why that might have happened? I used the file directly from the Dirty Santa folder, but maybe there is an issue since I flashed it over the previous kernel.

AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.

nikktrikk said:
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.
Click to expand...
Click to collapse
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.

AlkaliV2 said:
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.
Click to expand...
Click to collapse
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!

nikktrikk said:
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!
Click to expand...
Click to collapse
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.

AlkaliV2 said:
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.
Click to expand...
Click to collapse
Definitely makes sense. Yeah I have been having issues with battery drain and all that, as well. This is the very first time since I have been having issues with the US996/H910 conversion and incompatibility that I have actually got it to be stable. I also didn't like not having comfort view, and this actually fixed it! Comfort view now works on my phone, it didn't work earlier today before this most recent flash. I think that I will just give it some time before I make a decision and see how the battery fares. You have been a HUGE help, I really appreciate you taking the time to explain the process to restore my phone. I do want to do it, but being that it currently seems to be doing a lot better than before, I'll wait before making the leap back to stock just for comparison.

Help me
I also have h910 model but when i tried to boot after dirtysanta 3 rd step it didnt boot into twrp..even though i tried to flash recovery with fastboot flash recovery command.
I m stuck and static screen is a mess..plz help me

Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?

titmus said:
Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?
Click to expand...
Click to collapse
you where supposed to back up your original filesystem you would have gotten it from there.

'Official TWRP app' 1.17 is missing features?

To All who could help.
#1
I updated the official twrp app 1.17 on my Sprint HTC U11, running 7.11 & Bad Boyz 2.0 ROM, w/the FW build # 1.28.651.3 & now I've got none of the buttons to go into Install, Backup, Wipe, etc. that showed on the older version's startup screen; & I want to make a new nand backup.
Do I need to get ahold of an older version ofthe Official TWRP android app? If so, where to find it?
#2
Also, using the older version, whose startup screen shows all options Install, Wipe, Backup, etc, could I have accidentally encrypted my phone or TWRP or somethingthat would have caused this? I recall pressing a dbutton on the lower right corner of the old app, & some process ran on my screen too fast to see; I thought I was just 'exploring' what the older Official TWRP App could do & instead some script ran & I had to enter my security pattern & a msg showed that my pkone is encrypted & I have 30(?) attempts to enter the pattern before the phone would be wiped. Oddly, this behavior went away, the prompt for my pattern, when I went into old Official TWRP App & wiped Cache & Dalvik.
With this new version, I wouldn't be able to do that, or Restore a nand backup ? which makes me very concerned.
Please advise. TIA, oldwolf
All I get is what shows on this screenie:

What I see is only the TWRP App that is installed on the ROM to update your TWRP.
Did you reboot to recovery and check? If so please post some pictures and some logs.
In addition this would.habe belonged into the Q&A section, or - if pictures and log would've been available - into the TWRP thread. But let's leave it here for now and get this thread moved to Q&A later.
Sent from my HTC U11 using XDA Labs

5m4r7ph0n36uru, thanks for your reply! I guess I really mixed things up in my mind... I figured that since twrp is a recovery, my question belonged there. Feel free to move it if it is called for; please just leave me a link as to where it will be…
I have worked w/Odin & Safety Strap mod tools on my obsolete S4 & older Droid Razr utils. I only used twrp when I installed a custom rom once, I switched to Sprint just this past June… so I'm not as comfortable yet working w/twrp & its ins & outs.
The thumbnail I attached was fm what I thought would change me over to the new 3.2.1-2 version of twrp.
I followed your advice & rebooted into recovery & voila! The features are all there, Backup, Install, etc.(should have known better - but we all have to learn from our mistakes I guess).
In Recovery mode, I'm still on version 3.1.1-0 of twrp- running FW 1.28.651.3 & 7.1.1 Nougat OS.
#1. Can I put 3.2.1-2 onto my device w/the listed OS & FW versions? or do I need to bring it up to latest FW?
#2. If 3.2.1-2 will work with my current FW, should it be flashed from my computer & if so in which mode? Recovery Mode- or using the Official TWRP App, on my fone?
Not sure what the Official TWRP App fm that thumbnail is for…now I am confused
Your help is much appreciated. oldwolf

How to properly flash tulip with twrp and ota on stock?

Hello there.
I'm using tulip for few months now. One of first things that I've done, have been unlocking device, rooting it and put stock rom with root access on it. So far, so good. I did not encounter any serious glitches etc, but now I would like to finally upgrade miui to 11 (currently having 10.3).
And there's my problem. I would love to dodge making clean installation (wipe data etc) and I do not wish to risk to bootlooping my phone. I've read on some threads (older ones, but still) that you cannot simply install ota update in system, because due to changed recovery (I do have TWRP instead of fabric one) you will cause bootloop. I've tried alternative method of installing zip BY twrp, but program says, that it encounter a problem called "package expects build fingerprint (...) of tulip 0/PKQ1.180904.001/V10.3.2.0.PEKMIXM or PKQ1.180804.001/V11.0.2.0; this device has omni_tulip/tulip:8.1.0/OPM8.181105.002/1", and then sait, that in had error 7.
Is it simply wrong rom being installed and I have to choose something that is being named the same way and supports ota, or is there a way to go more swiftly through this process? If so and I should pick rom with ota - what to choose? I like deep level customisation, but compatibility with google store, being able to use store, payments and paid apps, instead of "opening them" by some lucky patchers kind of apps.
OR MAYBE I just need to change recovery from TWRP to something different - like PBRP f.e.? Just like this thread says - https://forum.xda-developers.com/re...how-to-setup-official-miui-breeaking-t3893703

Just a quick update - changing twrp to pbrp does not change anything in upgrade process - still get the same error, now just without telling me, which version do I have.
Also, what's interesting, apparently twrp said to me that I do have android 8.1, but "about phone" in system says, that its android 9 (9PKQ1.180904.001 to be exact).
That's werid, because everywhere I check, phone says "android 9" as a version of it.

Have you tried wiping system and installing?

Nitin Rai said:
Have you tried wiping system and installing?
Click to expand...
Click to collapse
Not yet. I've found method of flashing via PBRB with usage of downloaded file and one option check, but I'm not gonna try it, unless I do a backup of my apps. If that won't work, I'll perform a clean instalation and choose rom that supports ota.

well, I've tried to do this with the method, that I've described before, but this did not ended successfully. I'll look for rom with ota update possibility and then install it most likely. Apps had backup, so I lost almost nothing.

It worked. I had to download bigger patch (1.7 GB, instead of circa 700 MB, that I've tried before), I also had to use method described here -> https://c.mi.com/thread-1782169-1-1.html (pitch black recovery, instead of twrp + one tweak in options). Start after flash was very long (it took like 10 minutes or so), but it booted successfully in the end. Not sure which rom I do have after all, but as far as I remember it was so close to stock, as possible (with only few extra options and tweaks). So yea, it just works.