Related
I followed each one of your steps. I get an error when trying to install the signed zip. "Can't find update script" Can anyone please help me with this.
thank you
I'm doing option 2. I get it signed just get an error "Can't find update script"
This quick guide will teach you how to sign ROMs!
WARNING : YOU WILL NEED AT LEAST A BASE KNOWLEDGE OF HOW TO USE COMMAND PROMPT.
The knowledge of signing ROMs can prove useful to anyone! By knowing how to sign ROMs, you can modify your favorite ROM to add or delete APKs, so when you flash the ROM your favorite apps will be present! Or you can delete apps you don't use so they will not be installed when flashing the ROM!
Before starting, you need a couple of things. First you will need Java SE Development Kit and Java SE Runtime Environment . You can download them HERE.
After you have downloaded and installed both, you will need a very useful tool made by someone at XDA-Developers (if you know who it is please let me know).
Download this tool (attached) and unzip everything inside of it into one common folder. I personally unzipped everything into my Android SDK folder.
Signing
Now run the autosign.bat. You will have to go through commands 1(Set PATH variable for SDK) ,2 (Set CLASSPATH variable for signing tool) and 3 (Install registry entries). They are very easy to use and just follow the instructions. If you are asked to confirm and/or replace a file, always select yes!
Now you are finally ready to sign! There are two options to sign the .zip
1)Find the ROM (.zip) and right click and select "Resign Zip". If you use this option a command prompt box should quickly appear and disappear.
OR
2) Using the Autosign.bat, select option 4, and then write the directory and file name of the ROM. For example,
D:\Android\ROMs\YourROMHere.zip
It will hang for a bit at the part where it says "signing", and then it should say something along the lines of "Successfully completed if no errors above"
If this helped you, comment below!
http://androidforums.com/developer-101/8665-how-signing-roms.html
Anyone...... I know someone knows
You have to zip the contents of the rom, not the rom itself. i.e. if you sign the rom folder, it will be ROM_Signed.zip->ROM->system/data/metainf... you get the picture. Go into the folder you want to zip and then sign, select the contents, and zip them. It will then be ROM_Signed.zip->/system/data/metainf. Then just sign it.
update-script is a script that tells the flash utility what to do. It is located in the zip as part of the following directory structure:
META-INF/com/google/android
The contents can vary. For Darktremor A2SD 2.6.1, here's the contents:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
PACKAGE is used by android to reference the actual zip file, or package file.
SYSTEM is used to represent /system
DATA is used to represent /data
CACHE is used to represent /cache
BOOT is used to represent the boot partition (which is where you flash boot.img)
RECOVERY is used to represent the recovery partition. Never actually seen this used. I guess it used for an update.zip that you would flash via fastboot.
The zip file has to be structured in the same way as the file system on your phone. If you want to install something to, say, /system/bin, you must have a system folder, which in turn has a bin folder.
What I would do is take one of the available ROMs and unzip it. Then look for their update-script. Usually ROM packages are more detailed in the update-script.
If you don't have update-script in your zip file, the flash utility in recovery won't know what to do.
networx2002 said:
I followed each one of your steps. I get an error when trying to install the signed zip. "Can't find update script" Can anyone please help me with this.
thank you
I'm doing option 2. I get it signed just get an error "Can't find update script"
This quick guide will teach you how to sign ROMs!
WARNING : YOU WILL NEED AT LEAST A BASE KNOWLEDGE OF HOW TO USE COMMAND PROMPT.
The knowledge of signing ROMs can prove useful to anyone! By knowing how to sign ROMs, you can modify your favorite ROM to add or delete APKs, so when you flash the ROM your favorite apps will be present! Or you can delete apps you don't use so they will not be installed when flashing the ROM!
Before starting, you need a couple of things. First you will need Java SE Development Kit and Java SE Runtime Environment . You can download them HERE.
After you have downloaded and installed both, you will need a very useful tool made by someone at XDA-Developers (if you know who it is please let me know).
Download this tool (attached) and unzip everything inside of it into one common folder. I personally unzipped everything into my Android SDK folder.
Signing
Now run the autosign.bat. You will have to go through commands 1(Set PATH variable for SDK) ,2 (Set CLASSPATH variable for signing tool) and 3 (Install registry entries). They are very easy to use and just follow the instructions. If you are asked to confirm and/or replace a file, always select yes!
Now you are finally ready to sign! There are two options to sign the .zip
1)Find the ROM (.zip) and right click and select "Resign Zip". If you use this option a command prompt box should quickly appear and disappear.
OR
2) Using the Autosign.bat, select option 4, and then write the directory and file name of the ROM. For example,
D:\Android\ROMs\YourROMHere.zip
It will hang for a bit at the part where it says "signing", and then it should say something along the lines of "Successfully completed if no errors above"
If this helped you, comment below!
http://androidforums.com/developer-101/8665-how-signing-roms.html
Click to expand...
Click to collapse
HeroMeng said:
You have to zip the contents of the rom, not the rom itself. i.e. if you sign the rom folder, it will be ROM_Signed.zip->ROM->system/data/metainf... you get the picture. Go into the folder you want to zip and then sign, select the contents, and zip them. It will then be ROM_Signed.zip->/system/data/metainf. Then just sign it.
Click to expand...
Click to collapse
It took my brain a min, but i got it.
Thanks
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Thanks for this. Will try now.
Worked great. Had to copy the apk and odex file.
Good job! It's great to see the steps for Windows users!
Just a heads up that I simply extracted the files I needed from and on my N7 using Root Explorer, without using my PC at all.
Great guide! Method worked perfectly on my Nexus 7 going from 4.1.2 to 4.2, thanks
Please... is there some other way to update the files w/o installing Java on my Windoze PeeCee? I accidentally messed up my YouTube.apk with Titanium Backup... now I can't update from 4.1.2 --> 4.2 JB.
EDIT: JavaPortable FTW... updating (fingers crossed)
EDIT: SUCCESS TY OP!
For anyone who flashed the 4.2 clock/keyboard already
Hey, for anyone who flashed the 4.2 clock and keyboard on their Nexus 7 already and need to roll back to do the 4.2 update, I used OP's method to make a flashable zip that puts the 4.1.2 clock and keyboard back.
Worked perfectly for my Nexus 7 to get me up and running. Hope it helps anyone!
cantthinkofa.com/files/RestoreClockKeyboard.zip
galaxy nexus
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Nice Guide
perfect, the guide works just fine. Now finally running 4.2.
Awesome guide... Thanks... Happily running 4.2 now aften beeing stuck at libutils.so...
Sent from my Nexus 7 using xda premium
damagno said:
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Click to expand...
Click to collapse
I don't have a Galazy Nexus, but I think the steps should be the same. Here is a link to the factory images: https://developers.google.com/android/nexus/images#takju . It looks like they now have links for older versions, rather than just the newest images (which is how it was when I made my guide). So that's pretty sweet.
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1.
Click to expand...
Click to collapse
I was wondering if you could tell me how you did it? I'm searching a way to install 4.2.1 with no avail as of yet :crying:
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
Click to expand...
Click to collapse
Yes. I am having the same issue. I cannot update mine from 4.2 to 4.2.1. I wonder to know which original stock image you have used. Can you list a detail procedure?
Thank you very much.
Ric
dev/block/param
legom said:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Click to expand...
Click to collapse
my error 7 was generated by emmc: dev/block/mmdblk0p7 (the file is "param" any suggestions?
Thanks. After searching for a lot of time, this post helped me updating my SGS3.:victory: I previously tried to integrate youtube update into rom using titanium backup.
GallStones said:
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual)
Click to expand...
Click to collapse
Yes, that's what I mean. The reason I didn't want to do this on my device is because I had modified some other system files that I wanted to keep the modifications for.
Wow, thanks a lot OP! Your guide helped me fixing an error during the update to 4.2.2 on my Nexus 4.
please include a video ,im getting lost in the details
solved.
Hello all,
Using TWRP, I successfully flashed PAC-ROM to my Cricket 'jflteaio' or SGH-i337z ... I337ZTUUBND3, Galaxy S4.
A bit of helpful info for noobs: I rooted with 'towelroot' app --- Google it
And installed TWRP 2.7 from here
At this point...MAKE A BACKUP in TWRP!!! I AM NOT LIABLE FOR BRICKED DEVICES!
Now on to the real fun stuff! Follow these steps to flash Pac-Man ROM:
1. Download the GENERAL jflte rom 'zip' file and not the 'md5sum' from the PAC ROM website:
Download the zip HERE
2. Extract the zipped jflte pac rom into a new folder anywhere in Windows. In the new folder, navigate to this location:
\META-INF\com\google\android\
3. Download and install the free Windows program, NotePad++ --- Google it
4. Right-click on 'updater-script' in the folder \META-INF\com\google\android\
(IMPORTANT: Leave the 'update-binary' file alone; only modify the 'updater-script')
5. click on "Edit with NotePad++".
6. In NotePad++, Under the first word/command "assert" you will see a bunch of commands that start with 'getprop'. Find a spot where it reads '||' and make a new line directly after this. you will see many jflte codenames, so making your new line after you see 2 of the same codename and '||' will do.
7. Make sure the new line you made does not cut any commands in half and copy/paste in these lines of code:
Code:
getprop("ro.product.device") == "jflteaio" ||
getprop("ro.build.product") == "jflteaio" ||
(NOTE: This code will allow install of PAC-ROM on jflteaio)
8. Make sure to save the changes in the file. Close NotePad++.
9. Zip all the files you extracted from the original back up with 7zip or winrar... make sure the file extention is not '.7z' or '.rar'. Must be '.zip' to work. And the files you just zipped have to be in the root location of the zip file. In other words, make sure when you open your new zip, the first folder you see is 'META-INF'... for example in 7zip, you have to select all the elements(there are 5 in total...3 folders and 2 files) in the new folder you created earlier, and right-click and choose 7zip and 'add to archive'.
10. You can now flash the rom in TWRP from an sdcard by following the instructions HERE on XDA
(FINAL NOTE: By the way, make sure NOT to install the AT&T SafeStrap Kernel during the flash, as it may cause the ROM not to boot, and as always, make a TWRP BACKUP before you attempt flashing!)
I do not own any of the software in this guide. A special thanks to all the devs out there who make our lives better!
Best of skill (and luck) to you all!
raydantheman
Welcome to a simple tutorial that will help OnePlus 2 (OP2) owners and possibly other device owners install custom ROMs in such a way that eliminates most, if not all possibility of system errors, resulting in the longest lasting and most stable custom ROM installations!
DISCLAIMER: Your Warranty was voided long before you were ever even ready to complete this tutorial.
Therefore, I am not responsible for a broken or bricked device, especially if your rage towards a bricked device caused you to throw your device into a wall. This tutorial is actually designed to reduce the amount of "Rage Quitting" on modifying your device.
This Tutorial assumes you have already completed OEM Unlock, Root, installed TWRP or other Custom Recovery, and are basically ready to install a custom ROM on your OP2.
Before beginning, backup any files you may need, I upload mine to my Google Drive then download after completing the ROM install. You can also use Nandroid to backup your current system (optional as there are methods to restore even the most bricked OP2 that doesnt even have a working recovery or OS, trust me I have done it at least 5 times because I constantly try new ROMs and mods). There are three necessary prerequisite steps required to complete before using this method to install your custom ROM. These prerequisites are listed below:
Prerequisite One: Ensure your OnePlus 2 has been FULLY updated on the stock Oxygen OS ROM before you install your TWRP or other Custom Recovery. If not, Return to factory ROM, Un-Root, and update until you cannot update any more, then return to this tutorial afterwards.
Prerequisite Two: Ensure your OnePlus 2 has the latest update of the TWRP or other Custom Recovery. The Latest TWRP for the OP2 can be found here: https://twrp.me/oneplus/oneplustwo.html
Prerequisite Three: Ensure your device can receive files via ADB PUSH while in custom recovery. To do this, reboot your phone into recovery, connect to PC, hold down the "Shift" key and while holding, right-click in a window containing a file you wish to transfer, and select "Open Windows PowerShell Here" or "Open Command Prompt Here". Use the command "adb push Lin15.zip /sdcard" (remove the quotes, "Lin15.zip" is an example file) to push the file onto your device. Then, if your custom recovery has a file explorer as TWRP does, use it to navigate to /sdcard and see if the file is there. Also, your windows should show a successful transfer and should say "Okay" underneath your command line. If unsuccessful, install OnePlus 2 Drivers along with Universal ADB drivers and then try again. If still unsuccessful, try TWRP 3.1.1-0 (Download Link Below 2 Paragraphs in Blue Text Section). If unsuccessful at this point, there is something wrong as Win 10 with OP2 Drivers, Universal ADB Drivers, and TWRP 3.1.1-0 is my exact setup.
There are many custom ROMs available for the OP2. The method for installing custom ROMs is generally the same, but can differ in certain ways. This method SHOULD work for your custom ROM, but is not guaranteed. If this method fails, then visit your custom ROM's development page, and follow their instructions instead.
In this Example, I will be installing the latest (at the time of writing) Lineage 15 Android Oreo 8.0 Third Alpha Build OS/ROM and will be including instructions for the proper installation of the A.R.I.S.E. Magnum Opus System Sound Mod (Based on Viper4Android). I will include links to downloads, but their main XDA page can be found here: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 This installation will use the latest (at the time of writing) TWRP 3.1.1-0 Custom Recovery.
INSTALL TIME:
Begin by rebooting into recovery. Under "Wipe" options, you will first want to format data, select the option and type "yes" when prompted to confirm the operation. Repeat this step once again to ensure a squeaky clean wipe.
Next, also under "Wipe" Options, select the "Advanced Wipe" Options. You will then select EVERY BOX (Yes, this includes Internal Storage and will wipe EVERY SINGLE FILE from your device, this is INTENTIONAL and is why you MUST have a device that can accept ADB PUSH files in recovery!). This will wipe every file from existence, completely. This is what allows such a stable, squeaky clean install, as not a single piece of evidence from any other ROM/OS will be left behind, leaving basically no chance for errors or conflicts during installation of new ROM. You will want to complete this step again to ensure a squeaky clean wipe.
Navigate to the TWRP Home/Start-Up Screen and connect your device to your PC (WARNING: DO NOT USE ADB SIDELOAD MODE!!! I HAVE NEVER, EVER HAD A SUCCESSFUL ROM INSTALL FROM SIDELOAD!!!). Simply leave the device at this screen, and do not touch it. At this point, if you do not have all the necessary files to install your custom ROM and mods, you will need to download them now. I ALWAYS recommend the "Pico" Gapps package if installed in a ROM (some ROMs include Gapps). The reason for this is because the Pico package includes the bare minimum to get Google Play Services and Google Play Store up and running. This eliminates unwanted Gapps and reduces the chance of installation conflicts. The golden rule is: The less you install in TWRP, the better. If you want more Gapps, then after setting up the phone at the end of the ROM install, just search for them in the Google Play Store, its how I get mine every time. In the case of Lineage 15, the list of downloads is below:
Lineage 15 OS/ROM: https://www.androidfilehost.com/?fid=961840155545594199 (Dev Page: https://forum.xda-developers.com/oneplus-2/development/rom-lineageos-15-0-t3668056)
Android Oreo 8.0 Pico Gapps Package: https://www.androidfilehost.com/?fid=817550096634796662
Super SU 2.82 Root Installer (Select the Flashable 2.82 ZIP file): http://www.supersu.com/download
BusyBox Flashable Zip Package (Large page with many tools, scroll down to find the BusyBox tool): https://forum.xda-developers.com/showthread.php?t=2239421
A.R.I.S.E. Magnum Opus System Sound Mod (Select the "ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip" Option): https://www.androidfilehost.com/?w=files&flid=176171
Once all necessary files are downloaded, give them their own folder inside Windows and rename all of them to something simple as shown here:
View attachment 4273530
(Lin15.zip, Gap.zip, SU.zip, Busy.zip, Arise.zip)
Ensure your device is in custom recovery at the home/startup screen and is plugged firmly into your PC. DO NOT navigate ANYWHERE inside custom recovery or touch the device.
Now we will ADB PUSH these fresh install ZIP files over to your device. Inside the window containing your downloaded ROM files, hold down the "Shift" key and while holding, right-click and select "Open Windows PowerShell Here" or "Open Command Prompt Here". To ADB PUSH files, simply type "adb push FILE.zip /sdcard" where "FILE" is the target file and "/sdcard" is the target destination. Correct capitalization of letters is IMPORTANT! My window looked like this when finished:
View attachment 4273532
(adb push Lin15.zip /sdcard, adb push Gap.zip /sdcard, adb push SU.zip /sdcard, adb push Busy.zip /sdcard, adb push Arise.zip /sdcard)
Your ROM files should now appear on your device at your target destination. Disconnect your device and use the Custom Recovery File Explorer to navigate to the destination to confirm. "/sdcard" is the easiest to use destination.
Now we will install ALL of the ROM files, back-to-back with NO REBOOTS, NO WIPES, NO OPERATIONS WHATSOEVER INBETWEEN INSTALLS, THIS IS EXTREMELY IMPORTANT!!! Navigate to the Custom Recovery "Install" Section and navigate to your destination for your files. Flash the ZIP files in this order EXACTLY: Lin15, Gap, SU, Busy, Arise.
The A.R.I.S.E. Instillation is an AROMA style installer. It is a HUGE Sound Mod suite containing many options. Select the sound mods you like, but there is a module that is REQUIRED and 4 others that are highly recommended, listed below:
CORE Module is REQUIRED!!! Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions fix are all highly recommended no matter what the ROM or mods, just in case. If these problems do not exist, selecting the options will not change anything, so do not worry.
My personal A.R.I.S.E. install included the following modules and delivers absolutely AMAZING sound quality while keeping installed modules to a minimum (otherwise known as a "Lightweight" install): Core Module, Viper4Arise 2.5.0.5, Viper4Arise Profiles, Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions Fix. Its a highly recommended package
ONLY AFTER ALL FILES HAVE BEEN INSTALLED, navigate to Custom Recovery "Wipe" section, select "Advanced Wipe" and then check the "Dalvik Cache" and "Cache" options, DO NOT SELECT ANYTHING ELSE OR YOU WILL NEED TO START COMPLETELY OVER, WIPE PHONE AND RE-ADB PUSH FILES TO ENSURE A SQUEAKY CLEAN INSTALL!!! Perform this step again to ensure a squeaky clean wipe.
YOU ARE NOW FINISHED WITH A SQUEAKY CLEAN ROM INSTALL BUT THERE ARE A FEW MORE RECOMMENDED STEPS!
Recommended: DO NOT immediately reboot into system after install. Instead, navigate to Custom Recovery "Reboot" Section and select "Power Off" Instead. Once device is off, plug into A/C Outlet charger (DO NOT USE A PC, DETECTION OF PC WILL CAUSE DEVICE TO BOOT), and allow to fully charge, then cool off. This will ensure that Battery Calibration is set to 100% upon Initial Boot
Initial Boot: Boot Device, Initial boot will take around 5-10 minutes. DO NOT TOUCH THE DEVICE DURING THIS TIME. When you see the startup screen, STILL DO NOT TOUCH THE DEVICE! Instead, allow device to sit and idle, allowing the ROM to "Settle" for a MINUMUM of 5 minutes, 10 is recommended. Then, BEFORE setting up the device, reboot and allow another 5 minutes of "settling".
Run through the Device Initial Setup. You will want to select any desired options now, and avoid having to search settings later. Once at Device Home Screen, immediately open app drawer and select SuperSU app. Inside SuperSU, navigate to settings and apply the following options:
Disable Re-Authentication, Default Access: Grant, Enable SU During Boot, Trust System User
These SuperSU options will allow mods to function with complete stability and no interference, leading to a smoother experience. After, completing this step, Reboot your phone and ENJOY YOUR NEW, ROCK-SOLID, STABLE ROM INSTALL!!!
Nice job bro thanks working here!
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.
shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Now I tried it again and this time flashed busy box as well but the same error.
Screen shot for your reference. Is there another way to install it?
shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
pops106 said:
Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.
Click to expand...
Click to collapse
Well we all know performing this method of install is not a requirement for installing ROMs, but it is the most fool-proof method and ensures there are no file conflicts between old and new ROMs/OS's. I cannot even tell you how many times I have done quick, minimal work installs and end up with tons of errors, laggy or freezing screens at random times, force closing apps, busybox system link failures, the list goes on and on. After using the "Squeaky Clean" method, I can honestly say Lineage 15 is as stable as the Stock/Factory Oxygen OS.
wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Thanks. I got it install using a different method and it is working wonderfully.
wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Fair enough
And thanks to the opp for the thread
pops106 said:
Fair enough
And thanks to the opp for the thread
Click to expand...
Click to collapse
No problem, the thread was a random idea after accidentally stumbling across the fact that TWRP can accept ADB PUSH files. I honestly had no idea, and was stuck in a bootloop after a custom ROM failed to install correctly. I had no backup and was getting ready to just give up, enter Qualcomm Diagnostics Mode and perform the Oxygen OS Firmware/Software OEM install when I decided to reboot into Recovery and attempt SideLoad of a previous ROM that had worked.
This did not work, as sideload is apparently a dumb way of doing things. I never understood why sideload tries to install a file that is in the middle of transferring. Just seems like a flawed concept to me. Anyways the install was very slow, buggy and laggy, and when finished had installed such a corrupt system, due to installing a partially transferred file while it is being transfered and then sticking all the pieces together, was so unstable that more than a minute idling at the home screen or any attempt to open ANY app caused the phone to reboot.
Sideload is a worthless feature in my opinion and I will never use it for any operation ever again so long as I live. So all of a sudden I decide to plug the phone into my PC while in recovery and observe how Windows detects the phone when you turn Sideload mode on and off, as to try and troubleshoot my sideload to get an effective install (which by the way will never happen, to this day I have never had a sideload install work correctly), and noticed when I turned it off, the device still showed up as a recognized Android device under Windows Device Manager. Then, you may not believe me on this, but I did actually randomly decide that more than likely, it was interfaced on Universal ADB, and that it I typed "adb devices" into a windows command prompt, it should show, and it did. The rest is history.
I know the feature had been around for some time as I found out later on, but I had never seen any information about it anywhere on any thread, and even when I asked for ideas for troubleshooting, while XDA users helped for sure, I guess they just didnt have that idea, and gave me alternative routes as well such as the Qualcomm Diagnostics full OEM wipe method which I was already familiar with. This does show, however; that experimenting and troubleshooting on your own can be a great way to learn new things!
Hi, thank you for the post.
I am enjoying v4a bcoz of you only.
I got a query btw, can I install dolby & atmos along with v4Arise?
Please add a note for HaruhiOS
HaruhiOS checks if a clean flash is required before flashing and will abort to tell the user that a clean flash is necessary if ever. It is my design goal to avoid the need for clean flashing as much as possible
Due to this the user should avoid unnecessary clean flashing, which actually ruins performance and battery life and reduces device health when using my ROM
if already.....
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.
magnamentis said:
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.
Click to expand...
Click to collapse
Apparently e2fsck and fsck.f2fs is too hard
Once the storage card is corrupt no formatting will help you anyways
Just stop believing in dumb stuff. If you have to clean flash every other build a ROM developer releases they messed up big time and they should fix their code
Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
lleo_ said:
Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
Click to expand...
Click to collapse
The number of developers fixing issues on the pixel vs this phone is astounding...
rignfool said:
The number of developers fixing issues on the pixel vs this phone is astounding...
Click to expand...
Click to collapse
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
lleo_ said:
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
Click to expand...
Click to collapse
There are... But they come and go as far as updates and such...
The demand is for Google... And moar features without losing Google...
Now... What you can do/try is wander over to the Project Trebble area... I would assume that you will find a plethora of development...
You're gonna be wading in some unknown territory... And it'll be a mystery as to what works... And whether it's fixable... Good luck
EDIT: or... You can magisk yourself... And try NanoMod... I think that disables a ton of Google stuff and puts FOSS stuff in it's place...
Sir! Thank You for your post. At first I thought it was a joke, but I learned something today. The concept and related work of project Treble bypassed me. I have already a GApps-less LOS on my Ph1. Again thanks!
Don't know if this applies, but lots of ppl are successfully running GSIs on the Essential.
Maybe some of them are GAPP-less?
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
arjunv said:
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
Click to expand...
Click to collapse
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only having either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
DoR3M3 said:
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only have either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
Click to expand...
Click to collapse
Thank you so much for a detailed post
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Stoked to see two things here...1.) the answer to the question I was searching for about running my Essential with no gapps...and 2.) your choice in file explorers!