[BACKUP][TWRP][LOLLIPOP] [STABLE] Backup ROM Stock HTC 626s (Movistar) - Desire 626 General

Hello!
This is my first contribution, for this device so have some patience.
-IMPORTANT: FOR NOW ONLY IT IS POSSIBLE TO INSTALL IT BY RESTORING IT BY TWRP, I HOPE SOON TO MAKE IT A .ZIP.-
HTML:
* 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, and if
* you point the finger at me for messing up your device, I will laugh at you.
Well, let's move on to the important thing.
This is a BACKUP of the original system (Lollipop 5.1) of the HTC Desire 626s, from the operator Movistar (Mexico) -maybe it will work with another, please try it-.
The rom includes everything original from HTC (apps, sounds, wallpapers, fonts, bootanimation, etc)
BUGS:
You tell me.
Apparently there are problems starting the ROM. Wipe Data/Cache/Dalvik and go.
HOW TO INSTALL / RESTORE:
**I recommend, after installing it, do a factory reset to avoid problems with the apps. ***
1. Download the .zip or folder from the link below. (NOTE: It weighs around 1.6GB.)
2. Extract that .zip in TWRP / backups.
3. Reboot into download mode (Vol Down + Power)
4. Select "Reboot into bootloader"
5. Select "Reboot into Recovery"
6. Select "Restore" -> Select the Folder (TWRP/backups)
7. Wait a few minutes..
8. Although it is not necessary, I recommend doing a factory reset (data, cache, dalvik cache).
9. Reboot
10. Enjoy!
Download Links:
Version 1.0 (.ZIP FLASHEABLE) [15/11/20]:
Coming soon..
Version 2.0 (TWRP BACKUP) [08/03/21]:
https://mega.nz/folder/xA4inCRb#oAZ1fkxkYac0pxoUgSEklA
I AM ALREADY WORKING ON AN AOSP VERSION OF LOLLIPOP.
-IMPORTANT: FOR NOW ONLY IT IS POSSIBLE TO INSTALL IT BY RESTORING IT BY TWRP, I HOPE SOON TO MAKE IT A .ZIP.-
Thanks!!! (I will be on the lookout, any problems or improvements to report.)
XDA:DevDB Information
[BACKUP][TWRP][LOLLIPOP] [STABLE] Backup ROM Stock HTC 626s [Movistar] (Mexico), ROM for the HTC Desire 626
Contributors
alexito_dev
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP, Bootloader Unlocked.
Version Information
Status: Stable
Current Stable Version: 2.0
Created 2020-07-22
Last Updated 2021-04-15

Reserved

reserved

Related

[Q] ilyaaa299's CM10.2: No Wifi

Hi
So i just installed ilyaaa299's CM10.2 on my U8800.
My Problem:
No wifi detected. System settings grayed it out. Z-Device-Test crossed it out.
What i did:
* Had StockRom Jelly Bean
* Had CWM (and still have it)
* Did CWM full backup
* Wiped System, Data, Cache, Dalvic
* Applied Forumember partition.zip twice, rebootet CWM each after
* Installed Version 1 [4.2.1 Jelly Bean], then Update 1 for version 1, then Google Gapps full version. Then rebooted.
* Did wait a few mins for CM10 to load and did the basic settings(language etc)
* Checked for Wifi to connect, seems that there is none detected.
* Rebooted phone for failcheck. Still no wifi
So can anyone help me?
netzgeist said:
Hi
So i just installed ilyaaa299's CM10.2 on my U8800.
My Problem:
No wifi detected. System settings grayed it out. Z-Device-Test crossed it out.
What i did:
* Had StockRom Jelly Bean
* Had CWM (and still have it)
* Did CWM full backup
* Wiped System, Data, Cache, Dalvic
* Applied Forumember partition.zip twice, rebootet CWM each after
* Installed Version 1 [4.2.1 Jelly Bean], then Update 1 for version 1, then Google Gapps full version. Then rebooted.
* Did wait a few mins for CM10 to load and did the basic settings(language etc)
* Checked for Wifi to connect, seems that there is none detected.
* Rebooted phone for failcheck. Still no wifi
So can anyone help me?
Click to expand...
Click to collapse
Wifi doesn't work in Version 1 flash the latest Version 13 after doing all the wipes
ca1v1n said:
Wifi doesn't work in Version 1 flash the latest Version 13 after doing all the wipes
Click to expand...
Click to collapse
Thanks alot for your help!
What i did:
* Boot to CWM
* Clear system, cache, dalvic
* Installed v13 from your link
* reboot
* waiting a few mins for CM10 to finish installation
Wifi works like a charm now
As my problem was solved, all the explanations are for the archives so other forum users may benefit from it.
Thanks again for you help

[NEWBIE GUIDE] MIUI ROMs, TWRPs, ZIPs, UNLOCK, BACKUP, ROOT, FLASH, RESTORE

GUIDE SECTIONS QUICK LINKS
#1 - MIUI ROM, Types of MIUI ROM
#2 - TWRP, Types of TWRP, Flashing TWRP
#3 - Unlock, Root, Flashing via TWRP
#4 - Custom ROM, Types of custom ROMs
MIUI ROM
MIUI (pronounced as Me-You-I) is Xiaomi's custom built firmware like Samsung's OneUI, HTC's SenseUI, OnePlus's OxygenOS which is built on top of Android's AOSP base with its own modifications and features. At first glance it resembles like a hybrid between Google's Material Design and Apple's iOS. But unlike Stock Android or iOS, MIUI is very intuitive, feature rich and has multiple tweaking options. MIUI is updated regularly depending on the development branch. Xiaomi gathers reports, feedbacks and suggestions from the community, addresses the bug-fixes and integrates new features upon request. Most of Xiaomi devices are regularly patched with security updates every 2-3 months. The flagship "Mi" series like Mi9 receive quicker Android version updates than their budget "Redmi" series like Redmi 7, Redmi Note 7 Pro etc.
TYPES OF MIUI ROM
There are 2 development branches of MIUI ROMs for all Xiaomi devices.
A) Stable Builds
It is updated on a monthly basis or longer
New features are added slowly after testing
Higher system stability and less bugs than Beta ROMs
It has a four digit numbering scheme (X.X.X.X)
For eg. 8.X.X.X is MIUI8 Stable Build
Stable builds come in 2 variants
1. MIUI China Stable ROM
This ROM is pre-installed on all Xiaomi devices sold in China.
It is made for the Chinese market & contains Chinese MIUI apps.
Google Apps are absent. You can install them manually.
It supports Chinese & English languages.
2. MIUI Global Stable ROM
This ROM is pre-installed on all Xiaomi devices sold outside China.
It is made for the International market & contains English MIUI apps.
Google apps are pre-installed by default.
It supports 50+ languages.
B) Beta Builds
It is updated on a weekly/bi-weekly basis or longer.
New features are added quickly for testing.
Lower system stability and more bugs than Stable builds.
It has a three digit numbering scheme (X.X.X)
For eg. 6.11.21 is MIUI8 Beta build for 21th Nov, 2016.
This ROM is not pre-installed on any Xiaomi device.
You can install Beta build over Stable build manually.
Beta/Developer builds come in 2 variants.
1. MIUI China Beta ROM
It is made for the Chinese market & contains Chinese MIUI apps.
Google Apps are absent. You can install them manually.
It supports Chinese & English language.
2. MIUI Global Beta ROM​ It is made for the International market & contains English MIUI apps.
Google apps are pre-installed by default.
Supports more than 50+ languages.
TWRP
Team Win Recovery Project is a custom recovery which is flashed over the stock recovery as it gives user more options such as flashing custom ROMs, kernels & scripts, take full system backups, restore backups, root etc.
TYPES OF TWRP
1. TWRP by iscle: https://forum.xda-developers.com/mi-max-2/development/recovery-twrp-3-1-1-0-touch-recovery-t3652762
Based on Stock TWRP 3.1.1-0 with no modifications.
Ported from Redmi Note 4 (mido)
English language as default
Need to flash dm-verity zip immediately after flashing this TWRP, else your phone wont boot.
2. TWRP by xuefer: https://forum.xda-developers.com/mi-max-2/development/twrp-max2-oxygen-t3634437
Built using LineageOS 14.1 source
Built and tweaked for Mi Max 2 (oxygen)
Decryption support added for /data
Faster transfer using adb push
Extra fonts added
FLASHING TWRP
Unlock bootloader here: https://forum.xda-developers.com/mi-max-2/how-to/guide-unlocking-bootloader-mi-max-2-t3641257
Install "Minimal ADB+Fastboot Drivers": https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP file and copy the file in the C:\Program Files (x86)\Minimal ADB and Fastboot folder
Download dm-verity disabler and copy the file in your phone: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Switch off phone. Hold Power + Volume Down to boot into fastboot mode. Connect it to PC.
Inside the folder where TWRP file is present, open command prompt window.
Type "fastboot devices". Your phone will get detected with serial number.
Type "fastboot flash recovery <recovery_name.img>". TWRP will get flashed on your device.
E.g. "fastboot flash recovery twrp_3.1.1-0.img".
Type "fastboot boot <recovery_name.img>". You will boot into TWRP. Disconnect phone from PC.
E.g. "fastboot boot twrp_3.1.1-0.img".
On the screen, swipe to allow modifications and select your language. Uncheck "Keep system read-only"
Select Install and then choose the dm-verity disabler zip and swipe to flash.
Select Backup and check all partitions. Swipe to backup. The backup will be stored in "TWRP" folder
Select Reboot and then system. You will be asked if you want to disable the stock recovery. Swipe to disable.
You will boot into MIUI with TWRP installed.
TWRP ZIPs
These zips are meant to be flashed with TWRP with a specific order. Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
1. no-verity-opt-encrypt: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Also called as dm-verity disabler/lazy flasher
"dm-verity" is a feature in the MIUI kernel which checks and prevents the phone from booting normally if you modify the phone. (e.g. flash TWRP)
To prevent that, you need to flash the dm-verity disabler zip which removes dm-verity check and also decrypts the /data partition so that you can boot into MIUI normally.
Else you can flash a custom ROM immediately after flashing TWRP which removes the MIUI system and kernel
2. Xiaomi.EU ROM Patch: https://forum.xda-developers.com/mi-max-2/development/xiaomi-eu-rom-patches-dpi-change-t3656296
You need to install Xiaomi.EU ROM before installing these zips via TWRP.
MIUI to Google Apps: Replaces default MIUI apps with Google apps.
Google Now/Pixel Launcher: Replaces stock MIUI launcher and enables Google Assistant via build.prop tweak.
DPI changer: Change values from stock 440 (low res, bigger) to 325 (high res, smaller).
3. Hardware Key Disabler : https://forum.xda-developers.com/mi-max-2/themes/mod-disable-hardware-keys-lineageos-rom-t3696108
This mod enables on screen navigation bar and disables the hardware keys
You can revert back to stock configuration by flashing "enable_HWkeys.zip"
FLASHING VIA TWRP
Some important terms to remember:
Formatting data: Factory resets the phone, will erase internal storage, will remove encryption
Wiping data: Factory resets the phone, will not erase internal storage, will not remove encryption
Clean flash: Flashing a new ROM or an updated version of the same ROM by wiping or formatting data of current ROM in TWRP. Cache & dalvik is automatically wiped in TWRP.
Dirty flash: Flashing an updated version of the same ROM without wiping or formatting data of current ROM in TWRP. Cache & dalvik wipe is recommended in TWRP.
Treble TWRP: Custom TWRP which uses existing /cust partition and formats it into /vendor partition which is needed for non-MIUI Oreo and Pie ROMs where Treble is used.
Notes:
Always read the entire post & comments of the custom ROM page before asking any questions, chances are your query has already been answered.
You do not need to wipe /system partition manually, it its automatically wiped when a ROM is flashed by the updater-script inside the ROM zip. General rule of thumb is always clean flash any ROM, unless mentioned by the ROM developer or maintainer that dirty flashing is okay.
Requirements:
Unlocked bootloader with TWRP installed
Phone partition backup using TWRP
All data backup from internal storage (sms, contacts, files etc.)
Official MIUI ROM encrypts /data partition, you will need to Wipe > Format Data to decrypt it completely else need to flash dm-verity disabler zip or Magisk zip.
1. Rooting MIUI / non-MIUI ROM
Boot into TWRP (Power+Volume Up)
Install > Magisk zip
Reboot > System
2. Flashing official MIUI recovery ROM
Boot into TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Install > MIUI ROM zip + Magisk Zip
Reboot > System
3. Flashing custom MIUI ROM (Xiaomi.EU / RevOS / Mi Globe)
Boot into TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Wipe > Factory reset
Install > Custom MIUI ROM zip
Reboot > System
4. Flashing LineageOS/AOSP ROMs (Non-Treble)
Boot into TWRP
Wipe > Format data and Reboot > Recovery (if storage is encrypted)
Wipe > Factory reset
Install > Firmware + ROM Zip + Google Apps Zip
Reboot > System
5. Flashing LineageOS/AOSP ROMs (Treble)
Boot into Treble TWRP
Wipe > Format data (if storage is encrypted)
Reboot > Recovery
Wipe > Factory reset
Install > Firmware + ROM Zip + Google Apps Zip
Reboot > System
TYPES OF CUSTOM ROMs
There are mainly two types of custom ROMs for any Android device. You need to flash them on your phone using custom recovery such as TWRP.
1. Stock based ROMs
They are based on the factory ROM which came pre-installed on your device. In case of Xiaomi devices, developers take the stock China Stable/Beta MIUI ROMs as base, perform modifications and tweaking and then re-pack it. Examples of stock based MIUI ROMs.
Xiaomi.EU: https://xiaomi.eu/
MIUI Pro: https://miuipro.by/
Mi Globe: http://mi-globe.com/
Epic ROM: http://www.epicrom.pro/
2. Custom based ROMs
They are typically based on either AOSP or LineageOS code. They can either be ported from similar devices or built using the kernel source code of a particular device. Xiaomi has not yet released kernel source code for Mi Max 2. Kernel source codes are needed for relatively stable and bug-free experience on custom ROMs. Examples of some popular custom ROMs
A) AOSP based ROMs
AOSPExtended: https://www.aospextended.com/
Nexus Experience: http://www.nxrom.us/
SlimRoms: https://slimroms.org/
B) LineageOS based ROMs
LineageOS: https://lineageos.org/
Resurrection Remix: http://www.resurrectionremix.com/
XenonHD: http://www.xenonhd.com/
Reserved #4
Reserved #5
Thanks for wonderful explanation and for content too
Hi,
I flashed TWRP from PC using above procedure & tried to install no-verity-opt-encrypt (version 5.1.zip).
I got below error while installing :
Error: unpacking ramdisk failed
Phone booted normally & TWRP is not there.
How to fix this issue?
I know these questions are sometimes annoying, but for someone who hasn't been following Android development since Android 4.4.4, I'm a little overwhelmed by all this information. What does the "Oxygen" mean? Is it just a certain model of the Mi Max 2? I see all ROMs say Oxygen but none explain what it means. If it's a model of the Max 2, how can I know if the version I have is Oxygen?
Thanks and sorry if it's a dumb question
It's a code name for Max 2, so you don't mistakenly flash the wrong ROM, if it says Oxygen, than you're sure it's for your model, not for i.e. Mi Max...
Sent from my Mi Max 2 using Tapatalk
Hello,
I have a Mimax 2 bootloader unlocked, rooted, SuperSU, twrp 3.1.0-0 (cofface) installed. I installed, after some difficulties, the rom xiaomi.eu 7.12.28. When I'm in recovery, after the flash I sometimes have a red line that says "... no-verity-opt-encrypt ..." blah blah. But the phone boot normally, everything works fine. Do I have to install lazyflasher-no-verity-opt-encrypt or can I do without it?
thank you and sorry for my bad english
Hi, I have unlocked BL and installed Developer ROM 7.12.28. for a few weeks now. Can I install latest 8.1.4 developer ROM with TWRP without wiping cache/dalvik and will I keep my data/apps that way?
Thanks.
Sent from my Mi Max 2 using Tapatalk
@frulex, I installed the 8.1.4 (via updater) after using the 7.12.28, without any problem. That you erase the cache where not, you will not lose the data of your apps
What was the size of that update file you installed? I first got notification of 8.1.4 update and it said it's something like 95 MB file size. Tried to install it twice via updater, it starts updating, boots to TWRP and ends with error without installing. After reboot notification changed and now it offers update of full 1.5 GB 8.1.4 version ROM. I didn't have time to download and try that but I wonder will that also end in error and that's why I ask about downloading .zip and flashing through TWRP.
Sent from my Mi Max 2 using Tapatalk
These are the roms I used, as you see 8.1.4 weighs 1.2 Go
edit: I had uploaded an image of the explorer but it does not appear! (decidedly i'm struggling with this forum, lol)
Not many roms for this phone..it sux..I regret exchanging it with my oneplus 3..
How many ROMs have you expected in 3 days since kernel source has been released?
Sent from my Mi Max 2 using Tapatalk
good tutorial
thanks to you @SharkcpN . this is such a clearly, easily tutorial "How to Flash TWRP" for newbie like me..
I tried and succeed with no error at all.. once again, thanks for your good job :good:
Hi there! Thanks for the excellent thread and collection of links. I started here and found a setting on this phone's NVRAM that I have not seen mentioned anywhere else, and you will need it for LTE unlocking.
Below are the exact steps, many taken from this guide, that I used to go from a phone with an unlocked bootloader to flipping the LTE B2 and LTE B4 bits on. After I did it and rebooted, I suddenly had a working LTE connection!
I cannot yet PROVE that this actually enabled the bands, but it hasn't hurt anything. I will test for that in a couple days, because the only dumb thing I did was afterwards, when I accidentally re-locked the bootloader by not paying attention to what I was doing. If you use the MiFlash program to install a ROM, don't forget to change the setting in the lower right corner!
Notes for those wishing to use this as a guide:
I don't think you can brick the phone completely playing with just these settings, but you should be prepared to restore everything. Take backups where I mention them, and if you need the device working, you should have a current MIUI fastboot flashable image, available from the official website, on hand.
This is LTE only and there are different settings for GSM that work the same way.
The steps are numbered, but you should also understand mostly what they do.
You may ignore the VM part and just boot your normal Win7 with driver signature checking DISABLED (F8 on boot). I use Linux and I'm security-conscious about downloading programs that I can't verify, so I'm using a VM.
There is a dialpad option for opening the diag port (if you have root), but it did not work for me, so I have provided a method that I know works and it clears itself upon reboot
QXDM's NV browser has a checkbox for "DUAL SIM". You don't need to check it for this process, you won't lose SIM2.
Downloads section:
(REQUIRED) Most are in the links provided by OP:
MiFlash (official one)
QPST 2.7.460
QXDM 3.12.714
Minimal adb and fastboot
no-verity-opt-encrypt-6.0.zip
twrp-3.2.1-0-oxygen.zip
SuperSU-v2.82-201705271822.zip
(OPTIONAL, needed if you mess up. I chose to have it ready to go.):
From MIUI official site, go to the ROMs for the Max 2. The one on the download button here is NOT what you want.
Select Flashing guide, then on on the left hand side select FastBoot.
Download the image for your device. I have a copy of oxygen_global_images_V9.0.3.0.NDDMIEI_20171209.0000.00_7.1_global_298fd5f49c.tgz
SETUP SECTION (install tools and root phone):
Enable developer mode and USB debugging on phone
Boot into a Windows VM, pressing F8 to go into unsigned drivers mode
Install MiFlash, just to get the drivers
Install QPST and QXDM for later
Install adb and fastboot
Pass USB port through to VM and check adb is working by twice typing
Code:
adb devices
Shutdown phone and remove SD card from phone.
Add no-verity-opt-encrypt-6.0.zip and SuperSU-v2.82-201705271822.zip to SD card
Put SD card back in phone
Reboot phone into fastboot mode using PWR & VOL-, and re-pass to VM if needed
From cmd terminal in adb folder,
Code:
fastboot flash recovery twrp-3.2.1-0-oxygen.img
Code:
fastboot boot twrp-3.2.1-0-oxygen.img
Once TWRP comes up, install no-verity-opt-encrypt-6.0.zip
(OPTIONAL) Make a backup. I didn't because I don't want the ROM that's on there anyway.
Reboot and ensure MIUI loads
Shutdown phone and reboot into TWRP using PWR & VOL+
Install SuperSU as a system app
Reboot into MIUI
Access and edit the NVRAM:
Connect the device back to the computer, pass to VM if necessary
From your terminal in the adb folder,
Code:
adb devices
Grant debug permission on the device, if it asks again
Code:
adb shell
Code:
$su
Grant permission in superSU popup
Code:
#setprop sys.usb.config diag,adb
When the device reconnects, re-pass to VM if needed, and it may install another driver
Open QPST Configuration and make sure the device's port is enabled.
At the top, go to "start clients" and open "software download"
In the "Backup" tab, choose a location to save your file and hit Start, just in case you do break something
Once finished, close "software download" but leave QPST Configuration running
Open QXDM Professional
Under Options->Communications, make sure your phone is set "active" then set "target port" to the port it's on, then press OK
Go to NV Browser in the dropdown on the upper left.
Scroll down to 06828 :"nv_lte_bc_config_type.lte_bc_config"
Press READ and save this value somewhere in case you forget which bits you set! Mine was: 2061584302293
It's little-endian, and I wanted to flip bits from 0 to 1 to enable bands {2} and {4}, so I added 2^({2}-1)+2^({4}-1) = 10 to get a value of 2061584302303
Enter your new value in the "value" field and press "write"
Now, scroll down to the corresponding LTE prefs value at 65633
Read again. This should be the same number you had before, in hexadecimal format. Mine was 0x1E0000000D5, so to add B2 and B4 (Combined value 0xA), I changed it to 0x1E0000000DF
Again, enter your new value in the "value" field and press "write"
I doubt this requires any sort of "safe shutdown," but I hit "offline" then closed QXDM, then closed QPST, then rebooted the phone.
For a quick test, you can set network preferences to "LTE ONLY" by going to the dialpad and hitting *#*#INFO#*#*, then selecting your SIM card and using the dropdown in there. Mine was preferring HSPAP because the signal was stronger, even though the data was blocked.
Further testing I want to do when I get the bootloader unlocked again:
Use an app that shows what bands are in use to prove I'm on B2 or B4
Try disabling bands I will never use that have similar frequencies to the bands I want to see if signal improves
TWRP ZIPs
These zips are meant to be flashed with TWRP with a specific order. Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
1. no-verity-opt-encrypt: https://build.nethunter.com/android-...y-opt-encrypt/
Also called as dm-verity disabler/lazy flasher
"dm-verity" is a feature in the MIUI kernel which checks and prevents the phone from booting normally if you modify the phone. (e.g. flash TWRP)
To prevent that, you need to flash the dm-verity disabler zip which removes dm-verity check and also decrypts the /data partition so that you can boot into MIUI normally.
Else you can flash a custom ROM immediately after flashing TWRP which removes the MIUI system and kernel
2. Xiaomi.EU ROM Patch: https://forum.xda-developers.com/mi-...hange-t3656296
You need to install Xiaomi.EU ROM before installing these zips via TWRP.
MIUI to Google Apps: Replaces default MIUI apps with Google apps.
Google Now/Pixel Launcher: Replaces stock MIUI launcher and enables Google Assistant via build.prop tweak.
DPI changer: Change values from stock 440 (low res, bigger) to 325 (high res, smaller).
What does It mean??

[ROM][7.1.2][AOSP] UltimateROM [BETA][11.03.2018]

Current Information
Hi there, UltimateROM is AOSP-based ROM with some features and optimizations added.
Everything I do with UltimateROM I always test personally on my phone, but anyway...
Code:
#include <disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. 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.
*/
What's working:
RIL (phone/SMS/3G)
Video (playback & recording)
Audio (playback & recording)
Wi-fi
Bluetooth
Camera (Front and rear)
2D/3D HW Acceleration
USB, MTP, ADB
all native tethers (Wifi/BT/USB)
external storage
What's not
GPS
Vibration doesn't work (disabled temporarily due to an userspace vibrator driver issues)
Internal storage is not recognized
Formatting SDcard as adoptable storage will make it unusable
Buggy MTP implementation
Download
UltimateROM
Installation
before installation make sure you have a TWRP recovery
install chrono kernel (both ROM and the corresponding kernel are located in the same directory - see ROM link below)
reboot recovery
install ROM
install SuperSU
install chrono kernel again
If you proceed with installing GAPPS, you might have running out of space on /system partition. If you are planning to flash Gapps, you're likely need to use sdcard repartition (see below how to). Below is installation sequence with the repartition of the internal sdcard:
like before, make sure you have kernel with TWRP recovery inbuilt
install chrono kernel
reboot recovery
flash ReParted zip. This will wipe system, data and cache partitions!
install ROM
install SuperSU
install chrono kernel again
*please note a possibly undesirable effect of the repartition: cache partition will be decreased to 15 MB and some ROMs that rely upon this partition won't boot. To restore original sdcard partition layout, flash stock 4.1.2 ROM (with PIT file).
Sources:
https://github.com/UltimateROM/android_manifest
Credits
SergeyL - many-many thanks for an initial set of patches, device tree and TWRP 3.x.y! Also thanks for helping me implementing some features to this ROM.
mickybart, millosr, MWisBest - thanks for great cherry-picks!
@Meticulus - thanks for his great contributions on our devices!
@AGONTUK - thanks for an initial Marshmallow bring up!
@nieltg - Sources for Galaxy Ace 2 device
@golden-guy - thanks for great cherry-picks !
@TeamCanjica - vendor and hardware sources
@Unjustified Dev - Audio fixes
Google
CyanogenMod
AOKP
SlimROMs
EuphoriaOS
OmniROM
AOSPA
Viper4AndRroid Team
And many other devs, I could forget (please write me if I did so).
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
XDA:DevDB Information
UltimateROM, ROM for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, SergeyL, mickybart, millosr, MWisBest
Source Code: https://github.com/UltimateROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP recovery
Based On: AOSP, LineageOS
Version Information
Status: Beta
Created 2018-03-11
Last Updated 2018-03-11
Changelogs
11.03.2018 - build #1
initial release
Reserved
Flashed both of your roms on janice and... wow, nougat is much smoother than mm (w/o gapps)
Great JOB Chrono , Will test it immediately .
Was dreaming of this.
[YOUTUBE][https://www.youtube.com/watch?v=JgSBPf-jiiM&lc=z23gzrkgcrqcffykaacdp43bvodf3st2izucbuxtgidw03c010c]
Ok Chrono MC I installed the ROM on 2 on my Advance's and you are official KING of the Advance i9070 Now
Thank you very much , this helped me to create my Mod but now under Android 7.1.2 thanks to You and all that worked on this .
Keep up the fantastic work.
Channel48
Hey I have a problem with the reparted script. I get "error opening "data/media"" and "error: No such file or directory"
ErackGamer said:
Hey I have a problem with the reparted script. I get "error opening "data/media"" and "error: No such file or directory"
Click to expand...
Click to collapse
Do these messages lead to any other problems? Try formatting /data partition. If that doesn't help, flash stock 4.1.2 ROM (with PIT file).
ChronoMonochrome said:
Do these messages lead to any other problems? Try formatting /data partition. If that doesn't help, flash stock 4.1.2 ROM (with PIT file).
Click to expand...
Click to collapse
I think that the problem was due to the old twrp I had installed. After flashing the kernel and getting the newer twrp that it includes I was able to successfully run the script. More details at your Lineage 15.1 ROM post
Going to test
can't get it pass thru Setup Wizard :thinking:
it just stuck at Just a sec, do I need a data enabled sim?
I've inserted a fat32 sdcard.
I will try without gapps later...
EDIT : First boot cannot have GAPPS, it needs to be flashed after first boot. Whole system seems slightly unstable with GAPPS.
logcat is weird, the output looks "choppy"
Hi @ChronoMonochrome
I saw you successfully booted this ROM
Did you change much in kernel 6.0.1 to make it boot
unknown said:
Hi @ChronoMonochrome
I saw you successfully booted this ROM
Did you change much in kernel 6.0.1 to make it boot
Click to expand...
Click to collapse
I don't really remember exact changes, since we have booted 7.1.2 a long time ago. You might want to look mostly at the SELinux changes, probably there should be implemented some more (which is recommended but not required to boot the ROM).
For those who are going to use GAPPS on this ROM:
1. Flash GAPPS after first boot! If you flash GAPPS before first boot, you won't be able to pass through Setup Wizard.
2. After flash GAPPS, do not wipe cache/dalvik cahce/data. Wiping these partitions after flash GAPPS seem to make GAPPS causing massive instability to the system.
3. On every boot, open once Settings -> Google and wait for Google Play Services to crash once. I don't really know why, but several GMS services kept crashing and restart GMS is restarted non-stop by the system. After Google Play Services crash once, the GMS services won't crash anymore. This should lead to a more stable system.
Overall, I don't recommend GAPPS with this ROM. With and without GAPPS on this ROM is almost a day and night difference, in terms of stability.
Janice + Nougat (w/o GAPPS) = BEST!
fix ur instructions i got confuesed
hi there, am seeing no comments of usability of this rom after Jun 2018.
Also there have been no no updates on the rom, seems like the developer has given up on the development.
can anyone confirm the bugs and can it used with microg?

[RECOVERY][TREBLE][rosy][Unofficial] OrangeFox Recovery Project

OrangeFox Recovery Project Treble
{
"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 ROM
* 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-Unofficial-rosy-3.2.3-1.zip
Supports Miui, Treble/Non-Treble Custom Roms, GSI
CHANGELOG
Please check the 3rd post of this thread.​
Credits
ATG Droid and Dadi11 - for RedWolf
Kirillmaster4 & ZHANtech - for contribution to UI
z31s1g - for TWRP theme
ManoloRey - for Vince contributions (kernel, etc)
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
* White Flashlight
* Password, torch, led
* 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
* Bug fixes
* And many more!
Frequently Asked Questions, MIUI OTA, Troubleshooting, and Sundry Information:
Please check the 2nd post of this thread.
INSTALLATION
1. Download the OrangeFox zip to your device
2. Reboot to your custom TWRP-based Recovery
3. Install the OrangeFox zip as a normal zip installer
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
XDA:DevDB Information
OrangeFox is a recovery tool/utility for Android devices.
SourceCode:
https://github.com/LinuxPanda/android_recovery_rosy
https://gitlab.com/OrangeFox
Version Information
Created: Dec-10-2018
Last Updated: Dec-19-2018
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 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. 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 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 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.
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
ChangeLogs
3.2.3-1
• Minor changes & fixes
3.2.3-0
• Built with oreo sources.
• Treble/Non-Treble Custom Roms, GSI support.
I'll test it
Orangefox always give me internal memory omb error everytime i flash miuipro or xiaomi.eu rom.
Switchonthelight said:
I'll test it
Click to expand...
Click to collapse
Thanks.
carl sagan said:
Orangefox always give me internal memory omb error everytime i flash miuipro or xiaomi.eu rom.
Click to expand...
Click to collapse
Please give recovery log. Thanks.
Why OrangeFox Recovery does not recognize USB OTG?
Nice ans beautifull recovery !
I recommand it !
Recovery updated with minor changes & fixes.
ChangeLog
3.2.3-1
• Minor changes & fixes
GinNig said:
Why OrangeFox Recovery does not recognize USB OTG?
Click to expand...
Click to collapse
I have made few changes. Please check with latest build.
Thanks. It work well on my redmi 5. However, similar to the official TWRP, it cannot view the content of internal storage and ask for password to decryption (miui 10.2 eu roms). For flashing new ROMs, its not problem since I copy ROM/ Zip to SD card to mount in TWRP. With this new recovery hope that someday I will install Android P (pixel experience)
Orangefox creators are working themselves to release an official build. So this thread is useless now. You can download builds soon from the official websites itself, https://orangefox.tech/en/.
Request mods to lock thread. Thanks.
Thread closed @ op request

[GUIDE] CorvusOS for J7 Prime

As you all may know, CorvusOS is one of the most popular custom ROM At the moment, and the developers known as "Tipz Team Builds" Have made it compatible for J7 Prime!
(IMPORTANT!!, There are currently lots of bugs in CorvusOs, so i recommend waiting for a stable release, if you wanna install it then im not responsible for any damages done to your phone, i warned you!)
(Please as always take a nandroid backup of your phone as with any other custom rom installation!)
Credits :
Tipz Team Builds original thread : https://forum.xda-developers.com/t/gsi-beta-11-phh-corvusos-v16-8-avalon.4212765/
Downloads :
Treblue : https://www.mediafire.com/file/xskqacpul8glpfx/Treblue_v2.0.zip/file
NikGAPPS : https://www.mediafire.com/file/fk3xv8xr8i2bxrt/NikGapps-basic-arm64-11-20201231-signed.zip/file
CorvusOS : https://sourceforge.net/projects/ti...e-25082021-Beta-Official-0000.img.xz/download
Installation :
*I cannot stress this enough, Please always take a nandroid backup of your phone when installing a custom rom!*
1. Download all of the above
2. Boot into custom recovery
3. Wipe : Cache, Dalvik Cache, Data, System, Vendor *DO NOT WIPE INTERNAL STORAGE*
4. Extract the CorvusOs*version*.img.xz as .xz
5. Flash the extracted CorvusOs as system image
6. After flashing CorvusOs, Mount System and vendor, *If you can't mount it, Reboot into recovery again*, After mounting Flash Treblue
7. After flashing treblue Flash NikGAPPS
8. Wait for it to finish
9. To confirm it works reboot into recovery and look at terminal, it should say something like "Custom ROM (TREBLE) CorvusOs"
10. Now reboot into system and enjoy!!
After installation it should reboot a few times, let it rest for 5-10 minutes
Credits are given above, please give me suggestions on how to improve my guide!
Also, if you are gonna update to the latest version, do not download ones with "gapps" in their name, also the file must have either vndklite or nonlite on the file, so it looks something like this
CorvusOs-*version*-treble-arm64-vndklite/nonlite-*DATE OF RELEASE*-Beta/Stable-Official-0000.img.xz

Categories

Resources