Database Users

[Q] Best procedure for flashing Optimized CM12.1 on to the UK GT-I9505 (JFLTEXX)?

I successfully flashed CM11 on to my LG G Pad 8.3 without issue so I've done this before (but most of the downloads had Batch files to automate things) but want to still be sure of the procedure.
My I9505 was recently upgraded OTA to Android 5.0.1 along with Samsung's TouchWiz. Hopefully this won't complicate matters.
Is this the best/recommended procedure? -
Root: What's the best/recommended method to Root my S4?
Backup Stock Recovery: Using Flashify on Google Play.
Install Recovery: Is TWRP Recovery v2.8.7.0 the best Recovery to use?
The Optimized CM12.1 thread recommends TWRP 2.8.7.0 but the download doesn't contain a batch file to run?
Reboot to TWRP --> Backup my existing ROM image then choose the Wipe option
Install the Optimized CM12.1 ROM then GAPPS from SD Card
Related questions about the Optimized CM12.1 ROM and GAPPS please:
Wouldn't a regular CM12.1 Nightly for the I9505 be better than the Optimized CM12.1 ROM? The Optimized CM12.1 ROM looks to be older (2015-06-16), or am I splitting hairs over a few days? Thanks
The Optimized CM12.1 thread offers a link to download GAPPS for Lolilpop 5.1. Is this better to use than the one in the GAPPS for Lollipop 5.1 here (ARM download): http://wiki.cyanogenmod.org/w/Google_Apps
Thanks a lot in advance for your help.

Is the TWRP Manager on Google Play the best/recommended way to install TWRP 2.8.7.0? -
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Thanks again.

Regarding your steps...
1, 2: Cyanogenmod is pre-rooted, and the stock recovery images are readily available, thus these steps waste time.
3. Yes.
4. Yes. You'll use Odin to flash the recovery, thus no batch file.
5, 6: Yes.
As to your other questions...
1. You need to decide which you want more. Is having a more current build more important than the optimizations? Regardless of the final choice both install in essentially the same fashion.
2. The GApps in the thread is more up-to-date than the official download.
Finally, TWRP Manager stopped working properly some time ago and really isn't necessary. Download the image from the Optimized CM12.1 thread and install it using Odin.

Strephon Alkhalikoi said:
1, 2: Cyanogenmod is pre-rooted
Click to expand...
Click to collapse
Firstly thanks for the detailed reply.
I remember that from installing CM on my tablet but presumably you still need to Root the S4 to be able to install CM?
Strephon Alkhalikoi said:
4. Yes. You'll use Odin to flash the recovery, thus no batch file.
Click to expand...
Click to collapse
A few more questions please:
1. So when you run Odin it will ask for the location of the TWRP Recovery v2.8.7.0 folder?
2. Is this the best place to get Odin? - http://odindownload.com/
3. That link says I need "ADB & FASTBOOT TOOLS", where do I get these for the S4?
Strephon Alkhalikoi said:
2. The GApps in the thread is more up-to-date than the official download.
Click to expand...
Click to collapse
Oh great thanks. I noticed it was a smaller download. Is there much missing from it over the official one?
Thanks again Strephon.

1, 2: No. You only need to flash the recovery through Odin to be able to install Cyanogenmod.
2. I believe the apps that all can be downloaded from the Play Store are missing, which is a good thing.
4: You need to input the location of TWRP on your hard drive. Search on XDA for the most current version of Odin (3.10.6) and ignore that site's comment about ADB & Fastboot Tools. Simply download Samsung's drivers off their website and install them. As an alternative, you can install Kies, but make sure Kies isn't running when you run Odin.

Strephon Alkhalikoi said:
4: You need to input the location of TWRP on your hard drive. Search on XDA for the most current version of Odin (3.10.6) and ignore that site's comment about ADB & Fastboot Tools. Simply download Samsung's drivers off their website and install them. As an alternative, you can install Kies, but make sure Kies isn't running when you run Odin.
Click to expand...
Click to collapse
Great. Thanks for the further help. I'm nearly there, just a few more questions please:
Do I need to enable USB Debugging?
Running Odin and it's unclear what to do next? I presume these instructions under "Odin Install Method (No Root Required)" are correct? - https://twrp.me/devices/samsunggalaxys4internationalqualcomm.html
Those instructions say to press the PDA button, there is no PDA button. Do I press the AP button instead?
In Odin options is it safe to leave "F. Reset Time ticked"? It looks like it is.
The TWRP 2.8.7.0 in the Optimized CM12.1 thread only offers a ZIP file and the link here only offers an IMG file: https://dl.twrp.me/jfltexx/. But it looks like Odin needs a TAR file. Any ideas?
I presume this (Micro) GAPPS is as good to install as the GAPPS link in the Optimized CM12.1 thread (it's newer, just want to be sure it's compatible)? - http://opengapps.org/
Finally, is it a good idea/recommended to convert to F2FS?
Googling and it's unclear if I want "F. Reset Time" ticked or I should be converting to "F2FS", so I thought I should be sure first. Great I already have Kies installed.
Thanks again. I'm pretty close to installing CM12.1 now.

It won't hurt, but in download mode it shouldn't be needed.
Yes.
The instructions assumed an older version of Odin. Press the AP button.
If Odin fires up with it enabled by default, I'd leave it as is.
Grab the 2.8.7.0 TAR from https://dl.twrp.me/jfltexx/ and install it through Odin. Afterward, you can change over to the F2FS-compatible version using the upgrade instructions given on the twrp.me install page.
It should be compatible, but you may have better luck using the version in the thread.
F2FS is totally optional. I personally don't use it.

Thanks for the quick reply again. There is no 2.8.7.0 TAR file in that link, just a 2.8.6.0 TAR file .
* I presume I should install 2.8.6.0 TAR then install the 2.8.7.0 IMG file on top from inside TWRP?
* OR better yet install 2.8.6.0 TAR using Odin then install 2.8.7.0-F2FS ZIP from inside the TWRP 2.8.6.0 Recovery itself? I presume I use the same Install option I do to install CM2.1 itself?

I didn't look carefully at the page. Sorry. But yes, you can grab the 2.8.6.0.tar, install it, then install either of the 2.8.7.0 images afterward in TWRP.

Thanks Strephon Alkhalikoi. I finally got around to doing this last night and it went without a hitch. I got a pit error using Odin but a quick Google said to plug the USB cable direct into the PC.

Flashing OTA with TWRP on miui 8 cn dev (kenzo)

1. Make 2 copies of Ota. Name them 'ota6. 6.18-6.6.23' and 'boot6.6.18-6.6.23'
2. Extract both.
3. Go to folder ota6.6.18-6.6.23
4. Open metainf-Google-updater-script
5. Remove all verification entries and bootimg patching entries.
6. Go back and zip the ota folder.
7. Go to boot6.6.18-6.6.23
8. Delete everything except patch and metainf folder.
9. Open metainf-google-updater-script
10. Delete everything except bootimg patching entries.
11. Pack/zip it back.
12. Reboot to official twrp (not tested on alka)
13. Wipe system and then mount system read only
14. Flash the full rom package you have
15. Flash the Ota6.6.18-6.6.23 and any other Ota you have back to back.
16. Flash the boot6.6.18-6.6.23 and other boot patch you have back to back.
17. Flash universal boot patcher and any other zip like supersu GApps xposed etc.
18. Reboot.
Keep the patched boot6.6.18-6.6.23 and ota6.6.18-6.6.23 zip safe for further use.
I am on phone, guide will be more detailed asap.
Sent from my Redmi Note 3 using XDA-Developers mobile app

Sudeep Duhoon said:
1. Make 2 copies of Ota. Name them 'ota6. 6.18-6.6.23' and 'boot6.6.18-6.6.23'
2. Extract both.
3. Go to folder ota6.6.18-6.6.23
4. Open metainf-Google-updater-script
5. Remove all verification entries and bootimg patching entries.
6. Go back and zip the ota folder.
7. Go to boot6.6.18-6.6.23
8. Delete everything except patch and metainf folder.
9. Open metainf-google-updater-script
10. Delete everything except bootimg patching entries.
11. Pack/zip it back.
12. Reboot to official twrp (not tested on alka)
13. Wipe system and then mount system read only
14. Flash the full rom package you have
15. Flash the Ota6.6.18-6.6.23 and any other Ota you have back to back.
16. Flash the boot6.6.18-6.6.23 and other boot patch you have back to back.
17. Flash universal boot patcher and any other zip like supersu GApps xposed etc.
18. Reboot.
Keep the patched boot6.6.18-6.6.23 and ota6.6.18-6.6.23 zip safe for further use.
I am on phone, guide will be more detailed asap.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Works like charm ,updated my kenzo from 6.8.11-6.8.18 Miui 8, was tired of downloading whole recovery rom
and flashing it for small 100 mb OTA updates
Thanks awesome guide!

Thanks for this guide.

NVDX11 said:
Works like charm ,updated my kenzo from 6.8.11-6.8.18 Miui 8, was tired of downloading whole recovery rom
and flashing it for small 100 mb OTA updates
Thanks awesome guide!
Click to expand...
Click to collapse
Can you please post modified ota zips.

arunmcops said:
Can you please post modified ota zips.
Click to expand...
Click to collapse
Yes it ll be usefull for all.
Sent from my Redmi Note 3 using Tapatalk

arunmcops said:
Can you please post modified ota zips.
Click to expand...
Click to collapse
Here is my thread & all modded ota links are given and procedure to flash
Flashable MIUI 8 OTA Update 6.8.18 Via TWRP For Kenzo.?http://en.miui.com/thread-331079-1-1.html

Detailed instructions needed for downgrade from S219 to S208

Hi guys,
I'm in using k4 note with s219 build. I have to stick with Jio Join app to make calls. I have read some posts and found that by downgrading we can avoid sticking with join app.
Here are the instructions,
1. Downloaded S152 and S208 builds from various resources.
2. Found sp flash tool and lenovousb drivers within S152 rar.
3. Open flash tool and click scatter log.
4. Choose scatter loading file from target_bin
5. Click on download
6. Turn off the phone and connect with pc
7. Now, successfully downgraded to S152 build.
8. Finally, turn on ur phone and paste the s208 build package (rename it as update.zip) in internal/sd storage.
9. Go to stock recovery by pressing volume rockers and power simultaneously.
10. Choose update from internal/sd card where u kept the files.
11. Tada...! We are done..
Thanks for all the developers.. I have spent lot of time to find these steps. Hope, someone like me make use of it.

[MiUI Notch Notification Mod] for beta or global version

Requirements
We are updating MiUI Notch Notification Mod every week for MiUI dev and stable firmwares. In order to install this mod, you need to match the following requirements:
Xiaomi Android smartphone or tablet
v10 ROM
Unlocked Bootloader (for TWRP)
TWRP custom recovery
How-To
Click the download-button and select your Xiaomi rom version from the list to get the MiUI Notch Notification Mod for your correct MiUI ROM version. You can choose from two different packages, which will let you either Install or Uninstall the mod.
Download the ZIP File
Download link for all version
https://mi-globe.com/mod-download/?modtype=notchnot&id=13&codename=platina&phone=Mi+8+Lite
Copy the File to your phone/tablet
Reboot to TWRP Recovery
Select ‘Install ZIP from /sdcard’
Select the ZIP File
Install and Reboot

I'm in global 10.3.1.0, which version do I use?

renan1217 said:
I'm in global 10.3.1.0, which version do I use?
Click to expand...
Click to collapse
First backup your data after backup flashing last version

https://play.google.com/store/apps/details?id=zanini.andrea.notchtest
use this. no need to wait.

Bootloop?
My phone doesn‘t boot anymore. It is trying to but after a while seeing the bootanimation it restarts into twrp... I didn‘t backup my system. Is everything away now? Also tried installing the disable zip. Problem still there. I think I need to install the rom again with MiFlash

Install Magisk without permanent TWRP - is it possible?

I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402

cris2d2 said:
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
Click to expand...
Click to collapse
but what would that help you with? having the normal recovery?

mike500005 said:
but what would that help you with? having the normal recovery?
Click to expand...
Click to collapse
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
yes i understand but what would be the goal? what you dont like or are afraid that you dont want the recovery is it because OTA updates? or??? you can try to root it and then reflash the stock recovery.img and apply a patched boot image could work idnk cause i have already done a lot to get mine working with latest update and i don't really want to go threw all the backups again

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
custom recovey doesn't replace rom

indeed what you descripe is the official and recommended root method. TWRP is just for nandroid backup (not really needed since Migrate Backup and Magisk Modules can flash straight from android without TWRP at all), therefore the Magisk.zip is just for traditional reasons. Many devices don't even have TWRP (or with no working encryption support)
Installation
The Magic Mask for Android
topjohnwu.github.io
We no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support
Click to expand...
Click to collapse