Clean boot for nexus android o (8.0.0) (beta kernels) - Nexus 6P Android Development

CLEAN BOOT FOR NEXUS ANDROID O (8.0.0) (BETA)
CLEAN BOOT :
CLEAN BOOT - stock boot img with some better performance for Nexus devices
What is add to boot img ????
Multi window
Increase the overall touch response
Battery Save
Disable debugging notification icon in the status bar
Signal (3G) tweaks
Disable the animation to boot faster startup
Fix some application issues (Kernel)
THIS IS ONLY FOR ANDROID O (8.0.0) !!!!
STOCK FACTORY IMAGES FROM GOOGLE IS HERE https://developer.android.com/preview/download.html#revertDevice
YOU FLASH KERNEL AT YOUR OWN RISK , if kernel not work in your phone write a comment
HOW TO FLASH
FASTBOOT FLASH BOOT BOOT.IMG
POSSIBLY AFTER FEW UPDATES BOOT IMAGES BE NOT WORK , BECAUSE I BASE ON
Nexus 5X bullhead-opp4.170623.014-factory-e37b9eae.zip
Nexus 6P angler-opp4.170623.014-factory-747b8fd5.zip
, AND FOR THIS VERSIONS OF UPDATE BE WORK BOOT IMAGES , IN LATER VERSIONS I DON'T KNOW !!
SUPPORTED DEVICES :
Nexus 6P
Nexus 5X
DOWNLOAD :
https://drive.google.com/open?id=0B0j-ruvmukWhczNneE9ZcWlpaHM​

I don't know who , but please move my thread to correct topic , from Nexus Player

Related

[9.0] [PORT] ColorOS 6.0 GSI [A-A/B]

WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
The goal of this ROM is to experience ColorOS 6.0 on any non-oppo and non-realme phone.
For a list of treble supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki
How to flash:
1- Flash a treble pie rom (CAF vendor recommended.)
2- Extract 7z file and flash system.img
3- If base rom isn't permissive flash permissiver.
4- Reboot
Bugs:
- Fingerprint
- Since it's oem port maybe more on your device. But common bug is Fingerprint.
Download:
system.img for A-A/B ARM64 devices
Telegram Account: MacTavishAO In case of any problem please send me logs.
Thanks to: @erfanoabdi for everything..
Reserved. You can follow me on github.
Changelog:
1.0: Initial release.
Does it include stock sounds and ringtones? Thanks
ZoiraP said:
Does it include stock sounds and ringtones? Thanks
Click to expand...
Click to collapse
yes
Nice work.
Keep it up.
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
surfer30 said:
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
Click to expand...
Click to collapse
You need pie treble vendor, permissiver.
I flashed over Lineage 16GSI (android 9). But not flashed permissiver - you sugested tryed once more?
Kanka Lenovo Z5 direk crash diag bölümüne atıyor dediklerini harfiyen yaptığım halde.
Lenovo Z5(L78011) didnt work.
Stuck on boot logo. My Vendor is CAF and flashed permissiver V2
Couldn't flash in nokia 6.1 plus
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Either bootloops or doesn't get past the boot image on Note9 N960F no matter what. (Different kernels, flash on different systems etc.)
rahul387 said:
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Click to expand...
Click to collapse
That isnt how it works
Some random said:
That isnt how it works
Click to expand...
Click to collapse
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
I have 2 questions :
1) Can I flash this ROM on Mi Max 2 with Orange Fox 10 recovery?
2) Can this be used for daily life usage?
Thank you
No boot
System partition smaller than image
rahul387 said:
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
Click to expand...
Click to collapse
I read that we have to resize the system partition when that error occurs. It's too advanced for me so I left it.
Kicked into fastboot
I've tried installing it exactly as described here and also how it's described for other pie GSIs for oneplus5t but I only get kicked into the fastboot mode. I really like to try out this rom on an amoled display. Any specific methods I should follow? (I used mokee phh treble vendor as that was recommended in most forums, am also decrypted..maybe i have to try by flashing noverity too) all gsi tutorials and pages for oneplus 5t are about a year old so i'm not sure I can follow that and succeed. Any help would be appreciated. Thanks.
I cant install in redmi 6a
Galaxy A3 2017? (a3y17lte)
I have discovered a thread of the project treble port, how to fix stuck on boot screen?

[BOOT ANIMATION] Motorola Series [Project 9 ¾]

I have made some Boot Animations for Motorola phones and would like to share them with the community.
They also come with their own set of Boot Logos, so you don't need to flash any Boot Logo separately in case you are using the Boot Logos I made.
Features :
Full screen animations
Boot Logo + Boot Animation Pack
N/A hidden in Boot Logo
Redesigned bootloader menu
Some other minor changes in boot logo images
These Boot Animations can also be flashed to other Motorola Devices with 1080X1920 screen resolution like:
Moto G4
Moto G4 Plus
Moto G5
Moto G5 Plus
Moto G5s
Moto G5s Plus
Moto X4
Moto Z2 Play
Other Motorola phone users may use the version of the boot animation with motorola written on the image instead of moto g5 plus.
Use VX.0_BA+BL_9-3_by_4 Zip for Moto G5 Plus.
Use VX.1_BA+BL_9-3_by_4 Zip for other Motorola devices.
The file names with DT at the end stand for Boot Logos suited for Dark Theme.
All Boot Animations have been posted on SOURCEFORGE and more would be added in the coming future. The designs have been separated into two folders and further organized inside each folder by version numbers starting with V1. All the zips are functionally the same and you can flash whichever version you like. The only difference is in the text shown on the Boot Logo image. Head down for viewing previews and downloading the boot logos.
Specifications
This pack will only work for custom ROMs
This pack will not work on Stock Motorola ROMs
All the packs contain both Boot Animation and Boot Logo that goes along with the animation
If your ROM has Display Theme based Boot Animation, the corresponding Boot Animation will be automatically played
Flashing another ROM or updating your ROM may remove this Boot Animation. Flash the pack again to get your desired Boot Animation
Existing Boot Animation in your current ROM will be backed up before installing new Boot Animation
If you wish to restore your Boot Animation that came with your current ROM, you can flash Restore Previous Boot Animation.zip given in Boot Animation folder
How to Install (via Custom Recovery)
Download the desired ZIP file to your phone
Boot to your Custom Recovery
Go to Install
Go to the location where you have saved the ZIP file
Install the ZIP file and reboot
Boot Animation Previews
Boot Animation Downloads
If you are unable to download from SOURCEFORGE on your phone, request desktop site from your browser menu to enable download.
Disclaimer: Motorola Logo and Batwing Logo is owned by Motorola Inc. Some of the artworks are not entirely my own creation.​
Awesome job, thank u! Working perfectly Android 10
Pumardo said:
Awesome job, thank u! Working perfectly Android 10
Click to expand...
Click to collapse
Thanks for the feedback!
Maximum effort. ?
marshmello_61 said:
Maximum effort. ?
Click to expand...
Click to collapse
Thanks man!
how to remove boot animation
Anmol Preet Singh said:
how to remove boot animation
Click to expand...
Click to collapse
Flash the restore previous boot animation zip
OR
Dirty flash your custom ROM

64 bit FOR REDMI 7A

64-bit Base Package For GSI Redmi 7A
Flashing instructions ?
• Boot to recovery
• Flash given zip file (Downloads section)
• Wipe system
• Flash any arm64 GSI of your choice to system image
• Format data, wipe cache
• Flash gapps, magisk, etc...
• Boot to system, congrats you're on arm64.
Changelog:
- Fixed camera service crashing.
- Gcams can now run on Enforcing mode.
- Swap is disabled by default in favor of ZRAM.
- Fixed more services crashing that just filled up the logcat.
- Changed to Global for better overlay compatibility
- ViperFX now works in Enforcing mode where as before it would be unstable.
- Camera doesn't take as long to launch now.
Old Changes (from previous vendor/post):
• Fix bt audio, cleanup audio configs
• Add exfat fix
• Fix headphones
• Fix video recording
• Enable pseudo-gyro (emulated gyroscope from miui)
Downloads :
Base
mirror link
Bugs ?
• VoLTE doesn't work (fix: https://t.me/Redmi7AUpdates/98)
Things to point out:
- As mentioned on the previous release, Pie and Amber/Erfan based GSIs can't boot on Enforcing mode, in which case the Permissiver v5 zip from #permissiver is necessary.
- The FM Radio fix found in notes doesn't work anymore, use this instead (http://www.mediafire.com/file/wgnysvjo362yuco/FM_Radio-Fix.zip/file) and flash through Magisk.
- If you are having any camera related issues then switch to Permissive mode.
-Fixed some stuff and made a new one.
-Sadly, upgrading directly from the old one isn't possible and formatting data is required, I tried to make it upgradable but with no success.
*Currently using Havoc os 3.8"
And credits to telegram redmi 7a team and for the developers who work so hard for this project I do not own this work
Join here need telegram app on windows and android and dont forget to like my post https://t.me/PineOfficial
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
daizu said:
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
Click to expand...
Click to collapse
True, use MIUI A9 base to get encryption working on TWRP.
No chance to get this working on MIUI?
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
theres no way and also memeUI sucks
Custom Roms GSIs are better
edit:
there is new a update bluetooth already fix and other bugs..
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
You could try to use this on a MIUI GSI ported from the Redmi 8 maybe, but I don't know if it would work completely.
Maybe Erfan's GSI builds? https://mirrors.lolinet.com/firmware/gsi/MIUI/
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
Also, not to nitpick, but my username is different in XDA.
https://forum.xda-developers.com/redmi-7a/how-to/redmi-7a-arm64-kernel-t4134381
I'm the kernel dev.
---------- Post added at 03:29 PM ---------- Previous post was at 03:24 PM ----------
Also, I'm going to try out Ubports if I can. It would be interesing to see if it would work because of the Q vendor.
Great Work, congrats <3
i have ask helios developer (maintainer of helios gsi) to resize the gsi of redmi 8 (redmi 8 has 3.5 gb raw image that cant be flash easy to our phone which has only 3gb)
"Flash any arm64 GSI of your choice to system image" i dont know what is this, but can u give me yours?
all using just twrp to flash?
How did you root your device? Im currently on MIUI 11.0.3 Q and there's no TWRP or any magisk rooting files/guide that is updated.
Good work btw. If you can share your rooting method and TWRP this can be an ALL IN ONE guide. Many thanks!
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
regularfanb0y said:
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
Click to expand...
Click to collapse
Had the same situation here on my 7A with TWRP, i also couldn't transfer the files via file Explorer from Windows to the 7A
because of the encryption (the copy and paste window doesn't do anything and disapears after a while).
Solution to this is:
Format Data > Yes
[Warning - outdated - OP has replaced the fw+vendor file 11.0.3 to 11.0.11]
Explaning some stuff about GSI basics
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i had all the needed files to give it a try.
Instructions how to get from some sort of a corrupt status xy --> StockRom
Because i did some testing with Rom's i needed a "starting point" = this means unlocked Bootloader, Stock Rom V11.0.3, recovery installed
This was necessary for me to find out what step causes problems and also to "reset" the boot.img if i used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status "xy" back to "starting point":
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
go to recovery by holding Vol-Up & Power​
-->my starting point to testing different settings...
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section [Warning - outdated - OP has removed this file]
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead [EDIT: app doesnt work because of errormessage]
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
As already mentioned the FM Radio fix doesn't work, if you skip it LOS boots perfectly
another bug: No other color of the Notification LED than white
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
Whats the FM radio GSI zip for?
List of GSIs I've tried on 11.0.3 64 bit
Boots:
Havoc OS (Camera and Screenrecording bug)
Bliss Q (Camera and Weird cutted corners)
Bootleggers (Camera, Weird cutted corners and Brightness cant adjust)
Evolution X (Camera and Brightness cant adjust)
LOS 17 (Camera)
Dont boot:
N/A
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
regularfanb0y said:
Whats the FM radio GSI zip for?
Click to expand...
Click to collapse
If i boot LOS 17 without the FM radio GSI zip the default FM Radio App which should be preinstalled isn't. flashing the zip fixed that.
regularfanb0y said:
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
Click to expand...
Click to collapse
All i can say is that i tested Camera, Weird cutted corners and Brightness and Screenrecording on LOS 17 based on 11.0.3 64 bit . Everything works so far
PS: Can you please edit your quote so only the lines you refer to getting repeated? thx
does it work with the feature : wireless fm radio?
so you can play sky children of light with this or games 64 bit based?
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305​] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
I have two redmi 7a phones, and I tried both. The first one worked the first try, but the second one does not let me install the gapps, I get error code 70 don't have enough space, I tried to resize system but I get an error and if I try again it works but when starting the phone it stuck in the logo (I already installed FM radio gsi). I don't understand why that happens
Jak08 said:
so you can play sky children of light with this or games 64 bit based?
Click to expand...
Click to collapse
I would also wish to know this, will this allow arm64 apps to run? this is a new one to me ? didn't know this was even possible

[CLOSED] [ROM] ThinROM A13 v7 [08/02/2023]-[GWB1-[EXYNOS]-[SM-N986B]-[SM-N985F]

ThinRom A13
Based on Android 13 N986B N986BXXS5GWB1 February 2023 firmware
Supported Devices: Note 20 Ultra N986B N985F
​The "NEW" ThinROM now has a full option off apps to debloat in the aroma, along with fullscreen/halfscreen in call mods, system mods, build.prop mods and alot more!!!
The code is highly optimised and the battery consumption and fluidity has seen a huge increase along with over all performance.....
ROM Features
Supported devices: N986B N985F
Stock Samsung kernel
CSC features: camera shutter sound menu, real time network speed in statusbar, etc
Knox partially removed and full debloat options
Removed dm-verity, automatic encryption, proca & vaultkeeper services
Build.prop tweaks
Warning boot screen removed, custom boot animation
Automatic EFS backup
Full aroma debloat options
Not working
knox related apps: Samsung Pay,
February A13 v7
February 2023 patch level N986BXXS5GWB1
Added option of full or half screen caller in aroma
New build.prop mods
Added different Magisk options in aroma
Fixed Android Auto not working
Fixed a few typos in flashing scripts
December A13 v5/v6
January 2023
Completely forgot to post here due to being Ill over the holiday period
December A13 v4
December 2022 patch level N986BXXS5GVK9
New full debloat options in Aroma
Added b2k Mod
Added Full screen caller mod
Highly optimised build for a smoother experience, better performance and better battery
New ThinROM Boot logo and wallpapers. Choice of White or Blue
New Software info in phone settings
November A13 v3
nOVEMBER 2022 patch level N986BXXU5GVK4
New full debloat options in Aroma
Added b2k Mod
Added Full screen caller mod
Highly optimised build for a smoother experience, better performance and better battery
New ThinROM Boot logo and wallpapers
November A13 v2
November 2022 patch level N986BXXU5GVK1
New full debloat options in Aroma
Added b2k Mod
Optimised build for a smoother experience
November A13 v1
November 2022 patch level N986BXXU5GVJE
Updated magisk to v25105
New aroma splash
New boot animation
ThinROM wallpaper applied automatically when installing clean
Changelog October v1.5
October 2022 patch level N986BXXS5FVI5
Updated magisk to v25105
New aroma splash
New boot animation
ThinROM wallpaper applied automatically when installing clean
Changelog July v1.8
July 2022 patch level N986BXXS4FVG1
Updated magisk to v25101
Changelog June v1.7
June 2022 patch level N986BXXS4FVEA
Updated magisk to v25001
Changelog May v1.6.1
May2022 patch level N986BXXU4FVE7
Updated magisk to v24312
Changelog May v1.6
May2022 patch level N986BXXS3FVD6
Updated magisk to v24309
Changelog April v1.5
April 2022 patch level N986BXXU3FVC8
Updated magisk to v24306
Changelog March v1.4
Updated to ONEUI 4.1
March 2022 patch level N986BXXU3FVC5
Updated magisk to v24303
Changelog March v1.3
March 2022 patch level N986BXXU3EVB1
Added all CSC mods by default
Changelog v1.2
Unreleased (Personal build)
Changelog v1
Unreleased (Personal build)
Credits
- John Wu for Magisk
- Mr. Waehere for CRB kitchen
- corsicanu for N20 TWRP
- aliwaris for incallui mods
- dutchman89 for the new boot animation
- Alan Thomas for sammy disarm script
- All testing team
- @starbucks2010 for helping me from day one and still doing so
- All people who helped me with ROM (especially to @starbucks2010 @ZonalRipper and @aaatso)
Download Links
Official TWRP
Installation procedure
IS MANDATORY TO BE ON ANDROID 13 FW BEFORE FLASHING ThinROM !!!
0) Backup ALL your important files to PC, ext drives, etc
1) Download and copy the latest ThinROM zip into your external storage or USB stick if you're on stock fw encrypted
2) Download GWB1 stock FW for your phone model using Frija or Samfw and unpack it on your PC
3) Boot in download mode (Vol Up + Vol Down + plug the USB cable connected already to PC) and load up Odin on PC
Don't use USB adapters otherwise you might get issues flashing FW in Odin
Turn off Auto Reboot in Odin
4) Select files BL, AP, CP & HOME_CSC (keep data)
**do not start flash yet
5) Download latest compatible TWRP for your specific device from the official TWRP xda thread (link above), rename it to recovery.img. Download the patched vbmeta.img file from above and rename vbmeta.img. Using 7Zip app add the 2 files (recovery.img and vbmeta.img) into a .tar file.
6) Add the above twrp + vbmeta patched.tar file into the USERDATA slot in Odin
7) Uncheck the auto reboot option in Odin and start the flashing
8) When flashing completes (keep usb plugged in !!!), hold Vol Down + Power buttons and then as soon as the screen goes black hold Vol Up + Power buttons to boot to recovery
*be warned first time you boot into recovery it will initialize and then reboot so just keep the buttons Vol Up + Power buttons pressed longer
**if you boot in stock FW, your data will be encrypted and you'll need to wipe your data before flashing ThinROM
9) When boot in TWRP, wipe your data if you're encrypted, flash ThinROM zip and then reboot to system
10) After the first boot, open Magisk Manager and reply with YES (agree to reboot) after MM have setup your root environment
*after reboot, go to Magisk Manager settings and toggle On Zygisk
10) Enjoy....
1. Backup to PC all your important files: documents, pictures, contacts, SMS, etc. BEFORE starting to flash anything
2. If you have issues booting the ROM, try the clean flash
3. To boot into TWRP you need to use a USB cable connected to PC (same for DL mode) or a USB stick
4. If you like my work, consider buying me a coffee.
Enjoy!
Great human, great rom creator.
Respect.
To make less stupid questions, please read before asking
Does secure folder and call recorder work?
manngoooo9 said:
Does secure folder and call recorder work?
Click to expand...
Click to collapse
Call recorder doesn't for me but a tester said it did for him and no, secure folder isn't included.
Any chance of snapdragon support?
elmor0 said:
Any chance of snapdragon support?
Click to expand...
Click to collapse
Unfortunately not.
Fist post updated to latest FW that's based on ONEUI 4.1
Bravo.
Everything is perfect.
Flying like Ferrari.
Thank you!!!!
Does using this rom cause loss of warranty?..
Also for my region there is only EVA9. Will there be any issues using EVA9 over the absence of EVB1?
Fist post updated to April FW.
aloysius987 said:
Does using this rom cause loss of warranty?..
Also for my region there is only EVA9. Will there be any issues using EVA9 over the absence of EVB1?
Click to expand...
Click to collapse
It will void warranty in certain countries but that's for you to check. Please download the latest FW for DBT and then the rom will flash just fine.
Respect, Maestro
Hi @sevsman,
is Dex working in this rom or it is removed too? Thank you for response
Mitoush said:
Hi @sevsman,
is Dex working in this rom or it is removed too? Thank you for response
Click to expand...
Click to collapse
It's been removed mate.
sevsman said:
ThinRom V1.4
Based on Android 12 N986B XXS3FVC5 firmware
Supported Devices: Note 20 Ultra N986B​
This is an MPB (my personal build) that is heavily debloated and has pretty much only edge panels left in it. Everything that could be removed safely (except edge panel) has been removed however system apps like camera, calandar, calculator, play store etc are still included.
The aroma only has a choice of clean or dirty and will automatically flash a full screen caller mod, boot animation and all available csc mods.
The rom is only 2.97gb in size and because it's my personal build I will not be adding things back into it.
If you're after an extremely light rom that's optimised for speed and battery then this is for you!
ROM Features
Supported devices: N986B (N20 Ultra)
Stock Samsung kernel
CSC features: camera shutter sound menu, real time network speed in statusbar, etc)
Knox fully removed and ROM light debloated
Screenshots in secure apps allowed
Removed dm-verity, automatic encryption, proca & vaultkeeper services
Build.prop tweaks
Warning boot screen removed, custom boot animation
Automatic EFS backup
For Safetynet use kdrag0n patch v2.2.x
Not working
Some knox related apps: Samsung Pay, Samsung AutoFill
Changelog v1.5
April 2022 patch level N986BXXU3FVC8
Updated magisk to v24306
Changelog v1.4
Updated to ONEUI 4.1
March 2022 patch level N986BXXU3FVC5
Updated magisk to v24303
Changelog v1.3
March 2022 patch level N986BXXU3EVB1
Added all CSC mods by default
Changelog v1.2
Unreleased (Personal build)
Changelog v1
Unreleased (Personal build)
Credits
- John Wu for Magisk
- Superr for kitchen
- Ian Mcdonald
- anan1211 for watchdog fix
- aliwaris for incallui mods
- dutchman89 for the new boot animation
- @starbucks2010 for helping me from day one and still doing so
- All people who helped me with ROM (especially to @starbucks2010 @ZonalRipper and @aaatso)
Download Links
Telegram link
N986B ROM Link
TWRP + VBMETA
Volume booster
Installation procedure
0) Backup ALL your important files to PC, ext drives, etc
1) Download and copy the latest TR ROM zip into your external storage or USB stick if you're on stock fw encrypted
2) Download latest EVB1 stock FW for your phone model and unpack it on your PC
3) Boot in download mode (Vol Up + Vol Down + plug the USB cable connected already to PC) and load up Odin on PC
Don't use USB adapters otherwise you might get issues flashing FW in Odin
Turn off Auto Reboot in Odin
4) Select files BL, AP, CP & HOME_CSC (keep data)
**do not start flash yet
5) Download Android 12 compatible TWRP (For-odin-twrp-c2s-3.6.0_11-A12-1a7_ianmacd+vbmeta.tar) from above link.
6) Add the above twrp + vbmeta patched.tar file into the USERDATA slot in Odin
7) Uncheck the auto reboot option in Odin and start the flashing
8) When flashing completes (keep usb plugged in !!!), hold Vol Down + Power buttons and then as soon as the screen goes black hold Vol Up + Power buttons to boot to recovery
*be warned first time you boot into recovery it will initialize and then reboot so just keep the buttons Vol Up + Power buttons pressed longer
**if you boot in stock FW, your data will be encrypted and you'll need to wipe your data before flashing ThinROM 4.x
9) When boot in TWRP, wipe your data if you're encrypted, flash TR 1.x zip and then reboot to system
10) After the first boot, install Magisk Manager if necessary; when you'll start Magisk Manager for the first time, reply with YES (agree to reboot) after MM have setup your root environment
*after reboot, go to Magisk Manager settings and toggle On Zygisk
10) Enjoy....
1. Backup to PC all your important files: documents, pictures, contacts, SMS, etc. BEFORE starting to flash anything
2. If you have issues booting the ROM, try the clean flash
3. Starting with Android 11, to boot into TWRP you need to use a USB cable connected to PC (same as DL mode) or a USB stick
4. If you like my work, consider buying me a coffee (PayPal link)
Enjoy!
Click to expand...
Click to collapse
Hi,
I followed the steps, but my phone memory is -250gb, how to fix that ?
Thanks
triconix555 said:
Hi,
I followed the steps, but my phone memory is -250gb, how to fix that ?
Thanks
Click to expand...
Click to collapse
Can you post a SS because I don't really understand what you're saying mate.
How is battery in this ROM compared to stock?
Banking apps working?
Banking apps work fine as long as you know how to use zygisk and battery is different for every user but for me it is alot better.
First post updated with May firmware.
I love this ROM. One thing is bugging me as I use two SIMs and nned two accounts on WhatsApp but Dual Messenger option is greyed out, how to enable it

GSI and Xperia 1

I tried to install some GSIs, but they were stuck at the costum Romes Loading animation.
I installed the Firmware with Emma
Locked it to update to Android 11 and unlocked it again
Installed TWRP and booted into it
Wiped system and userdata
Pushed to system.img file from the custom rom to my device into /sideload/
In TWRP install-System Image—> Pressed on the folder and on the system.img
It installed successfully
Rebooted
Stuck in Loading animation(PixelExpirience == A Google G with loading bar, LineageOs == The blue line with the bubble)
No crashes or so what, it just hangs in there for ~20 min and than I turn the device off with volume(+) and Power button.
I know Sony Xperia 1 is not officially supported for project treble, but since this thread(https://forum.xda-developers.com/t/...el-expierence-android-12-gsi-patches.4097433/) requires Pixel Experience GSI I thought it should be possible to run GSI on Sony Xperia 1.
Any idea what I might have donne wrong or are there other GSI roms I could try.
PixelEX = PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img 3.7 GB
LineageOS = lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img 2.0 GB
Bkeinn_ll said:
I tried to install some GSIs, but they were stuck at the costum Romes Loading animation.
I installed the Firmware with Emma
Locked it to update to Android 11 and unlocked it again
Installed TWRP and booted into it
Wiped system and userdata
Pushed to system.img file from the custom rom to my device into /sideload/
In TWRP install-System Image—> Pressed on the folder and on the system.img
It installed successfully
Rebooted
Stuck in Loading animation(PixelExpirience == A Google G with loading bar, LineageOs == The blue line with the bubble)
No crashes or so what, it just hangs in there for ~20 min and than I turn the device off with volume(+) and Power button.
I know Sony Xperia 1 is not officially supported for project treble, but since this thread(https://forum.xda-developers.com/t/...el-expierence-android-12-gsi-patches.4097433/) requires Pixel Experience GSI I thought it should be possible to run GSI on Sony Xperia 1.
Any idea what I might have donne wrong or are there other GSI roms I could try.
PixelEX = PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img 3.7 GB
LineageOS = lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img 2.0 GB
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/android-12-up-and-running-on-xperia-1.4331341/
I think you should take a look of this post.
In theory this would be the post I needed, but following this guide, with their files, made my Xperia 1 not even show the Rom’s Boot animation and instead ended up in a boot loop which stopped ~2 sec after showing the Sony logo.
But nevertheless thanks. I will ask in this post for help.
Try using fastboot method to install GSI ROM.
See this thread for reference : https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4128911/
Thanks, I did it.
What did I do different:
vbmeta.img from google(was a little bit bigger than the one from the TWRP)
Started from Android 9(directly from Emma)
Flashed system.img as well as vbmeta to system_a system_b/vbmeta_a, vbmeta_b
i have the same problem till now i cant flash any gsi i flashed android 11 and flashed after that vbmeta to a and b and flashed system.img and got infinite loading

Categories

Resources