Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We 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 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.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
Androidfilehost:
Download: https://www.androidfilehost.com/?fid=24391638059057759
Google Apps Minimal Edition:
Download: http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Installation
1.) You must have twrp installed follow this guide here
2.) Download the ROM and Gapps and place them on internal or external storage (depending on your model you may only have internal storage)
3.) In TWRP navigate to "Wipe" and wipe cache, data, and dalvik
4.) In TWRP navigate to "Install" find the location of the downloaded zips and proceed with installation
5.) Once both ROM and Gapps have been successfully flashed reboot system and wait for the device to boot
XDA:DevDB Information
CyanogenMod 12.1 for Alcatel ONETOUCH IDOL 3 5.5, ROM for the Alcatel Onetouch Idol 3
Contributors
Unjustified Dev
Source Code: http://github.com/TeamRegular
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-10-14
Last Updated 2016-01-28
Status
Working:
Radio (Includes Dual Sim, Data and SMS)
Sound
Camera
BT
Sensors
Wifi
Known Issues:
Please share your bug reports (include a log if possible)
Tap to wake (Works, but disables itself randomly)
Horrendous battery drain
Changelog
20160218
remove unneeded qcom usb script
disable boot freq limit for cluster
20160216
Updated prima driver to LA.BR.1.1.3_rb1.45
Updated kernel to LA.BR.1.1.3_rb1.45
add back various alcatel kernel changes
set usb properties on boot (Fix the usb product model defaulting to Android)
set variant from init and add support for I806 (pivoq)
selinux enforcing (wcnss fixes by pivoq)
add peripheral manager
wcnss: restore stock config
20160128
update storage configuration (fix internal storage access)
don't set tct properties
set taptowake control state to 2
remove window cover support (revisit later)
remove unused zram script
remove tct cmdline garbage
remove unused hdcpService
remove power engine
remove powerup reason
remove unused Tct Daemon
disable secure discard
remove camera wrapper
use half res bootanimation
update WCNSS cfg from firmware bin
Stop the QC-QMI message spam
switch to init.qcom.power and update devfreqs
add script to identify device variants
switch to new cm-12.1 kernel
update adreno blobs
FAQs
Q: Is the device fully reversible on CyanogenMod as well?
A: Unfortunately no, it does allow all rotations but the dialer app currently will not allow you to place calls upside down.
Q: Does Dual Sim work with this ROM?
A: Dual Sim devices are now supported
Q: Why is my device 6045X?
A: The script failed to identify your device the supported model are 6045I, 6045B, 6045K, and 6045Y
Q: How can I get my device supported?
A: Post the model number and stock build.prop
Q: Is the Aero flipcase supported on CyanogenMod?
A:At the current moment it is not supported
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
salzy said:
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
Click to expand...
Click to collapse
No plans at the moment. There's is already someone handling 4.7 variants. Check out the CM port thread for details.
w00t!!!!!
Sent from my 6045I using Tapatalk
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
So close but yet so far.. I was so hyped when saw the thread but got down to earth quickly.. Stay focused my man, you're about to make something that's good into the great..
Just wondering if cm have some incompatibles with root apps like greenify, Viper 4 Android? Thank you
Sent from hell
Did you get the kernel to boot building from source or are you still repacking with stock?
Sent from my 6045I using XDA Premium HD app
brian117 said:
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
Click to expand...
Click to collapse
It's close. Just seeing how fast @Unjustified Dev has progressed to this point has been impressive.
Great Great Great my idol trembles park in the pits ready to receive new engine.
make sure everyone to get the minimal gapps as 5.1 before download
Whoohoo! so excited haha.
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:deleted
masterdex said:
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Click to expand...
Click to collapse
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Unjustified Dev said:
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Click to expand...
Click to collapse
Then I immediately delete the link to avoid problems.
My ADB is ready.
will it be regular flash or aroma installer?
masterdex said:
Then I immediately delete the link to avoid problems.
My ADB is ready.
Click to expand...
Click to collapse
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Unjustified Dev said:
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Click to expand...
Click to collapse
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
masterdex said:
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
Click to expand...
Click to collapse
You can flash gapps before and the boot.img isn't needed flash cm and gapps. Once they are done mount system and use the file manager to remove wlan module and that's it reboot and everything should be fine.
**** Disclaimer: I'm not responsible if you destroy your device. Learn at your own risk!!! ****
Alright, So I am a bit Moderately skilled to Custom Development. I do not know a lot of in-depth either.
However, I do know enough to help other new beginners out.
As I continue to learn more info and details, I will update this post frequently.
Completed guide, I'm saving and typing as not to lose progress. Last Updated- 01/03/2021
Please do note, CROSS-VERIFY if the info here is correct before following it.
What is a Custom ROM?
Simply put, it is a new Operating System [OS].
People find their stock (the one you got with your phone) to be boring, or they dislike it or want more customization and optimization, lesser bloatware (useless unwanted system apps).
Thus some Developers made their own ROM (aka OS). Then others made it compatible with our phone. Sometimes this works perfectly, most of the time it doesn't. Thus Asking people how the ROM is, is always good to ask.
STABLE means almost no errors, UNSTABLE means a few/lots of errors.
OFFICIAL means the Developer in charge will keep updating it and has been granted the task officially. EOL means End Of Life, aka Developer, won't work on it anymore.
FOD means finger on display icon, FP means fingerprint sensor, SOT means screen on time or how long your battery will last.BB means Battery backup, or how long the battery will last.
Click to expand...
Click to collapse
How To Get a Custom ROM?
So, to flash (insert) a new Custom ROM, we first need to unlock the Bootloader. The Bootloader is what allows us to wipe (remove/erase) our data, and current OS and flash a different one.
Then we flash a Recovery. (A software that makes flashing and wiping and other stuff easy)
Then flash the ROM, Then (if needed) vendor+firmware, gapps, magisk.
So in k20 pro/Mi 9t pro, there are 5 vendors. Indians use Indian Vendor, Chinese users use Chinese Vendor, similarly for EEA, Russian, and Global.
In this Vendor zip file, nowadays, the firmware is included in them, so it isn't required to flash it separately.
If you are coming from miui 11 and want to flash custom ROM you don't need to flash the vendor.
If you are coming from miui 10 to custom ROM Android 10, you need to flash the miui 11 vendor along with the ROM.
Click to expand...
Click to collapse
How To Unlock Bootloader?
So, you should first update your software to the latest miui OS [current: MIUI 11].
Go to Settings > About Phone > tap on MIUI Version 7 times -> you unlock developer settings
Go to Settings > Additional Settings > Developer Options > enable (switch on) USB Debugging > OEM Unlocking > click on MI Unlock status > link account and device.
To link the account, you must first have a Xiaomi MI account. You can make this in settings, or head to https://account.xiaomi.com
Wait 7-15 days
Once 7-15 days have passed,
USING WINDOWS PC
BACKUP ALL FILES, CONTACTS, WHATSAPP, ANY APP settings (if any), AND SYNC/LINK accounts to cloud => YOU WILL LOSE EVERYTHING NOW
Now download the Mi Unlock tool onto your PC https://xiaomitools.com/mi-unlock-tool-en/
IN A SEPERATE FOLDER
Then download Platform Tools from attachments below.
Then download TWRP (team win recovery project) from https://dl.twrp.me/raphael/
Then download Orange Fox Recovery (OFRP) from https://files.orangefox.tech/OrangeFox-Stable/raphael/ and download the latest file. [Currently: OrangeFox-R-10.1_3-Stable-raphael.zip]
Then download Disable force encrypt zip file from attachments below
Then download adb drivers from https://www.xda-developers.com/what-is-adb/ version 1.4.3 onto your PC and run the application. (Follow from How do I install ADB?) (Or you can skip that and just get the file from attachments below and extract it to C drive as a separate folder directly)
Then download the ROM (links are given below)
Then download gapps (optional). from https://opengapps.org/ and select ARMx64 and PICO then the download button.
Then download Magisk (optional). from https://github.com/topjohnwu/Magisk/releases download the Latest Magisk-vXX.xx.zip file there.[Currently: Magisk-v20.4.zip]
Download the latest vendor file from the below links. (make sure it's the proper file for your device's variant.)
Vendor and firmware are both combined and included in the same zip file.
Global, EEA (Europe), China, Russia Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphael/
Indian Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphaelin/
Check my third comment to learn how to recognize which device variant is yours, and what vendor to download and flash.
NOW! GET READY!
Now, connect your device.
Use your cable included in the box (the charging wire) and connect it to your phone and PC.
Go to 'adb' folder in your C-drive, (on that address bar thing where it shows) This PC >OS(C> adb click on it and type cmd . This will open a Command prompt to that folder.
Type adb devices and on your phone tap on the authorize button that pops up when unlocked. Now type adb devices again.
you will get
Code:
List of devices attached
365278234e device
Now, Switch off your phone.
Open the MI Unlock Tool on your PC, run the file that is an application. Read through everything, click on unlock, confirm.
Wait till the phone fully reboots itself. DON'T TOUCH IT NOW!
Congrats, the phone is now unlocked, and you have stock MIUI 11.
Now skip everything in the setup (we wanna add a custom ROM now remember, why stop here?)
again do the adb devices. You should get the same results.
Now, on your PC
Extract the Platform Tools zip file so you get its folder.
Move the TWRP.img file into the folder.
Open that folder. on that address bar, type cmd to get a new command prompt window.
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
342524356 fastboot
Then type fastboot flash recovery twrp(press the TAB key to autofill)
Now it's done! you have TWRP, but it isn't permanent.
Now, TWRP usage.
Now press and hold power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data
Now go to MENU > Reboot > Recovery
Now, to Flash your first Custom Rom.
Now from your PC copy the ROM zip file, Disable decrypt zip file, gapps ( if specified, optional), magisk ( if you want to root, optional)
Now go to MENU > Reboot > Recovery
Now go to FILES > tap on the ROM zip > add to queue > tap disable decrypt zip file > add to queue > (add gapps , magisk if needed) > flash
Now wait for a while (approx 10mins) till ROM boots up and complete the setup process.
Congrats you have your new ROM.
Now just let google download all your apps
Before you change settings like dark mode or use custom launchers etc...
Reboot once for the heck of it. Then Customize the way you like.
**** Backup Your Persist and save it on your PC always. ****
You can backup persist by having root then downloading a terminal app from Playstore. then typing these two commands
Code:
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Click to expand...
Click to collapse
How To Change My ROM? I wanna Try them all!
Now is the easy part, since all the setup is done!
First remove all passwords, fingerprints, and so forth.
For AOSP ROMs: (MIUI below)
AOSP ROMs will not break your L1
First Download the AOSP ROM you want, given below are some examples. (MIUI below)
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Then go to WIPE > select Dalvik, Cache, System, Data > then wipe them all.
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from miui and flashing AOSP, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the Vendor (if it's needed) (not required if moving between any android 10 ROMs) (Just make sure it's the right Vendor for your device/region) (If the previous AOSP rom uses OSS vendor, then you need to wipe vendor as well and flash the stock before proceeding) and flash it.
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (not required if you want to be encrypted, which is not recommended.) (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Gapps (if it isn't already included in the ROM, ask first).
and Magisk (optional if you want root).
For MIUI ROMs: (AOSP above)
First Download the MIUI based ROM you want ( stock, EU, MortalOS, etc), given below are some examples.
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Select the Vendor (if it's needed) (not required if it's currently the proper Vendor, cause EU ROMs to use a custom vendor that works on all devices) (Just make sure it's the right Vendor for your device/region) and flash it.
Then go to WIPE > select Dalvik, Cache, System, Data, Vendor > then wipe them all. (make sure you are on your device's vendor region before wiping it.)
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from AOSP and flashing MIUI, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Magisk (optional if you want root).
Some Android ROMs
With ROMs being built, changed, and modified on a daily/weekly basis. Some changing to Mi9 fod or LOS fod or using Stock or OSS vendors. Sometimes maintainers shifting or 2 devs building the same rom. The below list is not being maintained anymore. We currently have 50 ROMs. YAY Raphael!
Update: I'm removing most of the ROMs listed here and only adding my personal favorite ROMs
AOSP ROMs
DerpfestOS (two variants, I like em both) - by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-derpfest-t4132757
SuperiorOS by @HSgod -> https://forum.xda-developers.com/k20-pro/development/rom-superioros-t4130867
MortalOS (miui12) by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-havoc-os-3-3-t4063081
LineageOS, Pixel Experience, PE+, PE+ Fan Edition, ParanoidOS, MookeOS, TitaniumOS, MSM Xtended, OxygenOS, OmniOS, TreskMod, AOSIP, ColtOS, ArrowOS, BootleggersOS, ExtendedUI (exui), CRdroidOS, RevengeOS, IonOS, AICP, BlissOS, CorvusOS, DerpfestOS, HavocOS, NitrogenOS, HentaiOS, Corvus, TitianiumOS, CygnusOS, CesiumOS, Project 404, DescendantOS, SyberiaOS, EvolutionX, AOSPA, POSP, LegionOS, AncientOS, RebellionOS, SuperiorOS, ShapeshiftOS, WrathOS, ZenX, AIM OS, ConquerOS, PixelDustOS, CygnusOS, StagOS, Ressurection Remix OS, Quartz, PixysOS, PePlusUI, MalluOS, StatixOS, GrapheneOS, ShapeshiftOS, MortalOS, SuperiorOS, AwakenOS, DotOS, Lemon Branch, FluidOS, LiquidOS + more!
MIUI ROMs
EU ROMs, MortalOS, RevolutionOS, Miroom, MMX, Masik + 5 other ROMs
Kernels
Perf (miui kernel), F1xy, Immensity, Englezos, Marisa, R4v3n, Void, NotKernel, Smurf, Candy, Supermad, Antarctica, Evira
MY SUPPORT
I got help from multiple telegram guys for this.
Shoutout to @ishtiak02, @ComicoX, @logosA, Bruce Wayne, SSS, @Noobmaster69 @Lacentix @Raaj52 @nevoness @joshuah1971 and a lot of others teaching me about ROMs and answering my numerous questions.
I am using the Indian variant K20 pro (aka Raphaelin)
You can always ask in the Our Telegram Group, or me, or in the comments. (not allowed to link telegram group I think)
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Reverting Back to PIE, moving from Android 10+ to Android 9 -Just don't- (RIN users)
Right, so Anti-Rollback protection is not implemented for k20 pro or mi 9tp. YOU CAN REVERT IF YOU WANT TO.
This is confirmed by users who have reverted, and by Xiaomi.eu website. Which I trust regarding this.
We've done experiments regarding this and have concluded this applies to raphaelin users (Indian variant devices) only. Unsure why, and how it is not affecting the mi9tp variant. (no confirmation with RCN)
However,
When moving from an Android 10 vendor to an Android 9 vendor, your SENSORS will break!
You can fix this simply by flashing your persist img (Hope you took that backup).
You can also fix your sensors by flashing someone else's persist img. BUT YOU WILL LOSE L1 FOREVER.
You can get L1 back by replacing the motherboard which can be done via your warranty at a service center, or by playing a hefty sum of money. nearly half the cost of the phone. NO OTHER WAY. Also, they open your phone, so it isn't SPLASHPROOF as much anymore.
You can also fix sensors by simply updating back to android 10 via the OTA method, which is found in your settings remember. (Unsure if this will retain your L1 though)
BOTTOM LINE, IF YOU ARE ON ANDROID 10, don't go to ANDROID 9 back.
Stuck at Fastboot Fix
Best Recovery
So regarding Recoveries. Choose the one you like the most.
I prefer the latest OrangeFox recovery cause it looks better, has a better UI, better settings, more functionality, and so forth. https://files.orangefox.tech/OrangeFox-Stable/raphael/
You can also choose TWRP if you like. Completely your choice. You can get that from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363 and choose the most recent one, and follow the instructions given there.
If you are just comfortable with TWRP. Always use Mauronofrio's, which is recognized as OFFICIAL.
To flash either recovery, just download the zip file, and simply flash it directly in your recovery like you do for a rom (no need to wipe anything) and it will auto-reboot into your desired recovery.
All credits to those who made the recoveries and those people who helped them.
Stuck in Stock Recovery when Rebooting Fix
Full credits to @ SivSomRao (telegram handle, since no XDA)
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, I was scared half out of my mind. A guy named Shivsom helped me.
Basically what he made me do was
Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder in my WindowsOS C drive.
Now, on your PC. Copy your TWRP.img file, or your OrangeFox.img (I prefer the TWRP.img file by Mauronofrio.)
Open the Command prompt in that folder
You can do this by clicking on the address bar of File Explorer and typing > cmd > then Enter
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
Press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
3e2f2d356 fastboot
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery
Now, TWRP usage.
Now press and hold the power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on the "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data > type 'yes' (This will delete everything in your Internal Storage so Caution)
Then quickly flash the latest miui vendor,
Now go to MENU > Reboot > Recovery
I was OverJoyed when this worked.
Now you can flash your Favourite ROM (normal clean flash, tutorial is given above), and then boot the ROM.
This was a nasty disaster. Glad I got through it.
Right, so I tried LR-twrp (it's in Chinese, but I can change the language to English). PitchBlack and PitchBlack-old Both broke my phone to get stuck in fastboot mode no matter what I did.
HENCE I conclude that for all Xiaomi devices, OrangeFox [OFX] is the best recovery. TWRP is suited for Samsung.
ERROR 7 fix and how to modify UpdaterScript
WHAT IS ERROR 7? :
Error 7 is an error that says the ROM you are flashing is not meant for your device.
It does so by comparing the phone's codenames.....
k20p and mi9tp have two codenames, one is RAPHAEL and the other is RAPHAELIN (the Indian variant)
Flashing the Raphael/raphaelin ROM on either device won't cause any problems at all.
feel free to flash it.
Latest orangefox 10.8 works with Raphael (global and Chinese variant) and orangefox 10.6 works with Rapahelin (Indian variant).
Alternatively, It could also be caused because you are required to flash the latest vendor, which you may have not.
So please read the one-line error message that appears above the ERROR 7 red message for more details
SOLUTION to ERROR 7:
I'd recommend flashing the orangefox 10.6 recovery as it's a lot simpler.
However if this doesn't work you can try updating script.
Right, so instead of using a different recovery, you choose to update the updater-script.
Copy the zip folder of the ROM to your PC
You can use 7zip software on your Windows PC. Download this software if you don't have it.
Double click the zip (don't extract it!!!) to open the zip.
Navigate to meta_info> com > Google > Android > you'll find update_script
Find the updater-script. Right-click on it, and choose the "EDIT" option. And edit the word Raphael to raphaelin (if you have the Indian variant of the phone)
Save and exit.
Click to expand...
Click to collapse
Creating Backups
Creating backups is always the safest thing to do, and you can do so via your recovery (OrangeFox or TWRP)
First, make sure you have everything working, nothing is broken in the ROM.
Second, go to your recovery and tap on Backup. Then Click on Create Backup, rename the file if you want to.
Third, Select all the partitions, cause why not, and let it finish creating the Backup.
Finally copy the backup file created to your PC in a safe location, and later when and 'if' you mess up, you can copy the backup file back and restore it.
You can restore by first wiping everything and formatting. (For safety) Then using the same recovery you used to create the backup, Flash the backup file. DO NO FLASH SOMEONE ELSE'S BACKUP FILES!!!!!! ONLY YOURS!!!!!!
How to Decrypt Your Phone.
So encryption is the safest thing for devices, It uses a secret code/key that only your phone knows to read data and information. However, when in Recovery, we Custom ROM enthusiasts like to have our data DECRYPTED. Now, This is because we can access our files from the recovery, flash ROMs only when decrypted, and transfer files. (If we have MTP enabled in recovery)
Somehow you've found yourself encrypted, which means all the files in your recovery are showing random letters + alphabets. and you cant transfer files to your phone via recovery anymore!
To solve this, or decrypt yourself. You will have to format your data partition (this will delete everything in your internal storage, so I hope you have a backup of your photos, vids, gifs, contacts, and so forth)
Just a bit of quick advice, If you can boot into your OS, go there, and transfer all your internal storage to your PC or laptop before formatting to avoid losing your stuff.
If you can't boot into your ROM, then you'll have to lose all your data in internal storage. No known method is known YET to help without losing the files.
Now the SOLUTION: Go to Orangefox settings > manage partitions > select data > tap on format > type 'YES' > swipe to confirm > you lose all your internal storage data contents, and you are now successfully decrypted.
OR if you are using TWRP. Go to WIPE > (right side button) FORMAT DATA > type 'YES' > you lose all your internal storage data contents, and you are now successfully decrypted.
You can now transfer files to your phone properly.
To stay decrypted and not get encrypted again, flash the DFE (Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip) from attachments below (or from the file attachment called disable_force_encrypt.zip above in the first post/comment) and then boot into your ROM, or if you are flashing a new custom ROM, follow the tutorial above(first post/comment)
If you want to stay encrypted. (I advise against this) Just don't flash the DFE file.
The newer latest updated dfe file I have attached in this comment is from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and all credits for the file go to him. The dfe file in the first comment/post is different and also works.
How to Recognize Which Device You Have And What Vendor Should You Use?
Global, EEA, China, Indian, Russian variant?
All credits for this list go to @joshuah1971 aka Superuser1958 on telegram.
Box Packaging
k20 pro-China: purple+black box with Chinese writing.
k20 pro-India: angled photo of the phone on top+ white box (NO NFC capability. hardware, not software), identifier: raphaelin.
mi 9t pro-Global: black box+ picture of the device on top, English text on side sticker. (model: M1903F11G)
mi 9t pro-RU: same as global but with Russian text+ orange sticker on the phone.
mi 9t pro-EEA: white box.
Software Differences
miui Global: version number will include "QFKMIXM", google dialer, and messages.
miui EEA: version number will include "QFKEUXM", google dialer, and messages.
miui China: version number will include "QFKCNXM", miui dialer, and messages.
miui India: version number will include "QFKINXM", miui dialer, and messages.
miui Russia: version number will include "QFKRUXM", miui dialer, and messages.
So check which device variant it is, and use the appropriate Vendor when flashing. (Go to ROM's Settings-> About phone-> MIUI Version [code in the brackets])
Vendor Links
So regarding Vendors. Choose the one your device needs.
Namely, The Indian Variant is called Raphaelin. So get your vendor from https://xiaomifirmwareupdater.com/vendor/raphaelin/
The Global, Europe, China, and Russian Vendors are gotten from https://xiaomifirmwareupdater.com/vendor/raphael/
What is OSS Vendor? How to switch to the F2FS file system on OSS ROMs only?
What is OSS Vendor?
So our device has 5 variants.
Xiaomi firmware website has all 5 official (firmware+vendor) zip files.
"Always flash your variants vendor."
"Xiaomi never showed us what's in them. Aka closed source"
But this is so confusing for some people. Idky.
Therefore, some devs decided to make a universal vendor that will work on all variants. Since they are making it. They can optimize it and also always know what's in it.
This universal vendor is called an OSS vendor. (Open Source Software) (It's not yet perfect though)
Some custom ROMs don't include vendor (cause OSS isn't perfect yet)
Some custom ROMs include OSS vendor (so we can observe how good it is in daily use)
It's always good to know if the rom is using OSS or if we have to flash the official.
Currently. Since OSS isn't perfect yet. If the rom doesn't include vendor (or it's a custom miui) do not flash/use OSS with it.
How to switch to F2FS File system?
• Go to the rightmost tab on orange fox recovery > manage partitions > data > change FS > tap on f2fs > change FS
• Now reboot recovery
• Now reboot recovery again
• You are now f2fs.
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Info about Persist and why it is IMPORTANT to make a Backup
To make a Backup: Go to orangefox/TWRP recovery and select the Backup option and choose the persist.img option and back that up. Make a copy on your PC for added protection.
Persist.img is "persist" which contains data that shouldn't be changed after the device shipped, for example, calibration data of chips(wifi, bt, camera, etc.), certificates, and other security-related files. Persist is having keys to decrypt several pieces of stuff, it is device-specific and you shouldn't flash persist of others, very very bad idea.
How you are losing L1? By flashing someone else persist.img file, and if you have done that you already lost it. You cannot recover it. You can still restore your own old persist back up, and if you are lucky you will get L1 back. Never play with the persist partition it has important information specific to your device.
In case you've just lost it, and you've realized it immediately (cause sensors, pop-up, L1 are broken), & haven't done anything to modify yet. Then you can try to restore the context. Try doing this in a terminal emulator like termux (case-sensitive) Termux is an app on play store (requires root):
Code:
su
restorecon -F -R /mnt/vendor/persist/
There is also this really nice guide by William Feng that explains the same but a bit better here:
Backup and restore persist on K20 Pro and 9T Pro
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
Xiaomi.eu and other Custom MIUI ROMs
Right, so Xiaomi.eu is a forum like XDA where devs make miui like ROMs without the Mi ads and tracking and are more optimized.
The website is: https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Under there, you go to MIUI 11 ROMs > stable ROMs > download the proper ROM zip file.
The direct download link is https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv11/ or you can use: https://androidfilehost.com/?w=files&flid=300229
Now download xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip CAUTION, the word PRO has to be there. we have k20p not k20.
This works for only Raphael users, not Indian raphaelin users. (For raphaelin users use Orangefox 10.6 it will work then.)
The difference between Stable and beta is that in beta, newer features, security is implemented and tested, this has bugs, once those features are stable, it becomes a STABLE rom, then the next batch of features are added to the beta. Get STABLE though, it's better, the beta has weekly 2GB updates.
Now flashing is easy, Follow the rules in the first post/comment on how to flash a miui ROM.
Equally, you may also choose to use MortalOS which is a debloated MIUI ROM which can be found here -> https://forum.xda-developers.com/k20-pro/development/memeui-12-rc5-09-05-2020-t4097469
Issues Related to L1, restoring, and china-based miui roms
Thanks to @Raaj52 for conducting experiments to confirm and collect this information.
You must have a global/Indian variant phone which currently has widevine working properly to have a chance at restoring it later. China phones can't get L1 (or at least, I haven't learned a way to do so yet.)
What is Widevine L1 and L3?:
Right, so L1 or widevine L1 is a DRM security made by google after they noticed people use root, etc to steal copyrighted videos and movies in full HD and post them somewhere else for free. (Netflix and Amazon prime video app being affected.)
Losing this, means you get L3, and widevine L3 does not allow you to stream Full HD videos anymore, but you can stream SD low-quality videos. Which is never ideal.[
Now, EU latest stable, MortalOS uses modified china vendor with k20p L1 patch
So how do I save my L1 then? L1 Retention?:
Fortunately @Raaj52 found out that if you take a full Ofox or TWRP backup or everything from EU rom, (making a save on the PC, just in case) before moving to those aforementioned China-based ROMs is good.
When you try flashing miui EU latest stable after losing it by flashing a MIUI custom ROM based on China vendors, your phone gets L1, it shows you have L1 too, however, the apps on your phone DO NOT recognize it, technically the phone recognizes the widevine L1 as broken, and somehow considers it L3.
Here is where the Backup you made comes in handy, Clean flashing the backup completely and perfectly restores your L1. He also states that moving from China-based ROMs to AOSP ROMs like EvoX via clean flash (wiping vendor as well and flashing the proper vendor before flashing the AOSP ROM in the recovery) will also restore L1 (remember to format data partition when moving from miui to AOSP)
Now, It should be noted that cross-flashing vendors is very DANGEROUS, as this may break your Fingerprint Sensor, DTBO and proximity sensors. Therefore you must always flash the proper vendor for your phone (global, Indian, china) don't try flashing a vendor that isn't for your device. Unless if it's a custom MIUI rom as custom MIUI Roms come included with a Vendor. (wipe vendor before flashing custom miui ROM, after flash, don't touch the vendor)
Global vendor and Indian vendor are partially similar, and we have reason to believe that EU stable uses a modified vendor that works for both Raphael and Rapahelin. This is why EU ROMs works on both devices (MI 9t-pro and K20-pro)
Some Things to be Cautious about and to note:
Quoting our messages on telegram here:
The basic is, EU rom comes with vendor file so no need to flash a separate vendor for them. Flashing any vendor over the EU might break something because we don't know really which vendor they are using, assuming stables are global and betas are china.
On the other hand, AOSP comes without any vendor file, so it becomes mandatory to flash a vendor based on your device default vendor.
We flash vendors only when we flash AOSP's. In miui custom ROMs vendor is included.
Exception: If something is broken, clean wipe, flash your vendor, and then (advance wipe everything, including vendor) clean flash miui custom/AOSP.
Practically speaking, if you are moving from your stable own rom to Evox or any AOSP, no need to flash vendor since it is already having the default files but this is double confirm that the vendor is correct and it will not harm anyone. (AOSP to AOSP, not required to wipe vendor, but you can if you want to, I recommend wiping it and flashing your vendor again)
These are separate partitions and it will not override but to be on the safer side most rom devs prefer vendor and then rom.
If you flash an AOSP rom and want to move to a custom/stock miui rom make sure that you are own correct vendor. (Prior to wiping it in advance wipe) If not sure flash your vendor once again, then clean wipe and flash miui based rom.
Click to expand...
Click to collapse
How Get Back To My Stock ROM and/or Lock Bootloader?
To get back to your stock ROM, you have two methods, namely recovery zip ROM flash or fastboot ROM flash.
Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphael/
or if you need the Indian variant, Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphaelin/
Now, AND THIS IS SUPER IMPORTANT. Make sure you double-check and download the proper device's Region, codename, android version, and THE TYPE!!! (there are two types: recovery and fastboot types, choose the one you need)
Now for the recovery method, flash the recovery type .zip file the same way you flash any miui custom ROM. Check guide in first post/comment for method.
Now for the fastboot method, go to your mi-flash tool and enter fastboot on your device, and flash the rom there. (Now, I personally never did this method, so I can't guide the exact steps for this method, sorry)
LOCKING BOOTLOADER: You must first be using the proper stock vendor, stock rom via fastboot, and not have magisk or any MODs running on your phone. If you violate these, you WILL Hard brick your device. It is because of this I VERY STRONGLY advise against locking your bootloader for any reason whatsoever. JUST DON'T!!!
However, you can you the mi-flash tool (safest) or the debloater tool to lock your bootloader if you definitely must do it.
• Download MiFlash tool from MiFlashTool Website . The latest is the top left, marked with a NEW tag.
extract the file, and run the program "XiaoMiFlash.exe"
• Download the stock fastboot miui rom from Fastboot Website and extract the file (if its a .tgz or .tar extract again) you'll end up with a folder with one folder and 11 files (images, flash_all.bat.......misc.txt)
• Now in whatever rom you are on, go to developer settings, enable "OEM Unlocking" and "USB Debugging"
• Now boot into fastboot mode
• Connect your device to your PC
• Now in MiFlash tool, at the bottom, choose Clean all (and dont LOCK IT, I repeat do not choose to lock)
• Then on the top click on the "select" button and navigate to the folder with the 11 files & 1 folder and choose that folder.
• Click on the "Refresh" button and check if your device is shown (indicated by random numbers/letters)
• Now (recheck if its only CLEAN ALL only, and NOT lock or anything else)
• Now flash
• Wait 420s approx, or more, or less.
• It'll finish with an error and the message will say
• "error: Not catch checkpoint (\$fastboot -s . ' lock),flash is not done"
• This is cause it did not lock your bootloader. THIS IS GOOD.
• Now wait 5-10mins while miui 12.5 loads up/boots, it takes a while.
• Now, close MiFlash program, its done, no more needed.
• Now that's done, use miui 12.5 if you want, or go to recovery
• You'll see you have stock recovery now
• So go to fastboot mode, (phone connected to PC)
and flash the ofox recovery.img to get ofox recovery. via the cmd command like usual.
• Then go to recovery ofox.
• Go to wipe > format > type yes > format data to decrypt
• Reboot to recovery
• Now copy your ofox zip file to phone,
• Now flash that file to make OFOX permanent
• Now reboot to recovery again.
Click to expand...
Click to collapse
Latest MIUI-CN builds and miui custom ROMs soft bricking your device? (Mostly Raphaelin users)
Right, so this is a Xiaomi thing, which happens to many Xiaomi-based devices. It was later observed by a member on telegram that this usually happens to devices without NFC. In our case of Raphael - This would be Indian devices or Raphaelin devices.
I personally haven't experienced this, so I can't give a personal experienced-based guide on fixing this. However, another user on telegram @rockyanexpert solved his problem and shared this guide given below with me.
[
System has been destroyed. What I did:
1. Panicked a little
2. Started my lappy
3. MiUnlock Tool was pre-installed v3.xx
4. It took almost 10 minutes to show the login prompt. The connected device in fastboot. It failed to recognize the device. Started MiFlash. It did recognize the device.
5. Downloaded the latest MiUnlock. It too failed to recognize the device.
6. Downloaded XiaoMiTool v2
7. It detected the device fastboot serial correctly
8. Manually selected model Raphael.
9. Started with My device is bricked
10. It detected a locked bootloader. Opened its own version of Unlock Tool. Logged in to binded Mi Account. (My Mi Account n the binded one is the same)
11. Unlocked.
12. Tool went on ahead with waiting for the device to boot in fastboot mode.
13. I removed the device n forced boot in recovery mode. Ofox showed "Updating" n booted in orange ofox screen.
14. Rebooted system
15. Newly flashed Eu 21.2.3 started initial setup.
No data lost.
Click to expand...
Click to collapse
By these same people, they made a guide here: System destroyed issues
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
nice work @Sandeeep Kiran, keep it up.
Just got my 12/512 yesterday but my wait time is 15days (it said 360hours).:fingers-crossed:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
salva93 said:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
Click to expand...
Click to collapse
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Sandeeep Kiran said:
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Click to expand...
Click to collapse
Many thanks for your answer, so for now i will not risk and i will follow instructions on xioami.eu website, i'm in clean situation so i should not have any issue
bump
Good guide. Have a bump.
But till this day (Jan 6, 2020), no custom roms are stable or bugfree enough for the exception of xiaomi.eu
Default MIUIrom just works. But I hope in the near future we get to see bugfree roms and I will certainly try it! I have always used PE on my previous phones.
Cheers!!!!
bumpity bump
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
bigatim said:
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
Click to expand...
Click to collapse
Nah, Mount is to send/transfer files.
Since you arent doing that, you dont have to mount system or vendor, but mount your internal storage though.
and for the L1 flash, mount vendor for that only, soon a magisk mod will be available for it.
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
I've tried RevOS and I came back to mmx.
And widevine L1 is not break. Everything gone fine.
Krullendhaar said:
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case, you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
Click to expand...
Click to collapse
DFE is to remove encryption.
when you format data partition, you remove the dfe. You do this when moving from AOSP to miui or vice versa.
you can't decrypt before flashing cause there isn't a system or any data to decrypt. After you add a ROM or data, you can decrypt that.
yes, the format will get rid of your encryption. (but you also lose all your data) so flashing dfe helps retain your data. If you're scared someone will go to your recovery and steal data, add an orangefox password in its settings. Alternatively, you also have the dm-verity settings in orangefox settings you can enable. But redundant as its all included together in the dfe file I've attached.
Sandeeep Kiran said:
L3 Fix, Getting L1 after getting L3 for Global and Indian Users.
@Raaj52 Found a solution to fix L3 and get L1 again.
This fix however only works on Global and Indian vendors. (i.e mi 9t pro and k20p Indian variant)
No such solution has been found for china phones, using china vendor, DO NOT CROSS FLASH VENDORS!! it will cause a bootloop.
This patch was made for the latest EU beta, miroom. We hope it also works for future versions, and previous versions, but we are unsure. You can experiment and inform us though in the comments below.
Always have a proper fully working backup of everything rom. As caution. It's always good to take precautions.
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Click to expand...
Click to collapse
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
uurturk said:
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
Click to expand...
Click to collapse
The patch was intended to work on security patch Jan 20th and above, which maisk is not yet updated too.
(however, @ QasimXAli in the official telegram group did manage to make it work. you can tag and ask him there.)
Currently, the person who made the mod is still working to converting it to a perfect magisk module so it's easier to flash. Also, he is waiting for the next stable update to check whether the magisk module patch will continue to work.
We just gotta wait a bit longer.
ghaf85 said:
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Click to expand...
Click to collapse
Thanks.
Under add-ons, I added how to get WhatsApp dark (currently in WhatsApp official beta, which will roll out to stable in three months.)
For root, everyone just uses magisk latest stable.
and Solid Explorer or Mi-explorer
I like swift, liv and flux too. but those are straight-forward. I can add them to "add-ons" if you like.
Hi all,
I have created a GSI based on latest PHH AOSP Android 11
What is LeOS:
1. It's full ungoogled
2. It includes full Working MicroG
3. It includes Seedvauld
4. It includes SimpleGallery, SimpleContacs, Silence, Telegram, F-Droid, Jquarks, K9, DAVx5, OpenCamera, ASK, TotalLauncher
5. available as arm64avS, arm64avN, arm64bvS, arm64bvN
6. no google Apps will work !!!!
You can download latest release at https://leos-gsi.de/downloads
Which variant do I pick
To know which variant to download, use https://play.google.com/store/apps/details?id=com.kevintresuelo.treble . Don't use other Treble Check apps, they'll give wrong informations.
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
4. If you're on an Android 8.0 vendor, you'll need to stick to vendors with Security Patch Level before April 2019 (that's a bug of my GSI)
Join us a telegram group for support: https://t.me/LeOS_Support
Short overview: http://leos-gsi.de
November 3rd 2021:
from November builds on LeOS-R base will swap to Linage18.1.
November: 30ten 2021:
from December on LeOS-R will include AuroraServices
RESERVED
Download takes you to a login page with no option to register.
Vulnerability said:
Download takes you to a login page with no option to register.
Click to expand...
Click to collapse
For Username and Password try LeOS
I found the login info via Telegram.
Are you planning a real ungoogled version without microg?
Dunno if someone could be interested, but many users asked for an \e\ - a fully deGoogled mobile operating system (OS) and carefully selected applications, together forming a privacy-enabled internal environment for mobile phones - build for Exynos 7870-based devices...
Check here:
Request a Device
Did not find your device in the list of supported devices from /e/ ?<br> Please create a new topic with your device name.<br> The more the users who agree with your suggestion the better the chance of getting your device on the supported list.<br> Please note requests should be made in the...
community.e.foundation
forart.eu said:
Dunno if someone could be interested, but many users asked for an \e\ - a fully deGoogled mobile operating system (OS) and carefully selected applications, together forming a privacy-enabled internal environment for mobile phones - build for Exynos 7870-based devices...
Check here:
Request a Device
Did not find your device in the list of supported devices from /e/ ?<br> Please create a new topic with your device name.<br> The more the users who agree with your suggestion the better the chance of getting your device on the supported list.<br> Please note requests should be made in the...
community.e.foundation
Click to expand...
Click to collapse
I think a gsi would be a better option to let users try this os before asking for a full porting to \e\ foundation.
works on Huawei P10lite
forart.eu said:
Dunno if someone could be interested, but many users asked for an \e\ - a fully deGoogled mobile operating system (OS) and carefully selected applications, together forming a privacy-enabled internal environment for mobile phones - build for Exynos 7870-based devices...
Check here:
Request a Device
Did not find your device in the list of supported devices from /e/ ?<br> Please create a new topic with your device name.<br> The more the users who agree with your suggestion the better the chance of getting your device on the supported list.<br> Please note requests should be made in the...
community.e.foundation
Click to expand...
Click to collapse
The bad thing on eOS is, that it'S not uptodate. That's why I have created LeOS
ushilives said:
For Username and Password try LeOS
I found the login info via Telegram.
Click to expand...
Click to collapse
This is changed. No special login needed anymore
harvey186 said:
The bad thing on eOS is, that it'S not uptodate. That's why I have created LeOS
Click to expand...
Click to collapse
Are you planning to build a LOS degoogled by default? I really like your work but I want avoid every connection with Google and microG still has some connections with it.
eltanque9 said:
LOS degoogled by default?
Click to expand...
Click to collapse
I'm building from time to time an ungoogled LeOS-Q version, which is based on LOS17.1.
But my main work is building an ungoogled LeOS-R which is based on AOSP
Thanks for your precious share @harvey186
i tried to install Leos on my OnePlus Nord AC2003 (avicii), by following this guide
https://community.e.foundation/t/gs...note-9pro-with-super-partition-and-root/22648
but got the Qualcomm crashdump mode after finishing install and reboot.
Official LOS17.1 is working however, and now i'm trying to build an unofficial eOS build, but would love to have your LeOS working.
getthiswork2 said:
Thanks for your precious share @harvey186
i tried to install Leos on my OnePlus Nord AC2003 (avicii), by following this guide
https://community.e.foundation/t/gs...note-9pro-with-super-partition-and-root/22648
but got the Qualcomm crashdump mode after finishing install and reboot.
Official LOS17.1 is working however, and now i'm trying to build an unofficial eOS build, but would love to have your LeOS working.
Click to expand...
Click to collapse
Have you tried LeOS Q or LeOS -R ?? Which Android version (Pie or Q) was installed on your device ? Are you using OEM vendor or from a custom rom. Most issues are from not using OEM vendor sources.
We have one user which have installed LeOS on a AndroidGo device successfull
for better support, visit the LeOS community here
LeOS — NO GAPPS WILL WORK
Deutsch/englische LeOS support Gruppe. ACHTUNG: KEIN OffTopic erlaubt. Wer dagegen verstößt wird entlassen ————————————German/English LeOS support group. ATTENTION: NO OffTopic allowed. Whoever violates this will be fired
t.me
I tried LeOS R 20210106-RW-bvS.img.xz 2021-01-09 11:13 686M
My OnePlus Nord is delivered with Q (Oneplus 10.5.10 for the moment), and i think i'm using OEM vendor, since i haven't modified anything else.
From my understanding, it's an ARM64 A/B device, is the RW-bvs the correct ROM to use ?
Can you please tell us what's the meaning of RO RW avs avn bvs bvn ?
Thanks
OK, first a stupid question: You have decompressed the xz file ?
Why have you used such an old version ? Please try the latest. Yesterday I have uploaded a new set of GSI.
RW means system partition is write able. It's for people which want modify anything on /system.
RO means that system partition ins not write able. But all about versions you can find https://leos-gsi.de
Normally this way should work unlocked Q devices:
>adb reboot bootloader
>fastboot devices
>fastboot reboot fastboot
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
>fastboot reboot fastboot
>fastboot erase system
>fastboot reboot fastboot
>fastboot flash system LeOS.img
>fastboot -w
>fastboot reboot bootloader
>fastboot erase userdata
>fastboot reboot
if stuck in bootloop
>reboot in TWRP
>flash permissiver.zip
>reboot system
Great idea creating the ungoogled ROM! But it seems to be on the alpha stage yet, as I'm experiencing many issues after installing it to my Redmi 7A 3/32:
1) Screen is blinking sometimes, also brightness slider works very weirdly..
2) On initial load when opening location settings it crashes
3) When in battery saver mode the notifications indicator light constantly blinking and there's no setting to turn it off
4) Many apps have issues accessing SD card or even internal memory, so it makes them impossible to use (like apk downloaders, music players)
5) Contacts and calculator apps are missing, had to install additionally
The rest seem to be fine, the great thing is that all Magisk modules I use (Xposed, ViperFX, Dolby Digital) are working flawlessly!
To sum up - great work so far, but still requires a lot of polishing. Good luck!
Always make sure your system partition is big enough when installing. Apps missing or settings tabs not working correctly are symptoms that gsi did not install correctly.
thx, but I think it's more than a beta status.
to your issues:
1. it's a know issue of your device. On other devices it works as it should.
2. Seems you using an older version. It's fixed since January versions
3. Do you using OEM vendor? And which Android OEM version are the vendor sources ? A9 or A10?
4. Are you using FOSS apps ? Or Apps from Play Store ? Normally all apps have access to externalSD. You have to allow it. That's a A11 feature
5. You will never find a ROM or GSI wich has all apps you need. Most peopel are using the mini version because they don't want any default app.
I think you should try the latest LeOS from yesterday with the latest OEM vendor sources.
Sorry, i think you're confusing me with the user above me. Was just trying to help... I don't have this gsi installed
IamTheBRAVE said:
Sorry, i think you're confusing me with the user above me. Was just trying to help... I don't have this gsi installed
Click to expand...
Click to collapse
No, it was a helpful hint. That's why I have liked it
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
- Decrypts Android 11
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
Treble & Non-Treble Support
No compatibility.zip error while flashing OxygenOS
A lot of customisations
Extremely beautiful UI ready to please your eyes.
Dev team is always ready to fix your problems
F2FS support
Screenshots
Screenshots at
https://imgur.com/a/Ai8KWX9
and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://orangefox.download/
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!
Congratulations
Now official.
Long live the Fox
Device: Oneplus 5T
8GB 128GB.
UI 10/10
Installation 10/10.
Keep it up
Nice to see this recovery for oneplus
Maitreya29 post: 84100659 said:
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
...
Click to expand...
Click to collapse
Hi Maitreya29, and users,
Thank you for this! Will be trying this out soon...
I'm currently on the unofficial build from here:
[UNOFFICIAL] [RECOVERY] [OnePlus 5T] OrangeFox Recovery Project [R10.1]
OrangeFox Recovery /* * 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...
forum.xda-developers.com
Does this official build have any major changes or other functionality?
Has anyone tested a full backup and restore? Encryption? Custom ROM flash on A11?
Cheers
thkgop001 said:
Hi Maitreya29, and users,
Thank you for this! Will be trying this out soon...
I'm currently on the unofficial build from here:
[UNOFFICIAL] [RECOVERY] [OnePlus 5T] OrangeFox Recovery Project [R10.1]
OrangeFox Recovery /* * 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...
forum.xda-developers.com
Does this official build have any major changes or other functionality?
Has anyone tested a full backup and restore? Encryption? Custom ROM flash on A11?
Cheers
Click to expand...
Click to collapse
I would recommend switching for stability purposes only. This recovery is beautiful to say the least and everything as far as I can tell works completely well. I am on crDroid Android 11 flashed with this recovery.
Maitreya29 said:
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
...
Enjoy!
Click to expand...
Click to collapse
Hey OP, users,
I noticed something weird and I don't know if it's related to this build or just something wrong on my end (of course, running on a dumpling).
When I make a backup, the Fox directory (inside my storage root) looks empty inside Solid Explorer (and a couple of other file managers) inside A11. As if the directory is completely empty... No theme folder, no backup folder, like totally nothing. This is of course, with the option chosen of Solid Explorer showing all files, including hidden files.
But Fox's own file manager (and AromaFM) shows me my backups, and other files inside the Fox directory. The backups look like they are the right size too.
Something wrong with my set up? How come Fox's files are invisible to other file explorers?
Also, may I make a small cosmetic request for OP?
Please could you include the customisation option to hide the Fox logo on the splash screen? That way it wouldn't overlay on a user chosen splash wallpaper.
Thanks
thkgop001 said:
Hey OP, users,
I noticed something weird and I don't know if it's related to this build or just something wrong on my end (of course, running on a dumpling).
When I make a backup, the Fox directory (inside my storage root) looks empty inside Solid Explorer (and a couple of other file managers) inside A11. As if the directory is completely empty... No theme folder, no backup folder, like totally nothing. This is of course, with the option chosen of Solid Explorer showing all files, including hidden files.
But Fox's own file manager (and AromaFM) shows me my backups, and other files inside the Fox directory. The backups look like they are the right size too.
Something wrong with my set up? How come Fox's files are invisible to other file explorers?
Also, may I make a small cosmetic request for OP?
Please could you include the customisation option to hide the Fox logo on the splash screen? That way it wouldn't overlay on a user chosen splash wallpaper.
Thanks
Click to expand...
Click to collapse
Personally I use MiXplorer Silver, and I can see all of the Fox recovery files within the storage root. You may want to have a look at storage permissions from the file explorer you're using. If your willing to try another explorer I'd recommend MiX but I'm not entirely sure it'd solve your issue. Can you see anything with your default explorer, the one that came with your rom? Most if not all custom roms have a default. While bare bones it can at least give you an idea on if its your fault or the systems..
Mr.Conkel said:
Personally I use MiXplorer Silver, and I can see all of the Fox recovery files within the storage root. You may want to have a look at storage permissions from the file explorer you're using. If your willing to try another explorer I'd recommend MiX but I'm not entirely sure it'd solve your issue. Can you see anything with your default explorer, the one that came with your rom? Most if not all custom roms have a default. While bare bones it can at least give you an idea on if its your fault or the systems..
Click to expand...
Click to collapse
Hey Conkel
Thanks for the tips.
My default explorer (Files on MSM-Xtended 2.0) also shows that folder as blank - screenshot attached
Solid Explorer shows empty, but the correct modified date and time - screenshot attached
I installed MiXplorer 6.9.3 and gave it file system permissions as well as root permissions.
Fox folder Still empty - screenshot attached.
I'm stumped!
No big deal though, I can always use the Fox File Manager, but it's just so weird!
I'm going to delete the whole Fox folder later on tonight and start afresh. Maybe that might just work...
thkgop001 said:
Hey Conkel
Thanks for the tips.
My default explorer (Files on MSM-Xtended 2.0) also shows that folder as blank - screenshot attached
Solid Explorer shows empty, but the correct modified date and time - screenshot attached
I installed MiXplorer 6.9.3 and gave it file system permissions as well as root permissions.
Fox folder Still empty - screenshot attached.
I'm stumped!
No big deal though, I can always use the Fox File Manager, but it's just so weird!
I'm going to delete the whole Fox folder later on tonight and start afresh. Maybe that might just work...
Click to expand...
Click to collapse
I don't currently have any backups myself but as you can see here the fox folder + files are indeed visible. Keep in mind we're not on the same Android version or rom I'm on Android 10 CrDroid v6.13 I'm not sure why MsmExtended would be doing this but personally I've never used it.
Mr.Conkel said:
I don't currently have any backups myself but as you can see here the fox folder + files are indeed visible. Keep in mind we're not on the same Android version or rom I'm on Android 10 CrDroid v6.13 I'm not sure why MsmExtended would be doing this but personally I've never used it.
Click to expand...
Click to collapse
OK, so deleting the Fox folder seems to have fixed it... I can see the Fox files now.
Weird - probably a file system issue (not?) related to the ROM.
Or maybe because I was running the unofficial Fox and then flashed this official build on top.
Anyways, thanks for your help!
thkgop001 said:
OK, so deleting the Fox folder seems to have fixed it... I can see the Fox files now.
Weird - probably a file system issue (not?) related to the ROM.
Or maybe because I was running the unofficial Fox and then flashed this official build on top.
Anyways, thanks for your help!
Click to expand...
Click to collapse
Well incase it was for further reference I would recommend using fastboot to flash Orange Fox with the recovery.img it flashes right over top of the current recovery so nothing can go wrong like that. Anytime no problem.
Is there any ETA on the possibility of decrypting systems where a password is used (instead of pattern)?
Or is it something that will never be implemented for Android 11?
riki66 said:
Is there any ETA on the possibility of decrypting systems where a password is used (instead of pattern)?
Or is it something that will never be implemented for Android 11?
Click to expand...
Click to collapse
Much needed, now that we have twrp supporting android 11 pin/password decryption. @Maitreya29
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this these posts about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
What is the difference between cheeseburger and dumpling builds?
Self-answering myself: cheeseburger is for OnePlus 5, dumpling is for 5T.
Merry Christmas and Happy New Year, by the way.
Barkuti said:
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this these posts about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
What is the difference between cheeseburger and dumpling builds?
Self-answering myself: cheeseburger is for OnePlus 5, dumpling is for 5T.
Merry Christmas and Happy New Year, by the way.
Click to expand...
Click to collapse
Welcome to the family!! Also yes stock roms kill any custom recovery only way to avoid this is with a custom rom of your choosing, the recovery is replaced upon booting into system, if you need to reboot into recovery or bootloader for any reason it should work just fine. This is a beautiful recovery I highly recommend! As far as roms there are plenty to choose from. Good luck, have fun and most importantly enjoy your new device!
Thanks for the nearly instant reply Mr.Conkel.
Of course I am into custom ROMs, needless to say. I like stable, featured and powerful software (software as God commands I like to say). Right now I am still running AospExtended 5.7 on a Z2 Pro, you can guess I don't like to unnecessarily mess with my software when it works.
I am wondering what to choose for the 5T (which is not for me but it has to be like if it were), my intuition is leaning me for a crDroid build. Suggestions are welcome.
I also see people speaking about the “encrypted vs unencrypted” storage thing (I have never encrypted my storage), and the need to flash a no-verity-opt-encrypt zip (?) patch. Suffice to say I am green in this respect, just read Download no-verity-opt-encrypt All Versions @ Android Infotech, which still does not make much sense to me regarding the encrypted vs unencrypted thing. However, since I am rooting it smells like flashing no-verity-opt-encrypt is mandatory for me.
LoL sorry for the long off-topic.
Barkuti said:
Thanks for the nearly instant reply Mr.Conkel.
Of course I am into custom ROMs, needless to say. I like stable, featured and powerful software (software as God commands I like to say). Right now I am still running AospExtended 5.7 on a Z2 Pro, you can guess I don't like to unnecessarily mess with my software when it works.
I am wondering what to choose for the 5T (which is not for me but it has to be like if it were), my intuition is leaning me for a crDroid build. Suggestions are welcome.
I also see people speaking about the “encrypted vs unencrypted” storage thing (I have never encrypted my storage), and the need to flash a no-verity-opt-encrypt zip (?) patch. Suffice to say I am green in this respect, just read Download no-verity-opt-encrypt All Versions @ Android Infotech, which still does not make much sense to me regarding the encrypted vs unencrypted thing. However, since I am rooting it smells like flashing no-verity-opt-encrypt is mandatory for me.
LoL sorry for the long off-topic.
Click to expand...
Click to collapse
If your looking from a daily perspective I highly recommend running Android 10 as A11 is still pretty rough around the edges and isn't as feature heavy yet. Although that will come in time. For now I would recommend crDroid A10 or Resurrection Remix A10 (A11 isn't out yet). I use Rr as a daily with MadKernel it works great. All these threads are relatively easy to find. But for stability over features always go with LineageOS. Cr and Rr hardly have any bugs but they do exist and you can run into a few issues. Just let me know if you need more information.
Cheers!!
Thanks for the advice concerning A10 vs A11 Mr.Conkel.
One of the things I love from AEX is
a proper task switcher. Guess I got traumatized back in the day with the LAME Lollipop card task switcher which I swear to have seen on much more modern OSes. It also is super stable, the only noticeable issue I have found in it is the settings app crashing when I hit “root management” in the settings menu (an irrelevant hiccup).
Thanks for the tips in any case.
Barkuti said:
Thanks for the advice concerning A10 vs A11 Mr.Conkel.
One of the things I love from AEX is
a proper task switcher. Guess I got traumatized back in the day with the LAME Lollipop card task switcher which I swear to have seen on much more modern OSes. It also is super stable, the only noticeable issue I have found in it is the settings app crashing when I hit “root management” in the settings menu (an irrelevant hiccup).
Thanks for the tips in any case.
Click to expand...
Click to collapse
If task switching is what your looking for then I highly recommend Resurrection Remix OS I use slim recents and its wonderful. Here's a screenshot for perspective. Mad Kernel is what I use it with but that isn't mandatory.
Mmm, but Slim Recents can be installed onto whatever ROM, doesn't it?
We'll see, we'll see.
Important information:
This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
SELinux Permissive
Encryption
Connecting to some Bluetooth Classic devices
Installation:
If you are on the stock OS, you will first need a custom recovery. You can get the recommended Lineage recovery here.
If you are coming from stock or other ROMs, you need to do a factory reset, and resize your partitions with this tool. It is highly recommended to flash it using ADB sideload.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on wt88047
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
Google Drive
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to tipzrickycheung
Donate via PayPal to nicknitewolf
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@tipzrickycheung, @althafvly, @nicknitewolf, Lineage Team
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M8936FAAAANUZM-1.33887.1.41528.1
Based On: LineageOS
Reserved
New update!
20220218
- Fixed Bluetooth
- Baseband and IMEI now detected
Download
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
Yup, I am on Coolapk
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
About the expansion zip, you need to have the stock partition layouts to start with.
New update!
20220219
- Fixed LiveDisplay
- Added SEPolicy Changes
- Added Binder and lmk kernel backports
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
I'm just popping in to say this looks very promising! Thanks for caring about this device. Please don't give up with this build
New update!
20220227
- Fixed Hotspot (Can be fixed for 18.1 too)
- Software navkeys now works properly
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
BangJhon.id said:
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
Click to expand...
Click to collapse
Use the partition expand package first
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
I think I might have fixed bug 3, will push an update when appropriate.
one by one step i try, no fixed this message, from recovery all path, partisi, i not working instal lineage os based 19.0
New update!
20220228
- Fixed TimeKeep (?)
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
RandomNewbie said:
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
Click to expand...
Click to collapse
No, and we don't support using that tool.
tipzrickycheung said:
Use the partition expand package first
Click to expand...
Click to collapse
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
SaneComputing said:
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
Click to expand...
Click to collapse
Update your TWRP.
New update!
20220323
Android 12L!
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Still using latest twrp but error show up everytime