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:
https://drive.google.com/open?id=14YHXZtT2PCxrYY15z64Ho49HUdqESvNb
INSTALLATION:
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=77857767&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
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
* Built-in support for installing SuperSU (v2.82-201705271822 - non-Treble ROMs only)
* AromaFM
* 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!
Screenshots - see below
Other useful information - see below
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Xiaomi Poco F1
Contributors
DarthJabba9, MrYacha
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Current Stable Version: R9.0
Stable Release Date: 2018-02-15
Created 2018-09-21
Last Updated 2018-02-15
FAQ:
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 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 PCs 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. If your installed ROM is MIUI, then you can optionally go to the OrangeFox menu and install magisk or supersu
14. 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 phones 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 use MIUIs 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.
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:
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 (when you are preparing to flash a ROM), then you must first reboot OrangeFox - before flashing the ROM (that is - if you want OrangeFox to patch dm-verity and forced-encryption successfully).
3. Please note that, if you do not follow both 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. Other useful downloads/information:
Android SDK platform tools (adb, fastboot, etc): https://developer.android.com/studio/releases/platform-tools
ADB, Fastboot, & Drivers: https://forum.xda-developers.com/showthread.php?t=2588979
Mi Flash tool: https://www.xiaomigeek.com/download-xiaomi-mi-flash-tool.html
Xiaomi USB drivers: https://www.xiaomigeek.com/download-xiaomi-usb-driver-windows.html
How to install TWRP: https://www.xda-developers.com/how-to-install-twrp/
How to install adb: https://www.xda-developers.com/install-adb-windows-macos-linux/
7. 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
OrangeFox R8.3
* Improved support for disabling DM-Verity
* Improved support for f2fs formatting
* Improved support for installing Pie ROMs
* Enabled FBE (Default Pie Encryption)
* Fix notch mode
* No random freezes
* Fix vibro
* Support OTA update
* Update Magisk to v18.0 stable
* Bug fixes
OrangeFox R9.0 changelog:
* Major UI redesign, new OrangeFox logo.
* Support for disabling auto-reboot after incremental MIUI OTA updates.
* Updated the flashlight section (support more devices).
* Updated the led section (support more devices).
* Leds are now used correctly.
* Added green led feature (for devices that support it).
* Updated notch mode - now statusbar settings for devices with a notch are hidden.
* Fixed bug when welcome text can't be translated.
* Fully rewrote all translations from scratch - by our Crowdin page (thank to all translators).
* Fixed problem with formatting MicroSD cards to FAT/vFAT.
* Improved MIUI detection.
* Improved Treble detection.
* Updated Magisk, Magisk Uninstaller to 18.1.
* Added support to patch DM-Verify in new devices.
* Updated mkbootimg / unpackbootimg.
* We drank coffee and tea.
* Added magiskboot as alternative (enable when building).
* Added feature "Prevent auto reboot after installing OTA".
* Fixes in MIUI OTA mechanism.
* Removed SuperSU, Cam2API.
* Extended info in console.
* Support give info after decryption.
* Fixed load settings with FBE.
* Support non-Xiaomi devices as well
* Added bash shell.
* Fixed issues relating to ramdisks compressed using lzma compression.
* Busybox xz and lzma replaced with stand-alone versions - better compatibility and speed.
* Support toolbox / toybox.
* AromaFM moved to "/sdcard/Fox/FoxFiles/".
* Copy recovery log to /sdcard/Fox/ directory before every reboot.
* Many bug fixes.
UI Changes:
* Remove dark background from statusbar.
* Updated "About" page.
* Moved the tabs to the bottom the page.
* Updated navbar icons for all colours.
* Updated accent navbar.
* Use pixel style navbar.
* Pixel style lockscreen; now lockscreen show time, cpu temp and battery info.
* Bug fixes in themes mechanism.
* Updated all pages of OrangeFox UI Center.
* Updated Square buttons style.
* Added setting for using Green led.
* Redesigned the MIUI OTA page, use float info button.
* Use new fload "Add to queue" button in install zip page.
* Moved debug settings on settings page.
* More space for partition selector on backup, install, restore pages.
* More space for timezones.
* Fixed corner on Install button when 'Square button style' is active on 18:9 devices.
* Fixed white line on navbar on 18:9 devices.
* Fixed slider dot placement on 18:9 devices.
* Fixed splash image on 18:9 devices.
* Changes on Vibration page (looks much better).
* Now the buttons in reboot page turn dark when you click on them.
* Redesigned splash image (Thanks to KMP Design).
Device-specific::
- [riva, whyred, markw, beryllium]: Fixed and enabled flashlight
- [whyred]: support for F2FS
- [vince, kenzo, rosy]: updated kernel
- [beryllium]: FDE Fixed, notch mode, low screen brightness fixed, no lags, kernel updated
- [mido]: Updated blobs
- [tulip, markw, rolex, polaris, hermes, rosy, ysl,
kagura (Sony Xperia XZ), hannah (Motorola Moto e5+), pettyl (Motorola E5 Play GO) ]: Ready to be stable!
- [oxygen]: Drop official, now we will provide test-builds for it
- [platina, x00t, cheeseburger]: Test builds
Wow I've used this on redmi note 5, can't wait to try it on Poco as well:laugh:
Cool,
One hell of an instructions list
Does data decryption works??
Pourush Sharan Bhargav said:
Does data decryption works??
Click to expand...
Click to collapse
Yes. You need check it in OrangeFox menu - Disable Forced Encryption
How about returning to miui from custom rom. Can I just clean install miui?
Sent from my Xiaomi Poco F1 using XDA Labs
Awesome
Thanks for great work
I'm on the MIUI 10 8.9.20 beta and tried to update to 8.10.11 via OTA but it failed in recovery saying you need to first flash a MIUI rom. Can someone help me how to fix it??
Pourush Sharan Bhargav said:
I'm on the MIUI 10 8.9.20 beta and tried to update to 8.10.11 via OTA but it failed in recovery saying you need to first flash a MIUI rom. Can someone help me how to fix it??
Click to expand...
Click to collapse
dirty flash MIUI 10 8.9.20 and you can update ota :fingers-crossed:
Nice.. complete guidance. TQ
flash zip file from other twrp and reboot to orange fox recovery getting 0mb storage, did format data getting 0mb storage too..
I was suffering from the lack of miui ota with twrp so long. Thank you so much!!!
Can you provide the files needed in OTA folder?
flash zip file from other twrp and reboot to orange fox recovery getting 0mb storage, did format data (yes) getting 0mb storage too... any solve? already 3 times clean flash????
ronks888 said:
Yes. You need check it in OrangeFox menu - Disable Forced Encryption
Click to expand...
Click to collapse
So that means it supports DISABLING encryption; but not actually decrypting.
Also, does Aroma FM even work? I thought it only supports fb0 graphics (same as Aroma Installer) which means it will never work on newer drm graphics kernels. If so, may as well remove it.
I extract the recovery.img and flashed image from my previous twrp . And it's good to go. No issues.
can someone tell me whats differences between orange fox and red wolf ? which one is better . is it worth switching over from twrp ?
Aroma FM doesn't work for me
Related
{
"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"
}
OxygenOS 3.1.4 Stable
for
OnePlus One - A0001
Based on Official OPX Marshmallow release
►Official Changelog◄
DISCLAIMER
Code:
/*
* I am 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD OR THE ONE ON ONEPLUS FORUM, IF YOU LIKE MY WORK, YOU CAN SAY THANKS.
*
Whats Working?
• Everything
Bugs
• Sim detection takes time. FIXED IN 3.1.4
• long press and double tap key actions don't work. FIXED IN 3.1.4
• When the software buttons are turned on, the hardware buttons stay active and can also be used. (Solution in Downloads below) FIXED IN 3.1.4
• You can't change priority/no notifications due to there being no alert slider. FIXED IN 3.1.4
• If you see screen overlay detected when an app asks for some permission, let the toast notification finish and then allow or give that app storage permissions manually from app info.
There are three flashable zip's to choose from and all of them have the following in common.
• Ported TWRP 3.0.3-2 Recovery (TugaPower)
• H2OS firmware
• GApps comes baked in as a part of OxygenOS System
Main Differences
► OPO-OxygenOS_3.1.4_Stock
• Does not have root/xposed/magisk
► OPO-OxygenOS_3.1.4_SuperX
• Systemless SuperSu
• Systemless Xposed
► OPO-OxygenOS_3.1.4_MagiX
• Magisk
• Systemless Xposed
• Systemless phh's SuperUser
Flashing Instructions
• Reboot to recovery (TWRP preferred)
• Backup existing OS if any
• Wipe - system,data,dalvik/art cache, cache
• Flash downloaded zip
• reboot device
DOWNLOADSGoogle Drive links ►
OPO-OxygenOS_3.1.4_Stock_05FEB2K17.zip
MD5 - 7092e1678cb28845dc6076228ed10aea
OPO-OxygenOS_3.1.4_SuperX_05FEB2K17.zip
MD5 -6c59c722c6a3ce99f38cce9b54c7c36f
OPO-OxygenOS_3.1.4_MagiX_05FEB2K17.zip
MD5 - 2397d57b51f651de5ecc7a00b8320688
Kernel Source : oneplus_kernel_msm8974
Telegram Group : OxygenOS 3.1.4 Port - OPO
F.A.Q
► OMG!! OTA Update Available, what should i do?
> As there is no official OxygenOS (MM) release for bacon, we wont get updates officially. So i decided to remove the official OTA system and integrate another for my port which you will see on the 11 DEC 2016 release, so if you get an update then its from me & not OnePlus.
Flash and stay Oxygenated
► When will there be another Update for this PORT?
> Only when OnePlus Updates it for the X, else only in case a bug is fixed.
► NOOO!! What happened to my recovery? It wont boot anymore!!
> Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.
Video Credits Game of Roms
Screenshots
CREDITS
Myself for porting, fixing bugs and Custom Kernel.
OnePlus for the X and the bacon
OnePlus development team.
Sultanxda, Lord Boeffla, nikhil18, amardeep434 for their kernel contribution for bacon.
Chainfire for SuperSu.
rovo89 for Xposed framework.
topjohnwu for Magisk - The Universal Systemless Interface also for Systemless Xposed.
DVDandroid for Materialized Xposed Installer
phhusson for phh's SuperUser/ OpenSource SELinux-capable SuperUser.
danieldmm for TWRP recovery & TugaBrowser
pradeepsmehra for all the previous OxygenOS port's.
Changelogs
### 05 FEBRUARY 2017
* Fix SW home key touch delay
* Chrome 56 replaces TugaBrowser
* Strip system of bloats
* New power off charging animation
* Updated Modem (Nov 2016)
### Hybrid Kernel v0.20S
* Introduce F2FS
* MSM Limiter (Per-Core Control)
* Hotplug and Wakeup Boost
* Disabled MPDecision
* 5 Custom hotplugs
* Default Hotplug: MSM Hotplug
* Kernel Security Improvements
* Improved Fast Charging
* Many other Optimizations and fixes
* Root needed to Configure the Kernel
Old changelogs
UPDATE TO FIX ISSUES WITH BATTERY DRAIN
Existing users can download OTA directly from the inbuilt OTA System.
20-DEC-2016
### All 3 Variants
• Correct Regulatory info for Bacon
• Update Hybrid Kernel to v0.14-S
• Enable MPDecision
### Hybrid Kernel v0.14-S
• CPU oc to 2.88 GHz for SuperX and MagiX, Stock stays at 2.45 GHz.
• Fixed Battery Drain issue
• Removed Blu_plug
• Switch to MPDecision
• Improve KCAL
• Add Sweep2Wake
• Disabled some wakelocks
• Update I/O Scheduler's
• More custom governor's
• Many other optimizations and fixes
• Use KAMOD to configure the Kernel. (SuperX and MagiX Only)
11-DEC-2016
### All 3 Variants
• Fix Button remapping
• Add DND tile to QS
• Add proper WiFi band selection in Settings (2.4 and 5 GHz)
• Add OTA System
• Add Hybrid Kernel v0.13-S
• Improve Sim detection
• disabled mpdecision (idiotic freq jump)
• Bacon optimizations
• Fixed Slow Charging
• Add Vibration control (use KAMOD)
• Add KCAL
• Use blu_plug instead of mpdecision
• Many other optimizations and fixes
• Use KAMOD Configure the Kernel
### SuperX
• SuperSU v2.78 SR5
• Xposed Framework v87
### MagiX
• Magisk v9 and Magisk Manager v2.5
• phh's SuperUser r266-2 (Magisk)
• Xposed Framework v87 (Magisk)
13-NOV-2016
Port Updated to Official 3.1.4
Official Changelog can be found here.
• Sim detection is fixed and now sim should detect immediately
• Only Stock is updated to 3.1.4
• Flash SuperSU_v2.78_SR3_Systemless.zip if you want root
• Chrome replaced with TugaBrowser and Power Toggles
• Clean flash is required if you are coming from 3.1.3
• Zip size reduced to some extent.
• Fixed OnePlus System FC (rare case)
• Xposed flashes successfully but activating modules + reboot causes system to not boot anymore.
If you want to use xposed stay with 3.1.3 (SuperX or MagiX)
• SuperX and MagiX delayed for now because of Xposed, last is 3.1.3.
• There are some issues with the custom kernel, its been delayed but not cancelled so stay tuned.
• 3.1.3 (SuperX and MagiX) will be updated later with the current bug fixes if xposed refuse to function properly.
07-OCT-2016
• MagiX - Magisk v7 + Xposed 86.6 + phh's SuperUser r259
• SuperX - Now there's Xposed with SuperSu
• An app called Power Toggles has been added for SuperX and MagiX users, open the
app > notification > switch it on > customize > add toggle > select volume toggle >
touch done. You can also customize it to your liking.
• You can flash SuperX/MagiX/Stock over each other and not have any issues.
• Buttons remapping has been disabled for good in settings, use gravity box for
mapping the buttons. (its not that hard >_>)
• AFAIK 5GHz WiFi worked in previous port update, so it works now too.
• Charging is the same as previous update. ( Around 1200 mA )
• Button lights fixed and Zips to Disable/Enable keys added to downloads.
• WiFi draining your battery? Don't worry its a minor bug which is easily solvable.
- Open settings
- Backup & reset
- Network settings reset
- Reset settings
- Enter password/pin/pattern if any
- Reset settings
- Reboot your device.
• If you have flashed any additional zips over the previous MXRS or SUS, please do a clean installation of MagiX and SuperX.
01-OCT-16
Port Updated to 3.1.3
Official Changelog
Port Changelog
• HW key lights have been turned off, to enable them just edit the build.prop and change the value of
persist.sys.button.backlight from 0 to 1.
• STFU Silent Mode Widget has been added to the MXRS zip, this will help with switching between silent, vibrate and ringer mode. To use it you will need to add the widget to the homescreen of the launcher. SUS and STOCK users will need to install the app from Play store.
Download Links Updated...
Downloading now to test. Question though: is there a difference with the systemless supersu your posting to the actual supersu released by chainfire?
the_rooter said:
Downloading now to test. Question though: is there a difference with the systemless supersu your posting to the actual supersu released by chainfire?
Click to expand...
Click to collapse
There's no difference except in the installation script of the included supersu zip.
Normally SuperSu will install into system and the rom won't boot, so made a small change in the installation script to make it systemless.
SYSTEMLESS is set to true.
deadlyindian said:
There's no difference except in the installation script of the included supersu zip.
Normally SuperSu will install into system and the rom won't boot, so made a small change in the installation script to make it systemless.
SYSTEMLESS is set to true.
Click to expand...
Click to collapse
there is already a systemless supersu? or are u saying when it doesnt the script it only will do system?
the_rooter said:
there is already a systemless supersu? or are u saying when it doesnt the script it only will do system?
Click to expand...
Click to collapse
http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Untouched SuperSu v2.78 SR1 :
This zip auto installs into system or keeps it untouched depending on the rom.
Included SuperSU v2.78 SR1 in my SUS variant :
Installation script is forced it to do its stuff without touching the system partition, this is required for OxygenOS for now, else SuperSu installs into system and the OS wont boot.
Thanks for your work. You are awesome..
@deadlyindian nice rom, using it since yesterday.By the way v3.1.3 ota update is available, any plans to port the update too.?
baconxda said:
@deadlyindian nice rom, using it since yesterday.By the way v3.1.3 ota update is available, any plans to port the update too.?
Click to expand...
Click to collapse
Already on it :good:
i was so happy i can test it but no, every Oxygen OS rom i tried was hardbricking my phone. so what is wrong?
MorcSK said:
i was so happy i can test it but no, every Oxygen OS rom i tried was hardbricking my phone. so what is wrong?
Click to expand...
Click to collapse
So you are doing something wrong
By the way, oxygen os still charging slow. That makes me hate from OOS..
No, i did everything correct. After reboot from recovery phone vibrates and the screen not even lights up. I actually have cm11s with TWRP 3.0.2-0. Should i try to flash recovery from zip and try again?
MorcSK said:
No, i did everything correct. After reboot from recovery phone vibrates and the screen not even lights up. I actually have cm11s with TWRP 3.0.2-0. Should i try to flash recovery from zip and try again?
Click to expand...
Click to collapse
Flash twrp 2.8.6.0, wipe ur system, data, cache, dalvik cache and then flash rom. That will work for sure. Maybe ur twrp version is not flash firmware correct. That would cause issues.
Fataldose said:
Flash twrp 2.8.6.0, wipe ur system, data, cache, dalvik cache and then flash rom. That will work for sure. Maybe ur twrp version is not flash firmware correct. That would cause issues.
Click to expand...
Click to collapse
Even with TWRP 2.8.6.0 hardbricked......
MorcSK said:
Even with TWRP 2.8.6.0 hardbricked......
Click to expand...
Click to collapse
How come? I just did same thing hours ago..
Fataldose said:
How come? I just did same thing hours ago..
Click to expand...
Click to collapse
Again back on CM11a but it is weird that it doesn't want to work. I was trying to install it yesterday on multirom with multirom it froze on opo logo
MorcSK said:
Even with TWRP 2.8.6.0 hardbricked......
Click to expand...
Click to collapse
You didn't hardbrick. If u hard bricked it wouldn't be recoverable. You are definitely doing something wrong because I used 3.0.2 and it installed perfectly fine.
i don't think so.... because on http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 is:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Click to expand...
Click to collapse
MorcSK said:
i don't think so.... because on http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 is:
Click to expand...
Click to collapse
Incorrect....
http://forums.androidcentral.com/an...-what-difference-between-hard-soft-brick.html
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"
}
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
Downloads:
Mega: OrangeFox R11.0 - 2020.07.20
Documentation and Frequently Asked Questions: https://wiki.orangefox.tech/en/guides
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
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; Installation from stock recovery; MIUI OTA; Troubleshooting; Sundry Information:
* See
1. https://wiki.orangefox.tech/en/guides
2. https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Flashlight
* Password, torch, led
* Support for Miui and Custom ROMs
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Screenshots
See https://files.orangefox.tech/Screenshots/R10/
Other useful information - see below
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Xiaomi Mi 5X
Contributors
Magical Unicorn
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Current Version: R11.0
Created: 2020-02-15
Last Updated: 2020-07-20
Changelog: OrangeFox.
OrangeFox R10.1 (2020.02.15) :
Code:
• Save historic logs (compressed zips) - to the /sdcard/Fox/logs/ folder
• Now all logs will be placed in /sdcard/Fox/logs/
• Added support for incremental MIUI OTA on newer devices (eg, lavender, violet)
• Better support for system-as-root
• Improved support for Android 10
• Improved support for MIUI 11
• The default setting for the "Disable DM-Verity" and "Disable Forced-Encryption" boxes is to untick them. This is necessary because, first, the latest stock MIUI ROMs based on Android Pie or Android 10 are not happy at all with disabling DM"-Verity" (incremental MIUI OTA updates will fail, and there may be other issues); secondly, the recent stock MIUI ROMs may encrypt your device anyway, and ignore all settings to stop this behaviour; thirdly, some recent AOSP-based ROMs are not happy at all with disabling DM-Verity or Forced-Encryption. Thus, anybody who chooses to enable these settings must tick those boxes manually before flashing ROMs (maintainers for very old devices may have kept the original defaults, because old devices with MIUI based on older Android releases do not have this problem)
• The Magisk addon has been updated (now Magisk v20.1)
• Handle "Android Rescue Party" messages
• More detailed information is now provided about the installed ROM (if any)
• Harmonise some sources with stock twrp
• Encryption: don't try wrapped key if not needed
• Encryption: cryptfs: add support for keymaster 2
• Fixed issues with app manager
• Disabled some unnecessary warnings for custom roms
• Added Ukrainian, French and Vietnamese languages
• Updated all other languages
• Lots of little fixes
Reserved.
Problems
I reboot and it's not change into new Recovery (OrangeFox), Why
I use Evolution Rom 3.5 Android 10
chaiwat89752 said:
I reboot and it's not change into new Recovery (OrangeFox), Why
I use Evolution Rom 3.5 Android 10
Click to expand...
Click to collapse
Please be more precise, with things like "it not work" it will be hard for me to help you.
What did you do exactly ?
Have you followed the install procedure from thread ?
OrangeFox updated (2020.05.03) !
Device changelog:
Code:
• Device Tree updated from 8.1 to 9.0.
• Some minor other improvements.
OrangeFox updated (2020.05.04) !
Device changelog:
Code:
• Add a1kto5x, a1to5x, a1to5x10, a1to5x10+.
• Add SAR build ([I]For Android 10 ROMs only ! For older Android version ROMs use the normal build[/I]).
OrangeFox updated (R11.0 - 2020.07.20) !
Changelog: OrangeFox.
Code:
• Merged R10.2 changes
• Merged latest TWRP changes
• Match Android Q design guidelines
• Gesture navigation
• Multiselection: supports copying, moving, deleting multiple files
• View size and date of files in file explorer
• Show backup size when selecting partitions and predicted average time of backup
• Tap on title in file manager to open storage menu
• Tap 3-dot icon to access multiselection and file manager settings
• Gray theme replaced with theme from Google Clock
• New fonts: MI LanPro (MIUI Font), Euclid, Fira Code, Exo 2
• Font weight customization
• Full screen console
• Add brightness slider and flashlight to console
• Quickly add Magisk when installing ZIPs
• Use checkboxes to input chmod permissions like in Android file managers
• Splash redesign, simple splash customizator
• Fancy decryption page
• Better UX while searching
• Generate digests after backup
• Advanced security: ADB and MTP unaccessible during boot (on some devices)
• Ability to flash ramdisk/kernel and fix recovery bootloop (for AB devices)
• Magisk improvements, removed Magisk v18 support
• Added hints
• Many others UI/UX fixes and improvements
So thanks for alive our device
Code:
/*
* Your warranty is now void.
*
* I am 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 ROM
* before flashing it! YOU are choosing to make these modifications,
*/
{
"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"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI crafted by @SKULSHADY.
Many useful features that will blow your mind.
All you can dream of and all you'll ever need.
Just flash and enjoy...
Code:
[SIZE="3"][SIZE="3"][B][U]General:[/B][/U][/SIZE]
Material Design 2 UI
Android R Style Screenrecord Dialog
Rounded UI
Inbuilt GApps (optional)
Face Unlock
Enhanced QS Battery Estimation
Lockscreen Clocks
Font Customisation
Dark Theme Support for AOSP apps
Notification LED Settings
Pixel Lockscreen weather
Signature Spoofing
Micro-G support
Lockscreen charging animation
[SIZE="3"][B][U]Status Bar:[/B][/U][/SIZE]
Clock & Date Settings
Custom Logo
Brightness Control Gesture
Double Tap to Sleep
Network Traffic Indicator Settings
Carrier Label Settings
Battery Icon Style/Percentage Settings
Status Bar Icons Toggle
HD/VoLTE Icon Toggle
4G/LTE Icon Toggle
Data Disable Icon Toggle
Roaming Indicator Toggle
Small Mobile Type Icon Toggle
Bluetooth Battery Status Toggle
[SIZE="3"][B][U]Quick Settings:[/B][/U][/SIZE]
Quick Pulldown
Smart Pulldown
Battery Estimates Toggle
Background Opacity
Background Blur Configuration
Header Image Configuration
QS Customisations
Rows/Column
Tile Title
Vibrate on Touch
Brightness Slider Customization
Brightness Slider On Bottom/Top/Hidden
Auto Brightness Icon
Brightness Control Buttons
QS Footer Customization
Settings Icon
Running Services Icon
Edit Icon
User Switcher Icon
[SIZE="3"][B][U]Ambient Display:[/B][/U][/SIZE]
Show/Hide Battery Level
Ambient Options
Always On
Always On When Charging
Wakeup On New Notifications
Wakeup on New Music (Music Ticker)
Sensor Based Screen Wakeup (Tilt/Hand Wave/Pocket)
Double Tap for Ambient Display
Ambient/Always On Display Brightness Configuration
[SIZE="3"][B][U]Screen:[/B][/U][/SIZE]
Corners Customisation
Rounded Corner Radius
Corner Content Padding
Legacy App Scaling
Force Higher Aspect Ratio for Selected Apps
[SIZE="3"][B][U]Buttons:[/B][/U][/SIZE]
Navigation
Nav Bar Toggle
System Navigation Type
Arrows Keys
Volume Buttons
Swap Keys
Volume Steps
Long Press to Seek Tracks
Keyboard Cursor Control
Volume Rocker Wakeup
Volume keys Answer Call
Power Button
Power Menu Customization
Lockscreen Options
Visibility on the Lockscreen
Reboot
Advanced Reboot
Screenshot Option
Screenrecord
Screen-Off Torch
Double Tap Power Button
Long Press Power Button
Back Gesture
Arrow Animation toggle
Long Swipe Type (Swipe and Hold/Swipe Edge to Edge)
Long Swipe Timeout
Long Left/Right Swipe Action
Haptic Feedback toggle
[SIZE="3"][B][U]Gestures:[/B][/U][/SIZE]
Jump To Camera
System Navigation Settings
Prevent Ringing Gesture
Swipe To Screenshot
Touchscreen Gestures
[SIZE="3"][B][U]Lockscreen:[/B][/U][/SIZE]
Double Tap to Sleep
Media Cover Art
Media Cover Art Blur Level
Music Visualiser
Unlocking
Pocket Detection
Fingerprint
Screen Off FOD
Show Icon
Recognizing Animation
FP Authentication Vibration
FP error Vibration
Elements Customisation
Status Bar
Quick Settings
Lock Icon
Charging Info
[SIZE="3"][B][U]Notifications:[/B][/U][/SIZE]
Flashlight
Blink for incoming call
Blink for Call Waiting
Screen
Edge Lighting Customisation
Status Bar
Heads Up
System
FC Notifications
Misc
Kill App Button
Noisy Notifications
[SIZE="3"][B][U]Animations:[/B][/U][/SIZE]
Animation Duration
System Animation customization
QS Tile Animation Customisation
[SIZE="3"][B][U]Battery Saving:[/B][/U][/SIZE]
Smart Pixels
Suspend Actions
[SIZE="3"][B][U]Miscellaneous:[/B][/U][/SIZE]
Gaming Mode
Wake Up on Charge
Charging Animation
Screenshot Type (Full/Partial)
Adaptive Playback
Playback Timeout (30sec/1min/2min/5min/10min)
[SIZE="3"][B][U]Other Features:[/B][/U][/SIZE]
Vibration & Haptics Customization
LiveDisplay
Notch Hide Settings
Seperate ringtone for SIM1&2
Screen Refresh Rate (For Supported Devices)
ALways On Display
Smart Charging
Theming
Styles and Wallpapers
Dark Theme
Accent Colour
Icon Shape
[SIZE="3"][B][U]QS Tile Shortcuts:[/B][/U][/SIZE]
Heads Up tile
Caffeine tile
CPU info tile
Smart pixel tile
Live Caption
Screenrecord tile
Gaming Mode tile
Screenshot tile
LTE tile
Music Tile
LiveDisplay
Switch Data Card Tile
Reboot Tile
Reading Mode
Gaming Mode
Compass
Sound Search
Compass Tile
[/SIZE]
https://photos.app.goo.gl/WSbmYy7QeB6K9CSn6
Founder & Lead Developer:
SKULSHADY (Anushek Prasal)
Support Team:
theo.j22 (Tushar Jain)
If you like our work then please consider donating.
PayPal: https://www.paypal.me/ANUSHEK
UPI: [email protected]
Maintainer PayPal: https://www.paypal.me/SyberHexen
ROM: Havoc-OS Latest Official Build
Recovery: Official TWRP
Open GApps: https://sourceforge.net/projects/opengapps/files/arm64/
Magisk: Magisk
Factory Firmware: Stock Firmware Mirror
"Copy Partitions Zip" - courtesy of @filipepferraz
copypartition.zip
(To setup "Slot B")
01. Download the ROM, Firmware and GApps from the links above.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Create backup. i.e. EFS / Persist and put somewhere safe.
## YOU ONLY NEED THIS STEP ONCE.. When updating Firmwares ##
04.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
05. Flash the ROM and TWRP installer.
06. Choose Reboot -> Recovery
07. Install GApps & Magisk.
08. Reboot -> Bootloader
09. fastboot -w
10. Reboot and Enjoy.
*Note-1: Slots, ROMS install to opposite (inactive) slot
If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
*Note-3: Updating "Dirty Flash"
01. Flash ROM + TWRP installer.
02. Reboot -> Recovery
02. Install Gapps + Magisk
03. Reboot -> System
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
Nitrogen Project (https://github.com/nitrogen-project)
Omnirom (https://github.com/omnirom)
And all the other Developers, Testers, Donators and Users.
https://github.com/Havoc-OS
https://github.com/Havoc-Devices
android_device_motorola_ocean
android_device_motorola_sdm632
android_kernel_motorola_sdm632
XDA:DevDB Information
Havoc-OS 4.x ROM for Moto G7 Power, ROM for the Moto G7 Power
Contributors
SyberHexen, SKULSHADY, erfanoabdi
Source Code: https://github.com/Havoc-OS/
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-04-11
Last Updated 2021-27-05
Changelogs:
27/05/2021 - v4.5
Device changelog:
- Add FPS Info Overlay
- Smart Charging -> Adaptive Charging
Changelog: https://t.me/Havoc_OS/2963
Download Link: https://bit.ly/Ocean-Havoc-OS
Past Changelogs:
26/04/2021 - v4.4
Changelog: https://t.me/Havoc_OS/2911
16/04/2021 - v4.3
Changelog: https://t.me/Havoc_OS/2873
25/02/2021 - v4.2
Changelog: https://t.me/Havoc_OS/2829
22/11/2020 - v3.11
Device changelog:
- MotoActions: Import Stock Drawables
- Add GPS Parameters to CarrierConfig
- Disable SF backpressure
Changelog: https://t.me/Havoc_OS/2650
11/10/2020 - v3.9
Device changelog:
- Disable HD Statusbar Icon
- Fix Color inversion Issue
- Fixed Screencording (Green)
- Fix UI flicker while playing video/games
- Set some specific carrier props per variant
- Addressed more sepolicy denails
Changelog: https://t.me/Havoc_OS/2615
20/09/2020 - v3.9
Device changelog:
- Increase zram size to 2gb
- Enable zram writeback
- Enable APN menu for cdma carriers
- Addressed many sepolicy denails
- Updated TWRP to Latest Unofficial
Changelog: https://t.me/Havoc_OS/2494
15/07/2020 - v3.7
Device changelog:
- Switched to official Q River/Ocean Kernel
03/07/2020 - v3.6
Device changelog:
- Fixed Dual Channel(Stereo Audio)
12/04/2020 - v3.4
Device changelog:
- Updated To Q Blobs
- Kernel Built With Clang
- Prebundled Recovery Changed To TWRP(With Touch Fixed)
09/04/2020 - v3.4
- Initial Official Build
- OrangeFox Recovery Prebundled
Included twrp?
phyophyo1500 said:
Included twrp?
Click to expand...
Click to collapse
Just read.. Where you saw ROMs with included TWRP?
Every time an update comes out do I need to format the entire phone? Because today I went to do a new update I received loop I lost everything ...
Dark98 said:
Havoc-OS 3.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI crafted by @SKULSHADY.
Many useful features that will blow your mind.
All you can dream of and all you'll ever need.
Just flash and enjoy...
https://photos.app.goo.gl/U8YDbDZCEVDQrSKU6
Lead Developers:
SKULSHADY (Anushek Prasal)
ZeNiXxX (Viktor Hermann)
Support Team:
DankBoi (Apoorva Kr. Srivastava)
theo.j22 (Tushar Jain)
If you like our work then please consider donating.
PayPal:https://www.paypal.me/vhermann | https://www.paypal.me/ANUSHEK
UPI: [email protected]
ROM:https://sourceforge.net/projects/havoc-os/files/ocean/
Recovery:https://dl.twrp.me/ocean/
Open GApps:http://opengapps.org
Magisk:https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Telegram Support Group:https://t.me/havoc_ocean
Telegram Announcements Channel:https://t.me/Havoc_OS
Discord Server:https://discord.gg/YfhBCj4
Preparation for A/B Roms:
01. Download TWRP.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
Nitrogen Project (https://github.com/nitrogen-project)
Omnirom (https://github.com/omnirom)
And all the other Developers, Testers, Donators and Users.
https://github.com/Havoc-OS
Click to expand...
Click to collapse
Preparing for A/B ROMs:
01) done official twrp (.IMG and .ZIP)
03) done
04) done... but when i boot it touchscreen don't work! i've tried many versions but same problem.
05) where can I find this file? And which is differences between Slot A and Slot B?
06) done
07) done
ROM - Installation:
01) done
02) done
03) done
04) done
05) done
07) When I reboot system... don't work! No open system. I don't know why.
DarkAngelNoctis said:
Preparing for A/B ROMs:
01) done official twrp (.IMG and .ZIP)
03) done
04) done... but when i boot it touchscreen don't work! i've tried many versions but same problem.
05) where can I find this file? And which is differences between Slot A and Slot B?
06) done
07) done
ROM - Installation:
01) done
02) done
03) done
04) done
05) done
07) When I reboot system... don't work! No open system. I don't know why.
Click to expand...
Click to collapse
I have the same issue, i do all the steps and the rom does not start, just keep booting in TWRP
Cricamju said:
I have the same issue, i do all the steps and the rom does not start, just keep booting in TWRP
Click to expand...
Click to collapse
I gave up. I've reinstalled the stock rom, using Lenovo Moto Smart Assistant, as you can see.
I hope someone help us
Here's how I booted 04/12 build earlier today on my 1955-5. I was on another AOSP rom when I installed Havoc..
Booted into bootloader by holding power until it reboots soon as screen shuts off I let go power holding volume down entering bootloader,
Plug up to laptop...
fastboot set_active a
fastboot reboot bootloader
fastboot boot recovery (i use orangefox.img)
Format data in Orange fox recovery, wipe data system, cache, flash copy partition AB.zip, flash Havoc rom zip, reboot system. Then I kinda ran through rom settings and set a few things up really quick enabled dev options again and usb debugging, then fastboot boot recovery, flash Nikgapps, flash Magisk Canary zip reboot system. My installion methods differ slightly based on what happens during install and of course whether I boot into system afterwards or back to recovery or it hangs or whatever.. I kept going back in twrp as well after folllwing installation directions from the op which are the same one i use to install all roms usually and 95% of the time I always boot into system fine. Try booting Orange fox recovery and formatting data and wiping everything and see if it works for you. You probably already know this but always make sure your copy partitions AB zip gets installed with zero errors and copies everything how it should by watching your screen during flash and of course make sure you're in slot_ a when installing it. I'm pretty sure that's what I did today when I got it going and it booted. I was on AEX previously. Another great rom we have.
**If you were flashing the recovery installation zip during install skip that and instead try reboot bootloader then boot back into recovery: fastboot boot Orangefox.img ...instead of flashing the recovery installation zip. I've read that sometimes that can cause a rom to not boot up. I just boot recovery vs installing it. Takes like 2 seconds. If you do what I did and it still doesn't boot try fastbooting your firmware then doing installation again. I bet it's a recovery issue that's the culprit here.
@Dark98 I've only been gone from Havoc since 3.2 or 3.3 and talk about kicking ars! Awesome job on this!! One thing I love about Havoc is it has some nav bar options for long press, double tap: open app or power menu that I haven't seen in other roms and to me that's mandatory. I hope someone will some day port smart bar from Pie. I sure love and miss DUI from pie, mainly the smartbar part of it! Awesome job on this fine rom!!! A true work of art here!
flash713 said:
1) fastboot set_active a
2) fastboot reboot bootloader
3) fastboot boot recovery (i use orangefox.img)
Click to expand...
Click to collapse
1) understood
2)understood
3) i must type, for example: fastboot boot recovery "C:\.....\twrp.img"? or fastboot boot "C:\...\twrp.img"???
p.s.: where can i find OrangeFox for Moto G7 Power?
Hi, well. Now i say what i done. Maybe something wrong.
1) Removed Google Account on my device Moto G7 Power (XT1955-4).
2) Power off and booted into bootloader. Plug up to laptop.
3) Open CMD and type fastboot set_active a
4) fastboot reboot bootloader
5) fastboot boot "F:\....\OrangeFox-R1.2-Stable-ocean (3).img"
6) Formatted and wiped Dalvik/ART Cache, data, Internal Storage, system first on Slot B and then switched on Slot A and do same thing. (maybe i do this mistake).
7) I've flashed copy-partition-AB.zip on Slot A
8) Flashed Havoc-OS-v3.4 zip
9) Reboot System...but there's a message "No OS installed!".
I don't know the mistake!!!
I've replaced Stock Moto G7 Power ROM with LMSA. But i would like to flash Havoc-OS. In my Redmi Note 7 i have it.
DarkAngelNoctis said:
Hi, well. Now i say what i done. Maybe something wrong.
1) Removed Google Account on my device Moto G7 Power (XT1955-4).
2) Power off and booted into bootloader. Plug up to laptop.
3) Open CMD and type fastboot set_active a
4) fastboot reboot bootloader
5) fastboot boot "F:\....\OrangeFox-R1.2-Stable-ocean (3).img"
6) Formatted and wiped Dalvik/ART Cache, data, Internal Storage, system first on Slot B and then switched on Slot A and do same thing. (maybe i do this mistake).
7) I've flashed copy-partition-AB.zip on Slot A
8) Flashed Havoc-OS-v3.4 zip
9) Reboot System...but there's a message "No OS installed!".
I don't know the mistake!!!
I've replaced Stock Moto G7 Power ROM with LMSA. But i would like to flash Havoc-OS. In my Redmi Note 7 i have it.
Click to expand...
Click to collapse
I never pay attention to the whole "no os installed" message. Mine says that quite a bit and I reboot and I'm fine. That's just because of for formatting data I believe that that shows up.
When you switch slots are you rebooting bootloader afterwards? I do that so I am indeed in that slot because far as I know we aren't switched to another slot until we do that. As long as you get copy partition AB zip successfully installed/copied good while you're on slot A then if for some reason you don't boot you still should be safe far as bricking goes. While I don't wipe both slots same way you are I think you should still boot. I flash that copy AB zip every time I go to install anything on slot a and I've flashed 100+ times probably since my last brick and no more bricks so I'm gonna keep on flashing it in slot a every time just to stay safe.
If you don't boot after it gives you message "no os installed" and you reboot system after that and you still loop around to recovery try flashing your firmware then format data, flash copy AB zip then Havoc reboot system.
flash713 said:
I never pay attention to the whole "no os installed" message. Mine says that quite a bit and I reboot and I'm fine. That's just because of for formatting data I believe that that shows up.
When you switch slots are you rebooting bootloader afterwards? I do that so I am indeed in that slot because far as I know we aren't switched to another slot until we do that. As long as you get copy partition AB zip successfully installed/copied good while you're on slot A then if for some reason you don't boot you still should be safe far as bricking goes. While I don't wipe both slots same way you are I think you should still boot. I flash that copy AB zip every time I go to install anything on slot a and I've flashed 100+ times probably since my last brick and no more bricks so I'm gonna keep on flashing it in slot a every time just to stay safe.
If you don't boot after it gives you message "no os installed" and you reboot system after that and you still loop around to recovery try flashing your firmware then format data, flash copy AB zip then Havoc reboot system.
Click to expand...
Click to collapse
in the end I did this:
1) Switched off device
2) Volume down+Power to go in bootloader
3) CMD: fastboot erase userdata (maybe useless)
4) CMD: fastboot boot "C:\...\twrp.img" (or orangefox.img)
5) On Slot B mount "system" then wipe and format (maybe useless)
6) On Slot A mount "system" then wipe and format
7) Flash copy-partition-AB.zip
8) Flash Havoc ROM
9) Reboot -> Recovery
10) Flash GApps
11) Reboot -> Bootloader
13) CMD: fastboot erase userdata
14) CMD: fastboot reboot
For fix reboot message "5 seconds" i do this: fastboot flash logo_b "C:\...\logo.bin"
fastboot flash logo_a "C:\...\logo.bin"
Maybe i do something wrong, or useless step, but now i have Havoc-OS! LOOOL
DarkAngelNoctis said:
in the end I did this:
1) Switched off device
2) Volume down+Power to go in bootloader
3) CMD: fastboot erase userdata (maybe useless)
4) CMD: fastboot boot "C:\...\twrp.img" (or orangefox.img)
5) On Slot B mount "system" then wipe and format (maybe useless)
6) On Slot A mount "system" then wipe and format
7) Flash copy-partition-AB.zip
8) Flash Havoc ROM
9) Reboot -> Recovery
10) Flash GApps
.
11) Reboot -> Bootloader
13) CMD: fastboot erase userdata
14) CMD: fastboot reboot
For fix reboot message "5 seconds" i do this: fastboot flash logo_b "C:\...\logo.bin"
fastboot flash logo_a "C:\...\logo.bin"
Maybe i do something wrong, or useless step, but now i have Havoc-OS! LOOOL
Click to expand...
Click to collapse
No your method makes sense because when we reboot after rom install we switch to other inactive slot. Like an update is:
Boot recovery, switch slots to inactive slot, reboot recovery, flash rom update zip + recovery installer zip, reboot recovery, flash gapps and magisk, wipe delvik cache reboot system.
Now I guess since recovery comes in build so we skip the recovery zip part and just reboot recovery. Haven't done it yet but when an update comes I definitely will.
---------- Post added at 10:51 PM ---------- Previous post was at 10:43 PM ----------
tecnicaemail said:
Every time an update comes out do I need to format the entire phone? Because today I went to do a new update I received loop I lost everything ...
Click to expand...
Click to collapse
On update did you: Boot recovery, switch to other inactive slot, reboot recovery, flash rom update zip, reboot recovery, flash gapps and magisk , wipe delvik cache, reboot system?
I believe we skip the flash recovery zip after rom because the rom now comes with recovery as far as I know that's the proper update method.
flash713 said:
No your method makes sense because when we reboot after rom install we switch to other inactive slot. Like an update is:
Boot recovery, switch slots to inactive slot, reboot recovery, flash rom update zip + recovery installer zip, reboot recovery, flash gapps and magisk, wipe delvik cache reboot system.
Now I guess since recovery comes in build so we skip the recovery zip part and just reboot recovery. Haven't done it yet but when an update comes I definitely will.
---------- Post added at 10:51 PM ---------- Previous post was at 10:43 PM ----------
On update did you: Boot recovery, switch to other inactive slot, reboot recovery, flash rom update zip, reboot recovery, flash gapps and magisk , wipe delvik cache, reboot system?
I believe we skip the flash recovery zip after rom because the rom now comes with recovery as far as I know that's the proper update method.
Click to expand...
Click to collapse
DarkAngelNoctis said:
in the end I did this:
1) Switched off device
2) Volume down+Power to go in bootloader
3) CMD: fastboot erase userdata (maybe useless)
4) CMD: fastboot boot "C:\...\twrp.img" (or orangefox.img)
5) On Slot B mount "system" then wipe and format (maybe useless)
6) On Slot A mount "system" then wipe and format
7) Flash copy-partition-AB.zip
8) Flash Havoc ROM
9) Reboot -> Recovery
10) Flash GApps
11) Reboot -> Bootloader
13) CMD: fastboot erase userdata
14) CMD: fastboot reboot
For fix reboot message "5 seconds" i do this: fastboot flash logo_b "C:\...\logo.bin"
fastboot flash logo_a "C:\...\logo.bin"
Maybe i do something wrong, or useless step, but now i have Havoc-OS! LOOOL
Click to expand...
Click to collapse
Boy followed his advice and it worked here too!
Really.
Following the tutorial on the main page and also giving the same error, it keeps coming back to TWRP I don't know why!
Thank you.
Now I have another issue...LOL.
Battery go down 70% --> 0%
First I tried to charge my device using official charger but, I gone on fastboot mode, I have this message "Battery Low (Charging)", but if I connect on laptop I have this one "Battery OK (Charging)". I don't know why. I can't boot nothing. No ROM, no recovery. I tried use Lenovo Moto Smart Assistant to flash Stock ROM...but it failed...
If I try to disconnect my device charger wall or disconnect laptop...it power off and I can't go fastboot mode without to be connected in charger.
Good morning friends, I found a BUG with me at least if someone knows the solution if I put the 2 SIM CARDs to use I simply don't have mobile data to navigate, it only works if I leave a single CHIP. I've seen the config options all active, APNS etc ... only works if I leave with only chips.
My dear friends after installing HAVOC my GPS does not work, does anyone know how to fix it?
I'm having a problem where after setup, advanced settings is constantly crashing.
Force stopping doesn't help
I also don't have service.
tecnicaemail said:
My dear friends after installing HAVOC my GPS does not work, does anyone know how to fix it?
Click to expand...
Click to collapse
My weather apps and all have worked fine. Haven't used gps because stupid Corona lockdown situation lately but there are ways to make your GPS perform far better than stock on any device. I'll try and look that up and I'll check mine more now and report back within the hour.
Edit added: Gps won't even turn on at all on my device. I downloaded gps test app by barbeau and flipped it on on both my devices. Moto g7 power and my Xiaomi Mix 2 and G7 has no reading at all while my other Mix 2 immediately had a reading.. I've never even used gps on my G7. ?
Bweans said:
I'm having a problem where after setup, advanced settings is constantly crashing.
Force stopping doesn't help
I also don't have service.
Click to expand...
Click to collapse
I've never had any type of service issues whatsoever on this rom. Not sure what carrier you use or where you're located but you can try an apn swap using root explorer or another root file manager. To do the apn swap you simply delete your apn.conf.xml file (if there is one present) in system/product/etc and also in your /product/etc folders on your device. Just delete the current apn.conf.xml that's already there and replace with the one in this horrible video I made for a friend a while back. God I need to redo this video. ?? The quality is not so good but it shows how to do what I'm talking about. .
If you don't mind me asking, how did you install havoc rom? Like what was your exact installation procedure? Boot recovery, wipe xxxx
What model device do you have? Example: I have a 1955-5 Ocean Moto G7 Power , my device was purchased from Metro by TMobile...I use RETUS firmware ..
Only thing I can think of you have no service is maybe you installed in a way that caused this or possibly you were on a different firmware that may have caused this idk... If you do the apn swap and you have no data still then at least we can eliminate that. Here's a video on how to and the apn.conf.xml file is in the video description. Lemme know if you need help..
Team Win Recovery Project 3.x, or twrp3 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.
Code:
#include <std_disclaimer.h>
/*
* Devs are 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 them for messing up your device, they will laugh at you.
*
*/
Features:
- almost all classic TWRP features works (!)
- including backup / restore (tested by @jeryll on decrypted storage, more about this here and here)
- extra addons included
- - install Magisk
- - uninstall Magisk
- - GooglePay fix
- - SafetyNet fix
- - conversion script to make your /system /vendor /product on super partition RW by @lebigmac (more info HERE)
and more
Bugs:
- none known ATM
Screenshots:
{
"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"
}
Changelog - current version:
====================
TWRP-3.5.2_10-0
md5: a5d5647016b0e0deeec628d9869bcae4
====================
* Update to version 3.5.2_10
* Magisk update 22.1
* Included original script v 1.28 for converting to RW from @lebigmac
* Added a script for disabling partition journaling (Advanced menu)
* Fixed missing internal memory after formatting Data
* Added the ability to install IMG images of logical partitions
* Added system_ext section for MIUI on Android 11
and fixed the error output if it was absent on the A10
* And other minor improvements and edits ...
DOWNLOAD (also for older versions):
or see attached files
Changelog - older versions:
Spoiler
====================
TWRP-3.5.1_10-2
md5: 5ca7887a5870703220e1cbcbbfffb6be
====================
* Returned the buttons to the reboot menu
* Added a module for converting firmware to RW (Advanced menu) by @lebigmac
* Adaptation for 11 android
* Up Magisk-22.0
* Set mount system in RW (if the partitions are converted to RW)
* Update Ukrainian translation
* Correction of minor bugs
====================
TWRP-3.5.1_10-1
md5: 2534ed3b41daf2093ab685c004bd65eb
====================
* Added a module for converting firmware to RW (Advanced menu) by @lebigmac
* Correction of minor bugs of the interface and translation
* Adaptation for 11 android
* And so on...
====================
TWRP-3.5.1_10-0
MD5:
(zip file): dec44ae6a56b01f4ecce5132045e727c
(img file): 702828ed3a75c8ffc2c4be61439bc449
====================
* twrp release: 3.5.1_10
* bash: add to TWRP
* Strip strings containing '--' before conversion to XML comments.
* Added support for flash image in both slots
* New, missing and improved strings for Dutch and Spanish translation.
* Fix ungrammatical sentence.
* Fix unlocalised string.
* ors: Implement 'twrp format data' to format the data partition
* Fixed NO OS INSTALLED without encryption (mod)
* Kernel update
* Editing the interface and translations
====================
TWRP-3.5.0_10-5 (2021-03-01)
md5: b8ce7cdac35d308369d19bbdd25b5934
====================
* Include common names for Magisk app in list of flashable zip files. (official)
* partition: add support dm_use_original_path. (official)
* partitionmanager: support delayed adopted storage mount. (official)
* Include nano in TWRP by default. (official)
* nano: Add File Manager option to edit selected file (official)
-(Ability to edit text files)
* Added Support for terminal from filemanager. (official)
* tzdata: add to TWRP build automatically. (official)
* cryptfs: add support for keymaster 2. (official)
* android root: restore context for android system root (official)
* Remove duplicate Update_System_Details() function calls (official)
* fixup including magiskboot and resetprop (official)
* Add support to change TWRP Folder (official)
* bash: add to TWRP (test)
* Introducing the function of preventing the replacement of TWRP with stock recovery in the source code (Advanced menu)
* New patch AVB (if the system does not boot and only goes into fastboot mode)
* Editing the interface and translations
====================
TWRP-3.5.0_10-5 (2021-02-19) test version
md5: 1497353827e39d9cd3c8c4c72cc50caa
====================
* Include common names for Magisk app in list of flashable zip files. (official)
* partition: add support dm_use_original_path. (official)
* partitionmanager: support delayed adopted storage mount. (official)
* Include nano in TWRP by default. (official)
* Remove duplicate Update_System_Details() function calls. (test)
* nano: Add File Manager option to edit selected file (official) - (Ability to edit text files)
* Added Support for terminal from filemanager. (official)
* tzdata: add to TWRP build automatically. (official)
* cryptfs: add support for keymaster 2. (official)
* android root: restore context for android system root (official)
* Introducing the function of preventing the replacement of TWRP with stock recovery in the source code (Advanced menu)
* New patch AVB (if the system does not boot and only goes into fastboot mode)
* Editing the interface and translations
====================
TWRP-3.5.0_10-4
====================
* Updated Magisk 21.4
* Fixed bug of mounting (unmounting) System
* Added patch for mounting System and Product in RW (not supported at MIUI official)
* Added the ability to install Magisk - *. Apk (for the future)
* Change the interface of the top bar
=====================
TWRP-3.5.0_10-3
=====================
* Updated Magisk 21.3
* Fixed file transfer error in explorer (test)
* Added GooglePay patch fix
* Added SafetyNet fix patch (Magisk module)
* official fix "Thus resolve the 'No OS installed' warnings upon system reboot if only adb shell twrp actions were used on the device"
=====================
TWRP-3.5.0_10-2
=====================
* Fixed the ability to copy to internal memory after formatting Data
* Fixed recovery of BT partition
* Fixed ADB Sideload mode
* Added backup of Internal memory and FW
* Translation editing
How to flash the TWRP:
- via fastboot
Code:
fastboot flash recovery twrp-3.5.0_xx-x-surya.img
Next reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.5.0_xx-x-surya.img
REMEMBER: it is important that from fastboot you directly reboot into TWRP recovery or the TWRP will be overwritten.
- via custom recovery:
Code:
flash zip file (see attached file) in recovery
Credits:
- Thanks to TeamWin devs
- Thanks to brigudav
- Thanks to @lebigmac
jeryll said:
...Features:
- almost all classic TWRP features works (!)....
Not working:
- TWRP screenshots can only be saved to external sdcard or usb-otg device
Changelog:
=====================
TWRP-3.5.0_10-3
=====================
* Updated Magisk 21.3 (addon)
* Fixed file transfer error in explorer (test)
* Added GooglePay patch fix (addon)
* Added SafetyNet fix patch (Magisk module)
* official fix "Thus resolve the 'No OS installed' warnings upon system reboot if only adb shell twrp actions were used on the device"
....
Click to expand...
Click to collapse
would you recommend this over orangefox recovery? and, have you switched to this?
This TWRP is the most advanced, polished, constantly maintained recovery in TWRPs available for Poco X3 (that I tried), but it is still not as good as OFOX in terms of added extra features (like advanced file management, etc.)...
I'm using it now and will for some time as I want to do more tests on encrypted/decrypted storage.
Anyone who will choose to use this recovery will probably be only satisfied.
jeryll said:
...I want to do more tests on encrypted/decrypted storage....
Click to expand...
Click to collapse
eager to read about your tests on encrypted storage, the reason being i've not been able to decrypt as yet. i'm on crDroid v7.2 of 21.Jan and i'd like to update to 27.Jan without losing data - and with decryption - but i haven't found a way - a simple way (if one exists, i.e.).
Seems it's a new update (TWRP-3.5.0_10-4), but I can't find it available for download (in the russian forum i can't download it).
Alin45 said:
....new update (TWRP-3.5.0_10-4).... md5: 44FD2547230E58196AC77296160CD723
Click to expand...
Click to collapse
=====================
TWRP-3.5.0_10-4
====================
* Magisk updated 21.4
* Fixed a bug with mounting (unmounting) System
* Added a patch for mounting System and Product in RW (not supported at the MIUI office)
* Added the ability to install Magisk - *.Apk (for the future)
* Changing the interface of the top bar
So let me get this straight.
This twrp now actually supports making full nandroid backups and restores, just like on phones without dynamic partitions? Is there anything that has to be done differently, like making backups to and restoring from sd/external, or does it work on internal as well now? Is there still the "problem" of /vendor being unmountable? And what about wiping vs. formating when installing a new rom, any changes there?
Apologies for all the questions, but this twrp update really seems like a huge deal for new phones, that I wasn't expecting to happen that quickly.
[armitage] said:
So let me get this straight.
This twrp now actually supports making full nandroid backups and restores, just like on phones without dynamic partitions? Is there anything that has to be done differently, like making backups to and restoring from sd/external, or does it work on internal as well now? Is there still the "problem" of /vendor being unmountable? And what about wiping vs. formating when installing a new rom, any changes there?
Apologies for all the questions, but this twrp update really seems like a huge deal for new phones, that I wasn't expecting to happen that quickly.
Click to expand...
Click to collapse
- in terms of backup restore abilities this TWRP at least can do what latest OFOX can do, while the rest of TWRPs available for Poco X3 NFC are unsuitable/not recommended to do that...
- both recoveries (latest OFOX or this TWRP) using the "same engine" produce almost identical results, success or failures
- TWRP devs are still probably (hopefully) working on how to extract and backup only the system partition from dynamic super partition, because this you can't do now in any recovery (AFAIK) for Poco X3
- what you can do is to backup and restore the whole super partition, plus boot, dtbo, data partition... and depending on the encryption state of your internal storage... you can choose how to restore your backup:
if you're using decrypted storage
if you're using encrypted storage
- I had high hopes when I found out that this specific TWRP recovery actually can do backup restore, but after a few days of testing I found that results are (unfortunately) the same as using latest OFOX backup restore
- what I don't understand (can't figure it out) why while using decrypted storage you can't get always 100% identical restore while restoring super, boot, dtbo, data, metadata partition... sometimes it works, and the next day not - and what is sometimes failing to restore - is your PIN code Android protection (even if you provide the correct one, it will not accept it)
Hmm, ok. A bit disappointing, but still a nice step in the right direction. Thank you so much for your answer as well, I really appreciate it. As for the problems with restoring security challenge (pin etc.). I actually had that on older phones as well, when restoring different backups. Not always, but when it happened, I had to delete /data/system/locksettings.db from the recovery, after restoring and before booting.
i am currently running miui global 12.0.8. will i be able to flash twrp to my phone after unlocking. can anybody guide me through what are the ext steps that i have to get twrp flashed to my poco x3 karna version please? if not can i be able to flash it after degrading my UI? and if so how can i degrade from my current version to base version ?
Thanks
can I get .zip file for flash via recovery?? I have limited way to reach computer/laptop..
biladina.id said:
can I get .zip file for flash via recovery?? I have limited way to reach computer/laptop..
Click to expand...
Click to collapse
?? if you have recovery you can flash .img file directly from recovery and choose recovery partition to flash
jeryll said:
?? if you have recovery you can flash .img file directly from recovery and choose recovery partition to flash
Click to expand...
Click to collapse
Going from orange to this recovery, can i flash img directly from orange as well?
immi803 said:
Going from orange to this recovery, can i flash img directly from orange as well?
Click to expand...
Click to collapse
yep, no problem, I switching them regularly as I need
immi803 said:
...can i flash img directly from orange as well?
Click to expand...
Click to collapse
most important: choose recovery partition.
gawtham94 said:
i am currently running miui global 12.0.8. will i be able to flash twrp to my phone after unlocking. can anybody guide me through what are the ext steps that i have to get twrp flashed to my poco x3 karna version please? if not can i be able to flash it after degrading my UI? and if so how can i degrade from my current version to base version ?
Thanks
Click to expand...
Click to collapse
i am already create video about this here
denpangestu210 said:
i am already create video about this here
Click to expand...
Click to collapse
you've named your video 'Install TWRP POCO X3 NFC' and shown orangefox recovery. just saying...
denpangestu210 said:
i am already create video about this here
Click to expand...
Click to collapse
thanks for the updated tutorial man. Appreciate it
m0han said:
you've named your video 'Install TWRP POCO X3 NFC' and shown orangefox recovery. just saying...
Click to expand...
Click to collapse
all step same, orange fox, twrp, black etc
about code comand, if you using twrp.img
rename orange_twrp.img with twrp.img
simple
{
"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"
}
Awaken OS for Poco F1 [beryllium]
Code:
#include <std_disclaimer.h>
/*
* Your warranty is void. Or...Valid? Probably?
*
* Project Awaken and its maintainers are not responsible for bricked devices,
* dead SD cards, data loss, thermonuclear war, or economic crisis caused by
* Awaken OS. YOU are choosing to make these modifications, and if you
* point your finger at me for messing up your device, I will laugh at you.
*/
Born different, now awaken.
Awaken OS brings consistent, fluent and smooth experience with all your must-have customizations, for you, for the community, for everyone.
- Project Awaken Team -
Saikiran [Founder & Lead Developer]
Ninad Patil [Lead Developer]
Mukul [Developer]
Hugwalk [Lead Designer]
Jagadish [Designer]
Glitch [Designer]
Find us on Telegram! @AwakenOSNews
Display
Ambient edge lighthing
Fonts, Icon shape & Icon pack customizations
Force full screen app & hide app from launcher
Kdragon Monet
Monet customizations
Gestures
Advance reboot menu
Double tap to sleep and wake
Navbar customizations
Playback control
Three finger screenshot
Toggle torch when screen off
Volume button wake and cursor control
Lockscreen
Charging info
Media art & blur
Pulse visualizer
Notification
Headsup Customizations
Saner Headsup
Pixel Features
Columbus (Quick Tap)
Game Dashboard
Smartspace
Quick Settings
Brightness slider customizations
Internet speed meter
Quick QS pull down
Security
Applock
Disable qs pulldown on secure lockscreen
Face unlock
Hide power menu on lockscreen
Scramble pin layout and quick unlock
Secure qs tiles on lockscreen
Sounds
Custom ringtone vibration pattern
Cycle through ringer modes
Increasing ring volume
In-call vibration
Link ring and notification volumes
Per app volume
Ringtone focus mode
Smart pause
Statusbar
Battery styles
Clock customizations
Combined signal & 4G instead of LTE toggle
Mic, Camera & Location indicator toggle
Small mobile type icon
You tell
First Time Install / Clean Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Cache / Data / System
4. Format data only if you are encrypted
5. Flash ROM
6. Flash Gapps (optional)
7. Flash Magisk (optional)
8. Reboot to System and #beAwakened
Update / Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash ROM
4. Wipe Cache
5. Reboot to System and #beAwakened
Download Here / Official Announcement / Official Community
Kernel Source / Source Code
Bugs List
Currently : None
• Tell us if you found any bug
Device Changelog
Note:
2 Builds will be made from now onwards:
Vanilla Variant (without gapps inbuild)
Gapps Variant (with gapps inbuild)
Changelog:
04-11-2021
• Fixed offline charging
• Fixed recovery stuck issue
• Fixed screen off ok google
15-10-2021
• Initial Release
Ai Yeah ....great job
Wow! Thanks for hardworking!
All great, one more question! after installation orangefox does not start after shuts down!?
orangefox R11.1
Stuck in bootloop. Did a clean install.
The Android 12 animation is in constant loop and after a minute or so, the device resrtarts.
EDIT: After some tries, now it doesn't restart, just stuck in the logo animation.
alexcary77 said:
Stuck in bootloop. Did a clean install.
The Android 12 animation is in constant loop and after a minute or so, the device resrtarts.
EDIT: After some tries, not it doesn't restart, just stuck in the logo animation.
Click to expand...
Click to collapse
Did you manage to return to recovery?
Daniel Adelino Nascimento said:
Did you manage to return to recovery?
Click to expand...
Click to collapse
Yes, wiped cache/dalvik again, the same.
(I have installed the latest twrp version)
I also installed the latest one but it blinks and loads again (loop in twrp) then I hang up and when I turn it on it goes back to custon rom Awaken OS 2.0
the entire installation via adb is ok without error, but you cannot enter via volume + and power or fastboot boot twrp-3.5.2_9-0-beryllium.img
I was able to successfully install the rom. I got the bootloop as people have stated here but it worked when I wiped my device and installed from OrangeFox instead of TWRP. The rom is good. Tested for a few hours now. There is one huge thing that might force me to go back to Android 11 if I can't find a way around it. The rom is always detected as rooted. Can't use any financial app or anything that requires an unrooted device. Will update with other things I find.
Edit : Couldn't get the apps to work. Tried flashing the boot.img from the zip. Didn't work. Installed magisk and used magisk hide. Failed. Couldn't get it to work.
Those who have stuck recovery issue
Dont use sd card while booting into recovery
A12 has some issue with recovery
It will be fixed in future
Where's the awaken customizations? I'm not founding
REIGNZ3 said:
Awaken OS for Poco F1 [beryllium]
Code:
#include <std_disclaimer.h>
/*
* Your warranty is void. Or...Valid? Probably?
*
* Project Awaken and its maintainers are not responsible for bricked devices,
* dead SD cards, data loss, thermonuclear war, or economic crisis caused by
* Awaken OS. YOU are choosing to make these modifications, and if you
* point your finger at me for messing up your device, I will laugh at you.
*/
Born different, now awaken.
Awaken OS brings consistent, fluent and smooth experience with all your must-have customizations, for you, for the community, for everyone.
- Project Awaken -
Saikiran
Ninad Patil [REIGNZ]
Mukul [undead]
- Designers -
Hugwalk
Jagadish
Glitch
Find us on Telegram! @AwakenOSNews
Category
- Wallpaper based system colors (MONET)
- Three-fingers-swipe to screenshot
You tell
First Time Install / Clean Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Cache / Data / System
4. Flash ROM
5. Flash Gapps (optional)
6. Flash Magisk (optional)
7. Reboot to System and #beAwakened
Update / Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash ROM
4. Wipe Cache
5. Reboot to System and #beAwakened
Download Here / Official Announcement / Official Community
Kernel Source / Source Code
Click to expand...
Click to collapse
Please make Redmi Note 7 (lavender) ROM Android 12
i was stuck at Android 12 load screen as well.
after rebooting into recovery i saw strange folder names, so i assumed it was a problem with encryption so i formated data drive, fresh installed os and magisk.
Now all runs fine
alexcary77 said:
Stuck in bootloop. Did a clean install.
The Android 12 animation is in constant loop and after a minute or so, the device resrtarts.
EDIT: After some tries, not it doesn't restart, just stuck in the logo animation.
Click to expand...
Click to collapse
Do a wipe after ROM Installation - Wipe Which says YES
Dzień dobry. Pomimo wyjęcia karty SD, tryb odzyskiwania nie uruchamia się. Czy będą aktualizacje OTA, które naprawią ten problem?
Great work thankkkks
perfect job, so far everything is fluid like it should be
Can't find a way to change the icon's shape to squircle, square etc.