Moto-Lite Stock Nougat ROM
Android 7.0 / NPHS25.200-23-1
Moto X Pure Edition XT1575
TWRP Flashable Installer
Rooted, Debloated, Optimized
•••••••••••••••••••••••••••••••••••••••••••••••••••••
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's Moto-Lite?
Moto-Lite is an entirely stock-based Motorola ROM, with performance optimizations, systemless root, and some moderate debloating. This ROM is intended to give users a clean, slimmed down stock experience -- via a TWRP flashable installer.
_______________________________________
DISCLAIMER:
By proceeding further, you are assuming full responsibility for your device. Although this ROM has been thoroughly tested, I assume no liability in the event you damage your device or otherwise render it inoperable. Follow the simple instructions and things should go smoothly.
_______________________________________
BUILD INFO:
•Android Version: 7.0 Nougat
•Build No. NPHS25.200-23-1
•System Version: 25.211.1
•API Level: 24
•Build Date: October 30, 2017
•Security Patch Level: October 1, 2017
•Kernel Version: 3.10.84-perf
•Bootloader Version: AO.52
_______________________________________
FEATURES:
•Rooted with Magisk 20.4-Stable
•Static BusyBox Binaries: v1.31.1
•Moderately Debloated
•Safety Net Pass (ctsProfile/basicintegrity)
•Force Encrypt Disabled (Opt Encrypt)
•dm-verity/AVB 2.0 Disabled
•Custom Moto Boot Logo
•Optimized for RAM Efficiency
•su.d Support
•Fully Odexed per Stock Config
_______________________________________
Official Motorola Firmware for XT1575:
This firmware repo encompasses official firmware packages that originated from Motorola's servers. This link includes Android 5.1.1, Android 6.0 and Android 7.0-based firmware builds, including the NPHS25.200-23-1 build upon which this Moto-Lite ROM is based.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Kernel Source Code:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15
_______________________________________
PREREQUISITES:
Per the general rule of thumb, you will need an unlocked bootloader and a custom recovery such as TWRP. I recommend using the most current official TWRP build from here: https://dl.twrp.me/clark/
In order to circumvent force encryption during installation, you will need external storage such as a microSD card or an OTG USB storage device. (The /userdata partition must be formatted prior to installation; hence, all files and data stored on your device will be erased.) If you do not have, or do not wish to use, an external storage medium, alternative install instructions have been provided, for which you will need a PC or laptop computer and a good quality micro USB to USB syncing/charging cabke
NOTE: The below instructions assume that your device's firmware has been updated to the NPHS25.200-23 firmware build. It is also assumed that your device's modem/baseband version is M8992_1255331.29.01.88.09R SUPER_NA (the most current version).
_______________________________________
Instructions for installation are outlined under two separate headings: A. INSTRUCTIONS - STANDARD INSTALL, which apply to users who have an external micro SD card or an OTG supported external storage medium; and B. INSTRUCTIONS - NO EXTERNAL STORAGE, which should be used by those who do not have, or do not wish to use, a micro SD card or an OTG supported external storage device. For the latter you will need a laptop or computer and a good quality micro USB to USB syncing cable, for transferring the ROM zip file to your phone during the process
A. INSTRUCTIONS - STANDARD INSTALL:
1. Download the ROM zip from the below link and save it to external storage;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Select INSTALL, select the ROM zip, and commence installation;
5. Once the ROM is installed, the installation script will patch the stock boot image via Magisk v20.4-Stable to enable systemless root. BusyBox v1.31.1 static binaries will also be installed;
6. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
7. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions on your part;
8. Enjoy & profit...
B. INSTRUCTIONS - NO EXTERNAL STORAGE DEVICE
1. Download the ROM zip from the below link and save it to your computer;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Transfer the ROM.zip the file from its saved location on your computer to the now-formatted internal storage directory on your phone (via a micro USB to USB syncing/charging cable);
5. Reboot Recovery;
6. Select INSTALL, select the ROM zip, and commence installation ;
7. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
8. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions;
8. Enjoy & profit...
At the time I cooked up this ROM, the latest stable Magisk version was v20.4, so my systemless root installer encompassed within the ROM installer employs Magisk v20.4 stable. After installing the ROM, booting up and completing initial setup, open the Magisk Manager app to update Magisk to the most current version.
_______________________________________
THANK YOU:
Thanks to the amazing @osm0sis for his static BusyBox binary installer. And many thanks to @topjohnwu, the genius developer and creator of Magisk. Huge thanks to @pitflyer, who gave feedback and input on methods of install, and who revisited and outlined the steps for an alternative installation without using a micro SD or OTG supported storage device.
Thanks to @sd_shadow for his input and guidance on installation.
_______________________________________
BUGS:
Since this ROM is based entirely on an official Motorola stock firmware build, no significant bugs or instabilities should be expected. I have tested this ROM thoroughly after performing some optimizations (RAM, I/O Schedule tweaks. Entropy tweaks, etc.), moderate debloating and Magisk installation. I have noted no remarkable bugs, instabilities or performance flaws. However, please leave a comment in the event you discover flaws or bugs. I will look into the issue and try to resolve it. If possible, submit a bug report. Otherwise, list as much detail and specifics as possible regarding the issue.
_______________________________________
DOWNLOAD LINKS:
Moto-Lite XT1575 Android 7.0 ROM
**V2 updated ROM: Magisk v24.3, Busybox v1.34.1 static binaries, some additional debloating and some more RAM optimizations made on the kernel level.
V2 Moto-Lite xt1575 Android 7.0 ROM
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
bronkish said:
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
Click to expand...
Click to collapse
Thanks for your input on this. I'll take a look at the Moto Voice service and see if I have debloated a system app or process that is Moto Voice dependent. Did you notice the Moto Voice issue before installing Xposed & GravityBox? Yeah I absolutely love SD Maid Pro. A great system-level tweaking tool with many uses.
Gravitybox, yessir. I typically get my dumps in order, reboot to twrp, wipe it all, flash a ROM, reboot, initial setup, dev mode and those settings, airplane mode, reboot, flash xposed, reboot, set up my phone. You know, if I do it that way.
Lol, I got no time to see if your kung-fu works right before I fuk it up with xposed. I can't answer the only and perfect question that you asked me. What's even more perfect than that failure is that I bought a g power the other day and haven't used my Xpure since last week. This g power has a burn't pixel though. WTF. I had it 8 days to replace the phone I used 5 years.....sigh.
THanks for responding, sorry I can't help you help me. Probably going to return the g power and use the x pure again and wait for a sweet-ass black-friday deal to replace it. There's a 7T on craigslist winking at me, though... I probably won't reset anything on the Xpure though, runs sweet. Hard phone to replace.
Edit - yeah - been using SD maid for years - love it, use the hsit out of it. ONly realized yesterday that I can dump apks of all installed apps at one go. It just keeps on giving.
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
mddunner said:
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
Click to expand...
Click to collapse
Thank you for your feedback and kind words. Glad to hear the ROM worked well on your device.
thank you works great and its rooted.
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
pitflyer said:
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
Click to expand...
Click to collapse
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not have external storage mediums or, like many users, may want to expedite the installation process. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Hodgdon said:
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
Click to expand...
Click to collapse
Happens to the best of us. Is the ROM working ok for you?
Viva La Android said:
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not own an OTG based external storage device. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Click to expand...
Click to collapse
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
pitflyer said:
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
Click to expand...
Click to collapse
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Viva La Android said:
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Click to expand...
Click to collapse
No problem and thank you for sharing the updated ROM!
This looks like the solution I need ...
Could y'all PLEASE define exactly which TWRP yer using to get this from the SDcard into the phone?
Essentially, I UL my BL via moto, fastbooted TWRP (3.1? I'd heard going past 3.2 invited a.b partition foibles) however this still gives me the "Unlocked Bootloader" BSOD, ergo cannot USE twrp - it simply reboots into a functional fone (but obviously NOT secure)
The XT1575 came (used) with stock Nougat ... can supply logcat etc if that's of any use to removing this stupid VIBRATOR screen that won't let me get into TWRP at all
TYVM
VW
You may use any version of TWRP you wish for installing this ROM. I would personally recommend the latest official TWRP v3.5.2-9.0, released just last month. TWRP for the xt1575 Clark was built using device-specific kernel source code. Thus, no matter which version of TWRP you encounter, A/B partitioning will not be a factor because the Clark does not now, nor has it ever, used the A/B partitioning scheme.
So try these steps exactly: download TWRP v3.5.2-9.0 from here https://dl.twrp.me/clark/ , rename it to twrp.img and store the image in your ADB/Fastboot directory on your PC. Also, save a copy of this renamed TWRP image on your xt1575. Boot your Moto into fastboot mode and connect the device to your PC using an adequate data sync cable. Open a command window on your PC in the path of your ADB/Fastboot directory. After confirming.a proper sync, flash TWRP by executing this command:
fastboot flash recovery twrp.img
Now boot to TWRP using:
fastboot boot twrp.img
Once booted into TWRP, select Install, tap the Install Image option in the lower-right of the display, navigate to the saved location of twrp.img you saved earlier and select it. Now, select Recovery from the partition options presented. Commence installation. When finished, TWRP should be installed properly on your /recovery partition. To ensure its persistence as properly installed, choose Reboot and Recovery.
Now you may install the ROM by the instructions outlined in this thread.
NOTE: There have been reports for years of xt1575 owners encountering difficulty with "making TWRP stick" while using the stock Android OS; i.e., TWRP being overwritten or replaced by stock recovery upon the first reboot to the Android OS following TWRP installation via fastboot. This is a common occurrence on many Motorola devices when TWRP is installed alongside the stock OS. (The best I can recall, this glitch is related to a "boot.p" script present in the stock Android ROM.) The instructions I outlined above can be used as a workaround to this issue to prevent custom recovery from being replaced or overwritten by stock recovery.
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
mddunner said:
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
Click to expand...
Click to collapse
Yeah it's an older version, but other than the upstream codebase, the newer versions for the Clark (built on the Android 9 Pie tree) are not remarkably different in terms of the GUI. For purposes of what we are doing here --installing a stock ROM archived package --pretty well any TWRP or OrangeFox custom recovery build will suffice.
For any members interested, I have updated this build to include Magisk v24.3, BusyBox v1.34.1, and I've done a bit more debloating and added some RAM tweaks on the kernel level. I'll need testers as I no longer own this device. Let me know by leaving a reply if you would like to test. I am posting a link in the downloads section for the updated ROM, but again I emphasize, this is of yet untested.
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Dees_Troy said:
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Click to expand...
Click to collapse
hey Awesome
thanks a lot ..
@modding.MyMind is the one that made the much appreciated alternative but an official channel is very much appreciated indeed
gierso said:
@modding.MyMind is the one that made the much appreciated alternative but an official channel is very much appreciated indeed
Click to expand...
Click to collapse
Yes, thanks to all. (Timestamp on backups appear accurate now. )
Dees_Troy said:
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
Click to expand...
Click to collapse
FYI, The TWRP Manager app doesn't have an "advanced" option in settings and MT2L03 isn't in the device name list yet so the program doesn't work to install the image. Installing via ADB works fine though. I'm sure it's just a matter of updating the app on the Play Store until it does list it though Many thanks for the official support! Even off-mode charging works! Very cool
One question: Are the backups that were created with the unofficial version of TWRP still compatible with this version if I want to restore a backup created in the other twrp with this one will it work?
arcadesdude said:
FYI, The TWRP Manager app doesn't have an "advanced" option in settings and MT2L03 isn't in the device name list yet so the program doesn't work to install the image. Installing via ADB works fine though. I'm sure it's just a matter of updating the app on the Play Store until it does list it though Many thanks for the official support! Even off-mode charging works! Very cool
One question: Are the backups that were created with the unofficial version of TWRP still compatible with this version if I want to restore a backup created in the other twrp with this one will it work?
Click to expand...
Click to collapse
Flashify works very well though. You don't need a computer or ADB after the bootloader is unlocked.
Sent from my MT2L03
What's the difference between this and http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144 ???
unofficial made before the official one got thru
15 devs got mt2l03s at the big android BBQ
So they are the same thing? Or do we need to flash this new one? And how do we get rid of the old one if we do? Sorry too many questions I'm a noob.
Sent from my MT2L03
hope there would be one for mt02-l01/2 too.
Dees_Troy said:
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Click to expand...
Click to collapse
Thanks for support the device into official TWRP build.
I just submitted an issue regarding the adb, hopefully the working adb can make the MTP/Storage troubleshooting easier.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/305
EDIT: 2015/01/17, please dis-regards above issue, today, I tested again the adb actually works fine.
Thanks again
xordos.
xordos said:
Thanks for support the device into official TWRP build.
I just submitted an issue regarding the adb, hopefully the working adb can make the MTP/Storage troubleshooting easier.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/305
Thanks again
xordos.
Click to expand...
Click to collapse
You are a life saver!!! I already did thank you so I will thank you again. I also used google drive so that really helps. I cannot save my backup to my external SD drive. Hope that will be solved in the near future.
husky55 said:
You are a life saver!!! I already did thank you so I will thank you again. I also used google drive so that really helps. I cannot save my backup to my external SD drive. Hope that will be solved in the near future.
Click to expand...
Click to collapse
There are 2 different twrp build/thread in this forum, so please be clear which one you are using. And actually both version support save backup to external sd.
The adb/mtp issue i mentioned above is related to PC connection. The twrp main functions are fully working already
xordos said:
There are 2 different twrp build/thread in this forum, so please be clear which one you are using. And actually both version support save backup to external sd.
The adb/mtp issue i mentioned above is related to PC connection. The twrp main functions are fully working already
Click to expand...
Click to collapse
I used the TWRP manager to install. However when it downloaded and installed it crashed. Something about if this is the folder in your HAM2, yes or no, when clicked no it exited, clicked yes and it crashed. So I rebooted the phone into recovery and lo and behold, TWRP is there for the very first time. I had no idea what version that is.
Prior to all this I used the TWRP installer from the Play Store. It installed some version of TWRP but when rebooted into recovery, it was the Android recovery which showed up and allowed no backup at all. I also have the ROM manager installed. That installed some version of TWRP also.
I spent lots of time trying to backup to my 32GB external SD but I do not see it as an option. I used TWRP before on my Samsung S3 so I am somewhat familiar with it and CWM. I was able to make a copy of the backup file into the external SD using ES file manager. Not sure I can restore from it. I really like to save the internal memory for other things.
I am tempted to flash the twrp.img version 2.8 from your google drive again but I am not sure how it's going to workout.
One last note, I read both threads you referred to and lots more. But for some reason I have a hell of a time for something so simple.
husky55 said:
I used the TWRP manager to install. However when it downloaded and installed it crashed. Something about if this is the folder in your HAM2, yes or no, when clicked no it exited, clicked yes and it crashed. So I rebooted the phone into recovery and lo and behold, TWRP is there for the very first time. I had no idea what version that is.
Prior to all this I used the TWRP installer from the Play Store. It installed some version of TWRP but when rebooted into recovery, it was the Android recovery which showed up and allowed no backup at all. I also have the ROM manager installed. That installed some version of TWRP also.
I spent lots of time trying to backup to my 32GB external SD but I do not see it as an option. I used TWRP before on my Samsung S3 so I am somewhat familiar with it and CWM. I was able to make a copy of the backup file into the external SD using ES file manager. Not sure I can restore from it. I really like to save the internal memory for other things.
I am tempted to flash the twrp.img version 2.8 from your google drive again but I am not sure how it's going to workout.
One last note, I read both threads you referred to and lots more. But for some reason I have a hell of a time for something so simple.
Click to expand...
Click to collapse
OK...Got you. So, I would suggest use the "fastboot flash recovery" command in ModdingMyMind thread, both image file can be used, but I prefer the fastboot way, so we can see what's the output.
Some people has issue re-install TWRP after upgrade to B148, that's why I refer you to
yeah, I forgot that, after update, twrp install may have issues, check this thread around post 169:
http://forum.xda-developers.com/show....php?t=2897452
Click to expand...
Click to collapse
which pretty much says this:
Originally Posted by Kid_Ding View Post
For anyone having issues flashing TWRP after udpate, boot into stock recovery and install update from external SD. The path is above. Then reboot and then reboot to bootloader and flash twrp. Thank @foltz61
Click to expand...
Click to collapse
So, basically you need re-install the B148 update using above particular method, then afterwards, re-flash the TWRP.
We can continue discuss in the other thread.
Cheers.
I installed the TWRP.img latest release from the TWRP web site using ADB fastboot. The file is 14.300 kb in size. TWRP is working properly. I made a recovery backup and restored it. I also had Xposed Installed and some modules installed. When the HAM2 is on and charging everything is normal. i.e working properly.
The problem is when the HAM2 is off and charging, suddenly TWRP started. I got the slide to Unlock from TWRP. There was nothing that I could pinpoint on that would cause this. I installed Boot Manager but it did not show TWRP as being a application which should or will start at boot up.
I know this is a minor annoyance but being trained technically it bothers me. Is there anything I can do to prevent TWRP from starting when plugging in the micro usb connector to a HAM2 in the shut down state.
yes, this is a known issue about off mode charging. we have v2 fixed it (it is in the google drive i shared) but we never release it. because the official twrp team build released in this thread and it works fine.
So now that school is over (for now), I finally downloaded this installer and the correct recovery for the phone, and now it is asking me this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it just asking me to verify that the path exists?
Sorry I installed twrp so long ago I don't remember. Are you sure you got the 2.8.0 for the right version? The 2.8.1 is for the 05's and not the USA 03's.
oncouch1 said:
Sorry I installed twrp so long ago I don't remember. Are you sure you got the 2.8.0 for the right version? The 2.8.1 is for the 05's and not the USA 03's.
Click to expand...
Click to collapse
There are 2 versions available for the MT2L03: 2.8.0 and 2.8.3. Both give me that same warning message. Can anyone help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 6. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-shamu.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_shamu_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 1 GiB of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Tasssadar/androi...ree/android-msm-shamu-3.10-lollipop-mr1-kexec
Donations
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Thanks to all donors, it is much appreciated
Downloads
1. Main downloads
MultiROM: multirom-20160207-v33-shamu.zip
Modified recovery (based on TWRP): TWRP_multirom_shamu_20160210.img
MultiROM Manager Android app: Google Play or link to APK
Kernel w/ kexec-hardboot patch (Stock 5.0 and 5.0.1): kernel_kexec_shamu_500.zip
Kernel w/ kexec-hardboot patch (Stock 5.1): kernel_kexec_shamu_510.zip
Kernel w/ kexec-hardboot patch (Stock 5.1.1): kernel_kexec_shamu_511-2.zip
Kernel w/ kexec-hardboot patch (Stock 6.0 and 6.0.1): kernel_kexec_shamu_601.zip
Kernel w/ kexec-hardboot patch (CM 12.0): kernel_kexec_shamu_cm12-02-50134cb9df.zip
Kernel w/ kexec-hardboot patch (CM 12.1): kernel_kexec_shamu_cm121-01-8f9e2418f2.zip
Kernel w/ kexec-hardboot patch (CM 13.0): kernel_kexec_shamu_cm13-01-677c36b09.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Mirror: http://d-h.st/users/tassadar
2. third-party kernels with kexec-hardboot patch
Nicely ask your kernel developer to merge kexec-hardboot patch.
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller-shamu.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
4. Flashable factory images ZIPs
I usually release flashable ZIP files based on new factory images from Google, so that you can have clean stock ROM as a secondary system in MultiROM. They are not rooted, no anything, except for occasional small tweaks to make rooting with SuperSU possible. You can find them in this folder on basketbuild or dev-host.
Changelog
Code:
MultiROM v33
=====================
* Updates for Android 6.0 compatibility
MultiROM v32b
=====================
* Add support for Android M preview (MPZ44Q). SuperSU 2.46 doesn't work on M
and breaks boot - don't flash it!
MultiROM v32a
=====================
* Fix pattern encryption password incorrectly reporting "invalid password"
when the pattern overlaps itself
MultiROM v32
=====================
* First stable release for shamu
Recoveries:
Code:
10.2.2016
=====================
* Fix ZIP selector being set to wrong storage after flashing ZIP to a
secondary ROM
9.2.2016
=====================
* Fix confusing "Unable to mount..." error message
* Fix flashing of some kernels into secondary ROMs (e.g. Elite kernel)
6.2.2016
=====================
* Update to TWRP 3.0.0 (big thanks to nkk71 for doing most of the work)
* Use Material theme made by z31s1g - thanks!
* Fixes for 6.0 compatibility
* Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (
[url]http://bit.ly/m_su[/url] ) or newer!
30.6.2015
=====================
* Update to TWRP 2.8.7
* Add option to duplicate secondary ROM into "Swap ROMs" section
6.4.2015
=====================
* First stable release for shamu
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very unsatisfying to work on code for device I don't have - I invest hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
At last, multirom is official for nexus 6!
Congrads Tasssadar!
Been testing this since its release. Always been awesome! Thanks Tasssadar. Been using MultiROM for awhile now.
So glad to see this finally get a thread. So thankful for your work Tasssadar. Innovative as well as functional, love it!
I've been waiting until our device got a thread to ask this question, anyone who knows, feel free to answer - Some ROMs require a wipe of /system in order to boot. I believe I understand the flashing instructions as I have read them numerous times - you factory data reset to clean flash, wipe cache to dirty flash. How would one boot a ROM that requires a wipe of /system into a secondary ROM slot? Or for those users who mess with a lot of /system stuff and like to wipe on every flash, is there a way to do this for secondary ROMs that I simply missed? Or should something about the way MultiROM is structured, i.e. "All ROMs are separate" from the FAQ, eliminate issues in terms of needing to wipe /system for secondary ROMs? I figure I would rather ask a question I don't need to than find out the hard way given this is not standard flashing and thus not inherently obvious.
Nice work, like with your previous Versions. This will be awesome to use especially with the 64GB variant!
Amazing work. Thanks for all of it. Hope you got your N6 RMA back!
@tassadar
I had this problem with the test releases also, but decided to keep it to myself since it was a test release, but the "key press to launch multirom" option in TWRP doesn't work. We obviously can't use volume down because that boots you into the bootloader, I've tried holding volume up while the phone is off and then pressing the power button, but it just continues to boot my rom.
brando56894 said:
@tassadar
I had this problem with the test releases also, but decided to keep it to myself since it was a test release, but the "key press to launch multirom" option in TWRP doesn't work. We obviously can't use volume down because that boots you into the bootloader, I've tried holding volume up while the phone is off and then pressing the power button, but it just continues to boot my rom.
Click to expand...
Click to collapse
That's exactly what testing releases are for - finding bugs and fixing them. Next time you spot something like that, report it right away, otherwise I might not even know about the problem
But somebody else reported the key-based autoboot not working, and unfortunately, on shamu, there is no way to tell if a key has been pressed before the kernel has booted up. I could add a short period of time when you could press the key and it would work, but then it would be the same as time-based autoboot. I will hide that option in next recovery release, so it doesn't mislead people.
Awesome work :good:
I'm waiting for miui / any other good custom ROM port for nexus 6
Atm we have only cm12 /stock based roms :3 .
Anyway thanks for bringing this to n6 :good:
Been running this a week or so works great for me, love being able to have a main rom and test out a bunch as a secondary.
Encryption on CM12?
Anyone else having trouble with encryption?
I had CM12 installed before today working fine with a pattern required on boot. Installed multirom, now I'm stuck at Multirom's pattern prompt, when I enter my pattern I get "Invalid Password" Wiped the device, including internal storage and reinstalled CM. Set a pattern again and it's stuck at the pattern prompt again.
So I'm gathering that if I want to run a ROM off a USB drive, I can format it to extX and then let the image size grow (or shrink) as needed, whereas if I use a drive formatted NTFS or Fat32 I have to decide up front the image sizes.
Did I get that right?
Following
YES!
Thank you Tass!!!
Quick questions: Would flashing kernels and other things normally be installed in the primary rom without any added steps? What about changing/updating the primary rom? Would wiping the phone wipe the primary rom only or all roms? Thanks
katyl said:
Anyone else having trouble with encryption?
I had CM12 installed before today working fine with a pattern required on boot. Installed multirom, now I'm stuck at Multirom's pattern prompt, when I enter my pattern I get "Invalid Password" Wiped the device, including internal storage and reinstalled CM. Set a pattern again and it's stuck at the pattern prompt again.
Click to expand...
Click to collapse
Ups, I forgot to fix it in MultiROM (had the same bug in TWRP's pattern entry, it's was fixed there but I forgot to do the same in MultiROM). Fixed in v32a.
demlv said:
So I'm gathering that if I want to run a ROM off a USB drive, I can format it to extX and then let the image size grow (or shrink) as needed, whereas if I use a drive formatted NTFS or Fat32 I have to decide up front the image sizes.
Did I get that right?
Click to expand...
Click to collapse
That's right.
C00lBeanz said:
Quick questions: Would flashing kernels and other things normally be installed in the primary rom without any added steps? What about changing/updating the primary rom? Would wiping the phone wipe the primary rom only or all roms? Thanks
Click to expand...
Click to collapse
Yes, just flash it as usual (in recovery, if you use fastboot to flash whole boot.img from some kernel, you'll have to flash MultiROM ZIP again or go to "Advanced->MultiROM->Inject curr. boot sector". Wiping your phone (if you mean going to "Wipe" and swiping the slider at the bottom for "factory reset") will wipe only primary ROM's data (it leaves /sdcard intact, and that's where the secondary ROMs are).
Tasssadar said:
That's exactly what testing releases are for - finding bugs and fixing them. Next time you spot something like that, report it right away, otherwise I might not even know about the problem
But somebody else reported the key-based autoboot not working, and unfortunately, on shamu, there is no way to tell if a key has been pressed before the kernel has booted up. I could add a short period of time when you could press the key and it would work, but then it would be the same as time-based autoboot. I will hide that option in next recovery release, so it doesn't mislead people.
Click to expand...
Click to collapse
Haha this is true! I just assumed you couldn't fix it if you didn't have a working N6, also don't remove that option because I don't know if you changed anything or not relating to that yet but I just saw an update in MRM and flashed it and now I can hold volume up to boot into MultiROM!!
Wow nice feature for N6! Are you planning to support more devices? E.g. Exynos Galaxy S III LTE? That would be awesome!
OrangeFox Recovery Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Redwolf fork
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
OrangeFox is FREE SOFTWARE
Supports Treble, Miui, Custom Roms
Download:
Click Here To Download
INSTALLATION:
0. Backup your ROM and all your files
1. Download the OrangeFox zip file to your device
2. Reboot to your custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
Frequently Asked Questions, MIUI OTA, Troubleshooting, and Sundry Information:
* See https://forum.xda-developers.com/showpost.php?p=79074141&postcount=2
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* ATG and Dadi11 - for Redwolf
* Kirillmaster4 - for graphics
* z31s1g - for TWRP theme
* All our testers - for your patience and help
* Wajid for whole testing ; )
FEATURES:
* Supports Treble and non-Treble ROMs
* Up-to-date Oreo kernel, built from sources
* Increased compatibility with TWRP
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM [only for some devices]
* Password
* Support for Miui and Custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Known Issue - Encryption & Decryption seems to be broken so flash always DFE to be on safe side
Screenshots - see below
Other useful information - see below
Sundry OrangeFox information
FAQ:
#0. I HAVE ENCOUNTERED A PROBLEM WHILE USING ORANGEFOX:
1. Provide the logs - and -
2. Provide a full explanation of precisely what has happened, and precisely how you got to that point.
3. If you do not provide both of these, then I will simply ignore any report of any problem. So, it is advisable to (a) learn how to take logs before trying anything, and (b) always take the logs before rebooting after using the recovery.
#1. INSTALLING ORANGEFOX RECOVERY FROM STOCK MIUI RECOVERY (adb/fastboot method):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Install adb, fastboot, and the relevant USB drivers onto your PC
2. Install the Mi Flash tool onto your PC
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Unlock your bootloader
7. Open up a command line window on your PC
8. Change to the adb directory on your PC
9. “Hotboot” OrangeFox by running the command:
Code:
fastboot boot recovery.img
10. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
11. Select “Install”, then find and select the OrangeFox zip, and swipe to install it
12. After installation, the phone will automatically reboot into OrangeFox
13. Enjoy!
#2. SETTING UP MIUI OTA:
1. Download the most up-to-date release of OrangeFox Recovery
2. Download a full MIUI ROM that will be the basis of your future MIUI experience, and copy it to your phone’s storage
3. Flash the OrangeFox Recovery zip with your current custom recovery (or follow the steps in the thread for installing from adb/fastboot)
4. Reboot into OrangeFox Recovery (this will have happened automatically if you flashed the OrangeFox zip)
5. Go to the OrangeFox settings, and enable these MIUI OTA settings -
a. Support MIUI incremental OTA
b. Include system in OTA survival
c. Incremental OTA signature verification
d. Aggressive stock recovery deactivation
e. Disable DM-Verity
7. Go to the “Wipe” menu, and wipe data, cache, and dalvik
8. Flash your full MIUI ROM. After the ROM is flashed, OrangeFox will start the "OTA_BAK" process, which will backup your system and boot partitions into the /sdcard/Fox/OTA directory. You must NOT delete any of the files in the /sdcard/Fox/OTA directory. If you do, then incremental OTA updates will most definitely fail.
9. Reboot your phone, and start to use your phone normally
10. When MIUI notifies you that there is an update, download the update, using the MIUI updater app, and allow it to reboot automatically to OrangeFox
11. OrangeFox will install the update automatically (this might take several minutes)
12. OrangeFox will reboot the phone automatically upon completion of the installation of the MIUI OTA update
13. After this, you will not need to flash a full ROM any more - just follow the steps in #10 above
14. If you want to move to a completely different version/build of MIUI, then you will first need to clean-flash the full ROM of that MIUI build, as described above.
#3. RETURNING TO A MIUI ROM FROM A TREBLE ROM:
A. Treble ROMs on many devices use MIUI’s “cust” partition for their vendor image. This process removes the Xiaomi proprietary files that are necessary for MIUI to run. These files must be restored, otherwise MIUI will not work properly.
B. For this purpose, the cleanest and easiest way to return to MIUI from a Treble ROM is to flash a full fastboot MIUI ROM, using the Mi Flash tool.
C. If you did not create a backup of your MIUI cust partition to MicroSD or USB-OTG before installing a Treble ROM, then you must use the method just described above (or else you can try flashing a stock vendor image for your device (if there is one for your device there))
D. If you DID create a backup of your MIUI cust partition (in the newest versions of OrangeFox, this would be the “vendor” partition – it points to the same location as “cust”) to MicroSD or USB-OTG, then you can use OrangeFox to install MIUI when coming from a Treble ROM - but you have to take certain steps:
1) Backup your internal memory to an external device (eg, MicroSD, USB-OTG, or your PC). DO NOT SKIP THIS STEP!
2) Copy the latest stable MIUI ROM to your MicroSD or USB-OTG storage
3) Boot OrangeFox
4) Make sure that OrangeFox can read your MicroSD or USB-OTG storage, and can see the MIUI ROM that you copied there. This is the ROM that you will install in the steps below.
5) Select the “Wipe” menu and wipe everything - system, dalvik, cache, vendor, etc (except MicroSD/USB-OTG)
6) Format data (“format” - not “wipe”) - you will lose all the contents of your internal memory after doing this
7) Reboot OrangeFox - you will see a message saying “No OS installed …” - just swipe to reboot OrangeFox
8) Restore the backup of your MIUI cust partition (in the latest releases of OrangeFox, this will need to be restored to the "vendor" partition)
9) Flash your MIUI ROM
10) Reboot to system, and wait for a long time ...
11) When ready, restore your backup of your internal memory from your external storage device.
#4. FLASHING ROMS:
Flashing a ROM is usually a straightforward process. You can either do a "clean" flash, or a "dirty" flash.
First things:
When flashing a ROM, you want to ensure that the recovery is in a known state, before you start flashing the ROM. Therefore, you should always observe the following:
1. Do NOT flash a ROM in a queue with other zips. Always flash a ROM on its own, and when flashing is completed, reboot OrangeFox, before doing anything else.
2. If you ever wipe the /vendor partition, then you must reboot OrangeFox immediately afterwards - before doing anything else (eg, flashing a ROM or anything else you might want to do).
3. If you ever wipe the /system, partition, then you must reboot OrangeFox immediately afterwards - before doing anything else (ignoring any warnings about no OS being installed).
4. If you ever format the data partition, then you must reboot OrangeFox immediately afterwards - before doing anything else.
5. If your Xiaomi device has ARB, and you are on a MIUI ROM, then you had better tread very carefully if you want to change your MIUI ROM to a different MIUI ROM, or to a different version of the same MIUI ROM. Search on Google for "ARB", read and understand everything, and then decide whether you really need to proceed.
6. Make a full backup of your current ROM - before performing any other operations in the recovery. At the very least, backup the /system, /data, /boot and /vendor partitions.
7. Please note that, if you do not follow all of the above instructions, and you encounter problems afterwards (which you definitely will), I will not answer any questions.
A. "Clean flashing" (Strongly recommended)
1) Backup your applications, settings, SMS messages, call logs, etc Do NOT skip this step.
2) Bootup OrangeFox Recovery
3) Select "Wipe"
4) Swipe to reset to defaults (this will restore the installed ROM to a known state, and will remove apps/settings that might be incompatible with the ROM that you wish to install)
5) Return to the main OrangeFox menu
6) Select "Install"
7) Choose the ROM that you want to flash
8) Swipe to flash.
9) Reboot OrangeFox recovery - before doing anything else - so that any changes to partitions/filesystems done by flashing the new ROM will take full effect
10) Flash whatever else you might want to flash (eg, GAPPs, magisk, etc)
11) Reboot your device
12) Wait for a long time while the new ROM sets itself up (go and make a cup of tea!)
13) Enjoy
B. "Dirty flashing" (NOT recommended)
1) Bootup OrangeFox Recovery
2) Select "Install"
3) Choose the ROM that you want to flash
4) Swipe to flash
5) Wipe cache and dalvik
6) Reboot OrangeFox recovery - before doing anything else - so that any changes to partitions/filesystems done by flashing the new ROM will take full effect
7) Flash whatever else you might want to flash (eg, GAPPs, magisk, etc)
8) Reboot your device
9) Enjoy
NOTE: Dirty flashing a ROM is NOT recommended. It can cause all kinds of random problems. Always choose to "clean flash"
#5. "YOUR SYSTEM HAS BEEN DESTROYED" scenarios:
A) If you have one of these, then, yes, you might be in deep trouble! But this has nothing to do with OrangeFox. It is rather a result of your decisions and what you have chosen to do, or to flash.
B) For possible solutions, Google is your friend.
C) Salient advice: next time, look very carefully before flashing anything. It is your responsibility to ascertain and completely understand, a) what you are installing, b) what instructions it is giving to the recovery, c) what it will do as part of the installation, and d) what it will do after the installation. Otherwise, there will be tears.
#6. MY DEVICE IS ENCRYPTED:
This is excellent. If your device gets stolen or lost, at least your data on non-removable storage is secure. But, if, for some reason, you would prefer for your data to not be secure, then you can remove the encryption by formatting your data partition (note - format - not just wipe). This process will also permanently delete all the contents of your internal storage. So, you had better backup your internal storage onto an external device before formatting - else, you can say "good bye" to all the photos, files, music, videos, etc, on your internal storage.
Note: ticking "Disable Forced Encryption" will most certainly not remove encryption from your device. That is not its purpose. The only way to remove encryption is to format your data partition.
#7. I GET "ERROR 7" WHEN TRYING TO INSTALL <whatever>:
* This is a very old problem, which has nothing at all to do with OrangeFox. So, Google is your friend.
* Hint: this is usually an issue with the "updater-script" inside whatever it is that you are trying to install. It is checking for a specific device (with "getprop ro.product.device"), but either finds an empty value, or finds another device. Check that what you are trying to install is the correct version for your device (run the previously mentioned "getprop" command yourself, from a terminal). If so, then speak to whoever released the zip installer that you are trying to install, and ask them to fix their script. If you wiped your system partition, reboot the recovery.
* Hint2: whenever this happens, take a copy of the recovery logs immediately (ie, before doing anything else) and post the logs when you are trying to report the problem. The recovery.log file will provide devs with a lot of useful information in trying to get to the bottom of what has happened. Reporting the problem without posting the logs would be a complete waste of everybody's time.
#8. I GET "ERROR 1" WHEN TRYING TO INSTALL <whatever>:
* This is a very old problem, which has nothing at all to do with OrangeFox. So, search Google.
.................................................. .................................................. ..........................
Other useful downloads/information:
• Android SDK platform tools (adb, fastboot, etc): https://developer.android.com/studio...platform-tools
• ADB, Fastboot, & Drivers: https://forum.xda-developers.com/sho....php?t=2588979
• Mi Flash tool: https://www.xiaomigeek.com/download-...lash-tool.html
• Xiaomi USB drivers: https://www.xiaomigeek.com/download-...r-windows.html
• How to install TWRP: https://www.xda-developers.com/how-to-install-twrp/
• How to install adb: https://www.xda-developers.com/insta...s-macos-linux/
Supported Languages:
cz.xml
de.xml
el.xml
en.xml
es.xml
fr.xml
hu.xml
in.xml
it.xml
ja.xml
nl.xml
pl.xml
pt_BR.xml
pt_PT.xml
ru.xml
sk.xml
sl.xml
sv.xml
tr.xml
uk.xml
zh_CN.xml
zh_TW.xml
Thank working excellent
:good: Very thanks, excellent work.
Latest build 9.0.1
09/03/19
Bugs
1) If am/pm in enabled time and battery are overlapping
especially when charging see pics
2)For Poco f1 use green color led option is useless
Question CPU temp is dropped ??
gogib said:
Latest build 9.0.1
09/03/19
Bugs
1) If am/pm in enabled time and battery are overlapping
especially when charging see pics
2)For Poco f1 use green color led option is useless
Question CPU temp is dropped ??
Click to expand...
Click to collapse
You can look, vendor mounts?
[email protected] said:
You can look, vendor mounts?
Click to expand...
Click to collapse
Yes
[email protected] said:
You can look, vendor mounts?
Click to expand...
Click to collapse
I don't understand
ihad no problem mount vendor even with older versions
Hi,
I have the same Problem with this.
It says that data is encrypted and asks for a password . But it isn't encrypted. Any idea?
The recovery installed before Was official twrp.
Thanks
StefanV3
Gesendet von meinem Poco F1 mit Tapatalk
Any ideas... Im confused with newest and Stable battle between 9.0 and 9.0.1?
indhimaga said:
Any ideas... Im confused with newest and Stable battle between 9.0 and 9.0.1?
Click to expand...
Click to collapse
Why not just use official twrp from twrp.me?
Does everything you need and doesn't force dfe on you.
dalyer said:
Why not just use official twrp from twrp.me?
Does everything you need and doesn't force dfe on you.
Click to expand...
Click to collapse
Just curious and wanna make this thing clearly... Some said 901 has a bug but another one said its no problem... Actually i used pitchblack twrp... And wanna try orange
dalyer said:
Why not just use official twrp from twrp.me?
Does everything you need and doesn't force dfe on you.
Click to expand...
Click to collapse
Hi,
i like the theme of orange fox...
But, i want to know what's wrong on my poco why it asks for password. I use pin for OS and when i enter pin in ofr it says password is not correct... Same with Google password...
Thanks
StefanV3
Gesendet von meinem Poco F1 mit Tapatalk
StefanV3 said:
i like the theme of orange fox...
But, i want to know what's wrong on my poco why it asks for password. I use pin for OS and when i enter pin in ofr it says password is not correct... Same with Google password...
Click to expand...
Click to collapse
Surely there's nothing wrong.
It's simply been encrypted by the most recent vendor that you flashed and thus asks for a PIN/password to decrypt it?
If I Flash this recovery my internal data will be wiped or not.
Olystem said:
If I Flash this recovery my internal data will be wiped or not.
Click to expand...
Click to collapse
no
dalyer said:
Surely there's nothing wrong.
It's simply been encrypted by the most recent vendor that you flashed and thus asks for a PIN/password to decrypt it?
Click to expand...
Click to collapse
But why no password with official twrp?
StefanV3
Gesendet von meinem Poco F1 mit Tapatalk
StefanV3 said:
Hi,
i like the theme of orange fox...
But, i want to know what's wrong on my poco why it asks for password. I use pin for OS and when i enter pin in ofr it says password is not correct... Same with Google password...
Thanks
StefanV3
Gesendet von meinem Poco F1 mit Tapatalk
Click to expand...
Click to collapse
When you flash vendor always flash dfe (disable force encryption) zip
just use the password that you used in the rom otherwise full format
Thanks Sai for info
blitzfire3 said:
When you flash vendor always flash dfe (disable force encryption) zip
Click to expand...
Click to collapse
IF AND ONLY IF you don't want encryption.
It's very bad advice to just issue a blanket recommendation to always flash dfe after flashing vendor!!!
Hi,
My password aren't working... Neither pin nor Google password does decrypt in ofr...
StefanV3
Gesendet von meinem Poco F1 mit Tapatalk
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here.
Boot with AB only. Seems this was due to some ROM compatibility issue and the FW of Samsung that time. Any Treble based ROM, based on our partition structure works now.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Snapshots!
Attaching few snapshots for the build and successful flash.
Akhil99 said:
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Click to expand...
Click to collapse
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
vdbhb59 said:
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
Click to expand...
Click to collapse
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
nareshfree said:
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
Click to expand...
Click to collapse
I flashed the GSI by PHH (phhusson), the FLOSS one.
https://github.com/phhusson/treble_experimentations/releases
There are few groups on TG. I am no longer on TG (left a week/2 ago). I am available here for anything.
System partition or System image?
veekay said:
System partition or System image?
Click to expand...
Click to collapse
Flash as /system image.. By system partition I meant the /system portion of the OS.
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
veekay said:
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
Click to expand...
Click to collapse
It is the system image. Dont have Samsung turned on or fully setup to give snap.
There you go.. /system image..
One suggestion. Even with GSI do not try to flash any experimental zips from say Android 9 on Android 10. I just landed on bootloop and had to reflash system Magisk and DM again.
I switched to Havoc. Much more stable and has loads of features..
Couple of Havoc snaps..
vdbhb59 said:
Couple of Havoc snaps..
Click to expand...
Click to collapse
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
MiyamuraNEET said:
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
Click to expand...
Click to collapse
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
vdbhb59 said:
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
Click to expand...
Click to collapse
This is a matter of time soon customs will appear!
MiyamuraNEET said:
This is a matter of time soon customs will appear!
Click to expand...
Click to collapse
True. Just waiting for it. Will see if I can get to help Akhil, Sahil and Aditya.
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
thvardhan said:
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
Click to expand...
Click to collapse
I do not use gaaps, so not sure, but it does stick around on several reboots as well. Only time it will go to bootloop if you try to manually place any file within "/system/app" and "/system/priv-app" folders. Somehow, it ticks boot and does not start beyond Android logo.
could you please tell which phh to download exactly
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
It would be very kind of you if yould could tell me exactly which phh to download from github?
---------- Post added at 09:34 AM ---------- Previous post was at 08:46 AM ----------
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
when I am installing twrp and then formating data and the rebooting to system it is causing bootloop.Please help
Note
Before getting started, I'm not a developer and I'm not on that level yet but being an enthusiast of Android ROMs especially my favorite ROM Pixel Experience (PE). However what I can contribute (as of now) is to guide newbies and answer people who is confusing with flashing PE ROM, any custom kernels, mods, Gcam and help you out from problems while trying these things.
Tons credits to @jhenrique09, without his great effort there is no born of Pixel Experience project, and we would not have a taste of stock and pure Pixel ROM without having an actual Pixel phone.
It is good that you attempt new things and seek into the freedom of pure Android experience, and the whole world of Android development, though there's some risk when you try something new.
!!! Warning: I am not responsible for any bricked devices, it is your choice to modify your device software.
Pixel Experience ROM official thread - by Henrique Silva @jhenrique09
How to unlock bootloader?
https://xiaomiwiki.github.io/wiki/Unlock_the_bootloader.html
Official ROM downloads:
Download from Pixel Experience website
Screenshots
Check telegraph here!
Pixel Experience Official Wiki Page for Redmi K20 Pro/Mi 9T Pro - Info about raphael & raphaelin
Appreciation to
@jhenrique09, founder and lead developer of Pixel Experience, and maintainer for raphael & raphaelin (Redmi K20 Pro & Mi 9T Pro Series).
@WasikFahim, a friend of mine who assists me for creating this thread.
Thanks to all developers I have been know so far.
And all developers and original creators of the attached files below and for all of the following posts.
Special thanks to @Sandeeep Kiran (TG handle @ sandeeep, due to request from him), who has proposed the idea of creating this new thread for me.
Reserved.
Nice Thread ?
How To Flash Custom Kernels
Hello Guys Hope You're Fine, Today We're Going To Learn How To Flash Custom Kernels In Recovery, So Without Further Due Let's Jump Into It:
I'm Using PitchBlack Recovery
Prerequisite:
*Backup Stock Kernel [Boot.img & Dtbo(Optional)] Image=> 1 & 2
Steps For Flashing Custom Kernels:
1.Go To Recovery.
2.For OF(Go To Files) For TWRP/PBRP(Go To Install). Image=> 3
3.Select Kernel And Swipe to Install. Image=> 4 & 5
4.Wipe Dalvic/Cache.(Optional)
5.Reboot To System.
Enjoy!!!!!! :good::fingers-crossed:
Here Are Some Recommended Kernels:
We Use LOS FOD Implementation.
Gaming & Decent Battery = F1xy
Battery Backup & Decent Gaming = Immensity
Decent Performance + Battery = Englezos (Less gaming)
Mods tutorials
ANX Camera
ANX Camera TWRP
ANX Camera magisk
Working version of ANX magisk: 185
48MP fix for ANX camera magisk module: 181
Which ones should I download? Check attached screenshots below this post.
How to install and setup MIUI camera on PE?
* For ANX Camera TWRP
1. Save zip file to internal storage (/sdcard) and reboot to recovery.
2. For orangefox go to "files", for TWRP or Pitchblack recovery go to "install".
3. Swipe button to install.
4. Reboot to system.
5. Give all permissions to ANX camera, launch and quit app for at least 3 times.
6. You're all done.
* For ANX Camera magisk modules
1. Save both camera and 48MP fix modules to internal storage (/sdcard).
2. Open magisk manager, hamburger icon on top left corner, modules, tap on "+" icon and find ANX camera zip.
3. Same goes with 48MP fix module.
4. Reboot, give all permissions to ANX camera app, then launch & quit app for at least 3 times.
5. You're all done.
* 48MP fix is already included in ANX Camera TWRP, do NOT flash the 48MP fix magisk module.
* No root needed.
+ Credits to ANX developers and contributors, @HSgod, @nuub1k, for porting and debugging MIUI camera to AOSP ROMs.
Custom boot logo
MS drive Downloads
Head to XDA thread for more info, credits for @mouhannadsukkar creating boot logo collection.
Disable force encryption
Force Encrytion and difference compared with decrypted storage
1. All ROMs have force encryption by default for now, which should be enabled while booting the device for the first time.
2. Therefore DFE, also known as "disable force encryption", which shall force the device to be decrypted (Use #-dfe to get the DFE file).
3. If you format data, it will decrypt the encrypted storage, while everything on data partition including internal storage, also known as /sdcard directory, will be erased.
4. However if you already got a decrypted storage, simply wipe data and internal storage won't have any effects, unless you do a format.
5. To keep the storage decrypted, if you want, you will need to flash DFE for every ROM and vendor update.
6. Format data only if you flash custom ROM from stock MIUI, if you want to keep your storage decrypted or you want encrypted without flashing DFE while flashing custom ROMs and vendors (if the ROM uses MIUI vendor).
7. In short formatting data is to remove encryption for an encrypted device.
How to flash DFE?
IMPORTANT: Please make sure you perform a data FORMAT (NOT wipe) via recovery before flashing DFE, otherwise device may end up with bootloop or stuck in bootloader! Everything including all files on internal storage will lost so please backup everything to elsewhere. You have been warned, I am not responsible for data loss.
1. Go to recovery and format data (NOT wiping it, the place where you will type "yes" and confirm formatting).
2. Since internal storage is purged too, copy DFE from your PC or OTG storage etc., flash via recovery.
3. The recovery console will ask you to press volume buttons for picking options, so the recommended key combination is:
+ (vol up)
- (vol down)
- (vol down)
+ (vol up)
4. Done, reboot to system and see if storage is decrypted.
F2FS
What is F2FS?
F2FS, which stands for "Flash-Friendly File System", it was invented by Samsung coorperation, mainly focus on improving random read/write efficiency of flash storage and somewhat extends its lifespan.
Notice!!!
Currently, almost all known custom ROMs support F2FS on cache and data partitions but not system for compatibility and disk quota reasons, usually there's no writing actions to system partitions except flashing/updating ROM or using root access to modify it so keep system partition as EXT4.
How to enable F2FS?
You will lose all of your data including internal storage.
1. In recovery, convert data partition to F2FS via advanced wipe, same for cache partition (Do not convert system partition to F2FS to avoid some possible problems).
2. Flash f2fs-patched-fstab.zip (attached below) via recovery.
3. Reboot.
Note: You will have to flash patch again whenever flashing/wiping vendor, otherwise you will stuck at boot animation.
Fix low microphone problem (magisk needed)
Description
Sometimes, you might feel the microphone sensitivity isn't good enough on AOSP ROMs including Pixel Experience, this might related to device tree (or source code) of K20 Pro/9T Pro series. For instance you make or pick a phone call, using voice call of some IM apps the other side might not hear you clearly, that's the time when you can have a workaround if you have magisk installed.
How to fix?
Same as you install any magisk modules via magisk manager.
magisk_iem_mic_gain_0.3.zip attached below.
Magisk manager recovery mode
What to do if my device stuck at boot animation?
Sometimes, your device might stuck at boot animation because you flashed a buggy magisk module, for obvious reasons you have to delete that for letting your device boot into OS, so what about removing it via recovery? That's how this zip comes - Magisk Manager Recovery Mode.
How?
1. Boot your device to recovery, flash provided zip file.
2. Go to advanced => terminal.
3. Type this command to launch program:
sh /sdcard/mm
4. Type l to list all installed magisk modules, locate the one which might causes the problem.
5. Type r, enter, then the name of module name as the output shown, case-sensitive!
For example:
module[]
You should type:
module
Then enter.
6. If you see there's an X inside brackets like:
module[X]
Then you're good to go.
7. Reboot your phone and that's it.
Troubleshoot and advanced guides
Stuck at bootloader
Sometimes when you flashed ROM, custom recoveries, or updating vendor and try rebooting your device thereafter, your device does not boot into system or recovery but fall into bootloader (fastboot) screen. This is due to verified boot of our device being triggered, so flashing a custom vbmeta will usually get the problem solved.
How to flash vbmeta?
You need a working PC or laptop, USB cable and install fastboot driver if you are using Windows.
1. Download attached vbmeta file to your PC, connect your phone with USB cable, make sure PC has detected the phone and it's connected properly.
2. Open CMD (if using Windows) or terminal (Linux/Mac).
3. Type the following command:
Code:
fastboot flash --disable-verity --disable-verification vbmeta fake_vbmeta_williamfeng.img
4. Reboot your device to either recovery or system, it should work fine now.
Upgrade vendor
Note: You will not lose your data so you don't need to wipe anything, just flash vendor on top of current one, no matter if device is encrypted
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Reboot to system.
Downgrade vendor
Note: Before you downgrade your vendor you're suggested to backup all your data (including internal storage) elsewhere in case you lose them while doing so.
If your device is decrypted (NOT encrypted), the steps are same as you upgrade vendor.
Otherwise:
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Format data partition in your recovery (the place where you'll type "yes" and confirm formatting).
5. Reboot to system.
How to update PE ROM?
You don't need to download full zip file on PE, it gives small OTA which can be downloaded from "settings => system => system updater". After downloading simply tap on 'apply/install update', then the device will boot into recovery, update and reboot back into system.
WARNING: Make sure your device always have enough charge (30% or more is suggested) for updating process.
* The update file will be downloaded to /data/system_updates
Error 7 when updating PE
- If you see updating ROM doesn't work and the recovery shows you error 7, please make sure you update vendor to correct one first.
- Try updating your recovery (TWRP/OFOX).
If it still happens, try flashing full ROM zip of latest build instead of using built-in updater from ROM.
Miscellaneous info of Pixel Experience
Changing animation of Pixel Experience - just like you have a real Pixel device!
Power-off your phone and plug into changer, you'll see that.
Video link