Database Users

[TELUS T959D FASCINATE][NOT ACTIVELY MAINTAINED-last updated 04.29.13]One Stop Shop

Hi and welcome Telus Fascinate T959D Users.
The purpose of this thread was to join a few T959D users together. When I flash a ROM I usually have at least 6 posts open on XDA - on different methods, kernels, etc. So I started collecting information and organizing it here. I have been updating based on feedback and adding more and different content especially when more users found us here.
Special thanks to everyone who has helped with this thread over the past few years - and special call outs to @Matt5606, @iwebsource, @finneginsfast, @moosehead11, @Dayfid, @karmatose, @bucknetbucky.
However, please note that we the contributors take no responsibilities for your phone or anything you do to it - this is simply a collection of helpful posts to get you started and continue having conversations - they are by no means offered as full proof guides, nor do they imply a warranty of any sort.
Now on the fun stuff, but first a simple FAQ.
Q. What is the T959D and what ROMs can I use on it?
The T959D is Telus' Galaxy S phone - known as a fascinate. What is confusing is this phone has almost nothing in common with the Verizon Fascinate - in fact flashing a fascinate ROM will brick your phone. Fortunately for us, our phone is VERY close to the International Version - the i9000 or galaxysmtd. Those are the ROMs we use on this phone.
Q. Is there a place where I can get files for my phone?
Yes - all through XDA you can use i9000 compatible ROMs, Kernels, modems. As well, we have a stock pile of files available to you - as you read the OPs you will find those and how to get them.
Q. Can I brick my phone?
Yes - but from my personal experience it is very hard to do this, and you can always get a USB jig that gets you to download mode (if you are soft bricked) - load one of the stock images and you are right as rain again.
A USB jig is a small piece of modded hardware that plugs into your USB port on your phone and forces it into download mode on start up - EVEN if it is SOFT BRICKED. A necessity for flashing. Lots of 'how tos' on how to create them out there if you have a spare cord, or just order one on EBay
http://www.ebay.com/sch/i.html?_nkw=usb+jig
For me, the place to use the most caution is using Odin - when placing files into the fields ensure they in the right place (measure twice, flash once ) as that is the biggest risk to flashing your phone. I think this is the greatest risk to hard bricking your phone which I am not sure you can recover from (I have only ever soft bricked my phone in which the USB jig saved my hide).
Q. I put on an ICS/JB ROM and now my IMEI is gone? What is that and how do I get it back?
Your IMEI is the unique identifier on your phone. The number is written down behind your battery - and that is what your phone should be displaying when you go to About Phone in Settings. Something happened with ICS/JB that it sometimes gets lost. To prevent that you need to back up your EFS folder.
1. You must be rooted.
2. You must have a file explorer that has root access (root explorer or ES File Explorer - although, if using ES ensure you have enabled root access and mounted /system in the preferences.
3. Find your /EFS/ folder at root (/).
4. Copy the EFS folder. Ensure you have ALL the files and ALL the subfolders (one will your IMEI). However, there can be hidden files in here, I would not worry so much about those, simply ensure you copy over the EFS folder itself - that should do it.
5. Move this to your removable SD card. Zip it, keep it on your PC, put in dropbox, ensure you have a copy for safe keeping.
And that is it - after flashing a new ROM, if you are missing your EFS or your IMEI number if wrong, just copy back the folder, reboot, and voila!
Q. GPS sucks.
Yes, yes it does. Do a search if you are adventurous there are hardware fixes. There's also faster fix in the play store and there are files here you can load as well - but its a known issue with the Galaxy S family of phones.
Q. What should I run on my phone?
Well, that is entirely up to you. The last official firmware you can get is 2.3.3. If you like very stable and do not need to have the latest, just a stable working phone with great battery - maybe try a good gingerbread ROM like Darky's or CM7.0 - Darky's will give you that Samsung feel (and still have the right firmware for the camera).
There are literally tons of options - go to the i9000 thread and see what the latest is. Most users here in this thread are on SlimICS, SlimBeam, CM10 or CM10.1. I have been running latest (nightlies) CM10.1 for some time combined with my favourite kernel Semaphore.
If you are going to flash a new JB ROM though, I suggest as your first flash stable CM 10.0 - this will be the base of your next ROM and many ROMs such as slim recommend you flash CM first just to set things up for yourself.
Q. So what now?
Read, read, and read. Go through this thread - go through threads of the ROMs you want to install - see what users are saying about it lately. And please - come to this thread and ask questions - we have a small but friendly and very helpful community - and remember if we help you, stay active on the thread so you can help someone else.
Cheers - and happy flashing

ICS/JB ROMS from Scratch (updated May 31 2013)
THANKS to @karmatose and @Dayfid for creating an ODIN flashable 2.3.3 - this means no more KIES (yes!) and creating a fresh stock ROM - here's the steps for this procedure... (Updated September 26, 2012)
Please note that the links below provided by Karma http://t959d.karmatose.org will work BUT you will need a username and password to download the files. Karma or myself can make the login and password available to you.
1. Download the KG2 package from here - http://t959d.karmatose.org/index.php/apps/files/download/Shared/stock_roms/T959TLKG2_Gingerbread.zip
2. Extract the archive to a folder on your PC using your archive app of choice. Mine is WinRAR.
3. Open Odin3 v1.7.exe (the one that is in the ZIP file)
4. Place the PDA, CSC and PHONE and PIT files in the proper boxes. Take absolute care to make sure you don't mix them up. Ensure that repartition is ticked 'on' in this case.
5. Put phone in download mode (vol down + power from off or download jig) and connect it to the PC
6. Click start and wait just under 3 minutes. The phone will restart and you should be back to stock 2.3.3
7. If your intention was to get to stock, you're done. If you want to go to ICS/JB and you *don't* have a backup of your EFS folder, go to step 8. If you do have a backup of your EFS folder, go to step 10.
8A. If you need to backup your EFS folder (HIGHLY RECOMMENDED), you need to root the phone. Flash the Speedmod kernel with ODIN (in the PDA field). The phone will reboot and get stuck in a boot loop at this point. Pull and replace the battery and place the phone in Recovery Mode by holding VOL+ and VOL- and pressing the power button. When the screen lights up, release the power button and continue to hold the volume rocker until you see CWM Recovery. Using the Vol+ and Vol- to navigate the menu, go to the Speedmod Advanced Options menu and press the power button to select it. Choose to root your phone.
8B. (Optional) Now that you have custom recovery, would not be a bad idea to make a nandroid backup of your phone. So go to backups, and create backup from the CWM Menu.
8C. Once that is complete, go back to the root menu and reboot the phone. Pull the battery out and put the phone back into download mode. Flash the stock 2.3.3 kernel back (also in the PDA field) in Odin. The phone should now be rooted. Let it boot. Hopefully you're greeted with a lock screen
9. Install ES Explorer from play (or APK), enable Root Settings in the settings menu then navigate up to root and copy your EFS folder to your EXTERNAL_SD card. Power down the phone, remove the SD card and copy this to your PC, Google Drive and some other backup source. Don't lose this folder.
10. Installing ICS / JB - Depending on what OS you want to go to, you're going to need to grab an appropriate kernel to do so. The best option seems to be Semaphore's i9000 kernels. If you're going to flash an ICS rom, grab the 1.3.0s .tar file. If you're going to JB, grab the 2.1.0s .tar file.
11. Download your ROM of choice. i9000 versions of SlimICS/SlimBean/CM9/CM10 work on the T959D. You will also need grab the .zip version of the Semaphore kernel (ICS / JB) you're using and a Modem of your choosing. KG3 works best for me, your mileage may vary. Place the ROM, .zip version of the Semaphore kernel you're using and the ES File Explorer APK on your internal SD card.
12. Open Odin again. Put the .tar'd Semaphore kernel file you just downloaded in the PDA field, ensure Re-Partition is UNCHECKED. Put your phone in download mode, connect it to the PC and click start. In a bit more than 10 seconds, your phone should reboot itself. Pull the battery out and replace it.
13. Put the phone in Recovery Mode by holding VOL+ and VOL- and pressing the power button. Release the power button as soon as the screen turns on but keep holding VOL+ and VOL- until CWM appears. Use the VOL+/- keys to navigate, PWR button to select. Go to "Install zip from sdcard", then "choose zip from internal sdcard".
14. Follow the directions to install your ROM. CM9/10 comes in one flashable .zip file whereas SlimICS/SlimBean comes in multiple files. Consult the documentation for your ROM to get specifics on how to install it. Note that if you are installing CM10, CM10.1, Slim 3.x + that the partition layout has changed. This means you will need to flash the ROM at least 3 times - once you will get an error 7, then flash again, and then again - after that you will have latest.
15. Once the ROM is done flashing, flash the Kernel .zip you placed on your External SD card the same way you flashed the ROMs. Then flash your modem .zip. Note that if you are using an 's' version of semaphore, and a non-patched ROM like CM (Slim is already patched) you will want to flash the big mem library patch which is attached below after flashing the kernel.
16. Go back to the CWM main menu and reboot the phone. You should boot into ICS / JB at this point with no issue. It might take a bit so be patient.
17. Verify your IMEI number. Hit the Menu button on your phone and select System Settings > About Phone > Status. Look at your IMEI. If there's a lot of 0's in it, you need to replace your EFS folder. Use Oi Explorer to access your External SD card and install the ES File Explorer APK. Enable *all* the Root options in the application settings and return to the file browser. Locate your EFS folder backup on your external SD (emmc), longpress on the folder and select "Copy To". Hit the navigate up button in the dialog box and select /. Press OK twice then reboot your phone. Your IMEI should be back to normal now.
18. Enjoy the fruits of your labour and customize the heck out of your new ICS / JB rom.
----
This is an alternate method from @bucknetbucky created this quick 'how to'. This will put you on stock GB and allow you to flash ICS from there.
Why start from GB? The bootloaders. When flashing from froyo you'll see lots of tips on pulling batteries and the first flash always not working - this won't happen from Gingerbread AND you'll get to keep the logo for the kernel for some added bling.
For those looking to flash from GB here is how to do it...
Get back to 2.3.3 stock
1 flash stock froyo via ODIN (tick repartition! - See the 'Essential Files' section above).
2 install samsung kies (should have this if you have this device- AND update it!)
3 update to GB using kies
Root your phone and back up EFS
Backing up EFS is vital. Essentially do this.
4. Download Super1click to root your phone and following the instructions (http://depositfiles.com/files/n0dcxce3t)
5 Install a file manager with root access and backup your efs folder by copying it to the internal sdcard then your computer (instructions in OP)
Note: this is one way to root your stock GB phone - you can also use the speedmod kernel (the version I use is older --- but works --- and is attached below) which has a root option under 'advanced' but has more steps. If you already have backed up your EFS though, you really do NOT need to do this step and skip to the steps below to flash your ICS ROM.
Finally INSTALL your ICS ROM
Now to flash the latest super duper ROMs from the super duper devs you will need to do the following...
1 copy glitch v14 kernel and the rom of your choice to your internal sdcard (The version linked below is the BEST version to accomplish this with)
http://www.box.com/s/tov06pvzkkqbmui6tcmi
2 flash via ODIN the speedmod kernel (gives you a custom recovery)
3 when it tries to boot pull the battery and then boot to recovery
4 flash the glitch kernel from recovery (again you are boot looping)
5 pull the battery and boot to glitch recovery and wipe data, clear cache and such then flash your ROM
6 copy your backed up EFS folder back to the phone to restore yout imei
Just some notes
Most ROMs will come with a compatible modem, however, if having modem issues - please see a few posts down on getting modems.
A complete list of ROMs for the I9000 by Android version can be found here (as well as kernels). Please note the update dates as that will indicate how much active support there is for the ROM.
http://forum.xda-developers.com/showthread.php?t=1837223

Gingerbread ROMs (Updated 03/11/2012)
In terms of loading GB ROMs I have had success with a few - namely Darky ROM (up to 10.4.2).
Credit to the original poster, but I always start with this how to on loading a ROM.
http://forum.xda-developers.com/showthread.php?t=923712
I do not execute every step, but essentially use it to get to stock along with the custom voodoo kernel which will give you root and custom recovery to load your custom ROM.

ROM and Kernel TWEAKS (Updated 08/28/2012)
GPS Tweak
This how to can you help you tweak GPS
http://forum.xda-developers.com/showthread.php?p=17081413
Note the multiple GPS.conf entries you can have for country (Canada) as well as region (North America).
Darky ROM tweak
When installing Darky ROM you will find the buttons for home and back no longer work. There is a simple fix for this as long as you have a root explorer (like ES File Explorer) and a text editor.
Open up /system/usr/keylayout/melfas_touchkey.kl in a text editor.
Make sure that your 'keys' look like this:
key 139 MENU
key 158 BACK
key 217 SEARCH
key 105 HOME
key 106 SEARCH
Keep VIRTUAL as part of the keys and you will still have vibration as well.
Alternatively (Thanks @finneginsfast !) you can flash 'keylayout.zip' attached below from recovery.

Flashables (Updated June 29 2013))
This is reserved for flashables such as modems and kernels.
Ultimate Kernel Cleaner
Before flashing a kernel, you should run a kernel cleaning script. Matt (THANKS @Matt5606) gave me this one - it handles cache cleaning, etc. See the attached file for ultimate kernel cleaning script.
Modems
Lots of modems out there, and get Perka's file store for a ready list (see recommended apps). My favourite for a long while has been the i9000UGKC1 modem - it has GB versions as well as ICS - just make sure you get the right one!
You can also download modems diredctly from Perkas Site (/Samsung/ICS_CM_Modems/850_Modems_CM) or the android app (available in Play). Ensure you get the right modems for your ROM or Android version.
For Gingerbread: /Samsung/I9000/Modem_850_Enabled
For ICS and JellyBean: /Samsung/ICS_CM_Modems/850_Modems_CM
@finneginsfast provided me with this graphical link to help give you an idea of what modems work where: http://soggycashew.weebly.com/modem-location-map.html
Gingerbread Kernels
Semaphore. Great kernel to run with DarkyROM.
http://forum.xda-developers.com/showthread.php?t=1112908
Glitch Kernel. Great kernel to run with CM7 or MIUI GB as its made for our model!!!
http://forum.xda-developers.com/showthread.php?t=1315400
ICS Kernels
I run Semaphore almost exclusively - definitely a favourite.
http://forum.xda-developers.com/showthread.php?t=1468795
Glitch has a specialized kernel for ICS as well, but I typically do not use it.
http://forum.xda-developers.com/showthread.php?t=1459475
JellyBean Kernels
Semaphore has a JellyBean kernel for 4.1.2 as well as 4.2.2 - its my go to kernel.
http://forum.xda-developers.com/showthread.php?t=1786220
Be sure to get the LMK app from XDA (search it) to ensure your launcher and keyboard do not die, and get Semaphore manager from the Play Store as well.

Recommend APPs (Updated 09/28/2012)
Launchers - ICS/JB
- APEX Launcher (free and paid, on Google Play)
- Nova Launcher (free and paid, on Google Play)
- Holo Launcher HD (free and paid, on Google Play)
Launchers - 2.x
- Launcher Pro (free and paid - better widgets with paid - Google Play)
- GO Launcher (totally free - lots of great supporting apps - Google Play)
- ADW (free and paid, Google Play)
- Holo Launcher (free and paid, Google Play)
Keyboards
- Swift Key X (trial and paid, Google Play)
- Swype (trial and paid, Google Play)
File Management & Files
- ES File Explorer (Free, has root explorer - Google Play)
- Perka's File Stash Free and Donate - excellent file resource for modems - Google Play)

Other Stuff
Essential Files
Before we get started wanted to make available some essential files. These are from my public dropbox folder, so I may switch it in time, but felt they should be here.
Need to get back to stock, then here is the Stock Telus Froyo 2.2. http://dl.dropbox.com/u/2069701/T959TLJL3.zip
Want stock with a CWM kernel on 2.2, then here is the VooDoo Kernel http://dl.dropbox.com/u/2069701/voodoo.advanced.v666.2-20110111-21.53.tar
Remember when flashing back to stock to tick the re-partition box, and place the files as follows:
- s1_odin_20100512.pit in "PIT"
- T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
- T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
- SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
Additionally, Karma has some core files he is posting as well (Thanks @karmatose !!!) and you can find those files at:
http://t959d.karmatose.org
To access the files, you will need a login. @karmatose or myself can make the login and password available to you.
Starting Fresh
Buck provided this a while back. This is recommended after many flashes and you want to start out fresh without lingering script files and other crap we're all guilty of installing/flashing
WARNING: This clears up EVERYTHING - even TB backuped programs - so if you want your TB backups, change your backup location to the REMOVABLE SD Card.
If you want to start fresh and i mean bare bones this is how i do it.
1. Remove the external sd card (the one you put in the phone)
2. Go into storage under settings and unmount then format the sd card (the partition the phone makes that you see if you do not have root)
3. Flash stock rom via odin and repartition ofcourse.
4. When you are done the phone will be like you just took it out of the box.
5. Backup the card you took out and format that. Leave it out.
6. Grab some beers and start flashing whatever you want (except the neighbors they dont like that)

Awesome thread, subscribed!
Sent from my GT-I9000 using XDA

Do I have to root my phone after installing GB . Or I can wait
And witch app is the better to backup the EFS folder

You need to root to back up your EFS... so for that. Then use root explorer or ES to copy that folder over to your SD and computer.
If you ES make sure turn on root explorer and mount /system.
Sent from my GT-I9000 using xda premium

In Odin witch slot (PDA,PHONE,CSC,BOOTLOADER) that i put the file speedmod-kernel-k16-11 . and the other one

Pda
Sent from my GT-I9000 using xda premium

there is no root option in the recovery mode after i put the speedmodkernel
nevermind lolll

I've been lookin at that procedure and you root through recovery with the speed mod kernel? I'm pretty sure you can root while on stock GB without all that hassle by just using SuperOneClick.
Sent from my GT-I9000 using XDA

Thx a lot JP for this thread!!!! . I m now part of the ICS community . Only one thing my IMEI number inst the same was its written under my battery . I copy back the EFS folder tho . Does it change something ???
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Matt5606 said:
I've been lookin at that procedure and you root through recovery with the speed mod kernel? I'm pretty sure you can root while on stock GB without all that hassle by just using SuperOneClick.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
I finally found it but thx for the feedback

If you remembered to copy your efs folder before the flash, just copy the original folder back into your phone replacing the old files and reboot. You should have your number back.
Sent from my GT-I9000 using XDA

Yeppers
Sent from my GT-I9000 using xda premium

So get yourself the semaphore kernel and nova launcher and you are all set
Sent from my GT-I9000 using xda premium

it did not change my IMEI numbers?? .what is that kernel do (Semaphore) and how to install it odin??

jpmccarthy said:
Darky ROM tweak
When installing Darky ROM you will find the buttons for home and back no longer work. There is a simple fix for this as long as you have a root explorer (like ES File Explorer) and a text editor.
Open up /system/usr/keylayout/melfas_touchkey.kl in a text editor.
Make sure that your 'keys' look like this:
key 139 MENU
key 158 BACK
key 217 SEARCH
key 105 HOME
key 106 SEARCH
Keep VIRTUAL as part of the keys and you will still have vibration as well.
Click to expand...
Click to collapse
Or you can install this zip from recovery, I think it's the same fix or at least it's what I've been using for a while.

[tutorial]how to make nandroid backups without rebooting to recovery

WARNING: BEFORE YOU DO ANYTHING PLEASE READ THIS THREAD AND MAKE SURE YOU KNOW WHAT YOU ARE DOING. I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
A few days ago I came across this thread which made me think and try. At the beginning I couldn't flash the zips necessary for making backups without rebooting to recovery .
What you will need:
1.Bootloader unlocked and a rooted phone . If you don't have any of them please read here and here
2.Busybox
3.A root explorer of your choice
4.A terminal emulator app
5.The 2 files from the zip attached
6.Patience
Open your root explorer extract and copy the 2 files attached to /system/bin and set permissions 755( that's rwxr-xr-x).
Reboot your phone.
Open Terminal app and type su to obtain root followed by onandroid.
Sit back and relax while the script backs up your rom.
All thanks go to ameer1234567890 who gave us the Online Nandroid . I only found the thread and also found the method to copy the files to Razr I.
When i'll have some time i'll try to make a flashable zip for the lazy ones

As promised here are the zips for flashing from recovery with update binary working with the Razr I. I have only tested with CWM, but they should work with TWRP as well.
I suppose everyone knows what to do, but just in case someone new tries it:
-copy the 2 zips to you internal storage or external sdcard
-reboot to recovery
-select install zip from sdcard(now choose the location of your files)
-select zip
-install
-reboot
Enjoy

nandroid,etc, assistance
free2live said:
As promised here are the zips for flashing from recovery with update binary working with the Razr I. I have only tested with CWM, but they should work with TWRP as well.
I suppose everyone knows what to do, but just in case someone new tries it:
-copy the 2 zips to you internal storage or external sdcard
-reboot to recovery
-select install zip from sdcard(now choose the location of your files)
-select zip
-install
-reboot
Enjoy
Click to expand...
Click to collapse
Is this the best way to do a " nandroid " - I have been part of this site for quite some time , read numerous sites, but i have a very bad memory problem and that's why i have many text documents setup to the point i am confused. Right now I have an AT&T S4 which has a bad IMEI, so I want to use it as a test phone, but it has been updated to 4.3 -which from what I understand I would need to downgrade back to 4.1.2 order to unlock the phone via the dial pad. I was able to accomplish that one time when I first got a Samsung S4 and did it via the dial pad before the OTA came out for 4.3.
I also own a S3, also AT&T, so i can learn how to to root and unlock and use CWR or TWRP and than learn ROMS. I know I need to make a backup before I do anything, and also constantly reading the " Noob " general forums for both phones. I also am familiar with Samsung Kies, which does a backup but I don't think it's the same as this nandroid i have been reading about.
Thank you or taking out the time and reading my post. I will check back to see if anyone had some time to give me some direction or an answer to my problem with " nandroid" or if someone even could touch up on any subjects I have mentioned. Please don't think I haven't spent hrs of time on YouTube, Google, Howard forums and especially here on XDA.

[GUIDE] Get Xposed working on your deodexed TouchWiz based Lollipop ROM! 2015/08/17

DISCLAIMER
The process of flashing a custom recovery/kernel/firmware may and will trigger your device's Knox Counter. Neither XDA nor I can be held responsible for your actions. Proceed with caution. During this process you will lose all your settings and apps. As long as you follow the instructions, your device's storage, internal and external, won't be touched​
Still not compatible with x64 systems! Not compatible with Samsung 5.1.x (sdk22) ROMs!
Hello, Ladies and Gentleman
Many people seem to have a hard time to understand how all of this here on XDA works. I constantly get PM's from users, asking how to do the most basic stuff like flashing a .zip or stock firmware via Odin. Usually, I don't even read them and just hit delete. I know it's not ok to deny people help, so I decided to show you how you can get Xposed working on your TW based stock or custom ROM since it's the most frequently asked question I get.
It's nothing you couldn't do if you'd just....
We're going to use @arter97's customized Xposed Framework as the one made by @darkera13 needs the user to manually modify and replace files which may be too complicated for some.
Preparation
-READ EVERYTHING OVER AND OVER AGAIN.
-A custom recovery System like TWRP or CWM (PhilZ or Stock)
-A deodexed ROM. It's the only way to go. YOU NEED A DEODEXED ROM. If your ROM is not deodexed and you flash the framework, you'll end up in a bootloop. To deodex your existing ROM carefully follow Post #2
Here are a few made by XDA Senior Member @_alexndr
Stock deodexed for SM-N9005 Galaxy Note 3 International Qualcomm.
Stock deodexed for SM-G900F Galaxy S5 International Qualcomm
-And the framework itself from here
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
-Flash a custom recovery system of your choice. This is listed under preperation on purpose since this guide is about getting Xposed on your TW Lollipop device. A guide on how to get a custom recovery system is most certainly available in your device's forum.
-Store the ROM and the Framework in an easy to find folder, which we're gonna call "folder x". It doesn't matter where you store it (ext. SD or int. SD)
The Fun Part
-Boot into your custom recovery and make a full wipe:
TWRP users: "Wipe>Advanced Wipe> Tick System, Data, Cache, Dalvik Cache> Slide to format.​CWM users: "Mounts and Storage> hit Format /System; hit Format /Data; hit Format /Cache.​
-Still in recovery system, install, or flash the files we put in folder x;
TWRP users: "Install> Navigate to folder x and choose the ROM file first> Add Zip> now choose the Xposed Framework from folder x> Slide to flash.​CWM users: "Install Zip> Choose zip from /sdcard if folder x is on internalt storage or /storage/sdcard1 if folder x is on ext. storage (SD-Card)>​choose the ROM file first> -Yes - install ROMXY.zip.​Do the same with the Xposed Framework zip file.​
-Still in recovery system, reboot device and wait for it to boot. It can take up to 20 minutes. Enjoy Xposed on your Samsung TouchWiz Lollipop ROM.
-Stuck in a bootloop? Try this and repeat the process.

XDA Senior Member @Honzze kindly pointed out to keep following in mind; You have to start JoelDroid Lollipop Batch Deodexer with Admin permissions. Otherwise this error might return "path variable" of Java "is not set".
Deodexing your existing ROM without having to flash an entire ROM
As the title says, with this awesome guide by XDA Senior Member @townsenk you don't have to reflash an entire new ROM to your device. Instead, youll just deodex those parts of your System which need to be modified in order to get Xposed working. You don't necessarily have to perform a full wipe if you do it this way. But if you encounter fc's or end up in a bootloop, you know what to do
Guide for this guide:
Regarding point 1: "...launch a DOS shell..." just means, you need to open the so called "CMD" programm in Windows. To "launch a DOS shell" or CMD from within a folder, you simply have to hold down the shift key and right click in that folder. The context menu will show an entry "open command window here". And that's it! (Windows XP users may have to search the internet for another solution)
For Galaxy S5 and Note 3 users: If ADB returns "device offline" or an empty line after "List of devices attached" make sure your using a USB 2.0 data cable on a USB 2.0 port
townsenk said:
How to DeOdex YOUR (...) Rom.
I would like to note that I appreciate all the work that developers have put forth in creating and maintaining modified Roms. there are some awesome feature rich implementations available. My intentions are not to be critical of any specific Rom or mod. Without the developers we would have nothing.
(...)
This method is very common knowledge I thought I'd just explain it in an easy to understand way.
Here is what you need.
A stock (...) ROOTED configurated phone. Debloat as needed. Set the phone up exactly how you like it with apps and such.
Make sure it's stable. (If you have issues before DeOdexing they will be there afterward!)
Here's the files you may need to make this happen
LBD2.4.zip
7-Zip
Installer template (at end of post)
1> Make sure ADB is working on your computer. USB debugging turned on. Create a folder to store your soon to be download system files and launch a DOS shell from that working folder. Working folder name should NOT contain spaces. With the phone hooked up you should be able to type adb shell and get a prompt.
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
3> Extract and launch LBD2.4 (This is the DeOdexer and is AWESOME). Point it at your recently created "system" folder and let it do it's thing.
I'll assume this will occur without errors as I have never had any.
4> At this point you can manually apply modded apk's to the system folder but I don't really recommend it. They can be applied afterward using the seperate installer zips.
5> with 7-Zip installed open the provided Installer template. Do not Extract it. Just open it in the 7-Zip file browser using the right click context menu in windows.
Drag-Drop the contents of your system folder into the empty system folder in the 7-Zip browser It should be the three folders previously created but now they are Deodexed. Close the 7-zip file manager and select Yes if it asks you to save.
Note: The provided installer template has been modified to only wipe and replace the three system directories.
6. Copy the created installer to your sdcard and install with recovery. Wipe cache and Dalvik before rebooting.
Go have lunch. You will sit at a boot screen for about 10 minutes. Then another 20 to rebuild caches. Time varies.
7. Your system will now be Deodexed! At this point you can install your mods one at a time, I recommend this so you can test your system between installs to determine if a specific mod is creating problems.
This method has so far removed ALL of my stability issues.
Click to expand...
Click to collapse

Since I no longer own this device, I'm retiring from this thread as of now. Hope I could help you.

Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.

omg brilliant @nitrous² ! thanks so much! its been days i keep trying to deodex with others tool...

Sachitoge said:
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
Click to expand...
Click to collapse
Same happened to me.... Did you solved this problem?

Maurizio1953 said:
Same happened to me.... Did you solved this problem?
Click to expand...
Click to collapse
Nope, i ended up using CM12 (at that time, right now i got cm13 update).
Well i had to deodex apps to get xposed on TouchWiz, but i failed and didn't get headache because of the Xposed modules being not really well compatible on TouchWiz, so i jumped to CM, i find it more stable, and the CM13 is insane because it saves so much battery at stand by, compared to lollipop, the Android 6.0.1 Marshmallow is the biggest update in android history, that saves hell lot of battery (it can be also maybe because i don't have Xposed Framework in recent rom).
Anyway, im tired of it, and i don't need to hassle with Link2Sd because of Android Marshmallow offering to mount the SD Card, in the end, all my needs are being offered in this (for me) huge, best android update, being Marshmallow.
Try it i would say, so amazing.

Ok i would like to go to cm13 as you but i stil need the support to the gear s smartwatch so i decided to stay with touchwiz without xposed.

Any way to unlock the 5GHz WiFi band for US-version?

So the US-version of the Mediapad M3 does not support 5GHz Wifi as stated by Huawei and from my personal experience. Per Huawei's website:
Wi-Fi: IEEE 802.11a/b/g/n/ac at 2.4 GHz & 5 GHz (Products delivered to markets that impose FCC certification requirements do not support 802.11 a/ac at 5 GHz Wi-Fi)
I can't help but think that the hardware is there as I have never heard of a mobile WiFi chip that ONLY supports 802.11 ac at 2.4 GHz. Therefore, is or will there be any way to unlock the 5 GHz band of the WiFi chip assuming the hardware is there?

Well, if you have unlocked bootloader, you may try the following:
1) Get root access.
2) Open /system/build.prop and find ro.config.hw_is_hide_wifi_5g=true and change it to "false". Or to true if it's false.
3) If that doesn't work (cause I really don't know what this option stands for), see below.
4) Go into /cust folder and tell us what's in there. Maybe, there's something like "hw" folder with "eu" folder inside.
5) If there is, edit /data/custom.bin and put "hw/eu" there (without quotemarks), and see, if something has changed.
If you don't have "hw/eu" in /cust, you have two ways:
1) Ask me here to give you "hw/eu" folder, put it into /cust and do (3).
2) Find local.prop file (it's usually in "prop" folder, three folders down from /cust, but folders are those you have, not "hw/eu")
3) There you'll find ro.config.hw_opta and ro.config.hw_optb. Change them to 999 and 156 respectively.
If all that doesn't help, we'll need to find another ways.

Slavon-93 said:
Well, if you have unlocked bootloader, you may try the following:
1) Get root access.
2) Open /system/build.prop and find ro.config.hw_is_hide_wifi_5g=true and change it to "false". Or to true if it's false.
3) If that doesn't work (cause I really don't know what this option stands for), see below.
4) Go into /cust folder and tell us what's in there. Maybe, there's something like "hw" folder with "eu" folder inside.
5) If there is, edit /data/custom.bin and put "hw/eu" there (without quotemarks), and see, if something has changed.
If you don't have "hw/eu" in /cust, you have two ways:
1) Ask me here to give you "hw/eu" folder, put it into /cust and do (3).
2) Find local.prop file (it's usually in "prop" folder, three folders down from /cust, but folders are those you have, not "hw/eu")
3) There you'll find ro.config.hw_opta and ro.config.hw_optb. Change them to 999 and 156 respectively.
If all that doesn't help, we'll need to find another ways.
Click to expand...
Click to collapse
Has anyone been able to try this yet?

the7thson said:
Has anyone been able to try this yet?
Click to expand...
Click to collapse
C'mon, be the first one
Just another caution.
Please, do a backup first.
I had a factory reset after changing region in custom.bin. I don't know, what was the real cause, and now I don't do anything to my tablet, cause everything it setup and works fine.
You, probably, can avoid it in two cases:
1) Your original recovery was replaced by TWRP
2) You don't change the actual region, changing only the content of your region's folder.

the7thson said:
Has anyone been able to try this yet?
Click to expand...
Click to collapse
Changing ro.config.hw_is_hide_wifi_5g=true to "false" didn't do anything for me.
/cust folder contains /hw (subfolders /default, /normal, /oversea, and /usa), /lost+found, /preinstalled, and /special_cust. I haven't messed with any of them.

didn't work.
After unlocking the bootloader and getting root access I did the following:
1. Changed /system/build.prop: ro.config.hw_is_hide_wifi_5g=true to "false".
restarted the tablet but it did nothing
2. went to /cust. it contains the following folders: /hw (subfolders /default, /normal, /oversea, and /usa), /lost+found, /preinstalled, and /special_cust (just like for @neo_1221)
edited local.prop under /Cust/hw/usa/prop/ to ro.config.hw_opta=999 (was 567) and ro.config.hw_optb=156 (was 840).
restarted the tablet but it did nothing
What else can be done?

E.Vogel said:
What else can be done?
Click to expand...
Click to collapse
You may try to flash Chinese firmware. It's Something like BTV-W09C233B0xx or BTV-DL09C233B0xx
I don't have any other ideas, really. If even this doesn't help, then 5GHz is locked by OEMInfo or disabled in hardware.
Firmware can be found with this tool

Am confused by this thread. Are you saying you can only connect to 2.4 networks and cannot see 5ghz networks at all?? That normal only happens when a tablet physically does have a 5ghz radio.

The U.S version of the tablet does not support 5Ghz wi-fi.
We are assuming that there is only one variant of the tablet sold world wide (two actually LTE+wifi and wifi only),
and in order to comply with FCC requirements the 5Ghz wi-fi band was disabled by software and not hardware.
If that is the case than the band can be enabled back by flashing different non-U.S rom.
hopefully

It is WORKING!
I downloaded the latest Chinese version using the tool @Slavon-93 linked, version BTV-W09C233B022 from December 16 2016. I flashed it and after restarting the tablet, I have a Chinese version tablet, with 5Ghz band wi-fi working.
I lost custom recovery and root and may reflash them later.
I got some apps back that I previously removed, but happily all my other apps were still installed and configured.
Thanks @Slavon-93
p.s. I re-flashed TWRP and SU and now have custom recovery and root back

E.Vogel said:
I downloaded the latest Chinese version using the tool @Slavon-93 linked, version BTV-W09C233B022 from December 16 2016. I flashed it and after restarting the tablet, I have a Chinese version tablet, with 5Ghz band wi-fi working.
I lost custom recovery and root and may reflash them later.
I got some apps back that I previously removed, but happily all my other apps were still installed and configured.
Thanks @Slavon-93
p.s. I re-flashed TWRP and SU and now have custom recovery and root back
Click to expand...
Click to collapse
Can you select english as the language?

Yes you can, and since English was my selected language before I flashed the Chinese ROM it stayed as the selected language, so I never got a Chinese welcome screen and had to find out how to change it to English.

So this is a solution to get the "5Ghz band" working on a US WiFi only?

Those, who have a US tablet, could you please upload your entire /cust folder somewhere? If Chinese firmware is a solution, maybe there is something in /cust, that blocks 5GHz wifi? I wanna compare it to Chinese and Russian versions and maybe find something interesting.

@E.Vogel forgive me for being new to Huawei way of doing things. You said you flashed the Chinese ROM. Flashing makes me think of my Nexus 7 where I actually flashed the *.IMG files.
I downloaded the file you mentioned and I have update.app after extraction. I recall reading somewhere about creating a folder and transferring said file to device and restarting it. I'm curious if this is the route you took? I personally prefer fastboot flash but will have to do with what works. Thank you.

jmjm003 said:
@E.Vogel forgive me for being new to Huawei way of doing things. You said you flashed the Chinese ROM. Flashing makes me think of my Nexus 7 where I actually flashed the *.IMG files.
I downloaded the file you mentioned and I have update.app after extraction. I recall reading somewhere about creating a folder and transferring said file to device and restarting it. I'm curious if this is the route you took? I personally prefer fastboot flash but will have to do with what works. Thank you.
Click to expand...
Click to collapse
Forgive me for not being @E.Vogel, but let me explain. Huawei devices are not usual in terms of partition structure. For example, they have 2 recoveries, designed for different things. For a Nexus owner their update structure is also strange. Once upon a time, you could create a "dload" folder in /sdcard or in external SD, choose local update in update utility on your device, select update.app or update.zip, reboot and watch the device updating. Now we don't have an option to choose a local update, so the quickest way to install FULL OTA is from TWRP. You just need to put update.zip (~1.8 Gb) somewhere in /sdcard or other place, reboot into TWRP, press the Install button and select this file. TWRP installs it and you get your Chinese firmware. I recommend to make a backup first, in case something goes wrong. After installing FULL OTA you still get your apps and settings in place, but after a factory reset, you will lose Google Play and other a Google apps, and will have to manually install them from HiApp. Also, you will have to reinstall TWRP, root, xposed and other things you probably have flashed before.

I appreciate the reply all the same @Slavon-93. So creating the dload folder and dropping update.app in it no longer works?
I've not modified anything on my device other than fixing DPI so apps are in tablet mode.
Any idea what each recovery does since it has two of them?
I like to know there's a way out of a screwup if it happens. Nexus 7 was simple to fix.
Thank you.

jmjm003 said:
I appreciate the reply all the same @Slavon-93. So creating the dload folder and dropping update.app in it no longer works?
I've not modified anything on my device other than fixing DPI so apps are in tablet mode.
Any idea what each recovery does since it has two of them?
I like to know there's a way out of a screwup if it happens. Nexus 7 was simple to fix.
Thank you.
Click to expand...
Click to collapse
Huawei devices have two recovery partitions: recovery and recovery2.
Recovery has generally all the same features a typical Nexus recovery has, except it doesn't have an option to apply update.zip and has a touch interface unlike the Nexus recovery.
Recovery2, called eRecovery, also has a touch interface and is designed to make a totally screwed up device great work again. It has a button to download full firmware and install it but on my device it said "No firmware found" after connecting to Huawei servers. People in Russian forum say it works only if you're in China and have a Chinese device. Anyway, if eRecovery does nothing, I considered it totally useless and replaced with TWRP: fastboot flash recovery2 twrp.img
Generally Huawei devices can be restored the same way a Nexus device can. TWRP and fastboot work the same. Personally I prefer to make a total backup of all partitions in device with "dd". I think it will give me more flexibility in restoring if something goes completely wrong. On DL09 model, only modem partitions are the problem. You can find fastboot versions of Chinese ROMS easily, but after installing them, I've lost everything related to phone functions. The only way to fix it was installing Full Chinese firmware in form of update.zip with TWRP.
And about dload folder. I have no idea how it works. I am also a former owner of Nexus 7 and the logic of Huawei is new to me, so I don't know some nuances. On earlier devices there was another option to update: you put update.app to dload folder, dial *#*#2846579#*#*, select Software upgrade -> SDCard Upgrade, the device reboots and installs the update. Again, on my device this trick didn't work and update installation stopped at 5%, saying it's incompatible with my device.

@jmjm003, I also come from a nexus 7 and Huawei devices are different.
First of all there is no formal web site with all factory images and/or OTA to download, I had to use a tool an XDA user developed to find the factory image I needed.
The second change is that the factory image (file update.zip) does not contain *.img files inside like in Google images and contains "update.app" 1.8GB file and some other small files.
To flash the ROM I tried to use ADB sideload but got an error message about the file being unreadable, so I copied the file to the tablet and flashed it using TWRP install function like any other zip file.
@Slavon-93, my /cust/hw folder changed from before and now contains only two sub-folders "cn" and "default"
I uploaded the entire /cust folder to Google drive, use this link to download it.

E.Vogel said:
@Slavon-93, my /cust/hw folder changed from before and now contains only two sub-folders "cn" and "default"
I uploaded the entire /cust folder to Google drive, use this link to download it.
Click to expand...
Click to collapse
Thank you but I know what's inside Chinese /cust folder as I am using Chinese firmware myself. I am interested in untouched /cust of US version of tablet because I think there can be some option in local.prop or somewhere else, that blocks 5GHz Wi-Fi. I can try to look for it by comparing Russian, Chinese and US cust folders.

Fool-proof, 100% squeaky clean oneplus 2 custom rom installation for max stability

​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