[RECOVERY][UNOFFICIAL] TWRP-3.2.3-x [beryllium][20180831] - Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other

{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
twrp*.img
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
/data decryption does not work
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [beryllium], Tool/Utility for the Xiaomi Poco F1
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Alpha
Created 2018-08-31
Last Updated 2018-08-31

Reserved for changelog.

Shivam Kumar Jha said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod as /data decryption doesnt work.
twrp*.img
Kernel source: Prebuilt stock
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [beryllium], Tool/Utility for the Xiaomi Poco F1
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Alpha
Created 2018-08-31
Last Updated 2018-08-31
Click to expand...
Click to collapse
HAHAHA nice to see you here , finally things starting to pop . Thanks for the twrp , well how's you now ?

Downloading

Vatumb said:
View attachment 4584746
Click to expand...
Click to collapse
You have unlocked the device as well ?

+1

Harry_00s.HS said:
You have unlocked the device as well ?
Click to expand...
Click to collapse
Yes already unlocked the bootloader and rooted the phone

Vatumb said:
Yes already unlocked the bootloader and rooted the phone
Click to expand...
Click to collapse
Whoa,
I am not able to do as mi unlock gives error for 720 hours now
can you help and give steps how did you do ??

PrathaM X said:
Whoa,
I am not able to do as mi unlock gives error for 1440 hours
can you help and give steps how did you do ??
Click to expand...
Click to collapse
Even I get an unlock error for 720 hours ...

Noice

Can I restore vendor image from current rom on gsi treble rom?
Sent from my Mi A1 using Tapatalk

we have treble support for poco f1?

When i saw your name, I thought I landed on cancro thread by mistake great to see you here!
Mind sharing how you unlocked the bootloader? Official tool is asking me to wait 360hours. :/ Thanks.

Anybody interested about Custom Kernel for poco f1? I will need testers?
Sent from my Mi A1 using Tapatalk

themarine.sujit said:
we have treble support for poco f1?
Click to expand...
Click to collapse
Yes. Any phone shipping with Android Oreo and above is treble compliant.

anyone with root willing to test this?
https://forum.xda-developers.com/poco-f1/help/poco-f1-lte-bands-unlock-t3835467
please backup your efs and persist before you try.

munchy_cool said:
anyone with root willing to test this?
https://forum.xda-developers.com/poco-f1/help/poco-f1-lte-bands-unlock-t3835467
please backup your efs and persist before you try.
Click to expand...
Click to collapse
Do you mind sharing the method you used to unlock the bootloader? Waiting for 360 hrs is a bit too long.

Nigam666 said:
Do you mind sharing the method you used to unlock the bootloader? Waiting for 360 hrs is a bit too long.
Click to expand...
Click to collapse
there is no method buddy. if the app tells you to wait for 360 hrs you have to. no way around it. for those who have already unlocked the bootloader no one why they didnt have to wait for 360 hrs.
PS:- I do not own the device nor have I unlocked the bootloader. I am waiting for someone to test band 2 and 4 so I can buy it.

Wow! Thanks, gonna test soon.

Related

[SFOS] [EXPERIMENTAL}SailfishOS 2.0.2.48 for Redmi 2

{
"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"
}
The Alpha release was experimental and was not meant for the general public, but still recieved an overwhelming response. This new Beta version is free of most bugs encountered earlier and is suitable for everyone to get a taste of SailfishOS on their phone.
Read the installation instructions carefully.
Changelog from Alpha -->
* Bluetooth fixed.
* Audio now works out of the box.
* Camera Resolutions updated.
* Flash now works in Camera.
* Settings app now shows settings for cellular networks.
* FM-Radio now supported. ( Highly Experimental. Read the FM-Radio section below )
* Stand-by time vastly improved.
* Basic Jolla apps are now pre-installed. ( Before anyone talks about bloatware, you got the option to uninstall them)
* Warehouse, the community appstore is now pre installed.
Sailfish OS’s heritage lies in Nokia times, especially in the MeeGo operating system. Prior to 2011 Nokia and Intel had a vision of an open mobile operating system. Together they invested around 1 billion USD to the project and created an open source based operating system called MeeGo, which was used as a basis for several devices, such as the iconic Nokia N9. Although the Nokia N9 became the beacon of open source operating systems, Nokia decided to end the project and chose instead to continue with Microsoft’s Windows Phone OS. The rest of that is another story.
For more information about SailfishOS click here.
SailfishOS has now been successfully ported to Redmi 2 and here I am sharing the steps to install it on your phone.
Code:
Disclaimer: Your warranty is now void. You will lose all your data on your phone and may render it unusable. This software is provided as is without any warranty of any kind whatsoever. The user shall solely be reponsible for any consequence arising out of following this guide. I, or anyone else shall not be held responsible for bricked devices, dead sd-cards, thermonuclear war, you getting fired because the alarm app failed or any other consequence of following this guide. The linked zip contains some proprietary files.
tl;dr I wont be held responsible for any unfortunate incidence.
Prerequisites -->
1) Latest TWRP recovery installed (Others may work too but I haven't tested). You can get it here-->http://forum.xda-developers.com/redmi-2/development/recovery-recovery-built-source-inside-t3277621
*Note that the Cyanogenmod version is now changed.
2) cm-12.1-20160318-UNOFFICIAL-wt88047 zip by kumajaya. You can get it from his google drive link here--> http://forum.xda-developers.com/redmi-2/development/rom-cyanogenmod-unofficial-builds-t3200883
3) SailfishOS zip file. Download link given below.
This is not an Android ROM and thus the instructions to install are quiet different. Follow them carefully.
1) Boot to recovery. Wipe cache, dalvik-cache, system and data.
2) Copy the Downloaded files to the sdcard via USB.
3) Install cm-12.1-20160318-UNOFFICIAL-wt88047. Do NOT reboot after installing.
4) Install SailfishOS zip file. The installation will take around 10 minutes so don't think that its stuck. Ignore any errors about being unable to mount data partition.
5) Reboot System when installation succeeds.
Notes-->
1) This is not an Android ROM. Android apps will not work right now. But a way for Android apps to work is available but will take quiet some time before it gets on our device.
2) Root access (using devel-su in terminal) requires a password which can be set in Settings>Developer Options.
3) For advanced users, you can ssh into the device after setting a password in Developer options using ssh [email protected] over USB.
4) Do not register for a Jolla account. You will get an error about failed IMEI registration. This will be fixed as soon as Jolla allows ported devices to be registered.
5) The Store will not work. It needs a Jolla account. You can however use the openrepos warehouse for installing apps.
6) MTP over USB does not work.
7) Battery drains faster if screen is ON. Better than alpha but still needs improvement.
FM-Radio -->
You can play FM-Radio now but it is experimental.
Plug in your headphones and launch the PirateFM app for radio.
if it won't start, open terminal and use "harbour-piratefm" to start it.
Once the app starts, it should show a frequency. If its stuck at 0.0 MHz, then close the app(close, not minimise) and restart it again.It should show a frequency now. If you have echoing audio in the headphones, i.e. you hear your own voice in the headphones, then open terminal and " systemctl restart --user pulseaudio" and then try running the app again.
FM will not work through the speakers, and it also cannot be muted.
Download Link -->
The file has been named as alpha-2 because that is how it was initially intended but it would be better to designate this as beta since its almost stable.
https://www.androidfilehost.com/?fid=24591020540823211
DO NOT SHARE MY WORK WITHOUT MY EXPLICIT PERMISSION. IF YOU ARE SHARING, LINK TO THIS POST.
XDA:DevDB Information
SailfishOS 2.0.2.48, ROM for the Xiaomi Redmi 2
Contributors
adeen-s, @mal- @sledges @kimmoli @Stskeeps @spiiroin @Litew @jusa_ @ketut.kumajaya
Source Code: https://github.com/adeen-s/droid-config-wt88047 ; https://github.com/adeen-s/droid-hal-version-wt88047 ; https://github.com/adeen-s/hybris-boot/ ; https://github.com/adeen-s/droid-hal-wt88047 ; https://github.com/adeen-s/android_kernel_cyanogen_msm8916 ;
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Must not have flashed lollipop MIUI update.
Based On: SailfishOS
Version Information
Status: Testing
Current Beta Version: 1
Beta Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-09-17
Reserved
For Android app compatibility, I need help from someone with significant experience in compiling cyanogenmod. PM me.
Reserved
Warning : This procedure will wipe all data on your device.
MultiROM thread--> http://forum.xda-developers.com/redmi-2/development/mod-multirom-v33-t3381373
MultiROM Instructions -->
1) Get the modified twrp and multirom zip from the multirom thread.
2) Reboot to recovery, select Install, select install image, choose the modified twrp and flash it to recovery partition.
3) Reboot recovery. It should now boot up to the modified TWRP.
4) Wipe Data,System,Cache and Dalvik-Cache.
5) Select Install from Recovery main menu. Select cm-12.1-20160318 zip. uncheck all options and install it.
6) Again Select Install from Recovery main menu. Select SailfishOS zip file and uncheck all options and install it.
7) Select MultiROM settings ( small button on top right corner in main menu of recovery). Select inject current boot sector. Reboot or install secondary ROM of your choice now.
8) For adding Secondary ROMs of your choice, refer to the MultiROM thread.
I tried the first, alpha build, it was really really good, but can you please tell me how to install it as a secondary ROM havin it's own kernel via multiboot, as I was really tires of switching kernels everytime I had to switch between CM13 and SailFish.
I hope it's possible.
.
Also, will it not work with the latest, Lolipop Bootloader? (As i can make out from the "Required Firmware" section from OP)
shanx_verma said:
I tried the first, alpha build, it was really really good, but can you please tell me how to install it as a secondary ROM havin it's own kernel via multiboot, as I was really tires of switching kernels everytime I had to switch between CM13 and SailFish.
I hope it's possible.
.
Also, will it not work with the latest, Lolipop Bootloader? (As i can make out from the "Required Firmware" section from OP)
Click to expand...
Click to collapse
Since the base cyanogenmod will not work with the lollipop bootloader, it cannot be done. Sailfish will work if a way to run the base cm over the lollipop bootloader is found.
As for the multiboot, I haven't tried it yet but take a look at this http://forum.xda-developers.com/showpost.php?p=67519570&postcount=62 although it was already addressed to you.
@adeen-s well as per the updated devolvement for wt88047, CM now supports Lollipop bootloader. Can you please guide us through the process of having SFOS as secondary? Is it like installing any other secondaries?
@adeen-s can you change base sfos to cm13
Sent from my 2014817 using Tapatalk
NeoDarkness said:
@adeen-s can you change base sfos to cm13
AFAIK Sailfish OS 2.0 Can only run over CM 10.x 11.x 12.1.
Source- Sailfish OS Hardware Adaptation Development Kit
Click to expand...
Click to collapse
iamsubhranil said:
@adeen-s well as per the updated devolvement for wt88047, CM now supports Lollipop bootloader. Can you please guide us through the process of having SFOS as secondary? Is it like installing any other secondaries?
Click to expand...
Click to collapse
CM-12.1 still does not.
SF.OS doesn't work with LP BootLoader. Thanks for the Info.
adeen-s said:
CM-12.1 still does not.
Click to expand...
Click to collapse
Oh, and there I was, wondering why my SFOS wasn't booting on LP Bootloader.
wow sailfish os enters beta
What are remaining issue items? battery drain fixed?
Bugs
Hi, i love this os and hope android apps support is coming soon.
the bugs that i found is the music player seem to show the same mp3 file as 2 different file but one with correct duration and the other one is zero.
for problems, the battery draining quite fast :crying:
thank you for your hard work dev!!!
@adeen-s that means if i flash the rom as secondary having k loader, it'll work?
@adeen-s What a beautiful typographical OS with fluent transitions. Been using it with MultiROM keeping my previous primary RR 5.7.1 as secondary. Everything is pretty good on my side. Just animations are quite unfluent sometimes. And some USSD codes aren't showing when dialed. Like *143*0# and *400# on Aircel(404 91).
Using it, wow!
iamsubhranil said:
@adeen-s What a beautiful typographical OS with fluent transitions. Been using it with MultiROM keeping my previous primary RR 5.7.1 as secondary. Everything is pretty good on my side. Just animations are quite unfluent sometimes. And some USSD codes aren't showing when dialed. Like *143*0# and *400# on Aircel(404 91).
Click to expand...
Click to collapse
How did you return to the KK bootloader, buddy?
iamsubhranil said:
@adeen-s that means if i flash the rom as secondary having k loader, it'll work?
Click to expand...
Click to collapse
Not sure. I tried it once and it didn't work. It may need a workaround to work as secondary.
shanx_verma said:
How did you return to the KK bootloader, buddy?
Click to expand...
Click to collapse
I had backed it up using twrp. Just restored Firmware. U flash any miui kk fastboot
---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------
adeen-s said:
Not sure. I tried it once and it didn't work. It may need a workaround to work as secondary.
Click to expand...
Click to collapse
Yup MR showed some errors about not founding fstab
Here's some screenshots
Hey guys. It's wonderful!
iamsubhranil said:
Hey guys. It's wonderful!
Click to expand...
Click to collapse
Thanks for the screenshots. I'm glad to know you liked it.
iamsubhranil said:
I had backed it up using twrp. Just restored Firmware. U flash any miui kk fastboot
Yup MR showed some errors about not founding fstab
Click to expand...
Click to collapse
Okay, I have the firmware partition backed up. What all will it restore - will it restore the KK modem as well? (cuz I don't want KK modem, just the bootloader).

[RECOVERY][UNOFFICIAL] TWRP-3.2.3 [20181212]

{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
BUGS:
You tell
NOTE:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
XDA:DevDB Information
TWRP recovery, Tool/Utility for the Xiaomi Poco F1
Contributors
vasishath
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Beta
Current Stable Version: v2
Stable Release Date: 2018-12-12
Created 2018-10-11
Last Updated 2018-12-14
Reserved
Download links:-
https://www.androidfilehost.com/?w=files&flid=283470
THIS TWRP DOES NOT DISABLE FORCE ENCRYPTION. IT WILL DECRYPT THE ENCRYPTED DATA WITHOUT THE NEED OF FORMATING IT
DO NOT POST WITHOUT READING THIS:
Two reasons why you are unable to successfully decrypt data. (unable to get past the lock)
1. You must have flashed older security patch rom
Example: You have flashed a rom which has december security patch. Later flash a rom with November or Oct security patch. Decryption Fails
Reason: In Android 8.x, devices implementing Keymaster 3 or earlier were required to verify the version info (ro.build.version.release and ro.build.version.security_patch) reported by the running system matched the version info reported by bootloader. Such information was typically obtained from the boot image header. Further, they disallow any downgrade to older security patch or android version.
2. The person who compiled the rom failed to add encryption support.
Solution: Ask that person to add support or flash the one that supports encryption.
great work
Nice work!
Great work as always :good:
Many thanks Vasi for huge efforts!. Will give me another try with the encryption of LOS 16!
Inshallah boys played well
Great work!!!
Thanks! Its great!
Enviado desde mi POCOPHONE F1 mediante Tapatalk
Finally thank u very much!
Hello, I am kinda confused. What's the advantage of this over the other recovery? What decryption bug fix is applied onto this?
kishore1998 said:
Hello, I am kinda confused. What's the advantage of this over the other recovery? What decryption bug fix is applied onto this?
Click to expand...
Click to collapse
No need to flash force decryption anymore.
@vasishath does this support usb otg, and MTP?
Edit: nvm I flashed it and answer is yes & yes lol
Well done! I don't need to smash my head over it anymore
But where is source link? To device tree, not TWRP...
If I flash twrp every time I update ROM should I flash it again;
Στάλθηκε από το Mi A1 μου χρησιμοποιώντας Tapatalk
So if i have a encrypted phone with MIUI 10 Global Beta with this TWRP i can go to recovery type my PIN and it will decrypt so i can flash things and keeps the ROM encrypted ? or the things with this TWRP is that is keeps roms decrypted ?
tlf55 said:
So if i have a encrypted phone with MIUI 10 Global Beta with this TWRP i can go to recovery type my PIN and it will decrypt so i can flash things and keeps the ROM encrypted ? or the things with this TWRP is that is keeps roms decrypted ?
Click to expand...
Click to collapse
From the OP:
"NOTE:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit."
So, MIUI Global Beta 'might work'
Thanks for your hard work
Good job.
Thank you.

[ROM][9.0][OFFICIAL][PINE][NIGHTLY][SHARE] MoKee Open Source Android Project

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[SIZE="4"]
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* I am not the maintainer or developer, I found this and wanted to share it on XDA
*/
[/SIZE]
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
I AM NOT THE DEVELOPER OF THIS ROM AND I ONLY MAKE THIS THREAD FOR XDA COMMUNITY. IN ANY CASE, MOKEE AND GuaiYiHu HAS ALL THE RIGHTS OVER THIS ROM.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
VoLTE
ViLTE
Known issues:
You tell me
Instructions :
Download this TWRP Recovery and install it.
Download the ROM (MK90.0-pine-xxxxxxxxxx-NIGHTLY.zip)
Go into TWRP Recovery — Wipe — Advanced Wipe — Select: Dalvik、Data、Cache、System — Swipe to Wipe
Install the ROM (MK90.0-pine-xxxxxxxxxx-NIGHTLY.zip)
If you have problems during the flash, you have to unpack the archive and delete the "compatibility" file. Once that is done, put all the files together in a new archive. ZIP, and you will have no problems during flash.
Downloads:
[*]MoKee Download for PINEhttps://download.mokeedev.com/pine.html
MoKee Add-Ons:
[*]MoKee Extras
MoKee Help & Support links:
[*]MoKee Announcements
[*]MoKee Changelogs
[*]MoKee Forums
[*]MoKee Guides
[*]MoKee Statistics
[*]MoKee Gerrit
[*]MoKee Bug Reports
Sources: https://github.com/GuaiYiHu/android_kernel_xiaomi_sdm439
Credits:
GuaiYiHu
Mokee Development Team
LineageOS
If you like it, don´t forget to say thanks!
XDA:DevDB Information
Mokee Open Source Project, ROM for the Redmi 7A, ROM for the Redmi 7A
Contributors
GuaiYiHu
ROM OS Version: 9.x Pie
Based On: Mokee Open Source Project
Version Information
Status: Nightly
Current Beta Version: 2019-10-27
Beta Release Date: 2019-10-24
Created 2019-10-28
Last Updated 2019-10-28
Release types:
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
This is nice, but I think the flashing method is "copy pasted" from original site, and therefore will not work on this device. But i am not sure.
what i meant that wont work is that this device's normal flashing method requires a lot of reboot to recovery, while the OP's instructions is for A devices only.
regularfanb0y said:
This is nice, but I think the flashing method is "copy pasted" from original site, and therefore will not work on this device. But i am not sure.
what i meant that wont work is that this device's normal flashing method requires a lot of reboot to recovery, while the OP's instructions is for A devices only.
Click to expand...
Click to collapse
Actually 7A is A-only device, working as system-as-root.
The OP's instructions are right, cuz I installed it this way and everything works fine.
Thank you this is a good step forward. I'm going to try this rom later this evening.
Wipe data of format data?
Coming from stock MIUI 11 Android 9 do I have to format the data partition or to wipe it? Usually MIUI to AOSP needs a format.
Luelu said:
Actually 7A is A-only device, working as system-as-root.
The OP's instructions are right, cuz I installed it this way and everything works fine.
Click to expand...
Click to collapse
Alright my bad, but flashing a gsi rom, we need to restart a lot(wipe, reboot to recovery, flash gsi, reboot to recovery, flash zips, reboot to system)
While this rom is installed in a traditional way (wipe and flash just like the old days) if someone can explain why itll be really appreciated.
I am really new to GSI and this phone but i am willing to help testing stuffs for development for this device! only if TWRP restore function works
Davv said:
Coming from stock MIUI 11 Android 9 do I have to format the data partition or to wipe it? Usually MIUI to AOSP needs a format.
Click to expand...
Click to collapse
Nop, just wipe.
Luelu said:
Nop, just wipe.
Click to expand...
Click to collapse
Thank you so much
---------- Post added at 09:31 PM ---------- Previous post was at 09:00 PM ----------
cant download twrp, I cant create a QQ Account, evrytime i try to verificate my phone number it asks to send an sms to a chinese number but that doesnt work. can someone reupload it on some other cloud service?
I appreciate your work, but TWRP is impossible to download, not with all these chinese characters. I see a QR code but I want to download to my PC first.
Even google was unable translate it
Jazzda said:
I appreciate your work, but TWRP is impossible to download, not with all these chinese characters. I see a QR code but I want to download to my PC first.
Even google was unable translate it
Click to expand...
Click to collapse
I used twrp LR team from gsi post and worked with this recovery.if you need root download su add .magisk don't work...
Newest Magisk seems to be working through recovery at least work for me for installing NanoDroid.
There seems to be problem with setting up mobile hotspot. Mobile hotspot cant be seen or accessed with SSID either.
ROM also lacks possibility to have navigation bar binded.
Is it possible to use the SD Card as internal storage with this rom? It's more or less the single reason I'd flash a different rom for.
the batery life it is much smaller than miui's
I flash the rom following the instructions, but my cel doesn't boot, only reboot and boot to twrp, i'm only flashing the system without su, magisk or gapps, but it's the same, what can be wrong?
Ranfiel said:
I flash the rom following the instructions, but my cel doesn't boot, only reboot and boot to twrp, i'm only flashing the system without su, magisk or gapps, but it's the same, what can be wrong?
Click to expand...
Click to collapse
flash stock rom and flash again the rom
ElFanta said:
flash stock rom and flash again the rom
Click to expand...
Click to collapse
The same, doesn't boot, it's curious because the GSI roms doesn't work for me too, i don't know why. I'm coming from MIUI 11, but i rollback to 10.2.5 so shouldn't have problem with this, but i have.
I rollback with MiFlash Tool with fastboot rom global
EDIT: I get the GSI Rom working, just format DATA and type YES on TWRP
EDIT2: After make the DATA reset with TWRP i was able to boot with the MoKee Rom :3
mais 14 said:
I used twrp LR team from gsi post and worked with this recovery.if you need root download su add .magisk don't work...
Click to expand...
Click to collapse
Maybe try using patched boot img from gsi thread.
Ranfiel said:
I flash the rom following the instructions, but my cel doesn't boot, only reboot and boot to twrp, i'm only flashing the system without su, magisk or gapps, but it's the same, what can be wrong?
Click to expand...
Click to collapse
Try format data for twrp and reboot.
Ranfiel said:
The same, doesn't boot, it's curious because the GSI roms doesn't work for me too, i don't know why. I'm coming from MIUI 11, but i rollback to 10.2.5 so shouldn't have problem with this, but i have.
I rollback with MiFlash Tool with fastboot rom global
EDIT: I get the GSI Rom working, just format DATA and type YES on TWRP
EDIT2: After make the DATA reset with TWRP i was able to boot with the MoKee Rom :3
Click to expand...
Click to collapse
The batery life is good in your rom? In my phone is a sh*t

[DEPRECATED][ROM][diOS][N] Samsung Galaxy Tab A 7.0 LTE SM-T285 (gtexslte)

{
"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"
}
This is discoveryOS (diOS)
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About this project: discoveryOS (or in short: diOS)
I was not satisfied with any external car navigation system I can get because either they are ultra slow, outdated, having bad user experience, missing speed cam support or simply taking ages to get a gps lock within my car.
So the main approach here is not having the best ROM for all users but for those having the same need then I have. Usually these both should not conflict so if I fix an issue for my needs it might fix yours as well. But my focus is navigation, nothing (much) else.
Examples: if Camera has issues I might not solve it, if calling has issues I might not solve it, etc.
Features of discoveryOS
fully based on /e/ OS for a full google-free experience
F-Droid (OpenSource Apps as an alternative to Google Play) including extra repos
debloated everything not needed for diOS (for details check this list)
Integrated MagicEarth Navigation
Integrated Automate App
Integrated Aurora Store
Speaker output optimized for speech (i.e. increasing loudness as much as possible)
my builds come with full OTA update support (from v2.0 on)
(... you know that thing which informs you that a new update is there and where you just click to download + install)
Roadmap
Implementing Kiosk Mode for navigation only (might be provided as a separate build)
links: <--- abandoned by using the app "Automate" instead
the one I will go for (tested fine already): https://www.sdgsystems.com/post/pro...droid-devices-with-a-device-owner-application
older approaches:
Implementing Kiosk Mode in Android - Part 1
Part 2 Part 3 Part 4 Part 1: No Android Changes Required Note: Looking for Kiosk mode in Android Lollipop 5.0 or later? Skip to part 3. What is “Kiosk Mode” and why would you want to use it? Kiosk Mode basically allows a single Android application to have full control of the system. The user is...
www.sdgsystems.com
Implementing Kiosk Mode in Android - Part 3: Android Lollipop (and Marshmallow)
Part 1 Part 2 Part 4 Part 3: Android Lollipop (and Marshmallow) Android 5.0 (Lollipop) and 6.0 (Marshmallow) now have an official Kiosk Mode that anybody can use, but they don’t call it Kiosk Mode. They call it “screen pinning” or “task locking”. This article will provide information on how to...
www.sdgsystems.com
Implementing Kiosk Mode in Android - Part 4: A Better Provisioning Method for DPC / Device Owner
Part 1 Part 2 Part 3 In part 3 of our series on kiosk mode, we provided source code for our Set Device Owner app. This app allows you to provision Android Lollipop and Marshmallow devices using the “device bump” method, which configures device owner apps or device policy controllers (DPC) such...
www.sdgsystems.com
Integrate my created Automate flow to simulate a KIOSK mode (i.e. start navigation on boot and keep it on top always)
Requirements
Your device need to be unlocked (seriously?!)
Latest TWRP/SHRP build is highly recommended, e.g. mine: see my recovery post
Do a full Nandroid backup before doing anything else!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Backup
When you flash diOS the first time:
Wipe: System and do a factory reset !
A LOT of bad stuff can happen otherwise
Flash the ROM
Optional (if you want root): Flash Magisk
Flash OpenGapps ????? STOOOOOOOOP NO No no! you don't want that on a google-free phone! diOS contains everything you need to live without Google!
Boot (be patient on first boot!!! SIM detection might take a minute after the FIRST boot after clean flash as well)
Open Maps (MagicEarth) and click the download button to get your country/region maps
Open Automate to import the kioskmode flow
Open F-Droid -> Settings -> Repositories and choose those you want to enable (most of them are described here) & swipe down to update the repo list.
Open Aurora -> choose Anonymous as long as you don't want to have paid apps working
Enjoy
Known issues
no OMS support! OMS is a hack DEEP in the android sources and all these are outdated now. if you need that use jedl's build
build is ENG , i.e. "adb root" will work and no auth required for ADB
bluetooth is working but using the blobs by jedld's build until I find the time fixing the android sources (unfortunately the repo of jedld does not contain the full history so I have to compare manually...). Until then I keep it like that.
not charging on USB connection (normal power supply works fine) - still investigating. Seems to be an issue with my kernel.
This ROM is just coming with BASIC stuff so several apps you might want to see in a regular Android ROM are simply not there.
Examples (excerpt only!):
- no Camera app
- no Browser app
- no Gallery app
- no Email app
- no Calendar app
- no <fill-in-whatever-you-are-missing>
the complete list can be found here always
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Download
Get the builds from my leech server
discovery OS: https://leech.binbash.rocks:8008/discoveryos/nougat/gtexslte/
Note:
Builds are updated when I decide to do so. There is no build cycle.
Changelogs
search results from this thread: click
Credits
LineageOS
jedld, really! thanks dude, not just for giving a starting point but also for providing your sources.
... if I forgot to mention YOU, tell me
Sources
It took me a while (2 or 3 weeks iirc) to clean up all the sources from jedld in order to be able to update and keep in sync with LOS itself.. All these can be found here:
github org
build manifest
XDA:DevDB Information
discoveryOS, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld (without his work I would never had bought that tab! he made all the main parts until 2018!)
Source Code: https://github.com/smt285
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: /e/ OS
Version Information
Status: Beta
Beta Release Date: 2020-11-19
Created 2020-04-03
Last Updated 2020-11-20
everything around my recovery images
RECOVERY images
Download (shrp + twrp)
TWRP: here
SHRP (recommended): here
I provide 3 formats:
IMG (twrp only)
TAR (shrp & twrp)
ZIP (shrp only)
When to use the IMG (twrp only)?
If you flashed a custom recovery already
if you like to flash by download mode with heimdall
When to use the TAR (shrp & twrp)?
If you never flashed a custom recovery before you have to use this one
if you like to flash by download mode with ODIN or JOdin
When to use the ZIP (shrp only)?
If you want to switch from TWRP
if you want to upgrade from one SHRP version to another
if you flashed the TAR of SHRP in download mode by ODIN or JOdin you HAVE to flash this ZIP in SHRP once
How to flash the IMG?
boot to your custom recovery
push the IMG to your device (e.g. by adb)
select flash
ensure you select "IMG" (when in TWRP. when in SHRP that is not needed)
select the IMG file
choose "Recovery" as the "Target Partition" and flash
Reboot to Recovery to complete the setup.
How to flash the TAR?
boot to download mode
start ODIN/JOdin
put the TAR into the AP/PDA slot
ensure the "Auto Reboot" is NOT ticked/checked
flash
turn the device off (HOME+PWR+VOLDOWN) and directly switch just the VOLDOWN button to VOLUP when it wakes up and hold all 3 buttons until you see the recovery loading
How to flash the ZIP?
boot to your custom recovery
push the ZIP to your device (e.g. by adb) (or start and use adb sideload and you are done)
select flash
select the ZIP & Flash
Reboot to Recovery to complete the setup
Reserved
New build arrived
Changelog
Release date: 2020-04-03
Download: see OP
initial build:
I had a REALLY hard time to actually make LOS 14.1 boot with cleaned sources.. thought the ramp-up will take a week at most .. but that was way off..
jedld had done several patches within AOSP and I had to find out which are required where etc. the main reason why my build were not booting at all (which is f**** hard to debug without and log and/or adb ) was that one.
But I needed to clean the sources as several parts of these were incredible outdated and so needs to be udpated.
I had spent several more days to cleaning up even more stuff and finally uploaded a test build.
feel free to join but read the KNOWN ISSUES topic carefully before.
It is still in a very early state and I have tested pretty much nothing else then boot, apps, bluetooth, WiFi
Kernel:
switching to EUR kernel
implemented kernel build within LOS build!
added own TWRP defconfig
moving kernel modules like WiFi to /system
.... and more (see "Detailed changes")
LOS:
added alle needed TWRP configs
moving kernel modules like WiFi to /system
sepolicy updates for rild
.... and more (see "Detailed changes")
Detailed changes:
LOS: this build VS. last build (by jedld, yea 19 pages ... was a long time )
Device tree: github
Kernel: github
.-
For those interested I will also provide SHRP (skyhawk recovery) after some testing and fine tuning ...
Sent from my OnePlus 6T using XDA Labs
Testing and report
Thank You for this Great JOB
---------- Post added at 07:32 PM ---------- Previous post was at 07:10 PM ----------
steadfasterX said:
For those interested I will also provide SHRP (skyhawk recovery) after some testing and fine tuning ...
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
Migration from Lineage Jed for LOS 7.1.2
Recovery 3.3.1.1 Ok
installation Ok
Magisk Ok
Google Apps Ok
Fist Boot Ok
Wifi and sensors Ok
OpenCamera working Perfectly
ROM stable Ok no errors in all files i recomend this release for all users Galaxy Tab T285
Great Job Great ROM.
Hacker.
May I know how do I flash your TWRP build? I am using Odin and I am supposed to flash .tar.md5 file right? Yours is in disc img file and when I try to extract / mount it shows "corrupted file".
nicktsh said:
May I know how do I flash your TWRP build? I am using Odin and I am supposed to flash .tar.md5 file right? Yours is in disc img file and when I try to extract / mount it shows "corrupted file".
Click to expand...
Click to collapse
Ah yea I haven't uploaded the ODIN file yet. Thanks for reminding. You can either wait for that or flash any of the other available TWRP versions for the smt285 which have a ODIN package. Once you have TWRP you can simply flash my img from within TWRP to update .
Sent from my OnePlus 6T using XDA Labs
Great piece of work, very much needed. Thanks Bro.
I wished if volte would have worked, is there any chance!
---------- Post added at 07:24 AM ---------- Previous post was at 06:33 AM ----------
Getting CTSProfile false in Magisk 20.4, any fix ?
रRudra said:
Great piece of work, very much needed. Thanks Bro.
I wished if volte would have worked, is there any chance!
---------- Post added at 07:24 AM ---------- Previous post was at 06:33 AM ----------
Getting CTSProfile false in Magisk 20.4, any fix ?
Click to expand...
Click to collapse
VoLTE is always a pita. So no.
Will check cts profile, should be fixable ..
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
VoLTE is always a pita. So no.
Will check cts profile, should be fixable ..
Click to expand...
Click to collapse
ctsprofile issue solved, I can share the solution if u need! Thanks
रRudra said:
ctsprofile issue solved, I can share the solution if u need! Thanks
Click to expand...
Click to collapse
Fingerprint .. I just need to add it but if you can share the exact one from stock it saves 2min for me
EDIT: nvm got it.
Sent from my OnePlus 6T using XDA Labs
I recently flash the rom, mobile data to long to open. Thank for this, still finding bugs
Having trouble flashing a custom recovery. Odin doesn't seem to like me. Could anyone help me out?
Installed - works fine but found one annoying bug - lockscreen is not rotating at all - it's only vertical and not want to rotate to horizontal when I rotate device.
how to install this ?
im having error on flashing it through twrp 3.1.1.1 it states error 7
jayrakiztah said:
im having error on flashing it through twrp 3.1.1.1 it states error 7
Click to expand...
Click to collapse
use the latest TWRP linked in the OP.
steadfasterX said:
use the latest TWRP linked in the OP.
Click to expand...
Click to collapse
twrp 3.1.1.1? it is already installed
jayrakiztah said:
twrp 3.1.1.1? it is already installed
Click to expand...
Click to collapse
nope. 3.3.1.1 is the latest and it is linked in the OP
.-
steadfasterX said:
nope. 3.3.1.1 is the latest and it is linked in the OP
.-
Click to expand...
Click to collapse
i flashed your sharp recvoery and it still got an error 7

[ROM][13.0][guacamoleb] Project Elixir [OFFICIAL] [Stable][AOSP]

{
"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"
}
Project Elixir for the OnePlus 7 [guacamoleb]
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions, and proper bug reports are important to us but don't be disrespectful to anyone here. Your suggestions and proper bug reports will be taken into consideration.."​
Project Elixir is another aftermarket AOSP ROM which basically offers minimal UI enhancement & close to Stock Android ROM with great performance, security and stability. Most of the OEMs' these days will provide slow and untimely updates, but we don't do that here. We closely follow Google to bring the latest updates to our users, and even prolong support for devices that have been declared obsolete by OEMs. Our ROMs' source code is open-source, secure, stable, and outstanding. Your experience while using Project Elixir will be butter smooth without compromising the quality of the Android experience. In short, it's perfectly balanced between Great Performance, Security, stability, minimal UI & awesome features including pixel goodies So do not hesitate anymore, join us now and start enjoying the beauty of stock Android. Download and enjoy Project Elixir on your respective devices!​
- Saurav - Founder / lead Developer
- Nishant - Co-lead Developer / Team
- Master - Developer / Team
- Mayur - Developer / Team
- And Also Our Hardworking Maintainers​
// Checkout the latest changes you get //
Spoiler: Click Here to see
Latest Changelog: https://projectelixiros.com/changelog
NOTE : In Project Elixir you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
// A screenshot is worth of thousand words //
Spoiler: Click Here to see
Latest Screenshots : https://projectelixiros.com/gallery
NOTE : In Project Elixir you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
--------- > OFFICIAL Download Server < ---------
NOTE: Please keep in mind that these are Gapps Builds and there is no vanilla build of this rom available.
--------- > Visit Our OFFICIAL Website < --------- ​
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
CLEAN FLASH (Moving From A12 to A13)
- Download the latest build
- Take a backup for safe side
- Boot to Recovery
- Format Data
- Sideload the latest build
- Reboot
What works?
Wifi | RIL | Mobile data | GPS | Camera
Flashlight | Camcorder | Bluetooth | Fingerprint reader | Lights | Sound | vibration
Almost everything
What doesn't work? or Any Bug ?
You tell me!
BUG REPORT !!
As soon as the problem occurs, take a logcat and please inform us via Telegram or XDA.
for more READ THIS​
- Android Open-Source Project
- Pixel Experience
- LineageOS
- Proton AOSP
- Arrow OS
Special Thanks goes to Shantanu Sarkar
[PixelExp. guacamoleb Maintainer]
- Please note that this is my secondary device so all tree work is done by him.
XDA Banner and Template Credit goes to Amaan
- Others, I may have forgot to mention​
- Android OS version: 13.0
- Security patch: November 2022
- Build author/Device Maintainer : Saurav
- DEVICE: OnePlus 7
- DEVICE CODENAME: guacamoleb
---- Sources and Documentation ----
-- ROM Source Code --
-- Kernel Source --
-- Documentation & Maintainership --​
-- OFFICIAL Website and Telegram Support --
-- Visit our OFFICIAL Website --
-- Device Update Telegram Channel --
-- Support/Discussion Telegram Group --​
// Giving a little can HELP a lot //
- As you know build is free but building ROM needs server and in order to maintain the source, we need High-End Servers that are generally very expensive and need to be renewed every single month and as a student its quite difficult. To meet with our technical expenses, a cup of coffee, and the efforts of the developers we need your monetary support!
- Do consider donating or buying me a coffee on Paypal or join us on for sustainable support and rewards if you want to appreciate our work.
- Thank you for your support !
* UPI ID: [email protected] (Indian Users)
* Paypal: https://www.paypal.me/uglykid24
* Bitcoin (BTC): 3Pm6JtwqCuTfKe1Szn23C8ZutF32eFtzf9​
Reserved
I m gonna try this rom today and i m extremely happy that OnePlus 7 now have Android 13 custom rom
Thank you very much.im waiting for this looong time. i have one question is google unlimited photos upload mod works in this rom? Or how to get full backup of my 12.1 rom
laiya1 said:
Thank you very much.im waiting for this looong time. i have one question is google unlimited photos upload mod works in this rom? Or how to get full backup of my 12.1 rom
Click to expand...
Click to collapse
Look i haven't installed this rom yet but i will in one or two day and only then i can tell you if it has unlimited Google storage
But about other thing how to backup of 12.1 rom
You can just backup your personal files after that you are good to install this rom
If you want to go on stock 12.1 again then you can just use msm tool to flash Android 10 and fhen ota update to android 12.1 but make sure you have pc or laptop for flashing your device.
But thereis another shortcut method
After installing project elexir you can just go to twrp and then install official oxygen OS 12.1 on both slots and then you are again on 12.1
I liked this rom a lot and using it since the build was released. I like the fluidity of UI, Animations and Apperance of the rom. And the best part is, it comes with lot of customisation options. Thanks for making this rom for OnePlus 7.
Prinçe çharming ap said:
Look i haven't installed this rom yet but i will in one or two day and only then i can tell you if it has unlimited Google storage
But about other thing how to backup of 12.1 rom
You can just backup your personal files after that you are good to install this rom
If you want to go on stock 12.1 again then you can just use msm tool to flash Android 10 and fhen ota update to android 12.1 but make sure you have pc or laptop for flashing your device.
But thereis another shortcut method
After installing project elexir you can just go to twrp and then install official oxygen OS 12.1 on both slots and then you are again on 12.1
Click to expand...
Click to collapse
thank you. im currently on evolutionx 12.1. can you tell the steps to install this? im stuck at fastboot with downloaded rom
abhijeet.07 said:
I liked this rom a lot and using it since the build was released. I like the fluidity of UI, Animations and Apperance of the rom. And the best part is, it comes with lot of customisation options. Thanks for making this rom for OnePlus 7.
Click to expand...
Click to collapse
can you tell how to install this?
laiya1 said:
can you tell how to install this?
Click to expand...
Click to collapse
First flash the recovery which
laiya1 said:
can you tell how to install this?
Click to expand...
Click to collapse
Just flash the recovery in fastboot mode. I used pixel experience recovery but you can use TWRP or any other recovery available for your device. Then enter in recovery mode and by adb sideload install the rom in your device.
abhijeet.07 said:
First flash the recovery which
Just flash the recovery in fastboot mode. I used pixel experience recovery but you can use TWRP or any other recovery available for your device. Then enter in recovery mode and by adb sideload install the rom in your device.
Click to expand...
Click to collapse
i tried but it says cannot read package
Y
laiya1 said:
i tried but it says cannot read package
Click to expand...
Click to collapse
laiya1 said:
i tried but it says cannot read package
Click to expand...
Click to collapse
You unlocked bootloader of your device?
Watch tutorials on YouTube if you are new in this. Method of flashing is same for every rom just the recovery is different.
abhijeet.07 said:
Y
You unlocked bootloader of your device?
Watch tutorials on YouTube if you are new in this. Method of flashing is same for every rom just the recovery is different.
Click to expand...
Click to collapse
yes im on evolution x 12.1 rom. i tried on differnt recoveries too
abhijeet.07 said:
Y
You unlocked bootloader of your device?
Watch tutorials on YouTube if you are new in this. Method of flashing is same for every rom just the recovery is different.
Click to expand...
Click to collapse
can you send me the recovery of this rom?
abhijeet.07 said:
Y
You unlocked bootloader of your device?
Watch tutorials on YouTube if you are new in this. Method of flashing is same for every rom just the recovery is different.
Click to expand...
Click to collapse
it says * cannot read 'android13rom.zip' *
Hi guys. I've installed this rom and it's the best i tried until now. The only one problem i've found is that every video takes at least 5 seconds until play. It makes me nervous xD
abhijeet.07 said:
Y
You unlocked bootloader of your device?
Watch tutorials on YouTube if you are new in this. Method of flashing is same for every rom just the recovery is different.
Click to expand...
Click to collapse
i manged to install this rom. previous i downloaded zip was damaged. can you share your boot.img in this rom? i want to root
laiya1 said:
i manged to install this rom. previous i downloaded zip was damaged. can you share your boot.img in this rom? i want to root
Click to expand...
Click to collapse
As I said I used pixel experience boot.img. And u can download it from their site.
anyone have boot.img of this rom please?
abhijeet.07 said:
As I said I used pixel experience boot.img. And u can download it from their site.
Click to expand...
Click to collapse
i installed from that. i need to patch boot.img to root. i need boot img of this rom.
abhijeet.07 said:
As I said I used pixel experience boot.img. And u can download it from their site.
Click to expand...
Click to collapse
And I don't know by using boot.img file of Pixel Experience there will be no issue. So better ask your maintainer.

Categories

Resources