Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am proud to present first Dualboot project For Cagabi one. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (like /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Cagabi one and other MT6580 devices to the DualBootPatcher App, I am not the developer, I am just the maintainer.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app from the download section below.
What does the app do ?:
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set correctly and under Partition configuration select secondary (will install 2nd ROM in /system) or data or external SDCard slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like LO13-20170807-cagabi-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
Other How to ?
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Source:
Source
All Releases:
Releases
Downloads:
07-Aug-2017 First Release
12-Aug-2017 Second Release
15-Aug-2017 Third Release
19-Aug-2017 Fouth Release
25-Aug-2017 Fifth Release
13-Sep-2017 Sixth Release
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@RendyAK for inspiration, help and tips
@yshalsager I copied his thread because I am too lazy
Enjoy
Changelog
Changelog
07-08-2017
Code:
[U]Added support for:[/U]
- Cagabi one
- Doogee X5 max
- Doogee X6
- GiONEE P5W
- GiONEE Marathon Mini
- Leagoo Z5
- Infinix Hot 3
- Symphony P7
12-08-2017
Code:
Downgraded the source to a previous stable release (Reseted the commits)
[U]Added support for:[/U]
- Alcatel Pixi 4-4
15-08-2017
Code:
[U]Added support for:[/U]
- Cherry Mobile Flare S5 Max
- Micromax Q354
19-08-2017
Code:
[U]Added support for:[/U]
- Walton Primo GH6
- Cherry Mobile Touch XL
- Cherry Mobile Flare J3
- Wiko Lenny 2
25-08-2017
Code:
[U]Added support for:[/U]
-Alcatel Pixi 4(5)
- Alcatel Pixi 4(7)
- Symphony i10
- Tecno l8 Lite
- Walton Primo GF4
- Walton Primo N2
13-09-2017
Code:
- Updated source (Now it is stable)
[U]Added support for:[/U]
- Tecno W4
- Lava Iris821
- Archos Helium 55 Plus
- Mororola Moto C
Screenshots
Some screenshots of the supported devices
Note for all: If you are using a custom rom, make sure your build.prop has your device name correctly! Otherwise you will face issues. (same goes for the default.prop in the recovery.img)
Well-done buddy !
keep it rocking
Thanks for adding Gionee P5W
Great work sir. :good:
Download link for 07-08-2017 release have been updated
Hello all, I started Dual Boot Patcher project for MT6580 devices, and I already built for 9 devices, but it seems that the source of the app is unstable for now.
I have opened an issue on github for the original developer to fix, and I also found users who are having the same problems with DBP and opened an issue before. (Check on github)
So please wait for fixes, in meantime I will continue to maintain more MT6580 phones.
Regards,
Ahmed Rahmy
New release is up
- Updated download links
- Updated change log
Enjoy
Does this work with recoveries other than twrp?
Please Made This For Micromax Q354
Mine Device name: Micromax Q354 MT6580 3.18.19+
I can't Sent the link in your post....they said error
Hello Mr. Mysteryagr, I am making my request to build dualboot patcher for my device
---------- Post added at 07:25 AM ---------- Previous post was at 07:01 AM ----------
Can you make one for me?
liccolailo said:
Does this work with recoveries other than twrp?
Click to expand...
Click to collapse
Yes
EsTaHaD_MrIdUl said:
Mine Device name: Micromax Q354 MT6580 3.18.19+
I can't Sent the link in your post....they said error
Click to expand...
Click to collapse
Send a pm to me
liccolailo said:
Hello Mr. Mysteryagr, I am making my request to build dualboot patcher for my device
Can you make one for me?
Click to expand...
Click to collapse
Added Support already
New build is up
Added support for:
- Cherry Mobile Flare S5 Max
- Micromax Q354
Make one for Walton Primo GH6
Stock Build.prop: https://pastebin.com/x9D5VfRF
Mountpoints:
System- /dev/block/mmcblk0p18
Data- /dev/block/mmcblk0p20
Boot - /dev/block/mmcblk0p7
abid.nnt said:
Make one for Walton Primo GH6
Stock Build.prop: https://pastebin.com/x9D5VfRF
Mountpoints:
System- /dev/block/mmcblk0p18
Data- /dev/block/mmcblk0p20
Boot - /dev/block/mmcblk0p7
Click to expand...
Click to collapse
Added support, will be available in the next release
*Maybe it is off topic*
@Mysteryagr,
can you tell me why i am getting this error?
-
make[2]: *** [data/devices/devices.json] Error 1
make[1]: *** [data/devices/CMakeFiles/run_devicesgen.dir/all] Error 2
make: *** [all] Error 2
The command "make" exited with 2.
-
i tryed to compile the dualboot patcher (downgrade branch) using travis.
but it is ending with this error
i froked the repo from your git.
froked git : https://github.com/Parthib24/DualBootPatcher
EDIT:i think i found the problem....it is problem in walton.yml ....i am so foolish
Parthib said:
*Maybe it is off topic*
@Mysteryagr,
can you tell me why i am getting this error?
-
make[2]: *** [data/devices/devices.json] Error 1
make[1]: *** [data/devices/CMakeFiles/run_devicesgen.dir/all] Error 2
make: *** [all] Error 2
The command "make" exited with 2.
-
i tryed to compile the dualboot patcher (downgrade branch) using travis.
but it is ending with this error
i froked the repo from your git.
froked git : https://github.com/Parthib24/DualBootPatcher
EDIT:i think i found the problem....it is problem in walton.yml ....i am so foolish
Click to expand...
Click to collapse
Yes, it was your device.yml
-
Good news for Walton Primo GH6 users, chenxiaolong has merged my pull request and now your device is supported officially, and you can enjoy automated builds
Rest of the devices are still pending, I hope he accepts them all
Mysteryagr said:
Yes, it was your device.yml
Click to expand...
Click to collapse
and why latest patches not working in my phone?
only that downgrad branch is working ..
Parthib said:
and why latest patches not working in my phone?
only that downgrad branch is working ..
Click to expand...
Click to collapse
You should ask in the original thread, anyway they were unstable updates.. I guess it is fixed now, cherry-pick new commits
Hi everyone!
I present to you the practical and simple guide special for dummies that will allow you to try and use the wonders of google treble project in our beloved Moto Z [Griffin has no official support but...] thanks to the great work of the highly recognized developer @erfanoabdi we can enjoy project treble in an easy way [*could apply user restrictions] in our griffin.
*First of all, this guide is designed for those who are curious and have a high degree of autonomy when they try to solve low level or common problems of the Android system. You dont need to be a developer but you must have experience in using and applying the following words: unlocked bootloader, ADB and Fastboot basic commands, Lineage OS, TWRP, Magisk , Back to Stock, Frustration, No "daily driver user" or maybe according to your needs, contribute to general knowledge, dont demand from me more than here is already here because I'm not a developer, I'm just a curious user who likes to try new things in his griffin and I have already given you more than 168 hours of trial and error with the only goal of making the process easier and more fun to you.
Now let's go to what interests us, do you have your bootloader unlocked?
If the answer is no, go here and do it or you can not continue
First we start with the files that we need to download:
Latest Lineage OS from here:
https://download.lineageos.org/griffin
[Thanks to Erfanoabdi]GSI image of your favorite flavor from here:
https://mirrors.lolinet.com/firmware/gsi/
Only type A not AB just A like ColorOS-Aonly-9-20190605-ErfanGSI.img.7z not ColorOS-AB-9-20190605-ErfanGSI.img.7z and decompress the .7z file to get the IMG file inside.
To decompress the .7z file
https://www.7-zip.org/download.html
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
Official TWRP from here:
https://dl.twrp.me/griffin/twrp-3.3.1-0-griffin.img.html
Latest Stable Magisk from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Thanks to @topjohnwu
Magisk module "Device Spoofing Tool" from here:
https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435
Thanks to @Dreamer(3MF)
Device ID apk from here:
https://androidfilehost.com/?fid=673956719939830832
Latest Android System WebView APK from here:
https://www.apkmirror.com/apk/googl.../android-system-webview-76-0-3809-36-release/
Finally put this on favorites because you will need it for the final touch:
https://www.google.com/android/uncertified/
Only if you have all those files downloaded and placed in your PC in the folder that you want you can continue.
Now the easy way step by step if you are on Official Stock ROM:
1 - Reboot to Bootloader and flash twrp-oemasvendor-2.img you can use ADB and fastboot of the .rar adb-fastboot-latest.rar that you ¿downloaded? from the back to stock link
Use
Code:
fastboot flash recovery twrp-3.3.1-0-griffin.img.img
Hard-reboot to bootloader again, down two steps and select reboot to recovery.
2 - Already in TWRP do this:
2.1 - Wipe Data - if it gives you error go reboot and select reboot recovery and again wipe data it should have been erased without errors, back and
2.2 - Manually wipe caches, system, vendor, data, internal storage
2.3 - Do "Swipe to Factory Reset" probably not necessary but for me it works.
3 - Now connect your Griffin and copy the Lineage OS ROM downloaded [obviously still inside of TWRP]
3.1 Go to Install and select the copied Lineage ROM and then install
3.2 Finished the installation restart and skip all startup, now in the launcher screen shutdown your griffin
4 - Power on your griffin again in bootloader, two steps down and select reboot recovery again.
4.1 - Now in TWRP copy the GSI type A image that you downloaded [MIUI, ColorOS, OneUI, Pixel, Flyme OS, etc)
4.2 - Allready copied go to Install and select "Install Image"
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, clear cache and restart to System.
5 - Be very patient, you will see the warning image for having your bootloader unlocked for 5 to 10 seconds [may vary] then you will see the start animation according to the GSI image that you will select before, again be very patient it can take 3 to 15 minutes to your griffin to start completely (MIUI 3-5 minutes, Pixel 3-5 minutes, OneUI 5-10 minutes, Flyme 15 to 20 minutes in my experience) If you see that the start animation reduces its brightness after a few minutes, it means that we are on the right track wait a little longer.
5.1 - Finally we start system we enter directly without previous configurations (configure wifi, google account, PIN, etc) just start screen now go to step 6, if not then go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
And start again
6 - Ok you are one of those who managed to install and start their GSI image and you dont have google services enabled and your griffin is not certified you probably have app errors that crash infinitely [if they are 1 or 3 - example the camera] manage to go to app administration in the ROM and cancel auto-start of that apps, instead if you have so many apps errors that dont let you move anything in the interface you need to go to TWRP and clean davlink cache and cache and reboot.
That's why this step is important
Code:
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, [B][COLOR="Red"]clear cache and restart to System
[/COLOR][/B].
7 - Now Root your griffin with Magisk, you know how otherwise I dont know how you got here
8 - Already in system, install the "Device Spoofing Tool" magisk module and reboot to activate the module.
9 - Again already in system, install Device ID APK
9.1 - Open Device ID app and find your device’s GSF (Google Service Framework) Device-ID
9.2 In your PC go HERE and use your GSF to register and certify your griffin
10 - Now install Android System WebView APK
10.1 - Go to TWRP again and clean cache one more time and reboot to system
11 - Configure your google account and be happy
11.1 - Camera its a common fail, use Gcam or Snapdragon Camera instead of GSI stock camera app
12 - Enjoy your griffin :highfive:
Well that's all from me and remember if something goes wrong or it does not work you can always go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/mot...mware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
The 99.99999999 percent of all this, maybe more, it's thanks to @erfanoabdi If you want to thank someone, buy a coffee for him.
Screenshots (sorry just from MIUI with my emotion I forgot to save from the other GSI that I proble) I feel comfortable with MIUI and now it is my ROM-GSI of daily use in my griffin (I really love taking screenshot with my three fingers )
https://ibb.co/bmDkRrz
https://ibb.co/HX3mghC
https://ibb.co/10jGLNr
https://ibb.co/jz6njXm
https://ibb.co/vv1Nr2F
https://ibb.co/9Gr29nv
https://ibb.co/qsZ2pFD
https://ibb.co/948H110
https://ibb.co/42nXM72
https://ibb.co/Jd73QwC
https://ibb.co/vVs15Hq
https://ibb.co/MVfptZ5
https://ibb.co/SywLwrW
https://ibb.co/ZXvg0QG
https://ibb.co/z8DF8L1
https://ibb.co/bBv1wxW
https://ibb.co/09nBnHW
Finally dont be mad with my english, itis very bad and I use translator
Thanks for guide, very cool
Official TWRP is updated with treble support BTW
Nice ,thanx to your contributions.
whats the waiting time for the moto image? ive installed the moto image, and still waiting for the device to bootup. its been about 15 mins
---------- Post added at 07:46 PM ---------- Previous post was at 07:25 PM ----------
after installing the image, im stuck on this (device will boot in 5 seconds screen) Can i boot back into recovery, and re install the image? its been more than 30 mins on this screen
Pixel image is the only one I managed to boot, but couldn't get gsf id from it, and it constantly force closed (cache was cleaned) and couldn't make it work at all. Moto image just gives black screen, all other images couldn't even be installed (either error in twrp or something else.) I'll try miui image one of these days, but would really like to try to make pixel image work, but without gsf id it's impossible
EDIT: Changed twrp to twrp-oemasvendor-2.img version, and managed to boot miui (but after magisk it bootlooped) and to start booting moto GSI images (moto bootloops), and just tried to boot pixel images, will see later... but I think that the problem was that twrp uses cache as vendor partition, and deleting cache, well, deletes vendor partition (will need clarification from @erfanoabdi on this)...
Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?
anwesh said:
Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?
Click to expand...
Click to collapse
Nop, Omni does not have the type of partition needed
After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...
anwesh said:
After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...
Click to expand...
Click to collapse
Go to TWRP and make full wipe factory, that fix the problem
I've been hunting down and trying out some different gsi's. With the latest twrp + los16 installed I've had success with some from this list
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
AOSP 10 with gapps included
Msm xtended gapps included
Blissrom + gapps
Aosip + gapps
EvolutionX gapps included
DU13 + gapps (not on list but works)
If installing gsi's without gapps included, let it boot first then reboot TWRP and install gapps + magisk if you want root.
Available kernel ?
I cannot retrieve the GSF id, how can I fix this?
Flashed OneUI GSI but it's stuck on the boot logo
So on my Moto Z running LineageOS 17, I can't launch Netflix on it. Will Treble-ing my Moto Z fix that problem?
This also works on moto z force?
Please read the whole of the following before starting anything!
DISCLAIMER: I am in NO WAY RESPONSIBLE for the potential destruction or loss of your data, regardless of its importance or value to anyone. YOU chose to apply these modifications, not me, and hence YOU are solely responsible for whatever happens to your device. Failure to follow any of the instructions below may lead to an erratic non-functioning device. Even if you come back as keyboard warriors to blame me for your device exploding with the force of the Tsar Bomba, I'll simply take a drink and laugh at your behavior.
Hello, Walton Primo H5 users! For too long you've been stuck with a buggy, spyware-ridden OS, and so I come to the rescue!
Introducing the Dot OS ROM!
Features:
1. OS upgraded from 6.0 to 7.1
2. Substratum baked in + built in themes
3. MiraVision
4. Six built in themes
5. Trebuchet Launcher
6. Root access baked in
7. AudioFX fully working
8. Redesigned settings and QS panel
9. Various statusbar customisations
10. Advanced reboot menu
... and many more!
Bugs:
1. Bluetooth headsets connect, but don''t play any audio.
Please note that this is my first ever attempt at making a custom ROM, and I have made every effort to make it as bugless as possible. If you have any methods to fix the above, or have found any new bugs, please include the solution and/or problem below and I'll patch the ROM accordingly and credit you in the OP
Prerequisites:
1. Install TWRP from this guide. Ignore this step if you already have it installed.
2. Download the ROM from here.
3. Download OpenGapps pico 7.1 ARM from here.
4. Copy the ROM and OpenGapps zips to the Internal Storage of your device.
5. Remove all passwords from your phone
Instructions:
1. (Optional but highly recommended) Boot into TWRP and back up every single partition, and then copy and paste the TWRP folder in your Internal Storage / SDcard to your PC. This is to restore in case things get bad.
2. Boot into TWRP and wipe Dalvik/ART Cache, System, Cache and Data.
3. Install the DotOS zip package
4. Install the Gapps package
5. Reboot, setup google account, and enjoy!
To enable root access (recommended):
6. Now open settings. If it shows up blank, go to recents menu and slide it away, and open it again.
7. Go to the very bottom, click About phone, tap on the Build number 10 times in succession.
8. Go to developer settings, and click on Root access, then select Apps and ADB. In the prompt that appears, click OK.
To improve performance:
9. Install Kernel Adiutor app from play store.
10. Open the app, allow root permission, and click the three dots menu on top left.
11. Click on Low Memory Killer, scroll to the end, and click Very Aggressive.
12. You now have a faster, more up-to-date ROM! :laugh:
13. If you liked it, please hit the Thanks button below
All ROM credits go to ahadrox for his amazing ROM here! This ROM would not exist without his hard work, so go to his page and hit the thanks button too!
Welcome to POCO F1 Ultimate Collection!
(beryllium)
OFFICIAL STOCK MIUI ROM
You can check my Guides for installation.
Recovery ROM V12.0.3.0.QEJMIXM
Fastboot ROM V12.0.3.0.QEJMIXM
POCO F1 Global Stable ROM Library / POCO F1 MIUI Official ROMs Archive
FIRMWARE & VENDOR
POCO F1 Firmware
POCO F1 Vendor
POCO F1 Latest Firmware & Vendor
CUSTOM ROMS
You can check my Guides for installation.
Note: I've created an award system for people which are not familiar with custom ROMs, to help them choose a ROM which is stable for daily use, gets frequently updates with security patches every month and has active development, so they don't mess with ROMs which appearing and then dissapearing (and we have a lot of them).
ROMs under awarded ROMs are not order by rating and just have random order.
If you are knowledge, you can ignore my awards and choose any ROM you like.
My standards for giving award to a ROM are:
Open Source
Stable enough for daily use
SELinux Enforcing
Safetynet pass by default
Encrypted by default
Debloated
Active & Stable Development
Translations
Popularity
OTA
No Pixel Thermals
What is System_EXT? Check out here.
Based on MIUI ROM
MIUI MindEdition
MIUI 13 MindEdition A12 Unofficial
PocoOS
MIUI 14
BeosXPredator
Xiaomi.eu V12.0.3.0.QEJMIXM
Elite ROM
MIUI 12 Global Stable Modiefied
Linux Distribution
Ubuntu Touch
Droidian Unofficial
Android 13
crDroid [Installation Guide] [crDroid Recovery]
AwakenOS [Installation Guide] [TWRP by REIGNZ Recovery]
Official LineageOS / LineageOS microG [Installation Guide] [LineageOS Recovery]
PixelOS [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
ArrowOS [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
Paranoid Android / Unofficial PA [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
ReloadedOS [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
BaikalOS
SOSP-OS Project
Pixel Experience Unofficial
StatiXOS
Project Elixir
ArrowOS-MiPA Edition
EvolutionX
Project 404
DerpFest
LessAOSP
DivestOS
PixelExtended
CalyxOS
LibreMobileOS
CorvusOS
Project Blaze
BananaDroid
PixelPlusUI
BlissROM
Nusantara
riceDroid
Xtended
ColtOS
VoidUI
Black Iron
AncientOS
StagOS
SparkOS
AlphaDroid
SuperiorOS
ProtonPlus
CygnusOS
VoltageOS
CherishOS
xdroidOSS
EternityOS
Android 12/12L
Android 12L/12.1
crDroid [Installation Guide] [crDroid Recovery]
AwakenOS [Installation Guide] [TWRP by REIGNZ Recovery]
Official LineageOS / LineageOS microG [Same as crDroid Installation Guide but use LineageOS ROM / Recovery] [LineageOS Recovery]
Pixel Experience [Installation Guide] [PE Recovery]
ProtonAOSP
Paranoid Android
PixelOS
LibreMobileOS
CalyxOS
riceDroid
FluidOS
Project404
ForkLineageOS
Project Elixir
ArrowOS Unofficial
CorvusOS
EvolutionX
/e/OS
DerpFest
SyberiaOS
BiancaProject
VoidUI
LineageOS++ by side
CherishOS
SparkOS
StagOS
CygnusOS
AtomXCLO
FlamingoOS
KomodoOS
CipherOS
Nusantara Project
AncientOS
PixyOS
xDroid
LessAOSP
LeOS
VoltageOS
Kaleidoscope
ElytraOS
KryptonAOSP
Project Zephyrus
Project Arcana
ProjectBlaze
FusionOS
POSP
PixelBlaster
Android 12
MSM Xtended
PixelPlusUI
Project Radiant
BlissROM
CAFEX
SuperiorOS
Fluid
AOSPK
OctaviOS Unofficial
AospExtended Unofficial
Android 11
LineageOS / LineageOS microG
Pixel Experience
crDroid Android
ArrowOS
HavocOS
BaikalOS
EvolutionX
DotOS
AICP
Fork LineageOS
CalyxOS
/e/OS
AospExtended
PixelPlusUI
Paranoid Android
MSM Xtended
WaveOS
RohieOS
Project 404
BlissROM
CAFEX
xdroidCAF
DerpFest
BananaDroid
RevengeOS
AOSiP
ShapeShiftOS
Fluid
AwakenOS
POSP
PixelROM
SpiceOS
Styx Project
Project Sakura
StagOS
ArcaneOS
Syberia
TenX-OS
StatixOS
ColtOS
CherishOS
CesiumOS
Bootleggers
AOSPK
KangOS
ReloadedOS
CygnusOS
CesiumOS
Candy 11
AncientOS
OctaviOS
Nusantara Project
ConquerOS
HornbillOS
HyconOS
Android 10
Pixel Experience
LineageOS
crDroid
ReloadedOS
EvolutionX
Paranoid Android
CorvusOS
HavocOS / HavocOS Fan Build
ArrowOS
KeepQassa
CarbonROM
AOSiP
PixelROM
PixelDust
POSP
Ressurection Remix
MSM Xtended
AICP
OmniROM
CAFEX
DeepFest
NitrogenOS
Komodo OS
PixysOS
BlissROM
ColtOS
SuperiorOS
HornbillOS
ZenX OS
StagOS
NusantaraProject / Unofficial NusantaraProject
Project Sakura
CUSTOM KERNELS
What is System_EXT? Check out here.
Active Development
SilverCore Kernel
No Gravity Kernel [NGK Profiles -> Infos about Profiles]
Kawaii Kernel
Ingenium Kernel
Rockstar Kernel
EOL (Archived)
BAALAM Kernel
Gear Kernel
NexusCAF Kernel
Optimus Drunk Kernel
Franco Kernel
arter97 Kernel
Twisted Kernel
Illusion Kernel
Sphinx Kernel
Stealth Kernel
MiPa Kernel
MiPa Kernel
Canting Kernel
Delta Kernel
Seshstation Kernel
XDKernel
Simple Kernel
Parallax Kernel
Malakas Kernel
CUSTOM RECOVERIES
You can check my Guides for installation.
What is System_EXT? Check out here.
Unofficial TWRP Recovery by REIGNZ (Normal version= system_ext / NSE version=Non system_ext) [Telegram Support] [Current Bugs/Issues]
Official TWRP Recovery
LineageOS Recovery
crDroid Recovery
Pixel Experience Recovery
Dynamic Retrofit Recovery
OrangeFox Recovery
PitchBlack Recovery
Sky Hawk Recovery Project
GAPPS & microG
GApps
Note: be sure you have selected Platform: ARM64 and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
Retrial-NikGApps
NikGApps [Create your own NikGApps build -> Video Guide] [Guide for Packages Information/Description]
BiTGApps
MindTheGapps
FlameGApps [FlameGApps Config] [FlameGApps A13 Basic]
Open GApps / Open GApps Unofficial A12L
LiteGapps
microG
If you don't want to use Google Play Services and general move away from Google, microG and its variants is an open source alternative which replace these services.
NanoDroid
MinMicroG
BiTGApps microG
microG Revived
microG
MAGISK ROOT
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Magisk Delta
FoxMagiskModuleManager (This app replace the official magisk module repository since no longer available)
Momo (You can use this app too check if any modifications related Magisk are detected or not)
Universal SafetyNet Fix by kdrag0n [Video Guide]
Shamiko (Hide Root from apps) [Guide]
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
DISABE FORCE ENCRYPTION (DFE) & ENCRYPTION
You can check my Guides to find for what is used for.
Disable Force Encryption A13 (DFE A13)
Disable Force Encryption (DFE)
Encrypt Data
GOOGLE CAMERA PORTS & UNIVERSAL STOCK CAMERA UNINSTALLER & ANXCAMERA
Note: You can use 2 or more different GCams by installing GCams with different package names.
For example you can use Sanity's v9.6 ENG and BSG v8.1 MGC or Parrot etc... and vice versa.
That way you will have a stable GCam which everything works (Sanity's), but you can also have a latest version of GCam for features that v9.6 of Sanity's doesn't have, like astro mode etc.
Read the FAQ.
Poco F1 Photography: Telegram Group
san1ty
Parrot043
BSG (Public Version) [Video Stabilization Settings]
BSG (Private Version) [XML Configs] [Video Review]
Parrot043 (7.0.009_FinalBuildGoodbye_V1) / Settings (Apply the settings of this thread)
GoogleCameraMod07062019_xiaomi-sdm845 (Old 9.6 PE Default GCam)
ANXCamera (Magisk Module - No Addon needed)
Universal Stock Camera Uninstaller (Flash it in Recovery)
Note: If you updated GcamGo from the Play Store, you will need to flash this file and manually uninstall GcamGo from the app info.
GOOGLE PLAY SYSTEM UPDATE 🛡
You can manually update Google Play System by downloading and installing Main components.
ULTIMATE COLLECTIONS & GUIDES (APPS)
Check the Privacy & Security section in my Guides.
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Android Ultimate Collection & Guides
Windows Ultimate Collection & Guides
ReVanced & ReVanced Extended - Guides & Useful Links
UNIVERSAL ANDROID DEBLOATER
Universal Android Debloater
XIAOMI TOOLS
Mi Unlock
Xiaomi Mi Flash Tool
Xiaomi ADB/Fastboot Tools
Fastboot Drivers
Persist Partition (beryllium)
MINIMAL ADB AND FASTBOOT
Minimal ADB and Fastboot
ADB & Fastboot++
Fastboot Drivers
AMD RYZEN/INTEL FASTBOOT FIX
Check the AMD Ryzen Fastboot Fix Guide for the proper steps.
AMD Ryzen/Intel Fastboot Fix (Batch File .bat)
Fastboot Drivers
POCO F1 COLLECTION MIRROR
POCO F1 Collection AFH Mirror
HALL OF FAME OF DEVELOPERS
This section is to honor and support the developers who contribute to keep alive our device with active development over the years and they continue doing it.
This is also a kind of motivation for new or juniors devs to join the Hall of Fame of Developers.
By supporting the Devs not only is helpful for them but also for the community itself.
bgcngm
REIGNZ3
gwolfu
Pierre2324
Scroll Down to check the Guides
POCO F1 Ultimate Guides!
(beryllium)
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.
AMD RYZEN/INTEL FASTBOOT FIX
Some AMD Ryzen or Intel Systems may have problems to recognize your device in fastboot. Try the following ways:
1. Install Fastboot Drivers (Extract the folder for windows 10) at Device Manager while your device is connected in Fastboot mode.
2. Download this .bat file (unzip it) or manually create a .bat file with these lines below, and run it as an administrator, then reboot:
Code:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
3. Enable USB Debugging at device (Settings > Additional settings > Developer options > USB Debugging) and give authorization after connecting it to PC.
4. Use USB Hub.
5. Use USB Type-A 2.0.
6. Install AMD Ryzen Chipset Drivers or Intel Chipset Drivers.
Check the steps an another user did to make it work here.
If this doesn't help, unfortunately you have to use Intel System which is more likely to work.
UNLOCK BOOTLOADER
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
Please keep in mind by Unlocking Bootloader the device will reset and all your data will be lost. Make a backup of your data first to PC or to USB.
1. Create a Mi account on Xiaomi’s website.
2. Add a phone number to your Mi account.
3. Insert a SIM into your phone (If you haven't added already). [Do not insert 2 SIM, only 1 until the Bootloader is unlocked. If you have 2 SIM into your phone, remove 1 and reboot.]
4. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
5. Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status. Also enable USB Debugging.
6. Download the Mi Unlock app (Windows is required to run the app).
7. Run the Mi Unlock app and follow the instructions provided by the app.
8. Reboot your device into Fastboot mode. For that simply turn off your device, press the Power Button + Volume Down (–) button at the same time. Then connect the device to the Windows PC/laptop via a micro USB cable.
9. After device and Mi account are successfully verified, the Bootloader should be Unlocked and your device will restart by itself.
INSTALL CUSTOM RECOVERY
Fastboot Method (No Custom Recovery currently installed)
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
1. Make sure your Bootloader is Unlocked.
2. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
3. Enable USB Debugging in Settings > Additional settings > Developer options > USB Debugging.
4. Download a custom recovery of your choice and copy the .img to your Internal Storage or to SDCard. [You can find a recovery of your choice in my Collection]
5. Download the portable Minimal ADB and Fastboot and run cmd.exe
6. Reboot to Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
7. Once the device is in Fastboot mode, connect your device to PC and verify you can find it by typying in cmd: fastboot devices.
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-beryllium-v3.7.0-A12-V2.img
9. Now into TWRP, press Install > Install Image > Locate & Select the twrp.img you previously downloaded and copied from PC into your Internal Storage or to your SDcard > Choose Recovery and Flash!
10. Go back into Home page of TWRP and press Reboot to Recovery or manually by holding Power Button + Volume Up (+) until you boot to Recovery.
11. Done! You now have a new Custom Recovery installed.
Recovery Method (Custom Recovery already installed or booted)
1. Download a custom recovery of your choice. [You can find a recovery of your choice in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install > Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
CLEAN INSTALL CUSTOM ROM
Note: If you have issues after flash check possible solutions here:
Check integrity of all downloads (compare checksums), do the downloads again.
Make sure you Wiped everything and Formated Data (format data not just wipe) except external SDCard and USB OTG.
Flash only the ROM (without GApps and Magisk) and check if the problem persists. If yes, flash another ROM.
Try other GApps package.
If nothing helps, go back to stock and start from scratch.
Note: You can also Flash Custom ROM using ADB sideload Method.
What is System_EXT? Check out here.
You can also do the same steps below to install Stock MIUI Recovery ROM.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Unlock Bootloader. [Read the Unlock Bootloader Guide above]
3. Download: [You can find everything in my Collection]
Custom Recovery of your choice. [Recommened to use Unofficial TWRP by REIGNZ3 (A12_System_Ext) for A12L+ ROMs]
Custom ROM of your choice.
GApps (be sure you have selected Platform: ARMx64 and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root. [Optional]
Disable Force Encryption or Encryption. [Optional] (Read DFE & Encryption Guide above)
4. Move all these files in one folder to your PC or to External SDCard if you have one.
5. Install Custom Recovery. [Read the Install Custom Recovery Guide above]
6. Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, System_Ext, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back > Press Reboot > Reboot to Recovery again. [That step needed for the next step of formating the data because TWRP by REIGNZ have issue]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Connect your device to PC while you are on TWRP and transfer into Internal Storage, the ROM, GApps etc. and the files you want to flash.
Flash ROM > GApps [Optional]
[Optional] Mount Vendor and Flash DFE [Optional - Not Recommended] or Encryption [Optional] (Read DFE & Encryption Guide above)
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE or Encryption you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, System_Ext, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back > Press Reboot > Reboot to Recovery again. [That step needed for the next step of formating the data because TWRP by REIGNZ have issue]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional]
[Optional] Mount Vendor and Flash DFE [Optional - Not Recommended] or Encryption [Optional] (Read DFE & Encryption Guide above)
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System, System_Ext, Vendor, Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional]
5. [Optional] Mount Vendor and Flash DFE [Optional - Not Recommended] or Encryption [Optional] (Read DFE & Encryption Guide above)
6. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK MIUI ROM & RELOCK BOOTLOADER
Note: Some AMD Ryzen or Intel Systems may have problems to recognize your device in fastboot. [Read the AMD Ryzen/Intel Fastboot Fix Guide above]
1. Backup all your data to PC or to external SDCard, if it's possible. [All your data into Internal Storage will be lost]
2. Download the official Fastboot ROM and unzip it to your PC. [You can find it in my Collection]
3. Download Xiaomi Mi Flash Tool and run XiaomiMiFlash.exe.
4. Turn off you device and then boot in Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
5. Connect your device to PC via USB Cable.
6. On the Xiaomi Mi Flash Tool, Click on Select and browse to the folder where you have Unzip the downloaded ROM file then press OK.
7. Click on Refresh button and you will see that your device connected to port com.
8. Select what method you prefer:
Clean All: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will remain unlocked.
Save User Data: The process will flash Fastboot ROM without wiping user data.
Clean All and Lock: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will be relocked
9. Now click on the Flash button to begin the flashing progress.
10. Once your ROM is successfully flashed, you’ll see green bar inside XiaomiMiFlashtool.
BACKUP & RESTORE ROM (NANDROID BACKUP)
Check this Youtube Video to see the process in action.
Backup:
1. Remove Lockscreen Method. (You will have to set fingerprints again after Restore)
2. Reboot to Recovery (Power Button + Volume Up (+))
3. Choose Backup and Select Boot > System Image > Vendor Image > Data (excl. storage)
4. Select Storage and choose SDcard if you have one otherwise let it on Internal Storage.
5. Swipe to Backup.
6. Done!
Restore:
1. Reboot to Recovery. (Power Button + Volume Up (+))
2. Select Wipe > Advanced Wipe.
3. Select Dalvik / ART Cache, System, System_Ext, Data, Vendor, Cache and then Swipe to Wipe.
4. Press Home Button to go back and Select Restore.
5. Select the backup file with the ROM and make sure Boot, System Image, Data (excl. storage) and Vendor Image are selected.
6. Select Swipe to Restore and when completed Reboot to System.
7. Done!
Note: After you restore backup you might be unable to use old lock method such as PIN or Pattern to unlock your device (that's why you remove it before you take backup), in order to remove lock method you need to boot recovery and then:
Mount system
Go to file manager
Go to data/system
Delete locksettings.db
This way, you will not have any lock method set, but added fingerprints will remain.
FIX FOR STUCK ON OREO FIRMWARE (SOFTBRICKED)
FIX (Read Carefully)
MAGISK ROOT
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]2. Download the Magisk [You can find it in my Collection]3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]Note#1: From Official TWRP Recovery 3.5.1 and onwards (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.Manually Creation of Flashable Zip:Download the latest Magisk APK and rename the Magisk.apk → Magisk.zip.Note#2: If your bank apps detect root, follow this Guide.
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
DISABLE FORCE ENCRYPTION (DFE) & ENCRYPTION
[You can find it in my Collection]
Disable Force Encryption
Disable Force Encryption (a.k.a DFE) is flashed during installation of a custom ROM to avoid the system encrypting /data partition when the devices boot for the first time.Some ROMs are not encrypted by default and so is not necessary to flash DFE. However if your ROM comes with encryption by default you can always flash DFE after clean installation of ROM and always after every update or flash or you can use any custom recovery like OrangeFox, Pitchblack, Skyhawk Recovery Project which can automatic flash DFE after every flash.I don't recommended to use DFE if you don't switch ROMs frequently and you are casual user. Beside the fact that if you lose your device your data are not protected, many people get in confusion while doing OTA or manually updates, which if the ROM is encrypted by default and flashed DFE and in next update you forget to flash DFE you will lock out from your data and you wil get into bootloop (use custom recoveries mentioned above to avoid that).
Encryption
Encrypted ROMs are recommended if you are stable and casual user of a ROM. Encryption have the benefit to protect your data, in case you lose your device for example. Always use the latest TWRP Recovery so you can be able to decrypt the data by filling the same lock screen password you have set in ROM.Some ROMs are not encrypted by default but devs provide an Encryption.zip (script) which can encrypt the ROM. Same as DFE you need to flash it after clean installation of ROM and always after every update to stay encrypted and not get into bootloop. Unfortunatly there is not any custom recovery automatic doing that like with DFE, so you must be careful, avoid doing OTA updates and flash it every time you manually update a ROM.
REMOVE SECURITY PIN/PATTERN (LOCKSCREEN SETTINGS)
Check HERE and HERE.
SCREEN RETENTION FIX
Screen Retention FIx: If you have an issue with screen retention apply this configuration to your device ROM.
HOW TO TAKE LOGS
How to take logs on Android
BATTERY TIPS
Xiaomi POCOPHONE F1 Battery Model: BM4E
Battery Replacment (Video)
Recommended Battery: NOHON for POCO F1 (AliExpress)
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Method 1
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Method 2
Notes: It won't dramatically extend battery life, but it will give your old battery at least 30 minutes additional run time.
Steps:
1. Get "GSam or Ampere" from the Google Play Store.
2. Launch the app and fully charge your phone. (Important: Only proceed with the calibration when the word "Full" appears in GSam or Ampere.)
3. While your phone is still connected to the cable reboot your phone to recovery mode, open file manager and navigate to "/data/system" and delete "batterystats.bin," "batterystats-checkin.bin," and "batterystats-daily.xml."
4. Reboot your phone (while it is still plugged in) and charge it until it reads "full" on GSam or Ampere.
5. Unplug the cable and use your phone normally until it shuts down (0 percent )
6. Charge your phone to 100% while it is turned off.
7. Boot into os and plug in your phone and charge it until it says "full" on the GSam or Ampere.
8. Unplug and have fun!
Battery Capacity Health
Notes:
1) Before checking the battery health, charge the device to 100%.
2) Check charge counter values and consider first 4 digits from left as your battery capacity in mAh. And check charge counter. (Charge counter/level)*100 is the battery capacity.
To find battery capacity in Windows:
Enable Developer options in your device.
Enable USB Debugging in your device.
Conect your device to PC and give permissions.
Open Minimal ADB (run cmd.exe) or Platform tools.
Type "adb shell dumpsys battery" command in Minimal ADB or Platform tools.
To find battery capacity in Android (Terminal) - Root needed:
Download an android terminal app like Termux,
Open terminal and type: cat/sys/class/power_supply/battery/charge_full
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at Privacy Guides.
Electronic Frontier Foundation.
Check if your email address or your phone number is in a data breach at Have I been Pwned & at Firefox Monitor.
PrivacyTests: Open-source tests of web browsers privacy.
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF and at Bromite fingerprint mitigations tests.
WebRTC IP Leak Test. WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN. You can find more infos how to disable it at Privacy Guides in browsers section.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
εxodus: εxodus analyzes Android applications in order to list the embedded trackers and ads.
Spyware Watchdog Article Catalog: A catalog which determinate under tests and tracking if an app is spyware and what data it collects.
CryptPad: CryptPad is built to enable collaboration. It synchronizes changes to documents in real time. Because all data is encrypted, the service and its administrators have no way of seeing the content being edited and stored.
PrivateBin: PrivateBin is a minimalist, open-source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256-bit AES. It is the improved version of ZeroBin.
ShutUP10++ , Privacy.Sexy: Disable major tracking features of Windows.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted. You can also find and use FOSS apps at F-Droid or at Droid-ify (Recommended).
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
You can also check if the app includes trackers and ads with εxodus.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use Droid-ify client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in Droid-ify or F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG and use Aurora Store.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users. You can also use the tool ShutUP10++ or Privacy.Sexy to disable major tracking features of Windows.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails or SMS you may get. Always check the address of the email or the number of SMS and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email. You can also create and use email aliases of your email with SimpleLogin which is open source and awesome service.
Changelog
Note: Changes in Collection & Guides happens in real time. The date I post these Changelogs is just a sum up since I can't post all the changes the time that happening to avoid spamming the thread. So you can always consider the Collection & Guides Up-to-Date. However, I may announce some big changes in posts before I include them in the Changelogs.
LATEST
Update: 07/06/2023
Changelog
ARCHIVED
Update: 08/04/2023
Changelog
Update: 18/01/2023
Changelog
Update: 16/12/2022
Changelog
Update: 29/10/2022
Changelog
Update: 24/09/2022
Changelog
Update: 02/08/2022
Changelog
Update: 01/07/2022
Changelog
Update: 30/05/2022
Changelog
Update: 01/05/2022
Changelog
Update: 28/02/2022
Changelog
Update: 28/02/2022
Changelog
Update: 07/02/2022
Changelog
Update: 20/01/2022
Changelog
Update: 23/12/2021
Changelog
Update: 20/11/2021
Changelog
Update: 16/10/2021
Changelog
Update: 31/08/2021
Changelog
Update: 02/08/2021
Changelog
Update: 17/07/2021
Changelog
Update: 22/06/2021
Changelog
Update: 23/05/2021
Changelog
Update: 01/05/2021
Changelog
Update: 19/04/2021
Changelog
Update: 04/04/2021
Changelog
Update: 16/03/2021
Changelog
Update: 27/02/2021
Changelog
Update: 26/02/2021
Changelog
Update: 23/02/2021
Changelog
Update: 21/02/2021
Changelog
Update: 25/01/2021
Changelog
Update: 14/01/2021
Changelog
Update: 13/01/2021
Changelog
Update: 17/12/202
Changelog
Update: 20/11/2020
Initial Release
Awesome job, my friend! :good:
Great job. Everything in one place.
Sent from my POCOPHONE F1 using Tapatalk
Amazing Work. All silly and important questions have been answered at one place.
+Add Mi Assistant (Xiaomi PC Suite China) in Xiaomi Tools. It Helps to fix bootloop in locked bootloader nowadays.
this in one stop for all poco stuff...
amazing work.... [emoji106][emoji106][emoji106][emoji106]
SPLESHER said:
Awesome job, my friend! :good:
Click to expand...
Click to collapse
Kadajo said:
Great job. Everything in one place.
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Krisranger said:
Amazing Work. All silly and important questions have been answered at one place.
+Add Mi Assistant (Xiaomi PC Suite China) in Xiaomi Tools. It Helps to fix bootloop in locked bootloader nowadays.
Click to expand...
Click to collapse
Mr.Sm1th said:
this in one stop for all poco stuff...
amazing work.... [emoji106][emoji106][emoji106][emoji106]
Click to expand...
Click to collapse
Thank you guys! I will try to keep the thread always up-to-date.
If you find a broken link, something wrong or you have a suggestion, please do not hesitate, tell it!
Today I made couple of changes in Guides & Collection so infos can be more clear and I've added some stuff!
Retrial said:
Thank you guys! I will try to keep the thread always up-to-date.
If you find a broken link, something wrong or you have a suggestion, please do not hesitate, tell it!
Today I made couple of changes in Guides & Collection so infos can be more clear and I've added some stuff!
Click to expand...
Click to collapse
Im in now miui global 12.0.2
I facing problem while voice call
Another end of caller hear a noise
Is there fix
Please guide me ...
hari1jack said:
Im in now miui global 12.0.2
I facing problem while voice call
Another end of caller hear a noise
Is there fix
Please guide me ...
Click to expand...
Click to collapse
Try to do factory reset (firstly save all your personal data to PC or to external SDCard). 12.0.2 and general all the latest miui updates are full of bugs and slow down your device. Also the chances to get new android version in miui are very low. I will not talk about security and tracking.
I recommended you to move away from miui and use a custom rom of your choice. :fingers-crossed:
Awesome thread, everything at one place. Thanks man.
You have gathered so much collective information at one place. It will be helpful if we found which Roms are from Pixel Ports and supports Google photos free unlimited high quality storage.
OP, this is a godsend! Thank you so so much. Any idea what settings I should be using for the most "pixel like" photos on parrots gcam?
raydialseeker113 said:
OP, this is a godsend! Thank you so so much. Any idea what settings I should be using for the most "pixel like" photos on parrots gcam?
Click to expand...
Click to collapse
Hey thanks! I mostly use the default settings and I get very nice photos.
Krisranger said:
You have gathered so much collective information at one place. It will be helpful if we found which Roms are from Pixel Ports and supports Google photos free unlimited high quality storage.
Click to expand...
Click to collapse
Unfortunately, It's unknown yet. I will keep an eye on it but I doubt if it will work. Even new pixel phones will not have free unlimited storage. We will see...
Retrial said:
Hey thanks! I mostly use the default settings and I get very nice photos.
Click to expand...
Click to collapse
Any idea why the autofocus on the camera is so broken?
Using PE+ and ngk2.0
raydialseeker113 said:
Any idea why the autofocus on the camera is so broken?
Using PE+ and ngk2.0
Click to expand...
Click to collapse
I don't know but you can try the latest port of Parrot or use Sanitys or BSG ports. Try and find out which is the best for you You can also try to ask on Photography thread.
Retrial said:
Try to do factory reset (firstly save all your personal data to PC or to external SDCard). 12.0.2 and general all the latest miui updates are full of bugs and slow down your device. Also the chances to get new android version in miui are very low. I will not talk about security and tracking
I recommended you to move away from miui and use a custom rom of your choice. :fingers-crossed:
Click to expand...
Click to collapse
Thank you for the reply ...
Can you suggest me bug less rom without mic issue during call
Retrial said:
Unfortunately, It's unknown yet. I will keep an eye on it but I doubt if it will work. Even new pixel phones will not have free unlimited storage. We will see...
Click to expand...
Click to collapse
Yes new pixel phones will not have this advantage. (New pixel phones which ain't even launched yet)
But we have some roms which are ported from existing pixel phones like Pixel 3 and Pixel 4.
I got to know that Awaken OS based on Android 11 is detecting as Pixel 4 in Google photos. I'm not sure, I personally didn't install it yet.
I'm sure about some Roms and Ports like Pixel Rom and Pixel 4 xl ports are obviously detecting as Pixel 4 and they are enjoying new Google Assistant and Google One features as well.
hari1jack said:
Thank you for the reply ...
Can you suggest me bug less rom without mic issue during call
Click to expand...
Click to collapse
I personally use Pixel Experience the Plus Edition. It's stable and ready out of the box.
However there a lot of nice ROMs, you check them in my collection and decide which fit for you.
Krisranger said:
Yes new pixel phones will not have this advantage. (New pixel phones which ain't even launched yet)
But we have some roms which are ported from existing pixel phones like Pixel 3 and Pixel 4.
I got to know that Awaken OS based on Android 11 is detecting as Pixel 4 in Google photos. I'm not sure, I personally didn't install it yet.
I'm sure about some Roms and Ports like Pixel Rom and Pixel 4 xl ports are obviously detecting as Pixel 4 and they are enjoying new Google Assistant and Google One features as well.
Click to expand...
Click to collapse
Well the thing is we don't know yet if POCO F1 detecting as Pixel 4 in Google Security is enough to bypass and trick Google to have unlimited storage. We need to wait till June 1st, 2021 which this change will take place. Until then, the storage remain unlimited.
Project Treble - https://forum.xda-developers.com/c/project-treble.7259/
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.
Project Treble results in GSI ROMs.
There are quite a few GSI ROMs available, but not all of them are suitable for T30 tablet.
I started this thread to summarize my experience with using different GSI ROMs.
The prerequisite for installing GSI ROM is an unlocked Bootloader.
Description of GSI ROM versions installation file names:
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
The most suitable GSI ROM for T30:
T30 requires A/B ROM instalation file type and Android 10.
Suitable are files with key "arm64-bgN" or "arm64-bgS" in filename. "g" if you want use GAPPS.
b = a/b
g = gapps
N = no superuser
S = superuser included
HavocOS
-> Installation video guide + download all necessary files
-> tested file: Havoc-OS-v3.8-20200821-Official-GApps-arm64-ab.img.xz
-> in TWRP install "RebootFix.zip" to aviid random restarts from attachment.
LeOS - https://forum.xda-developers.com/t/aosp-11-0-2020-11-27-leos-ungoogled-gsi.4195571/
-> installation, see bellow
-> Download tested file: 20201218-RW-bvN.img.xz
Family of TrebleGSI ROMs:
CAOS - Custom AOSP OS
-> installation, see bellow
-> Download, tested file: caos-v300j-201213-arm64-bgN.img.xz
LOSQ - LineageOS 17
-> installation, see bellow
-> Download, tested file: losq-v224-201017-arm64-bgN.img.xz
cRDrom - crDroid 6.11
-> installation, see bellow
-> Download, tested file: crdrom-v224-201019-arm64-bgN.img.xz
qiDroid - BootleggersROM 5.2
-> installation, see bellow
-> Download, tested file: qidroid-v224-201021-arm64-bgN.img.xz
Bless - BlissROM 12.12
-> installation, see bellow
-> Download, tested file: bless-v224-201015-arm64-bgN.img.xz
Nusantara 2.6 - Nusantara ROM
-> installation, see bellow
-> Download1, Download2 , tested file: Nusantara_v2.6-11-arm64-ab-GApps.img.xz
This is Android 11 ROM which fits to our System partition (file size is 2.7GB ONLY)
----------------------------------------------------------------------------------------------------------------------
How to install GSI ROMs on Teclast T30:
a) use this HavocOS Installation video guide, but use specific GSI ROM System file
b) use instructions from 2nd post
GSI ROMs are not perfect, they have bugs, and on the T30 tablet I noticed the following two:
- The battery charging animation does not work (charging works OK) when the tablet is switched off
- watching youtube videos in Chrome browser sometimes ends with a system restart (youtube application and embeded internet browser usually works OK)
I have tried all the above GSI ROMs and I was most satisfied with HavocOS and LOSQ.
I continue to use LOSQ, because it has the fewest errors and supports the NTFS filesystem on the inserted SD card.
If you want to try GSI ROM on your Teclast T30, choose LOSQ / HavocOS as the first choice.
I would be happy if here will start a discussion about GSI ROMs suitable for Teslast T30.
in any problems with PC and tablet communication (with platform tools or Flashtool), install the drivers "MTK_USB_All_v1.0.8.zip" or "platform-tools_r30.0.5-windows.zip" from attachment in the 2nd post
Alternative way to install GSI ROM:
(Prerequisite for installing GSI ROM is an unlocked Bootloader)
a) Unlock Bootloader
- To make the item "For developers" available on the tablet, in Settings / System / Advanced / Tablet information you need to click on the Build number 8 times
- A new "Developer menu" item will now appear in Settings / System / Advanced, turn on the "unblock OEM" item here
- In the task manager on the PC, check that there is an ADB device
- Turn off the tablet
- Hold down the Vol+ and Power buttons together, until the tablet starts
- Then use the Vol+ key to select the second Fastboot item and press the Vol- key to select it
- Connect the tablet to the PC via USB, in the PC to hear the sound of the connection
- Unzip platform-tools_r30.0.4-windows.zip to drive "C:\platform-tools" on your PC
- On your computer, click Start / Run, enter command "cmd", click OK, will appears black command window
- In the command window go to Platform-tools folder by command:
cd c:\platform-tools
- In the command window, enter:
C: platform-tools> fastboot devices
0123456789ABCDEF fastboot
- numbers may vary.
- If all is well, enter the unlock command:
fastboot flashing unlock
- You will be asked on the tablet whether or not you want to unlock the Bootloader by pressing Vol+ confirm it
- As soon as you confirm the action, what you see on the tablet, it will be unlocked
Next, enter the command:
fastboot reboot
- The tablet will restart (ALL your data will be deleted) and the tablet will return to its original state
- tablet will start initially setup
b) Install Hybrid ROM 1.2a
- in TWRP install GSI ROM image file to System partition
- in TWRP install Boot 1.05 image file to Boot partition (unpack ZIP from attachment, will get IMG file)
- restart System
- done
in any problems with PC and tablet communication (with platform tools or Flashtool), install the drivers "MTK_USB_All_v1.0.8.zip" or "platform-tools_r30.0.5-windows.zip" from attachment.
-> New version of HAvocOS from December 31, 2020
Lineage os is not booting and my tab is stuck on teclast logo.Any fix ??
Lightning Killer said:
Lineage os is not booting and my tab is stuck on teclast logo.Any fix ??
Click to expand...
Click to collapse
I assume you didn't follow the installation instructions exactly.
Maybe you forgot to install the Boot image from ROM 1.05 to Boot patition or you didn't unlock Bootloader.
You need to do install Boot 1.05 image in the end of installation process, after installing Lineage GSI on the System partition. Also, Bootloader must be unlocked (it is mentioned in that installation video)
I added necessary img file to attachment. Install it in TWRP to Boot partition. Then Lineage GSI ROM will boot (Bootloader must be unlocked!!!).
(unpack ZIP from attachment, you will get IMG file)
For everyone, I added a new alternative installation guide to the second post.
I have been using it for a long time HavocOS from December 31, 2020
(Havoc-OS-v3.12-20201230-Official-GApps-arm64-ab.img.xz)
It works well. Of course, it has minor flaws like all GSIs.
This is latest version HavocOS on Android 10.
Newer versions of HavocOS 4.1 are based on Android 11.
Unfortunately, the System image with GAPPS is too large to fit in the system partition of our tablet.
The System IMG size limit is 3GB.
GSI HavocOS 4.12 based on Android 11 available
I used this files:
Havoc-OS-v4.1-20210208-arm64-ab-vndklite-Official.img.xz
NikGapps-basic-arm64-11-20210130-signed.zip
It is necessary to incerase System partition size before install, do tgis steps:
- go to TWRP
- Wipe->Advanced Wipe->Select System->Repair or Change File System->Resize File System
- if errors will apperas, restart to TWRP a repeat the previous step again
It may not work first time for whatever reason, you may also try Repair FIle System there in this case, or just try a reboot
rbt07 said:
GSI HavocOS 4.12 based on Android 11 available
I used this files:
Havoc-OS-v4.1-20210208-arm64-ab-vndklite-Official.img.xz
NikGapps-basic-arm64-11-20210130-signed.zip
It is necessary to incerase System partition size before install, do tgis steps:
- go to TWRP
- Wipe->Advanced Wipe->Select System->Repair or Change File System->Resize File System
- if errors will apperas, restart to TWRP a repeat the previous step again
It may not work first time for whatever reason, you may also try Repair FIle System there in this case, or just try a reboot
Click to expand...
Click to collapse
Hi after installing this, I`m in a boot-loop, What can I do?
H1S8V87 said:
Hi after installing this, I`m in a boot-loop, What can I do?
Click to expand...
Click to collapse
Hi, you have to install Boot.img from ROM 1.05 to Boot partition through TWRP.
File is here in 2nd post.
Unpack ZIP anf install IMG file to Boot partition.
rbt07 said:
Hi, you have to install Boot.img from ROM 1.05 to Boot partition through TWP.
File is here in 2nd post.
Unpack ZIP anf install IMG file to Boot partition.
Click to expand...
Click to collapse
Hi, yeah I`ve done this several times. Nothing helps, I`m back to your Hybrid Rom
It worked for me, but I still preferred to go back to the older Havoc.
H1S8V87 said:
Hi after installing this, I`m in a boot-loop, What can I do?
Click to expand...
Click to collapse
For me it works...
I've found a fix for random reboots !!! Just flash this zip file in twrp
GSI HavocOS 4.5 based on Android 11 available
I used this files (click to download):
HavocOS-4.5-official-arm64-ab-vanilla.img
open_gapps-arm64-11.0-pico-20210713.zip
Links:
Havoc 4.5
arm64-ab-vndklite • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGAPPS
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
How to install:
- as a base system is my Hybrid ROM 1.2a
- Install GSI System image Havoc4. 5
- then increase System partition, do this steps:
a) go to TWRP
b) Wipe->Advanced Wipe->Select System->Repair or Change File System->Resize File System
c) if errors will apperas, restart to TWRP a repeat the previous step again
If incerasing fails, reboot to TWRP recovery and try again, now it will works now
- install GAPPS.
- reboot System
Add nusantra project gsi to the list !!! It is much more smoother than havoc and lineage os Here's the link for 2.5 (based on android 11 )
[email protected] - Browse /Nusantara-11 at SourceForge.net
sourceforge.net
+ It comes with gapps and can easily be flashed without having to resize the system partition
deleted
Lightning Killer said:
I've found a fix for random reboots !!! Just flash this zip file in twrp
Click to expand...
Click to collapse
Hi, thanks, it reallly work for HavocOS 3.8 GSI ROM.
rbt07 said:
Added to 1st post, thanks for info.
Do you use it? Write somthing about this ROM please.
Click to expand...
Click to collapse
It's the best gsi rom for teclast t30 I have used till date !!! It is very smooth and responsive. There are some customisation settings which crash when using in landscape mode but they work just fine in potrait mode.else this rom works like a charm for me.
Another gsi for teclast t30 that I would recommend is cr droid gsi based on android 11 . Here's the link -
TrebleGSI - Browse /crDRom11/2021.05.21 at SourceForge.net
sourceforge.net
Lightning Killer said:
It's the best gsi rom for teclast t30 I have used till date !!! It is very smooth and responsive. There are some customisation settings which crash when using in landscape mode but they work just fine in potrait mode.else this rom works like a charm for me.
Click to expand...
Click to collapse
I will try soon, thanks.