Database Develop

[ROM-STOCK] Amazon OS 8.4.3 (Flash .zip for TWRP) [07/11 - Version 8.4.3]

Amazon Stock OS for Kindle Fire HD 8.9 - Version 8.4.3
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
This flash .zip file contains the Amazon OS 8.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
NOTE FOR LTE USERS: This does *NOT* contain the wankit update for LTE modem firmware.
Download Information for OS 8.4.3:
Mirror 1: http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.4.3.zip
md5sum: d67ab5cd944dbf9d9509b44aa1d4a7e3
Download Information for OS 8.4.1:
http://d-h.st/VnR
md5sum: a39c815becf8517729c2baec2ad13582
OLDER VERSIONS:
Download Information for OS 8.3.1:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.3.1.zip
md5sum: 6a2584c9a52d9d57dc13e64e05558985
Download Information for OS 8.3.0:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.3.0.zip
md5sum: 9394219ae608bb73b292fcbb84d48aa2
Download Information for OS 8.1.4:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.1.4.zip
md5sum: c9e87973e42d6b34f8269469f9fb479a
INSTALLATION (TO REVERT TO AMAZON OS):
Place flash .zip file onto your SD card
Reboot into recovery
Wipe system
Use "INSTALL" and find the .zip file (NOTE: CM10.1 may create a "0" directory under /data/media so you may need to navigation up to /data/media and back down to find .zip)
Make sure to WIPE CACHE if you're currently on stock (and do a full FACTORY RESET for wiping data/cache if you're on CM10.1 going to this).
Reboot
Go back through the stock Amazon setup process

Works flawlessly thank you Hashcode!!

Works great - but not without a 'heart attack moment' first time around.
I pushed the kfhd8-amazon...zip to the /sdcard/download folder from a Windows box. It was put into /sdcard/0/download.
Once in TWRP, I naviguessed to the /download folder to install the old software - and the folder was blank (apparently TWRP defaulted to the /sdcard/download folder). Ok...Hashcode warned us about the duplicate folders in JellyBean, so I backed out of 'install' and used to file manager to find the kfhd8-ama...zip in the /sdcard/0/download folder. It was an easy click to select it to copy, then navigate to the 'other' download folder, then press paste. FAILED I tried again and that copy failed as well.
Navigating back to the 'install' menu refreshed the screen and the update software zip was magically there. Maybe the failed copy didn't really fail? Maybe the initial read of the /download folder failed and needed to be refreshed? Dunno.
But the flash worked perfectly. And it's apparently resilient enough to catch newb errors - I was so happy that the software appeared that I forgot to wipe the system again after installation. Pressing reboot to the system resulted in an attempted boot and a return to TWRP where I could give the system a good wipe. The next boot was normal.
Whew.

Does TWRP backup of CM10 work as other normal phones or we also need to take care of the "stack" file? because I saw these lines in the update-script. Will a backup/restore of CM10 overwrite this?
---------
run_program("/sbin/sh", "-c", "rm -f /tmp/stack; for i in $(seq 1024) ; do echo -ne '\\x00\\x50\\x7c\\x80' >>/tmp/stack ; done");
run_program("/sbin/dd", "if=/tmp/stack", "of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "bs=6519488", "seek=1", "conv=notrunc");
---------

thanks, will try this later...

stock room problem
Hello I opened this post: http://forum.xda-developers.com/showthread.php?p=38337627#post38337627
What can I do to solve. Thank you

Re: [ROM-STOCK] Amazon OS 8.1.4 (Flash .zip for TWRP)
field3d said:
Hello I opened this post: http://forum.xda-developers.com/showthread.php?p=38337627#post38337627
What can I do to solve. Thank you
Click to expand...
Click to collapse
You can start by following the instructions given to you in that thread and directing all non-development related questions to the Q&A forum.
Sent from my KFJWI using Tapatalk 2

I just flashed back to this until the CM built has working sound. I'm not sure if this is already known, but if you flash a ICS based gapps package on top of this you have all the gapps =D

vln004 said:
I just flashed back to this until the CM built has working sound. I'm not sure if this is already known, but if you flash a ICS based gapps package on top of this you have all the gapps =D
Click to expand...
Click to collapse
Seriously? And everything works? I already have everything installed but if this is true that would make going back and forth between cm and Amazon really easy

wojo797 said:
Seriously? And everything works? I already have everything installed but if this is true that would make going back and forth between cm and Amazon really easy
Click to expand...
Click to collapse
Only had about 30 minutes to play with it before going to bed. But everything that i tested worked fine. Google play installs apps fine, youtube works as expected, installed a couple other apps and everything works as it should.

vln004 said:
Only had about 30 minutes to play with it before going to bed. But everything that i tested worked fine. Google play installs apps fine, youtube works as expected, installed a couple other apps and everything works as it should.
Click to expand...
Click to collapse
So I bought a demo unit Kindle Fire HD 8.9 (you know, the ones in the store with just a demo OS installed) and I should have it by next week. When I root it I can install this ROM and everything works (sound, camera, HDMI etc.) just like a full one bought in the store?

OP updated for a new 8.3.0 stock ROM .zip file to flash in TWRP.
It includes the new kernel + stock ROM, but NOT the wankit update for LTE users.

Hashcode said:
OP updated for a new 8.3.0 stock ROM .zip file to flash in TWRP.
It includes the new kernel + stock ROM, but NOT the wankit update for LTE users.
Click to expand...
Click to collapse
Just install? Or wipe cache and dalvik? Thanks for doing all this work.. Very much appreciated

If you are on stock, then you can just install this over the top of 8.1.4. If you've been playtesting CM10.1 you will need to wipe data/cache.

Re: [ROM-STOCK] Amazon OS 8.3.0 (Flash .zip for TWRP) [04/02 - Version 8.3.0]
Hi,
Is it possible install flash plugin to use with DolphinHD? I ask this because i use Kindle to see NBA games from Game Time.
Sent from my Incredible S using xda premium

Running stock rooted so I simply installed this update over top..no cache or dalvik wipe. After reboot the play store kept force closing.went back into recovery and wiped cache and dalvik. Play store no longer force closing.maybe just isolated to me but I would wipe caches

wojo797 said:
Running stock rooted so I simply installed this update over top..no cache or dalvik wipe. After reboot the play store kept force closing.went back into recovery and wiped cache and dalvik. Play store no longer force closing.maybe just isolated to me but I would wipe caches
Click to expand...
Click to collapse
Good point. Adding wipe cache to the OP.

Wow, this is great, with 8.3.0!!
But I never succeeded downloading the file as everytime it stopped at 30%-70%. Anyone can help?

Finally I managed to download it through a proxy.

I am new to rooting and tablets. I cannot understand how to load "flash in TWRP". I try running adb commands in CMD but it says it is a unrecognized command. Can someone make this idiot proof? I am doing something wrong and I don't want to brick my kindle hd 8.9

[ROM] [2016.12.07] XT1096 5.x stock based rom

Updated 2016.12.07 - Post updated with current files, see end of post for links to helpful posts.
Updated 2016.04.14 - Post updated with current files.
Updated 2016.01.23 - This post has been rewritten for people who have unlocked their Verizon XT1096 through the Motorola unlock page. It is presumed that you have fastboot installed and working and that you have at least a 5.x version of Android on your phone. (Android version in Settings -> About phone) If not and you're still on 4.4.4, the information hidden at the bottom of this post will help you upgrade.
This ROM is based on the Stock ROM and has SuperSU v2.65, Xposed v80, Xposed Installer, BusyBox v1.24.1-Stericson, sqlite3, zip, aapt, and DNS support for Busybox apps pre-installed. System is mounted R/W via su.d script, addon.d scripts are supported, the Verizon part of the boot animation is removed, tethering is enabled. The following obsolete files are deleted from the stock image:
Avatar
AvatarPermissionsApp
Bug2GoStub
com.customermobile.preload.vzw
CQATest
DemoMode
fswriter
GuideMe
LMIRescue
LMIRescueSecurity
LocalWipePolicyManager
MediaShortcuts
MotoCare
MotoCareInt
VerizonSSOEngine
VMobileSecurity
VzwAVS
vznavigator
In addition to TWRP mentioned next, you'll need a few files on hand to complete the process:
XT1096-23.32-25-5-5-Firmware.zip - TWRP zip to update firmware.
xt1096-5.1-23.32-25-5-5-Mod.zip- The factory based modified ROM
A GApps package, this is possibly the most confusing part for new ROM flashers and will be discussed below.
xt1096-5.1-debloat.zip - Optional, removes some Verizon bloat, see list below
xt1096-5.1-debloat-keepconnect.zip - Same as above but retains Moto Connect and some files need for the Moto Gallery app.
If you want root, flash SuperSU from this thread: SuperSU Release (As of the time of this posting the direct link to the download is here: SuperSU-v2.78-201609011115.zip
If you want Xposed, flash xposed from this thread: Xposed thread you want the version for SDK22 for ARM. (As of the time of this posting, the direct link to the download is here: xposed-v87-sdk22-arm.zip
Here is the list of apps deleted by the debloat zip, the keepconnect version does not remove Motorola Connect:
ECID_VZW_Victara (Verizon Caller ID $)
GoogleHindiIME
GooglePinyinIME
iWnnIME
KoreanIME
com.gotv.nflgamecenter.us.lite
VZMessages
BodyGuardApp (Alerts)
Verizon Cloud
Verizon CloudSetup
Entitlement
MotorolaConnect
MyVerizon
VVM3 (Visual Voice Mail $)
GApps are Google Applications, the stock ROM originally had many of the GApps but they are outdated. Note: Due to changes in the Open GApps package, the minimum level that will work correctly with this ROM is the Micro package, the nano and pico packages probably won't work. Like other custom ROM's, if you want to use any Google services and/or the Play Store, you must install a GApps package. One source is here: Open GApps with an XDA discussion group here: XDA Open GApps When selecting your GApps package, choose ARM for the platform and 5.1 for the version of Android. Then any of the variants will work to give you access to the Google services. The XT1096 has plenty of room and resources for the larger packages. The "Full" variant is probably most like what the phone came with as stock. Be advised that the "Stock" and "Super" variants, by default, will replace the excellent Motorola camera app with the Google camera app. You can avoid this by creating a gapps-config.txt file kept in the same place as the installer zip. In addition, all but the "Nano" and "Pico" variants will put Google Photos in place of the stock Gallery app with it's Highlight Reel tool. Creating a gapps-config.txt file is described on the pages linked above. To avoid losing the Moto Camera and Gallery apps, you might have a gapps-config.txt file like this:
Code:
+Gallery
CameraGoogle
Collect all the needed zip files and place them all in your download folder on the phone or on a USB-OTG drive.
Install TWRP. The TWRP app from the Play Store doesn't always work reliably, install TWRP using fastboot. The latest official version is 2.8.7.1 and you can download it from here: https://dl.twrp.me/victara/. (Note: Some people have reported problems with official versions of TWRP getting stuck at the splash screen. See post 1013 for alternate versions of TWRP that may work for you.) Put the .img file in the same place that you run fastboot from, put the phone in bootloader/fastboot mode and run the following command (replacing the file name at the end with the file you want to flash):
Code:
fastboot flash recovery twrp-2.8.7.1-victara.img
The process only takes a couple seconds, ignore any errors about size mismatch. Use the volume down key to highlight recovery, then press the volume up key to select. The phone should reboot into TWRP. Make a backup, preferably to a USB-OTG drive before you do anything else. If something goes wrong with the next steps, you'll be able to restore the backup and be back to where you started.
In TWRP select WIPE, then Advanced Wipe. Select, Data, System, Cache and then slide the slider to begin the process. This will wipe the phone except for your pictures and other things on the "SDCARD" or internal storage. (The phone will enter setup when booting the first time after flashing the ROM. You might be able to get away with not doing the wipe, most people will have problems if the wipe isn't done due to the Google apps being updated from the stock installed versions.)
Return to the Home menu in TWRP, select install, then add zip. Select xt1096-23.32-25-5-2_gpt.zip. Tap add zip again and select xt1096-23.32-25-5-2_Firmware.zip. Tap add zip again and select xt1096-5.1-23.32-25-5-2_1.zip. These 3 must be first. Tap add zip again and select the GApps zip file that you selected. If you are debloating, tap add zip again and select that zip file. If you want the CM AudioFX, tap add zip again and select that zip (you can actually do this step in the future by itself if you want.) At this point you have at least 4 zips and possibly 6 selected; slide the slider to begin the flashing process. This will take a while, don't interrupt it. If the screen turns off, use the power button to turn it back on. When done, use the Reboot System button to restart the phone. The phone will reboot, it will show the logo and then the boot animation. It will take 4-5 minutes during which time the boot animation will appear to be stuck, don't panic, this is normal and will only happen the first time after a clean install. The phone should start an optimizing apps process and when that completes, you will see the first set up screen.
Enjoy your rooted stock ROM!
See post 2 for zips to add Viper4Android, restore Exchange2, or remove Xposed and links to other useful things.
See post 886 for flashable zips to change the boot logo and boot animation to a Marshmallow style.
See post 1009 for more info about the current files listed here.
See post 1057 for more info about the April 2016 security update.
See post 1108 for more info about the August/November security update and instructions to flash your phone to stock.
The info below is about mofo and previous versions of this rom. Most people won't need to look at it!
Updated 2015.09.16 - Jump to post 781 for the TWRP Stagefright patch update!
Updated 2015.09.12 - Jump to post 783 for the MOFO Stagefright patch update!
Below is the original information for using Mofo to flash 5.0 images, upgrade to 5.1 and other Mofo info. If you have used Sunshine to unlock your bootloader, you can still flash any of the old images using fastboot. Now, this thread will have images for flashing with both mofo and TWRP..
I've created a base XT1096 v5.1 stock based image that is setup like a custom ROM. This image has tether enabled in build.prop, Busybox and SQLite3 are installed. The ROM has been rooted with SuperSU. Support for DNS in Busybox is included. Certain apps that are potentially spyware or are outdated have been removed. Even more stock apps can be removed via TWRP with the xt1096-5.1-debloat.zip file available in post 2. As time permits I'll create some more TWRP zip files to add Viper4Android, the stagefright patches when released, etc.
Important: This ROM, like other custom ROMs, does not included GApps (like PlayStore, etc.) Most everyone will want to download a GApps package and include it in the list of zips to install in TWRP. There are several GApps packages out there, TK GApps are very flexible and can be configured to install just the bare minimum or the full set of Google Apps: TK GApps 5.1 If using Xposed, you will need to reinstall the Xposed Installer app from here: XposedInstaller_3.0_alpha4.apk; you will then need to open the Xposed Installer and enable your installed modules before they will function.
The TWRP flashable image is available here: xt1096-5.1-stock-20150820.zip
If you do a clean flash (wipe data), it takes 4-5 minutes for the phone to start the first time.
See some useful links and additional TWRP zips in the next post!
Here is a nice guide for upgrading from the Mofo to the unlocked bootloader with Sunshine, installing TWRP and using the TWRP compatible zips by @betarepeating:
Starting with 5.1 Mofo Rooted image provided in this thread:
First install/run sunshine. This process was painless and easy and I'm not going to waste my time typing instructions here.
Nuke the "Warning Message" boot logo
Instructions | Download
Just opened that folder and typed:
Code:
fastboot flash logo logo.bin
Installing TWRP
Instructions | Download
then do
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
Now when you boot to recovery you will see TWRP!
Installing Apps
===============
Boot into recovery (TWRP)
Made backups of /system and /boot (didnt backup /data because I don't have an OTG cable or room on my internal storage - but you should!)
Copied backups to my PC
Copied the following to the TWRP folder on my phone (could put them anywhere doesnt matter):
xt1096-5.1-stock-20150820.zip
xt1096-5.1-debloat.zip
xt1096-5.1-CM-Stuff.zip
tk_gapps-modular-mini-5.1.1-20150816-signed.zip
xposed-v71-sdk22-arm-by-romracer-20150816.zip
Links to download are in the second post of this thread
Went into Wipe > Advanced Wipe and checked system and dvalik-cache and wiped them.
Installed all the zips from above in the listed order (all that matters is the xt1096-5.1-stock-20150820.zip goes first)
Rebooted
Phone sat and optimized for a long time
While waiting I downloaded:
XposedInstaller
AdAway
CF.Lumen
Dropped the APKs onto my phone once it was booted and ran them from file explorer.
Done.
=================================================
Here is the original info and links for Mofo 5.0 images:
The mofo image file with Xposed v65 baked in is listed below. It is based on the image posted by btdownloads7. It includes root, tether, BusyBox and SQLite3 while adding Xposed v65.
You need to flash an image with root from here: http://forum.xda-developers.com/showpost.php?p=60537982&postcount=1 to be able to follow the instructions below.
You also need to install the alpha Xposed apk from here: http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440 Download the apk to your phone, find it with your phone file manager and click on it to install. Do not try to install the framework from within the Xposed installer.
While in your root file manager, navigate to /data/dalvik-cache and delete both the "arm" and "profiles" folders. (This is needed one time due to a glitch in the alpha Xposed for Lollipop.) You must do this!
Connect your phone to your pc and issue the "adb reboot-bootloader" command to get into fastboot mode (or use the proper key combination on the phone to enter fastboot mode.)
Flash the image file with mofo as normal.
After mofo completes its work, enter "fastboot erase cache" from your pc to flush the system cache.
Once done, reboot the phone. The boot animation will end and seem to freeze for a minute or two, then it will start the upgrading/optimizing apps process. Once your phone is booted up, open the Xposed installer from the app drawer, install a module (like Gravity Box for LP) and enjoy!
Note: If you get system memory full errors after the reboot, you didn't delete the folders in /data/dalvik-cache as noted above; with luck you will be able to delete them in between error messages and reboot. Otherwise, you'll need to flash an image without Xposed and start over.
XT1096_5.0-tether-root-bb-sqlite3-XposedV65.img.7z - XT1096 image for use with mofo. Includes HDR fix, tether, root, busybox, sqlite3 and Xposed v65
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440 - Link to Xposed Installer Alpha 4 needed for Xposed v65
XT1096_5.0-tether-root-bb-sqlite3-XposedV65-DeBloat.img.7z - Image with bloat removed, see this post for details: Post 169
XT1096_5.0-tether-root-bb-sqlite3-XposedV65-DeBloat-AdAway.img.7z - Image for AdAway users with symlink for hosts file, see this posrt for details: Post 188
Here is the info for 5.1 Mofo Images, updating, patching, etc.:
Thanks to @JulesJam and @Slack3r we have Android 5.1 for the XT1096 with mofo! Below are links to the 5.1 mofo image and patch files.
These images have tether enabled, root, Sqlite3, BusyBox, Xposed, CF.lumen and support for AirAudio, AdAway, iOS Emoji fonts and Viper4Android with the latest TK Gapps installed. Here are the main files:
5.1bins.7z - Kernel, modem and other 5.1 update files
xt1096-5.1-v3.1g-pkg.7z - Base image
You should save the base 5.1 image file. When there are updates in the future, patch files will be used to work with this base image.
@JulesJam has written an excellent guide for new users (and those who might need a refresher) here: Mofo Noob Guide
These images are for Android 5.1. If you are still running 5.0, here are instructions for upgrading to 5.1:
The following presumes that you already are running a rooted mofo version of Android 5.0. You shouldn't loose your data by making this upgrade, however, it is always wise to backup anything on your device that isn't also stored somewhere else. As usual, I can't be responsible if your phone malfunctions in some way. I have installed these files following the instructions below without any difficulty.
First, download the 5.1 base file and the 5.1 base image with patches.
Do not remove your SIM card, leave it installed.
Using your root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache - YOU MUST DO THIS! Then reboot into bootloader mode.
Extract the files from the 5.1bins.7z archive and then run these commands:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Then, immediately use mofo to flash the 5.1 image. Reboot your phone and enjoy Android 5.1!
The base image can be patched to enable/disable features. The patch files are listed below and instructions on how to apply them are here:
First, you need to have the Xdelta3 program:
xdelta3 for Windows x86
xdelta3 for Windows 64-bit
xdelta3 for Linux
For Linux, extract the files from the archive, enter the folder with the extracted files and run the following command to install xdelta3 to your system:
Code:
./configure && make && make install
For windows extract the xdelta3-3.0.9-x86.exe file from the zip and rename it to xdelta3.exe.
Put the patch file(s), the xdelta3 program and the base image mofo file into the folder where your mofo program file is.
Open a command window in this folder.
Enter the "dir" command (Without quotes. You should see your files listed including xdelta3, mofo, etc.)
For both Windows and Linux users enter the following cmd while in your mofo directory:
Code:
xdelta3 -d -s base_image_file patch_file
In other words, to patch the base image to add Xposed, your command would look like this:
Code:
xdelta3 -d -s xt1096-5.1-mofo-base-v2.img base-to-base_xp.patch
The patched image will be created and you can then flash that like normal.
Make sure the newly created image is the exact same size as the original image. If a patch for another image is applied to the wrong image, there will be an error message displayed. Even if there is an error, a patch file may be created but it will usually not be the same size as the original.
The patch files for the base image are included in the image archive
In the archive are patches to do the following:
3.1{x}--3.1{x}-de - Removes some apps from v3.1f image
3.1{x}--3.1{x}-cf-de - Removes some apps from v3.1f image, keeps CF.lumen
3.1{x]--3.1{x}-v4a - Adds Viper4Android to the image
3.1{x]--3.1{x}-v4a -cf-cmt-de - Adds Viper4Android to the image with some apps removed
The apps removed in the Debloat patch(es) are listed here:
Code:
3c_main (Moto Apps Manager)
3c_checkin (Moto Apps Connector)
3c_notification (Moto Apps Notifications)
3c_ota (Moto Apps Data Manager)
BodyGuardApp (Moto Alerts)
Books (Google Books)
CF.lumen
Chrome (Google Chrome)
Cloud (Verizon cloud storage)
Drive (Google Drive)
Ears (Google Sound Search)
ECID_VZW_Victara (Verizon CallerID pay service)
EditorsDocs (Google Docs)
EditorsSheets (Google Sheets)
EditorsSlides (Google Slides)
FaceLock (Face Unlock)
Google Earth (Google Earth)
Google HindiIME (Hindi keyboard)
Google PinyinIME (Pinyin keyboard)
Google PlayGames (Playgames (not playstore))
Hangouts (Google Hangouts)
Inbox (Google Inbox)
iWnnIME (iWnn keyboard)
Keep (Google Keep)
KoreanIME (Korean keyboard)
Maps (Google Maps)
Messenger (Not Messaging)
MotorolaConnect (Connect to watches or your PC)
Music2 (Google Play Music)
MyVerizon (My Verizon Mobile)
News & Weather (News & Weather widget)
Newsstand (Google Magazines)
Nflgamecenter (NFL App)
PlusOne (Google+)
Quickoffice (Google Quickoffice)
Talkback (Google Talkback)
Translate (Google Translate)
Trebuchet (CM Launcher)
Videos (Google Play Movies & TV)
VVM3 (Verizon Visual Voicemail)
VZMessages (Verizon Messages)
VzwEntitlementService (Not needed with tether in build.prop)
Wallet (Google Wallet)
YouTube (Google YouTube)
Tips:
The image includes AdAway support. If you want to use AdAway, go into the AdAway settings and set the location of the hosts file to /data/data/hosts
To change the bootup animation, place your desired bootanimation.zip file (not the installer zip) into /data/local/moodle and set the permissions to rwx rwx rwx (chmod 777) and owner:group u0_a40:u0_a40
To use iOS Emojis, follow these instructions:
Code:
If iOS Emojis are desired,
Copy /system/fonts/NotoColorEmoji.ttf.iOS to
/data/data/NotoColorEmoji.ttf
To restore the stock font,
Copy /system/fonts/NotoColorEmoji.ttf.stock to
/data/data/NotoColorEmoji.ttf
Or, just delete the file and the system will copy the
stock one into place at the next boot.
Changelog:
Code:
xt1096-5.1-v3.1f - 2015.08.06
- Major improvement to updated /system app cleanup
of apps in /data. Now takes 2 seconds instead of 90
Cleanup happens seamlessly, no reboot required
- Add CF.lumen v3.00, will add to debloat list if any requests
- Add CM's AudioFX, remove moto Audio Effects
- Add CM's Trebuchet Launcher, not in debloated image
On first boot of image with Trebuchet, you will be prompted to retain
the Google Now Launcher, select Always to keep the current launcher.
Launcher can be changed in Settings->Home
- Add patch to include Viper4Android v2.3.4.0 in image
Patch disables Selinux enforcing to allow V4A to work
Patch removes AudioFX
- Update Xposed Framework to v69
Minor changes don't require clearing dalvik-cache
- Updated Chrome to v44.0.2403.133
- Updated Docs to v1.4.292.15.35
- Updated Drive to v2.3.283.23.35
- Updated Moto App to v3.0.45
- Updated VZ Message+ to v5.6.5
- Patches now included with image & version update patch archive:
3.1e--3.1f.patch - Version update patch
3.1f--3.1f-v4a.patch - Patch to add Viper4Android
3.1f--3.1f-de.patch - Patch to debloat image
Requests for additional patch variations will be considered
xt1096-5.1-v3.1e - 2015.08.01
- Fixed incorrect permissions on Inbox causing fc
- Update Xposed Framework to v68
- Update Google Play Services to v7.8.95
- Update Chrome to v44.0.2403.128
- Update Connect to v2.06.16-pc-249
- Update My Verizon Mobile to v10.0.751
- Update Google Play Music to v6.0.195S.2109908
- Update Google+ to v6.0.0.99065591
- Update Maps to v9.12.1
- Update NFL Mobile to v12.0.28
- Update Photos to v1.2.1.99143001
- Update Translate to v4.0.0.RC08.99220384
- Updated debloat list
xt1096-5.1-v3.1d - 2015.07.29
- Fix problem with Connect force closing.
- Add Google Camera in addition to stock Moto Camera
xt1096-5.1-v3.1c - 2015.07.28
- Made change in updated play store app cleanup to account for
unexpected data in /data/system/packages.xml possibly causing
system failure to set correct processor parameters. Possible
infinite loop corrected.
- Added Google Inbox, rolled in updated versions of Google Photos,
Verizon Cloud, Message+, MyVerizon.
- Add Google Inbox to debloat list.
xt1096-5.1-v3.1b - 2015.07.25
- Fixed problem where apps updated by play store could be incorrectly
reverted to /system version which was actually older.
- Rolled into /system latest versions of: Google Keep, Maps, YouTube, Wallet.
- Restore stock Email app that was accidentally removed.
xt1096-5.1-v3.1a - 2015.07.21
- Fixed some directory permissions.
- Restored stock mms app to image.
- Rolled updated versions of apps into system:
NFL Game Center
Google Docs
Google Slides
Verizon Message+
- Added functionality for system to automatically remove
obsolete copies of apps in /data/app when new image has
newer or equal version of those apps (same as custom Roms.)
Release 5 - 2015.07.20
- Base file name: xt1096-5.1-v3.1.img
- Exchange is enabled in Gmail, old stock email was removed.
- Add PA-Gapps Stock package 20150717 - updates all Google
apps to versions available as of the date noted. Thanks
to TKruzze & osm0sis @ xda for their work.
- Updated Motorola and Verizon apps are integrated into image.
- Removed deprecated Spotlight player
- Installed AdAway and Xposed Installer into /system
- Corrected permissions on auto created /data/data/hosts file
- Install Air Audio in base image. (Future MMU will give option
to disable/enable this as well as other apps.)
- Updated Xposed to v67 (nothing major changed from v65)
- Made iOS Emoji support permanent by creating a symlink.
The Emojis will not be available until the second time
booting with this image.
If iOS Emojis are desired,
Copy /system/fonts/NotoColorEmoji.ttf.iOS to
/data/data/NotoColorEmoji.ttf
To restore the stock font,
Copy /system/fonts/NotoColorEmoji.ttf.stock to
/data/data/NotoColorEmoji.ttf
Or, just delete the file and the system will copy the
stock one into place at the next boot.
Release 4 - 2015.07.15
- Base file name: xt1096-5.1-v3.0.img
- Fix security context and ownership on BusyBox symlinks
- Add symlink for /system/etc/resolv.conf to /data/data/resolv.conf
Does not require user action, allows BusyBox DNS resolution by
creation of /data/data/resolv.conf file. Make one like the
following if you want to use Google's nameservers for DNS resolution
in adb shell programs like nslookup, traceroute, etc. Remember.
the adb shell nslookup, etc. only work after you su to root.
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 4.4.4.4
- Add Better Battery Stats XDA version as a system app
- Add /system/etc/mofobuild.prop with name of image installed
- Alpha version of Mofo Utility
Release 3 - 2015.07.10
- Base file name: xt1096_5.1_mofo-base-v2.img
- Fix broken BusyBox installation
Release 2 - 2015.07.09
- Base file name: xt1096_5.1_mofo-base.img
- Correct security context on /system/etc/install-recovery.sh to value
in original ROM instead of value as (not) set by SuperSU installer
causing script to not run at boot.
- Make AdAway support the default. Added functionality to create
/data/data/hosts file on boot, if it doesn't exist, for users who
don't wish to use AdAway ensuring there will be no problems in
resolving localhost for apps/processes that might use that.
- Shorten and simplify names of base and patch files.
- Upgrade SuperSU from v2.46 to v2.49
Initial Release - 2015.07.05
- Base file name: XT1096_5.1-tether-root-bb-sqlite3.img
XDA:DevDB Information
Mofo XT1096 5.x Images, ROM for the Moto X 2014
Contributors
mikeoswego
ROM OS Version: 5.1.x Lollipop
Based On: Stock
Version Information
Status: No Longer Updated
Created 2015-05-04
Last Updated 2017-06-28

Updated 2016.01.21 - xt1096-5.1 & 23.32-25-5x TWRP based zips
The zips attached below are available for use with TWRP on the xt1096-5.1 & 23.32-25-5x images:
xt1096-5.1-Viper4Android.zip - Adds Viper4Android (disables selinux security and removes Audio Effects app)
xt1096-5.1-Mail-Exch2.zip - Restores stock email & exchange2, included in xt1096-5.1-23.32-25-5_3. Flash after flashing GApps
xt1096-5.1-Rem-Xposed.zip - Removes Xposed from ROM, use only after ROM has been started and setup is complete
See post 886 for a flashable alternate boot logo and boot animation.
Useful Links:
CF.lumen xda thread - Or search the Playstore fo CF.lumen
BetterBatteryStats xda thread - Get the BetterBatteryStats installer here
TWRP for Motorola Moto X 2014 - TWRP info page for MotoX 2014
TWRP for victara - TWRP download page
Open GApps for Android 5.1 - Google Apps installer
AdAway xda thread - Get AdAway from here

Was first!

Are the steps the same to flash the updated image with the boot animation or can I just flash and wipe cache. I literally just booted the previous Xposed image after installing GravityBox and a few other modules and this is the first thing I see lol.
Thanks so much for the image though, it took a while to boot and start apps but it hasn't given me any issues otherwise yet.

fakieskr8333 said:
Are the steps the same to flash the updated image with the boot animation or can I just flash and wipe cache. I literally just booted the previous Xposed image after installing GravityBox and a few other modules and this is the first thing I see lol.
Click to expand...
Click to collapse
If you are already running the previous image with Xposed, you can just flash the new one in the normal way with mofo, no special steps needed.

Nvm

That's some animation! Sometimes I reboot just to watch it.

I don't seem to have the new animation....everything else is working fine though..

Empty \data folder
I didn't seem to have anything in my \data folder so I proceeded with flashing the image. Now, it appears I have the memory issue. Also, the apk for the xposed intaller seems to be for Alpha 2 - does that matter?
Thanks for everything!

Updated without any issues at all. Now time to get crazy with modules! Thanks again!

dudicle said:
I didn't seem to have anything in my \data folder so I proceeded with flashing the image. Now, it appears I have the memory issue. Also, the apk for the xposed intaller seems to be for Alpha 2 - does that matter?
Thanks for everything!
Click to expand...
Click to collapse
Hmmm. Found 'em! Wonder if I needed root to see those files in the first place. Since this was my first flash away from unrooted stock, I didn't have root yet. Anyhow, deleted them and reflashing the image. So far so good...

I can't seem to be able to install the Xposed Framework after I flashed this image. Is there something I'm missing??

dudicle said:
Hmmm. Found 'em! Wonder if I needed root to see those files in the first place. Since this was my first flash away from unrooted stock, I didn't have root yet. Anyhow, deleted them and reflashing the image. So far so good...
Click to expand...
Click to collapse
Right you have to have root to be able to delete the dalvik-cache files. I'll edit the first post.

Aroch925 said:
I can't seem to be able to install the Xposed Framework after I flashed this image. Is there something I'm missing??
Click to expand...
Click to collapse
The framework is already installed in the image. You can't install the framework from the Xposed installer for two reasons. First, this root doesn't open up /system for writing (which Xposed normally needs for installation), and two, this alpha version of Xposed for Lollipop doesn't install the framework on its own anyway, it has to be flashed from recovery (but we don't have a recovery yet so it has to be baked in.) Hope that makes it more clear!

mikeoswego said:
The framework is already installed in the image. You can't install the framework from the Xposed installer for two reasons. First, this root doesn't open up /system for writing (which Xposed normally needs for installation), and two, this alpha version of Xposed for Lollipop doesn't install the framework on its own anyway, it has to be flashed from recovery (but we don't have a recovery yet so it has to be baked in.) Hope that makes it more clear!
Click to expand...
Click to collapse
So does that mean I can't actually use Xposed yet?

Aroch925 said:
So does that mean I can't actually use Xposed yet?
Click to expand...
Click to collapse
It means you just go to the download section and choose the modules you want to install. The installer can't install the framework but it does install the modules you want to use. :good:

tjohnstone3 said:
I don't seem to have the new animation....everything else is working fine though..
Click to expand...
Click to collapse
The new animation is quite different so you would know if you had it. I had the previous version of this image with Xposed linked in the OP for a few minutes after first posting it. The file you dl'd should have been named XT1096_5.0-tether-root-bb-sqlite3-Xposed.img.rar. If not, dl it again from the link in the OP.

dudicle said:
Also, the apk for the xposed intaller seems to be for Alpha 2 - does that matter?
Click to expand...
Click to collapse
The Xposed framework is alpha 4 but the installer is only alpha 2 because no changes have been needed in that part.

What is the fix for low memory. I flashed this img with mofo but I cant seem to resolve the low memory issue? Thanks
---------- Post added at 12:46 AM ---------- Previous post was at 12:39 AM ----------
Jah Ruggz said:
What is the fix for low memory. I flashed this img with mofo but I cant seem to resolve the low memory issue? Thanks
Click to expand...
Click to collapse
Disregard..I did not realize I had a recovery that I could wipe cache from. I will try that and see if it works.

Thanks for the image- love it, well documented tutorial helped heaps. Do you plan on updating this thread with new updates or by chance taking feature requests?
Cheers - Harrison

[GUIDE] OOS v4.0.3 ---> FLASH & ROOT STOCK -OR- CUSTOM ROM WITH EASE & CORRECTLY

[GUIDE] OOS v4.0.3 ---> FLASH & ROOT STOCK -OR- CUSTOM ROM WITH EASE & CORRECTLY
If you think that I need to add more information to this guide, please post your request. I'm not able to guess what you want from me to add to this guide.
Thank you!
INTRODUCTION:
This guide is mainly for users who tried flashing OxygenOS v4.x.x the easy and short way (like in post #9 in this thread), which had issues in the process.
I covered the most common issues with flashing OOS v4.x.x in this guide. However, you can use this guide to flash OxygenOS (latest Stable and Beta versions)
and root them OR flash your custom ROM. Just follow the instructions.
Now, you ask “why I decided to write this guide?”. Well here’s my story:
I had FreedomOS v1.7 with Google apps installed (including Dialer and Contacts from OpenGApps), encrypted, official twrp (v3.0.2-1), Xposed (v3.1.1), framework (v87),
AdAway v3.2, YouTube AdAway and SuperSU v2.79 (stable). Also, stock kernel, no Dolby ATMOS or A.R.I.S.E apps.
So, when OOS v4.0 came out, I waited for FreedomOS v2.0 to come out too. Once it did, I downloaded the ROM, OpenGApps, modified twrp .28 and started
the flashing process (I backed up my data first).
First, I flashed twrp .28 (had no problems booting into it), and clean flashed FOS v2.0. I selected “Yes” in “Pin/Pattern backup in data partition”, so I wouldn’t have issues with encryption. I selected the regular apps (for OOS to work properly) and installed the OS.
When it was done, I rebooted the device to the OS. I was confused with the new “dm-verity” message popping from nowhere, but the OS booted successfully.
When I rebooted to the twrp (to install OpenGApps), it asked for a password. I couldn’t enter the right password, because it wouldn’t accept any and it blocked
my access to my internal storage.
I started panicking, looking for answers, and I was afraid that I bricked my phone. However, after some research, I calmed down. I realized that my bootloader was still working and could roll back to OOS v3.2.8 (with stock recovery), which I did. From there I flashed FOS v1.7 and waited for more information about the new Nougat update for OnePlus 3.
Now, I’m using Stock OygenOS v4.0.3 with Stock Kernel (see FAQ #16) and so far, no issues (no dm-verity message or password upon entering modified twrp).
I tried to repeat the dm-verity issue and fixed it (see FAQ #6). I was so frustrated that no one posted a proper guide on how to fix these issues, or they were too advanced. I didn’t want to mess around with the core of the system too much. Therefore, I decided to post a simple-to-follow guide.
DISCLAIMER & IMPORTANT:
I am not responsible for any damages done by this guide. You are tinkering with your phone and held responsible for that. This is not an advanced guide. Therefore, I will refer you to the advanced guides when needed. Furthermore, this guide is based on the issues that I and other users encountered while
flashing OOS v4.x.x ------------>***BACK UP PERSONAL DATA BEFORE PROCEEDING ANY FURTHER***
This guide is intended for owners of OnePlus 3. But, after some poking in OnePlus 3T forums, you can use this guide. The only differences the OnePlus 3T
have are a newer processor, newer front camera and a different color from OnePlus 3. Make sure to use the appropriate tools (Stock recovery, TWRP,
OxygenOS v4.0.3, etc.) for OnePlus 3T. Again, I will not be responsible for any damages caused by this guide.
Please follow this guide to get rid of: dm-verity, encrypted twrp, encrypt or decrypt your device (as OnePlus 3 comes encrypted by default), change your file system from EXT4 to F2FS (vice versa as well). Also, flash a Marshmallow or Nougat Stock OOS (Stable or Beta versions), root them OR unroot your device, OR flash a custom ROM.
As far as I know, tested and read in forums, Android v6.0.1 (OxygenOS v3.x.x) supports only EXT4 file system, and Android v7.0 (OxygenOS v4.x.x) supports both EXT4 and F2FS file systems. However, F2FS is recommended for Android v7.0 (OxygenOS v4.x.x). When you perform, a full factory reset in OxygenOS v4.x.x, the file system changes from EXT4 to F2FS. ONLY “Data (userdata)” is affected by this. If you want to go back to Marshmallow, OxygenOS v3.x.x will change your file system from F2FS to EXT4 when you sideload it.
OxygenOS v4.0.3 still comes with some issues, bugs, and some rooting services are not fully supported yet (i.e. Xposed for Nougat). Luckily, OnePlus released kernel sources of Nougat, and we need to wait a little longer for Xposed and other rooting services to be supported. Therefore, I advise staying away from it,
for a little while, until those issues are fixed, and new ones don’t pop up. Also, until rooting apps are fully supported. Follow OnePlus community forums and
XDA forums for updates, troubleshooting, and solutions for your issues. MAKE SURE TO BACK UP YOUR PERSONAL DATA, time to time.
Before posting questions or issues or requests, check FAQ and posts in this thread. Thank You!
WHAT WILL YOU NEED?
You don't need to download everything in this section, only what you prefer to roll with.
ADB drivers installed on your computer (I have version 1.0.32 installed)
Unlocked bootloader (if you haven't done it yet, follow this guide: https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733)
DiskInfo app from the Play Store:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en
OxygenOS v3.2.8 OTA:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
OxygenOS v4.0.3 OTA:
https://www.androidfilehost.com/?fid=457095661767136075 OR http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
*** Download speeds might be slow. Be patient. ***
OxygenOs Beta 11 (Nougat):
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_11/
Stock Recovery v2.0 (compatible with OOS v3.x.x and OOS v4.x.x):
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Official TWRP (v3.0.2-1 for OxygenOS v3.x.x ; v3.0.3-0 for OxygenOs v4.x.x):
https://twrp.me/devices/oneplusthree.html
Unreleased Official TWRP v3.0.4-1 for Nougat (OxygenOS v4.x.x): *** Recommended for Nougat ***
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Unofficial TWRP (v3.0.3-0 for LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk:
https://forum.xda-developers.com/devdb/project/dl/?id=23082
SuperSu v2.79 (Stable):
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
OpenGApps (latest version):
http://opengapps.org/
Your desired custom ROM (I tested FreedomOS v1.7 and v2.3 and v2.4-CE, Experience ROM v10.1 [Stable and Beta 11], LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348 (FreedomOS - Stable [v1.7 - OOS v3.2.8 ; v2.3 - OOS v4.0.2])
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660 (FreedomOS - Beta [v2.4-CE - OOS Beta 11])
https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 (ExperienceOS - Stable and Beta 11 [v10.1])
https://forum.xda-developers.com/oneplus-3/development/rom-cyanogenmod-14-1-oneplus-3-t3496850 (LineageOS v14.1 - based on Andriod v7.1.1)
Code:
[I][SIZE="4"][B] * I'LL BE USING OOS v4.0.3, OFFICIAL UNRELEASED TWRP v3.0.4-1 AND FreedomOS
v2.3 AS AN EXAMPLE FOR THIS GUIDE. OTHER VERSIONS OF OOS AND TWRP
(PROVIDED) ARE APPLICABLE TO BE USED IN THE GUIDE (ONLY WHAT I TESTED).
[COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to Section C (FLASHING YOUR CUSTOM ROM)
-OR- Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
* If you do have dm-verity issue, file system change issue or password upon
entering TWRP, then continue to Section A (DM-VERITY).[/I][/COLOR]
[/B][/I][/SIZE]
A - PROCEDURE (DM-VERITY):
Code:
[I][SIZE="4"][CENTER][B]***** Check FAQ #5 before proceeding any further! *****[/B][/CENTER][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Now, for some people, it will ask a password. If not, continue to #9 and ignore #8. If it asks you to enter a password to decrypt your data, choose “Forgot password” and let it erase all your data and let it reboot. (MAKE SURE YOU BACKED UP YOUR PERSONAL DATA BEFOREHAND). Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
For those who doesn’t have to enter a password, press “English”. Press “Wipe data and cache” > “Erase everything (Music, pics, etc.)” > “This cannot be undone, continue?”. Moreover, let it wipe your data. Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
Code:
[CENTER][I][SIZE="4"][B]AT THIS POINT IF YOU HAD DM-VERITY ERROR/ISSUE, IT SHOULD BE FIXED AND GONE.
IF IT STILL APPEARS, DON'T WORRY IT WILL BE GONE AFTER #12
IT CAME BACK TO ME ONE MORE TIME, BUT I GOT IT FIXED.
***** Check FAQ #6 for more information *****[/B][/I][/SIZE][/CENTER]
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
Sign-in into your Google account and Download the “DiskInfo” app from the Play Store. Launch it, and press “Data (userdata)”. You should see:
- Encrypted: yes
- Decrypted block device: /dev/block/dm-1
- Mount point: /data
- File system: f2fs
A. If you see that it is in F2FS file system format, proceed to Section C (FLASHING YOUR CUSTOM ROM) OR Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
B. However, for some people (for some reason) it does not happen. You would see that your file system format (for userdata) is still on EXT4. Don’t be frustrated. A little bit more work needed to be done. Therefore, go to Section B (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE). It will solve that problem.
Code:
[I][SIZE="4"]* Your phone needs to be encrypted by default. It comes like that from the
manufacturer. See the following links:
1. [url]https://forums.oneplus.net/threads/encrypted-oneplus-3.452572/page-2[/url]
2. [url]http://www.androidpolice.com/2015/10/19/android-6-0-will-finally-require-manufacturers-to-enable-full-disk-encryption-by-default-on-new-devices/[/url]
3. [url]http://arstechnica.com/gadgets/2015/10/android-6-0-re-implements-mandatory-device-encryption-for-new-devices/[/url]
4. [url]https://source.android.com/security/encryption/[/url]
5. [url]http://www.howtogeek.com/141953/how-to-encrypt-your-android-phone-and-why-you-might-want-to/[/url]
6. [url]http://www.extremetech.com/mobile/216560-android-6-0-marshmallow-makes-full-disk-encryption-mandatory-for-most-new-devices[/url]
[/I][/SIZE]
B - PROCEDURE (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE):
Go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone (Encrypted)”. To make sure
you will need to do a factory reset.
Now go to: Settings > Backup & reset > Factory data reset. In “Optional” select “Erase internal storage” and press “RESET PHONE”. Confirm by pressing “ERASE EVERYTHING”.
It will reboot to Stock Recovery and wipe your data. When it’s done, it will reboot to the OS.
Again, download the “DiskInfo” app from the Play Store. Launch it, press “Data (userdata)”. Now you should see (it wouldn’t show “Encrypted: yes” at all):
- Mount point: /data
- File system: f2fs
Now go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone” and that you can press it. (DON’T ENCRYPT YOUR PHONE WITH THAT OPTION)
Now you successfully changed your file system to F2FS and decrypted your phone!
Code:
[I][SIZE="4"] * With Official TWRP v3.0.3-0 and modified TWRP v3.0.3-x v16 (from [user=3873953]@eng.stk[/user])
you are able to use the phone in encrypted mode, password request at
boot up and with Stock or rooted OOS v4.0.3 (Also, I tested it myself).
* Therefore, I will ask you to encrypt the phone back again. Proceed with
the following instructions:
[CENTER]***** Check FAQ #9 for more information *****[/CENTER][/I][/SIZE]
Reboot to Stock recovery v2.0
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash Oxygen OS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot your device. Now you back to being encrypted and “userdata” was changed successfully to F2FS file format on Stock Oxygen OS v4.0.3!
Go to Section C (FLASHING YOUR CUSTOM ROM) to properly flash your custom ROM. *** IT’S YOUR CHOICE ***
OR Go to Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) to remain in stock, root or unroot. *** IT’S YOUR CHOICE ***
C - PROCEDURE (FLASHING YOUR CUSTOM ROM):
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Code:
[I][SIZE="4"] * The “PASSWORD UPON ENTERING TWRP” should not be an issue any longer (only
if you followed the whole guide). It is caused by the TWRP being modified
(has an issue with encryption), not being officially released and fully
supported for the Nougat update. Versions “.28”, “.22” and “.19” are known
for that issue. Therefore, DO NOT USE THEM. If one of them works for
you, then use it at your own risk.
[CENTER]***** Check FAQ #9 for more information *****
[/CENTER][/I][/SIZE]
Press “Wipe” > “Advanced Wipe”, and select “Dalvik / ART Cache”, “System”, “Data” and “Cache”. Then swipe “Swipe to Wipe” for a clean flash.
After it’s done, go back to the main menu. Press “Install” and look for your desired custom ROM and press on the zip file to install it.
* I used FreedomOS v2.3 as an example and I didn't have any battery drain issues. (For more information, see FAQ #10)
D - PROCEDURE (FLASHING AND ROOTING STOCK OOS OR UNROOT):
Code:
[I][SIZE="4"][COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to #1.
* If you came from having dm-verity issue, file system change issue or
password upon entering TWRP (solved by using Procedure A and/or B),
then go to #12.
[/I][/COLOR][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
A. UNROOT - At this point, if you want to unroot and go back to completely stock, then use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
*** Most of the procedures for unrooting you have already done. Only locking bootloader is left. Good Luck! (YOU CAN STOP HERE)
B. ROOT - Continue to #13
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Connect you OnePlus 3 to your computer and copy the SuperSU v2.79 (Stable) to your device.
Pick up your phone. From the main menu, press “Install” and look for the SuperSU v2.79 (Stable zip file). Press it to install the root and after it's done, reboot to the OS.
That's it! Everything should be working properly
(except the bugs and issues on OxygenOS Nougat update).
ENJOY!​
CREDITS:
@NevaX1 --------------> For FreedomOS ROM
@jamal2367 -----------> For ExperienceOS ROM
@cpt.macp ------------> For in depth dm-verity remover guide
@Adithya R -----------> For in depth file system formating from EXT4 to F2FS guide
@eng.stk --------------> For modified TWRP that supports F2FS file format
@LELBOT --------------> For in depth dm-verity remover and file system formating from EXT4 to F2FS guides
@Naman Bhalla ------> For in depth bootloader unlocking, flashing TWRP, rooting, nandroid backup guide
@calvinistmac --------> For providing an unroot for OnePlus 3 guide
@Nishidh --------------> For providing OxygenOS v4.0.3 and Beta 11 OTA download links
@jcadduono ----------> For providing Official TWRP
@dianlujitao ----------> For providing Unofficial TWRP and LineageOS 14.1 ROM
@th3g1z ---------------> For providing an easy solution for Dm-verity issue
--------------------------> OnePlus Community and XDA forums for providing with issues, solutions and requests

FAQ (Q&A):​
Q: I can’t boot into TWRP! What to do?
A: Try using the previous TWRP or Stock Recovery.
[*]Q: I can’t boot into the OS! What to do?
A: Most likely some of the OS files are damaged or executed incorrectly. Try flashing or sideloading the OS again.
[*]Q: I can’t transfer files to my OP3 after wiping Internal storage OR Data folder/s in TWRP! What to do?
A: Don’t panic. Reboot to TWRP. It will create a folder so you can transfer files again.
[*]Q: I got an error sideloading the OS. Why is that?
A: Sometimes it occurs when the USB cable is wiggled side to side (the process stops at 92% with an error). Try again without touching
or moving the USB cable and the phone. Alternatively, it could be that USB debug is not enabled (not sure about that).
[*]Q: Is there an alternative way to get rid of dm-verity issue?
A: One simple command-line (enable) in bootloader can solve it. Check this post: https://forum.xda-developers.com/showpost.php?p=70698410&postcount=112
Otherwise, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685 This guide uses the .28 twrp
(NOT RECOMMENDED, BUT USE TWRP FROM @eng.stk) to use Stock Recovery, which I think is a bit more complex.
OR: https://forum.xda-developers.com/showpost.php?p=70415499&postcount=33
My guide uses only bootloader, Stock Recovery and TWRP from @eng.stk. Either way, they are the same guides.
[*]Q: The "dm-verity issue" came back after flashing OTA of stock OOS v4.0.2 via the TWRP! What to do?
A: Simply follow "Section A" instructions until #13. After you sideloaded the OTA it will be gone. It happened the second time when I tried to
flash the OTA via TWRP. Therefore, don't flash OTA of stock OOS v4.x.x via TWRPs. Only via Stock Recovery v2.0
I got it fixed only after sideloading the OTA via Stock Recovery v2.0 (Check post #29 for more information)
If it still doesn't work check this thread and read it thoroughly: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129
For more information, read FAQ #12
[*]Q: Your guide to change file format doesn’t work, OR I want to change “Cache” and “System” to F2FS as well. What to do?
A: Simply go to this link and at your own risk: https://forum.xda-developers.com/oneplus-one/general/guide-formatting-ext4-to-f2fs-losing-t3352116
Furthermore, @cpt.macp mentioed in post #34 in this thread that "/system and /cache need not to be f2fs . Oneplus Supports only /data
as f2fs and nothing else ."
[*]Q: I can’t log in into Snapchat after a clean flash of my desired custom ROM or after rooting my device. How to fix this?
A: I had the same issue, and it doesn’t occur to everybody. Before DIRTY flashing (wiping System, Cache and Dalvik only) the custom ROM
-OR- rooting your device, install Snapchat and log into it (on stock OOS v4.x.x). It might be a SuperSU (root) issue with Snapchat
(they enforced their security with rooted devices).
Also, OnePlus 3 has an issue with on-screen navigation bar. So, disable it in the "Buttons" menu until OnePlus fixes the glitch/bug.
[*]Q: Why did you choose TWRP v15 from @eng.stk -OR- Official TWRP v3.0.3-0 -OR- Unofficial TWRP v3.0.3-0?
A: They all work with the phone being encrypted, requesting a password on bootup to the OS and support F2FS file system.
.28 – had issues with encryption and F2FS file system, but for some users it works wonders.
.22 and .23 – I did not test, but I have read that .23 worked (decrypted).
.19 – Tested and solved the password issue, but had a mouse pointer in the middle of the TWRP (wasn’t a big deal). Worked in decrypted mode.
P.S. The official TWRP has issues with the name of the device. If you encounter those issues, then let the developer of the ROM
you're using know about it. So, he could fix it (it's a small fix). OR use TWRP v15 from @eng.stk. Unofficial TWRP is to be used
with LineageOS 14.1 & Experience v10 ROMs. Also, here is the reason why: https://forum.xda-developers.com/showpost.php?p=70593986&postcount=53
Also, Official TWRP v3.0.2-1 doesn't support Nougat. Therefore, you won't be able to boot to this TWRP. Don't use it for Nougat.
[*]Q: I am experiencing a battery drain. Why?
A: Facebook was the main issue for that, but it is now fixed (some users said that it still exists). I use Freedom OS v2.2 and no
issues so far with the battery. I got 5 hours SOT (Screen On Time) with 45% left (on the first day), and 5½ hours SOT with 26%
battery left (on the second day). Now, I think the OS is balanced because I get almost 8 hours of SOT. Try looking for a solution
in the forums. Also, disable mobile data when using WIFI and vise versa. Furthermore, battery life may vary with the applications
you use on a daily basis, screen brightness, how much and long you touch the screen, etc. (See the attached thumbnails)
[*]Q: I am experiencing issues with the Play Store app (It’s stuck on downloading). Is there a fix?
A: When you first launch it, it tries to update itself. It will crash 1-2 times. After that, everything works just fine. Also, uninstall or don’t
install Truecaller app (well known to cause this issue). It was fixed in OOS v4.0.2, but some users still experience this issue.
In addition, if nothing works, then try uninstalling the Play Store app and reinstall it via OpenGApps. For those who are not rooted,
try finding the Play Store app via the web (install it under your own risk, as I'm not responsible for the damages).
[*]Q: Why do you use stock recovery to sideload the OS?
A: First of all, you’re going to sideload OTA of Oxygen OS, which you can’t flash in the TWRP (some people can and you might get dm-verity
issue). Secondly, the stock recovery is simple and easy to use. Thirdly, If you flash the OTA from the official TWRP, you will get a dm-verity
message. Besides, OnePlus provided only with "OTA" zips and not "signed flashable" zips.
THE DM-VERITY ISSUE (CHECK THE FOLLOWING SOURCES FOR MORE INFORMATION):
https://www.xda-developers.com/qualcomm-maintains-its-dedication-to-security-with-secure-boot/ ; https://www.xda-developers.com/stri...r-correction-to-come-with-android-7-0-nougat/ ;
https://source.android.com/security/verifiedboot/ ; https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129 ;
https://forum.xda-developers.com/showpost.php?p=70574596&postcount=34 ; https://forum.xda-developers.com/showpost.php?p=70622726&postcount=97 ;
https://forum.xda-developers.com/showpost.php?p=70622760&postcount=98 ; https://forum.xda-developers.com/showpost.php?p=70622849&postcount=102 ;
https://forum.xda-developers.com/showpost.php?p=70622999&postcount=104
[*]Q: What if I want to go back using Oxygen OS v3.2.8 (Andriod v6.0.1) or custom ROMs based on it?
A: Simply instead of using Stock Oxygen OS v4.0.2 OTA in this guide, use Stock Oxygen OS v3.2.8 OTA.
It will bring back EXT4 file system and you can use Xposed.
[*]Q: After clean flashing my Custom ROM in TWRP, I get the following message: "No OS Installed. You Sure You Want
To Reboot". What to do?
A: Try dirty flashing your Custom ROM. (Source: https://forum.xda-developers.com/showpost.php?p=70622460&postcount=5291)
[*]Q: Android System WebView is disabled in the Play Store. When I try to enable it, it won't do anything. Unless I tap
it rapidly and it's still in disabled mode. What to do?
A: No need to worry here. It is normal due to Chrome being the new WebView in Android Nougat.
(Sources: http://www.androidpolice.com/2016/07/20/google-explains-chrome-will-become-webview-android-7-0/ AND https://productforums.google.com/forum/#!topic/nexus/Ni35XW6eRR0
https://www.reddit.com/r/GooglePixel/comments/5ayh5d/android_system_webview_not_enabled/ AND https://www.reddit.com/r/Nexus6P/comments/57t1hw/android_system_webview_keeps_disabling/)
[*]Q: Should I flash a custom Kernel (ElementalX or Blu_spark) on a custom ROM?
A: You can, but you might have CPUs being on max load and overheating issues (it's not caused by the kernel itself).
They work best, and only, if you have stock OOS v4.0.2 installed and rooted with SuperSU v2.79 Stable. Yes, for some
users the custom kernels work. But, for some they won't, due to firmware issues. You can try them on your Custom
ROM, but it's not guaranteed to work. The developers of FreedomOS and ExperienceOS solved this issue.
**Some users found a solution by setting SELinux to Permissive mode instead of Enforced.
I do not recommend setting your SELinux in Permissive mode! (as well as the developer of ElementalX)!
For more information, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/potential-fix-cpu-battery-drain-aosp-t3543369
Also, check these articles: https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/ ; https://www.xda-developers.com/onep...lus-33t-bootloader-vulnerability-in-next-ota/
[*]Q: I'm getting the error (cannot read "image.zip") when trying to sideload Stock OOS. Why and how to fix this?
A: For some reason, the thread added a space in the OOS file name. If you copy the file name for Stock OOS v4.0.2 from this thread,
make sure it doesn't have spaces in it (-OR- in any other file -OR- in the console).
** Also, make sure to enable USB Debugging in Developer Options.
** Follow these guidelines separately (if the first one doesn't work, use the second or third guideline):
Reinstall OnePlus Drivers using the attached zip (OnePlus_USB_Drivers_Setup.zip) and try again. In addition,
make sure your file name is not ending with ".zip.zip" or written like that in the console.
Bootup to your OS and connect the phone to the computer (make sure to choose transfer files mode).
Copy Stock OOS v4.0.2 OTA zip to the device and reboot to recovery. Select "Install from Internal Storage",
look for the OTA file and install it.
Read the following threads/posts/articles: https://forum.xda-developers.com/showthread.php?t=1990405&page=2 ;
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ ; https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/ ;
https://www.reddit.com/r/oneplus/comments/504qgv/adb_cannot_read_error/ ; https://www.androidexplained.com/fix-cannot-read-sideload-update/ ;
https://forum.xda-developers.com/android/general/guide-how-to-adb-to-push-pull-files-t3372710
[*]Q: Every second song in Google Play Music gets skipped. What to do?
A: Make sure to disable AdAway, then reboot the device. Everything should come back to normal.
P.S. I will add more questions and answers if they get repeated in the forums, or the issue can be solved.​

Updates & News:​Updates:
January 14th, 2017 ---> Reverted modified TWRP v3.0.3-x v12 from @eng.stk back to v3.0.2-0 v11
(Reason: https://forum.xda-developers.com/showpost.php?p=70556176&postcount=2540)
January 15th, 2017 ---> Added an introduction section; Modified sections A, B and C for more fluent and easier guidelines; Added one more Q&A
January 20th, 2017 ---> Added Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) ; Modified sections A, B and C ; Modified FAQ (Q&A)
and added more Q&A ; Updated to OOS v4.0.2, Beta 11, Official TWRP v3.0.3-0, Unofficial TWRP v3.0.3-0, Modified TWRP v14 from blu_spark ;
Modified Intoduction, "Disclaimer & Inportant" and "What will you need?" sections.
January 23rd, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v15 from @eng.stk
January 25th, 2017 ---> Added Unreleased Official TWRP v3.0.4-1 for Nougat ; Minor updates to the guide and FAQ.
February 9th, 2017 ---> Added and updated the thread with OxygenOS v4.0.3 ; Added one more FAQ and a new story
February 10th, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk
News:
January 14th, 2017 ---> Oxygen OS v4.0.2 coming next week! Confirmed.
(Sources: https://forums.oneplus.net/threads/4-0-2-in-works-roll-out-by-next-week-confirmed.488348/ AND https://twitter.com/OnePlus_ITA/status/819200734067617792 AND
http://www.androidsage.com/2017/01/14/oneplus-3-and-3t-oxygen-os-4-0-2/)
January 15th, 2017 ---> We as a community of developers and users, urge OnePlus to release kernel sources by complying with GPLv2.
(Source: https://www.xda-developers.com/xda-developers-urges-oneplus-to-comply-with-gplv2-and-release-kernel-sources/)
January 18th, 2017 ---> OnePlus said that OxygenOS 4.0 doesn’t use a Debug Kernel
(Source: https://www.xda-developers.com/oneplus-oxygenos-4-0-doesnt-use-a-debug-kernel/)
January 20th, 2017 ---> Seems like OnePlus released Kernel Sources for OnePlus 3/3T. Finally!
(Sources: https://www.xda-developers.com/oneplus-releases-android-nougat-kernel-sources-for-the-oneplus-33t/ AND https://github.com/OnePlusOSS/android_vendor_qcom_thulium/commits/oneplus/QC8996_N)
January 20th, 2017 ---> The Best ROMs, Kernels, and Mods for the OnePlus 3
(Source: https://www.xda-developers.com/oneplus-3-best-stuff/)
January 21st, 2017 ---> Remap your phone’s hardware buttons with "Button Mapper" app
(Source: https://www.xda-developers.com/xda-...an-app-to-remap-your-phones-hardware-buttons/)
January 21st, 2017 ---> How to move Chrome’s address bar to the bottom without a visual bug?
(Source: https://www.xda-developers.com/psa-...ar-to-the-bottom-no-longer-causes-visual-bug/)
January 22nd, 2017 ---> Enable this Chrome Flag to Lock Rotation in Fullscreen Videos
(Source: https://www.xda-developers.com/enable-this-chrome-flag-to-lock-rotation-in-fullscreen-videos/)
January 22nd, 2017 ---> Deeply Integrated Progressive Web Apps (WebAPKs) are Live for Chrome on Android
(Source: https://www.xda-developers.com/deep...-apps-are-already-live-for-chrome-on-android/)
January 25th, 2017 ---> Open Betas updates are paused for a month for OnePlus 3/3T due to Chinese New Year
(Source: https://forums.oneplus.net/threads/...s-3-and-3t-will-be-paused-for-a-month.492623/)
January 25th, 2017 ---> Security Analysts Identify a Trojan that Quietly Purchase Apps, a Rootkit that takes over your Device,
and Ransomware that Locks your Device
(Source: https://www.xda-developers.com/secu...device-and-ransomware-that-locks-your-device/)
January 28th, 2017 ---> An update from @rovo89 about developing Xposed for Nougat
(Source: https://forum.xda-developers.com/showpost.php?p=70773752&postcount=41)
February 1st, 2017 ---> OnePlus got caught red-handed in Benchmark cheating and came clean
(Sources: https://www.xda-developers.com/benc...ght-red-handed-and-what-theyve-done-about-it/ ; http://www.androidauthority.com/oneplus-meizu-just-got-busted-benchmark-cheating-746640/)
February 9th, 2017 ---> Two Critical OnePlus 3/3T Bootloader Security Flaws Discovered, One Patched and Other being Addressed
(Source: https://www.xda-developers.com/two-...overed-one-patched-and-other-being-addressed/)

Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?

Thanks so much, mate. This is a really good job which is gong to help to many people

Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+

Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?

I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.

Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs

Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?

You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW ?
Sent from my OnePlus 3 using Tapatalk

Greetings ?,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance

laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
I cant't download it from that thread v12 - says file might have been deleted.

mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs

VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Yup my bad. I was on first page and just used reply button. Never mind.

Answers to your concerns:
I apologize for the late response. I was doing a bit of research to answer all of your questions.
Thank you for your patience!
jackiass said:
Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?
Click to expand...
Click to collapse
Seems like "sideload"ing OOS v4.0.1 didn't change your file system, correct?
I would recommend to start over. When you are done B7, "sideload" OOS v4.0.1 to encrypt the device again. After that's done, continue to section C.
Crazyhat said:
Thanks so much, mate. This is a really good job which is gong to help to many people
Click to expand...
Click to collapse
You're welcome!
Thank you!
I tried very hard on gathering the right information and doing the testing on my OP3.
I almost got it bricked because of OOS v4.0.0, so I decided to post an easy to follow guide.
laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
Thank you very much! I have updated the thread.
UPDATE: Reverted back to v11 due to data corruption issues.
playerboys10 said:
Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?
Click to expand...
Click to collapse
I think it's not normal and you should see an immediate change in your free space.
I couldn't find any information about that.
Your best options are to follow this guide (if you didn't already) AND/OR post this issue in OnePlus 3 community forums.
yohan_xda said:
I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.
Click to expand...
Click to collapse
Did you "sideload" stock OOS in stock recovery OR flash custom ROM via TWRP (I think this one)?
Also, where did you stop (section and number)?
VincentJoshuaET said:
Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Yes, that might be the easy way when you have no issues. But, this guide deals with common issues (dm-verity, twrp password etc.) users face when they tried to update to OOS v4.0.x
If you'll face these issues in the future, you'll know where to find the related guide to fix them.
Hurizen said:
Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?
Click to expand...
Click to collapse
You are very welcome!
You could flash OTA via TWRP (full size zip and not the small 40mb zip), but I'm afraid that it might "break your root" (you wouldn't have it anymore). It can be fixed by flashing SuperSU.
Technically, you could dirty flash (wipe System, Cache and Dalvik only) the new OTA. If you would have issues after dirty flashing, post your bugs/issues, and most likely you would have to clean flash the OTA.
Give it a try (backup your personal data and dirty flash) or wait for user feedback on the new OTA.
VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Thank you for replying back to him! I appriciate it!
mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
I appologize about that. I have updated the thread.
Explorer23 said:
You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
With a bit of delay, I've put back the link to v11.
Thank you, and I hope it helped you!
dinesh7208 said:
Greetings ,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance
Click to expand...
Click to collapse
Personally, I don't mess around with fonts. But, this guide will be applicable for rooting your phone.
Check the following threads for the fonts: https://forum.xda-developers.com/oneplus-3/help/change-font-t3426785
https://forum.xda-developers.com/oneplus-3/help/how-to-change-font-one-plus-3-t3434351
https://forum.xda-developers.com/android/themes/fonts-flashable-zips-t3219827
https://forum.xda-developers.com/oneplus-3/help/cb7-custom-fonts-t3509759
I hope they help.

I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.

mit2nil said:
I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.
Click to expand...
Click to collapse
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.

dbabaev21 said:
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.
Click to expand...
Click to collapse
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.

mit2nil said:
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.
Click to expand...
Click to collapse
Then start from the beginning.
I was scared to death that I bricked my phone, but managed to get out quickly.

Issues with Flashing Roms Onto Kindle 7"

Recently got a kindle fire 7" and wanted to root it and flash a rom onto it, but having troubles with that part.
Using this guide https://forum.xda-developers.com/amazon-fire/general/root-t3471289
Rom:
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
Usb debugging/install from unknown sources/kingroot done
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Tried with and without mounting
Crashes after and starts a boot loop going into the amazon logo only
I'm new in regards for rooting, sorry if I'm a bit slow with this.
Thanks in advance for the help!

Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear

Mr McBoatface said:
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
Still nothing, leads me into another boot loop.
New things:
Rebooted after installing flash fire
Verified the hash
Move the rom onto the internal drive (flashed from there)
No Automount
Any other ideas?

IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Shugumi said:
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Click to expand...
Click to collapse
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
ggow said:
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?

crazyates said:
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
Click to expand...
Click to collapse
Had the zip on storage and wiped before flash, nothing :/

Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.

Mr McBoatface said:
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Click to expand...
Click to collapse
I might disagree with a few things you said there...
You only have to remove KingRoot if you're using v5.0 or newer. If you can use 4.9.6 to root, which I believe is what the SuperTool uses, then you can download SuperSu from the play store, update SU binary, then uninstall KingRoot with no issues.
As far as FF is concerned, the ROM developer says 0.55.1 is required, so I wouldn't stray from that.
The only other thing I would recommend is using the not-newest version of the ROM. For the last 6 months, the ROM has been based on a 5.3.2 boot.img, and recently switched to a 5.1.4 boot.img. Maybe the newer firmwares don't like the downgrade? I would try the Feb-2-2017 version of the ROM and try again.
Steps:
Restore to stock 5.3.2 (NOT 5.3.2.1)
SuperTool to install KingRoot 4.9.6 & GPlay
Kingroot to root
Install SuerSU (newest) & FF (newest) from Gplay
Use SuperSu to update SU binary
Put Feb-2-2017 zip on SD card
Use FF to wipe System, Data, Cache, Dalvik, 3rd party apps, & then install zip from SD.
Let sit for 5-10 minutes & do it's thing.

Having 2 root managers is not a good idea.
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
The version of flashfire shouldn't matter, but he is having issue so best to rule it out. The behavior of 0.53 is different to 0.55.1 . it flashes a lot quicker and is fine to use. I've used it several times in the last fortnight with the latest ROM.
The current ROM is fine, boot image and binary change won't cause the issue experienced here. The older ROMs are broken , in so far as either the camera or screen cast won't work. The latest ROM with the proven and stable binary is a better option, everything works
EDIT , also there are reports of several users losing supersuser seemingly random after upgrading to the latest SuperSU , hence why I suggested sticking with the current one on supertools.
I also suggested wiping cache, just incase an amazon update has downloaded while rooting and attempts to install at the same time at the nexus ROM is being flashed.

I have a Fire running Nexus Fire ROM (2/8/17), and my fiance has a Fire running stock 5.1.2 with root, OTA updates disabled, Nova Launcher, and Gplay Store. I wanted to flash hers from Stock to Fire Nexus, and ran into the same issues I had before.
FF was supposed to Wipe System Data, 3rd party apps, Dalvik, and Cache, then install zip, then inject SuperSU. When it did the wipe, it deleted the ZIP on the Internal Store, so FF sat there for 15 minutes not doing anything, and I didn't have a system to reboot into anymore.
I had to do a sideload recovery of 5.1.2, root, install FF, and do all the same steps as above, but this time install the zip from an SD card. Worked great.
Mr McBoatface said:
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
Click to expand...
Click to collapse
I used the SuperTool to root, and this is what I did also. Afterwards, I used the Gplay to update the SuperSU, which updated to the newest binary. I haven't seen any problems as of yet.

Unless internal storage was selected that shouldn't have happened, unfortunate that it did for you. The only time I've seen FF hang was when wipe was in the wrong order or when the USB cable was connected..... Don't know why the USB cable has that effect but I've seen it on 2 devices, other people have not had any problems.
Not seen the issue with SuperSU myself but read plenty of reports about it.
It seems users are affected by several random issues even if following the same instructions.
@Shugumi any update ?

Been swapping out roms and trying each suggestion but its been giving me the same boot loop.
So, I returned the kindle fire, and am waiting to try it on the new coming device :/, but thanks to everybody that replied to this thread. Even though we didn't get to root my kindle, it was great help! Thanks everybody.

How to ROOT Samsung Galaxy Tab Active 2 T395 - SOLVED !

First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!

How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.

Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!

I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.

[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)

Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you

oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.

RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew

Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,

Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.

Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.

Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt

Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?

Hello, did you manage to remove the "format as internal" lock?

Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?

alguma fortma?