Database Users

Lineage OS (official nightly) installation problem

I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.

Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.

i am on zui 2.3.045

hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
i am on zui 2.3.045 tell me full installation process if possible

Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?

+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Can i flash in fastboot or install Lineage os recovery?

Mikuzukz1 said:
Can i flash in fastboot or install Lineage os recovery?
Click to expand...
Click to collapse
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.

+∆bhijith said:
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
Click to expand...
Click to collapse
it's showing error that way

Mikuzukz1 said:
it's showing error that way
Click to expand...
Click to collapse
Even now? Even after rebooting to recovery via ADB?

+∆bhijith said:
Even now? Even after rebooting to recovery via ADB?
Click to expand...
Click to collapse
I don't know how to boot via adb ijust wiped all partitions in twrp

got it working finally....installed it over cm13.0 and done

Mikuzukz1 said:
got it working finally....installed it over cm13.0 and done
Click to expand...
Click to collapse
Wonderful ! Good to go for any 7.x.x rom now...
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Because i faced same problems before and searched in XDA and that is the solution available right now.

Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
I think file is not completely downloaded...
Once same happened when I checked I chose wrong file wwhich was half downloaded.. Check it

i'm facing the same problem. i don't know how to use adb boot.
isn't there any other way.
also i checked the file was completely downloaded
and i'm on zui 2.5

I also have problem when flash nuclearom from cm13. I have some zuk devices but got problem with 2
First, it has bootloop
I have to flash China ROM then it works
I can flash CM 13
But up to 14 or 7.x will have bootloop again
Pls help

Install Resurrection Remix Project Treble!

Here's a little info if you have never used treble. ?
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
Download Treble system-arm64-aonly
https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This guide is for people coming from emui. If your already on treble see my guide on next thread to switch between different system images without losing data.
I got this Resurrection Remix up and running with gapps and magisk. Copy RR img, gapps and magisk to sdcard or OTG. Because this TWRP you won't be able to use internal storage. YOUR BOOTLOADER MUST BE UNLOCKED AND BE ON OREO UPDATE.
Download open gapps I use arm64 Android 8.1 micro gapps https://opengapps.org
Download Magisk 16.4
https://drive.google.com/file/d/1YftvNNZVruyYgtFE5wFsgLTDDb4Yux5W/view?usp=drivesdk
Need to have this twrp installed. Here --https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk put twrp in adb folder
In adb in fastboot mode "fastboot flash recovery_ramdisk
complete_twrp_ramdisk.img"
After flash hold POWER VOLUME UP AND VOLUME DOWN IF YOU HAVE USB CONNECTED. OR JUST VOLUME UP PLUS POWER IF YOU DISCONNECT USB. TO REBOOT TO TWRP.
In TWRP select advanced wipe and wipe everything but sd card. Go to wipe again and select format data type yes. In TWRP hit reboot, reboot to recovery. Once back in recovery touch install. On bottom right select install image. Now find system-64-aonly img and select it. It will ask you where you want to install it, scroll down and select system image. Should take about a minute to install. Now reboot to system. After your in system reboot to twrp and flash gapps. After that select wipe format data. Reboot back to system and setup Google play services. Finally flash magisk for root in TWRP. ITS IMPORTANT TO INSTALL IN THIS ORDER OR YOU WILL END UP HAVING ISSUES WITH PLAY STORE AND INSTALLING APPS.
People that are getting uncertified play services error here is the APk to get your Google services device id. https://drive.google.com/file/d/1YjNZuS3RfSrQ7DnmzOZMH74I63fmHGwN/view?usp=drivesdk
Once you get your id go here and copy it in.
https://www.google.com/android/uncertified/
IT HAS EDGE GESTURES ????

I updated the installation flashing instructions on 6/2 added how to switch between different treble GSI system images. Below -------V
BUGS?
VOLTE NOT WORKING
THEME IN RR CONFIGURATION SETTINGS DOESNT WORK.
ANYONE ELSE NOTICE ANY BUGS LET ME KNOW SO I CAN ADD TO BUGS LIST.
Here's the Generic System Image List
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Thought I would make a guide for people who would like to test different treble GSI. So if you already on treble and would like to try a different one. This guides for you. Backup all your apps in titanium backup you can save them to internal storage. Copy system.img to SD card or usb to otg.
Download these gapps and copy to SD card to. https://drive.google.com/file/d/1Jz9gFWTUqKWr2y4X6FXIt5wQbR1-TrFH/view?usp=drivesdk
The reason using these gapps is because normal open gapps are to large and you will get an error in twrp saying not enough system storage available.
Boot to twrp and go to advanced wipe and wipe system data cache and dalvik. Don't wipe internal or SD card. Than flash system.img. Boot to system. Boot back to twrp and flash gapps. Go to advanced wipe and wipe data. Reboot to system. That's it, now you can test different treble gsi. Good luck.
Currently not booting GSI'S are DU and AEX.

This install process works with the other treble ROMs too for anyone interested.
Sent from my Honor 7X using XDA Labs

Has anyone successfully gone from a Treble based ROM (AOSP, LOS, RR, ECT) back to a fully working stock? These 1 off pages are great for information on flashing, but if we could create a generalized WIKI or something, that would be very helpful for everyone.

smokinjoe2122 said:
Has anyone successfully gone from a Treble based ROM (AOSP, LOS, RR, ECT) back to a fully working stock? These 1 off pages are great for information on flashing, but if we could create a generalized WIKI or something, that would be very helpful for everyone.
Click to expand...
Click to collapse
Either restore a twrp backup or flash the stock system image.
Sent from my Honor 7X using XDA Labs

Great but if you just want rr without root you can use fastboot flash
BTW I prefer the custom build here bcs it has huawei camera app built in but the ROM not update for some time

optionalmgrr.la said:
Great but if you just want rr without root you can use fastboot flash
BTW I prefer the custom build here bcs it has huawei camera app built in but the ROM not update for some time
Click to expand...
Click to collapse
Or you could just not flash magisk.
Sent from my Honor 7X using XDA Labs

allrockedout said:
I was having issues with play store now everythings working
Click to expand...
Click to collapse
What issues were you having, I can't seen to get some apps to open from playstoreb while others do.

jmoss1972 said:
What issues were you having, I can't seen to get some apps to open from playstoreb while others do.
Click to expand...
Click to collapse
You need to do flash system.img boot to system. Boot back to TWRP flash gapps. Factory data reset. And than boot to system. Pain in the ass I'm on AOSIP now. Took me forever to figure it out. After reboot apps weren't opening. Just keep trying clean install.

Thanks, I also ended up flashing AOSP vanilla and pico gapps and no issues with play store. Now if I could figure out how to make a proper back up I can use in TWRP.

jmoss1972 said:
Thanks, I also ended up flashing AOSP vanilla and pico gapps and no issues with play store. Now if I could figure out how to make a proper back up I can use in TWRP.
Click to expand...
Click to collapse
I know the p10 lite TWRP will let you backup data and system. But I've had some trouble booting into the p10 lite TWRP. Maybe need to install via fastboot I'm not sure. But I have a backup of system data kernel and boot made with p10 TWRP for stock emui that works perfect.

I want to install Resurrection Remix 7x specific build because it has Huawei camera built-in
BUt it hasn't been updated for long time @surdu_petru
https://forum.xda-developers.com/honor-7x/development/rom-t3765201
Treble build (AOSP or RR) seems more stable but they don't have Huawei camera...................
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
https://forum.xda-developers.com/pr.../huawei-stock-camera-app-treble-roms-t3735169

optionalmgrr.la said:
I want to install Resurrection Remix 7x specific build because it has Huawei camera built-in
BUt it hasn't been updated for long time @surdu_petru
https://forum.xda-developers.com/honor-7x/development/rom-t3765201
Treble build (AOSP or RR) seems more stable but they don't have Huawei camera...................
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
https://forum.xda-developers.com/pr.../huawei-stock-camera-app-treble-roms-t3735169
Click to expand...
Click to collapse
I have found a magisk module that is the hauwei stock camera. Don't remember where that was. Maybe you can find it

I don't want root though.... bu tthx!

Cannot find Edge gestures.
Cannot find edge gestures. Help please

mrmazak said:
I have found a magisk module that is the hauwei stock camera. Don't remember where that was. Maybe you can find it
Click to expand...
Click to collapse
I tried the p20 port and honor 10 camera ported but they don't work. P20 port I'm able to launch camera but the app force closes. If we could get a stock camera working that would be amazing.
Someone's just posted this haven't tested https://androidfilehost.com/?fid=746163614322262817

Adithya Krishnakumar said:
Cannot find edge gestures. Help please
Click to expand...
Click to collapse
Settings/configurations/gestures

allrockedout said:
I tried the p20 port and honor 10 camera ported but they don't work. P20 port I'm able to launch camera but the app force closes. If we could get a stock camera working that would be amazing.
Someone's just posted this haven't tested https://androidfilehost.com/?fid=746163614322262817
Click to expand...
Click to collapse
I'll give it a try
---------- Post added at 01:16 AM ---------- Previous post was at 12:43 AM ----------
Failed when I tried flashing.
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
allrockedout said:
I know the p10 lite TWRP will let you backup data and system. But I've had some trouble booting into the p10 lite TWRP. Maybe need to install via fastboot I'm not sure. But I have a backup of system data kernel and boot made with p10 TWRP for stock emui that works perfect.
Click to expand...
Click to collapse
Did you flash the p10 lite TWRP IMG in TWRP?

jmoss1972 said:
I'll give it a try
---------- Post added at 01:16 AM ---------- Previous post was at 12:43 AM ----------
Failed when I tried flashing.
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
Did you flash the p10 lite TWRP IMG in TWRP?
Click to expand...
Click to collapse
Yeah but magisk or something causing issues. I've gotten it through fastboot on emui in the past.

I'll try it, hopefully if it fails I can still use the TWRP I have installed.

Tested Treble Roms

Hey guys just wondering what Treble roms have been tested on our essential. Additionally, i want to start testing some myself and wanted to know if twrp actually allows us to make backups and if we copy to an external source if we can successfully restore later on. Thanks! I want to test bootleggers and others but wanna keep my data.

GuestK0010 said:
Hey guys just wondering what Treble roms have been tested on our essential. Additionally, i want to start testing some myself and wanted to know if twrp actually allows us to make backups and if we copy to an external source if we can successfully restore later on. Thanks! I want to test bootleggers and others but wanna keep my data.
Click to expand...
Click to collapse
Are there set instructions for flashing GSIs to the Essential, My last 4 devices had all separate commands, and modified vbmeta. I am yet to see solid flashing instructions, whether it be via Fastboot or TWRP....
*edit*
I ordered this device last night and due to receive it on Thursday. Just trying to figure out whats different from the Pixel 2 XL, Pixel XL, OnePlus6 and now my Essential. So im new to these parts of XDA, please dont be an ***.

I couldn't find a TWRP that supported Treble. Which is something you need to access the vendor partition.

Ascertion said:
I couldn't find a TWRP that supported Treble. Which is something you need to access the vendor partition.
Click to expand...
Click to collapse
Thats when Fastboot comes into play... There are no Fastboot commands for Essential to be able to flash a GSI on A/B?

U can flash gsi's via fastboot. And u can install them with our twrp. Every a/b gsi on the treble threads boot, except for havoc P . It bootlooped. Some are better than others. Oreo havoc works great. I am running pixel experience P right now. To flash them and get them to work, just have to fastboot -w then install via fastboot stock Oreo (firmware ending 267) then wipe system only, and flash gsi. Boot. Some of the older gsi's u have to flash the gsi system image to both slots. And regarding twrp nandroid backups, make your backup, then copy to external. After testing, fastboot -w again, flash android P (firmware 091) then after setup, copy backup back to phone, boot back to twrp, and restore. Oh yeah be sure to flash the kernel u use with regular use in twrp before making the nandroid or u will just backup twrp as your kernel... there are some issues, but if u can fix them, its a fun experiment.

Benzo 9.0 gsi rom works amazing and has every customization one can think of

jacksummers said:
Benzo 9.0 gsi rom works amazing and has every customization one can think of
Click to expand...
Click to collapse
I'm currently on stock pie. Do I have to downgrade to Oreo before I can flash benzo gsi? Is there any other steps that are required to get it to work? Thanks for your help.

Joylesstuna said:
I'm currently on stock pie. Do I have to downgrade to Oreo before I can flash benzo gsi? Is there any other steps that are required to get it to work? Thanks for your help.
Click to expand...
Click to collapse
Yes last Oreo firmware. Then after setup back to boot loader, fastboot erase system, flash the gsi, switch to other slot, do same thing, reboot.after u get it setup, back to boot loader then recovery, factory reset, then set it up flash twrp, mount system, flash phhhsuperuser ab zip, then reboot

Is there a reason we can't flash a 9.0 GSI from stock Pie? Just curious as to why we need to downgrade to 8.1 to flash something on 9.0..

MoistPicklez said:
Is there a reason we can't flash a 9.0 GSI from stock Pie? Just curious as to why we need to downgrade to 8.1 to flash something on 9.0..
Click to expand...
Click to collapse
U need the vendor files from 8.1 with the 9.0 pie gsi's. I tried to go from pie and just wipe everything and then before flashing the gsi flashing a vendor.img from 8.1, but it had weird issues, so maybe the firmware needs to directly place the vendor files where they go directly with a proper flash

Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.

MoistPicklez said:
Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.
Click to expand...
Click to collapse
Only had that once or twice, make sure u aren't rooting before setup, and try to use gsi's with gapps in built.the newer builds have them included and phhhsuperuser is the only rooting method that truly works without issues
---------- Post added at 03:31 PM ---------- Previous post was at 02:54 PM ----------
MoistPicklez said:
Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.
Click to expand...
Click to collapse
Benzo rom is the best, at least until havoc p gets fixed. It's the only one I can't get to go

MoistPicklez said:
Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.
Click to expand...
Click to collapse
Device is Uncertified on stock Pie with Magisk on OP6...
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
jacksummers said:
U can flash gsi's via fastboot. And u can install them with our twrp. Every a/b gsi on the treble threads boot, except for havoc P . It bootlooped. Some are better than others. Oreo havoc works great. I am running pixel experience P right now. To flash them and get them to work, just have to fastboot -w then install via fastboot stock Oreo (firmware ending 267) then wipe system only, and flash gsi. Boot. Some of the older gsi's u have to flash the gsi system image to both slots. And regarding twrp nandroid backups, make your backup, then copy to external. After testing, fastboot -w again, flash android P (firmware 091) then after setup, copy backup back to phone, boot back to twrp, and restore. Oh yeah be sure to flash the kernel u use with regular use in twrp before making the nandroid or u will just backup twrp as your kernel... there are some issues, but if u can fix them, its a fun experiment.
Click to expand...
Click to collapse
Thanks for all your information, PM sent...

jacksummers said:
Only had that once or twice, make sure u aren't rooting before setup, and try to use gsi's with gapps in built.the newer builds have them included and phhhsuperuser is the only rooting method that truly works without issues
---------- Post added at 03:31 PM ---------- Previous post was at 02:54 PM ----------
Benzo rom is the best, at least until havoc p gets fixed. It's the only one I can't get to go
Click to expand...
Click to collapse
So no Magisk then?

governmentissuejoe said:
So no Magisk then?
Click to expand...
Click to collapse
Correct no magisk. Search for phhhsuperuser ab zip flash in twrp

governmentissuejoe said:
So no Magisk then?
Click to expand...
Click to collapse
On my OP6, I have NOT been able to get Magisk to flash properly on ANY P GSIs....
---------- Post added at 05:00 PM ---------- Previous post was at 04:45 PM ----------
jacksummers said:
Correct no magisk. Search for phhhsuperuser ab zip flash in twrp
Click to expand...
Click to collapse
So you didnt have to use ANY cmds to disable Verity or Decryption on Fastboot? That was a BIG deal on OP6 and Pixel 2 XL. I'm guessing the Essential TWRP build decrypts instead?
---------- Post added at 05:04 PM ---------- Previous post was at 05:00 PM ----------
jacksummers said:
U can flash gsi's via fastboot. And u can install them with our twrp. Every a/b gsi on the treble threads boot, except for havoc P . It bootlooped. Some are better than others. Oreo havoc works great. I am running pixel experience P right now. To flash them and get them to work, just have to fastboot -w then install via fastboot stock Oreo (firmware ending 267) then wipe system only, and flash gsi. Boot. Some of the older gsi's u have to flash the gsi system image to both slots. And regarding twrp nandroid backups, make your backup, then copy to external. After testing, fastboot -w again, flash android P (firmware 091) then after setup, copy backup back to phone, boot back to twrp, and restore. Oh yeah be sure to flash the kernel u use with regular use in twrp before making the nandroid or u will just backup twrp as your kernel... there are some issues, but if u can fix them, its a fun experiment.
Click to expand...
Click to collapse
Firmware ending in 267 is for Sprint, FYI

So I thought I'd get the flashies and attempt more then a few GSI's.
I had some varying results. I installed all the GSI's in the same manor:
- Flash latest stock O
- Wipe "fastboot -w".
- Install "fastboot flash system example.img". This also wipes System before flashing.
Benzo 9.0 - Success!
Bootleggers 3.0/8.1 - Uncertified and unable to complete setup.
DU 8.1 - Uncertified and unable to complete setup.
Pixel Exp 9.0 - Success!
Pixel Exp 8.1 - Uncertified and unable to complete setup.
RR 8.1 - Success!
Benzo is by far my favorite so far. Give it a shot!

Did you do anything to the benzo rom after downloading it? And by latest stock o is 267?

martinezs89 said:
Did you do anything to the benzo rom after downloading it? And by latest stock o is 267?
Click to expand...
Click to collapse
No, maybe unzipped it, but otherwise I just used the steps in my other post, and yes I used stock O 267.

I can't seem to get it to flash on fastboot. Idk what I am doing wrong

[ROM][10.0.0_r33] Lineage os 17.1 [UNOFFICIAL]

LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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.
*/
DOWNLOAD ROM FROM HERE: https://sourceforge.net/projects/romz/files/lineage-17.1-20200416-UNOFFICIAL-kuntao.zip/download
WHAT'S WORKING?:
Fingerprint
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Sensors
GPS
SElinux is enforcing
Issues:
Audio and video playback (will be fixed soon)
FLASHING INSTRUCTIONS:
Code:
[b]-Download the ROM and GApps of your choice
-Backup every partition from TWRP Recovery
-Make a full wipe (system, data, cache, dalvik)
-Flash LOS17.1
-Install GAPPS package
-Wipe cache!
-And at last Reboot!
[First boot will take a few minutes! Have patience]
Clean Flash is always recommended![/b]
SOURCES:
Device tree: https://github.com/LineageOS/android_device_lenovo_kuntao
Vendor: https://github.com/TheMuppets/proprietary_vendor_lenovo
Kernel: https://github.com/LineageOS/android_kernel_lenovo_msm8953
I would like to thank Priyesh anna for teaching and helping me in rom compiling. I would like to thank Swalih for testing my builds. cheers.
XDA:DevDB Information
LINEAGE OS 17.1, ROM for the Lenovo P2
Contributors
amrish7799, PriyeshP, SWALIH
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest firmware
Version Information
Status: Beta
Created 2020-04-16
Last Updated 2020-04-16

Reserved

Is there screeshoot and sound panel in QS?

Andro8275 said:
Is there screeshoot and sound panel in QS?
Click to expand...
Click to collapse
There is screenshot tile and volume panel tile in quick settings. Sound tile is not present.

Does sound work, while playing YouTube, Spotify etc?

yajdintaydemir said:
Does sound work, while playing YouTube, Spotify etc?
Click to expand...
Click to collapse
Yes. Works fine.

Face unlock included ?

Does this Rom have all the extras that AICP Rom does?
Thanks.

Not booted bro format data and install not boot !

myjess said:
Does this Rom have all the extras that AICP Rom does?
Thanks.
Click to expand...
Click to collapse
Actually no. Lineage OS is pure vanilla ROM with almost no customisation other than just the basic ones

Bro rom not booted . Format data and install not booted.

Shades_of_death0 said:
Bro rom not booted . Format data and install not booted.
Click to expand...
Click to collapse
Booted fine for me. Didn't format data. Use compatible twrp. Check my screenshots. Provide logs, will look into it.

Bootloop for me too

Booted OK from TWRP wipe and adb push zips to /twrp/.
Data is f2fs.
1. Lineage 17.1 has its own recovery but how the heck do I install a magisk boot image with this lineage 17.1 recovery.
Going to try to put twrp3.3.1-1 back onto it.
2. I cannot see any device serial in adb devices or fastboot devices with the phone booted into OS. I can only see an adb device ID in Recovery. I can only see fastboot device ID in bootloader. This may be normal, I cannot remember.
I forgot to enable "Android debugging" in developer options. Now OK.
3. Why has the boot.img from this rom got a different MD5 sum from the AICP boot.img, and a different MD5 sum from the boot.img from Lineage 16.0?
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\AICP\boot-20200415.img MD5
MD5 hash of ..\AICP\boot-20200415.img:
c9d965f1ecbd8496debc540f649e140c
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile boot.img MD5
MD5 hash of boot.img:
c98e46c7c3d9118e78f458dce847b7a5
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\Lineage16.0\boot.img MD5
MD5 hash of ..\Lineage16.0\boot.img:
415ca883bc162e159ba00cc22b895d5c
CertUtil: -hashfile command completed successfully.
4. Facebook / Youtube / Whatsapp stuttering very badly.
Now working fine, only thing I did was turn on Android debuggin and do a full adb backup. Very strange.
Thanks.

Face unlock included ?

amrish7799 said:
Booted fine for me. Didn't format data. Use compatible twrp. Check my screenshots. Provide logs, will look into it.
Click to expand...
Click to collapse
will this ROM be maintaind time to time?
---------- Post added at 08:44 AM ---------- Previous post was at 08:39 AM ----------
siemens_marolikar said:
Face unlock included ?
Click to expand...
Click to collapse
no way
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
siemens_marolikar said:
Face unlock included ?
Click to expand...
Click to collapse
even the official one havnt:silly:

myjess said:
Booted OK from TWRP wipe and adb push zips to /twrp/.
Data is f2fs.
1. Lineage 17.1 has its own recovery but how the heck do I install a magisk boot image with this lineage 17.1 recovery.
Going to try to put twrp3.3.1-1 back onto it.
2. I cannot see any device serial in adb devices or fastboot devices with the phone booted into OS. I can only see an adb device ID in Recovery. I can only see fastboot device ID in bootloader. This may be normal, I cannot remember.
I forgot to enable "Android debugging" in developer options. Now OK.
3. Why has the boot.img from this rom got a different MD5 sum from the AICP boot.img, and a different MD5 sum from the boot.img from Lineage 16.0?
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\AICP\boot-20200415.img MD5
MD5 hash of ..\AICP\boot-20200415.img:
c9d965f1ecbd8496debc540f649e140c
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile boot.img MD5
MD5 hash of boot.img:
c98e46c7c3d9118e78f458dce847b7a5
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\Lineage16.0\boot.img MD5
MD5 hash of ..\Lineage16.0\boot.img:
415ca883bc162e159ba00cc22b895d5c
CertUtil: -hashfile command completed successfully.
4. Facebook / Youtube / Whatsapp stuttering very badly.
Thanks.
Click to expand...
Click to collapse
Will try to fix video stuttering issues. Rest all good.

Media sound issue. Automatically got no audio output.

Mrinmay Medhi said:
Media sound issue. Automatically got no audio output.
Click to expand...
Click to collapse
+1
---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------
amrish7799 said:
Will try to fix video stuttering issues. Rest all good.
Click to expand...
Click to collapse
+1
yt video plays at slow mo, audio not working.

markmywordz said:
+1
---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------
+1
yt video plays at slow mo, audio not working.
Click to expand...
Click to collapse
+2

A Guide To Install Android 10 (With Fixes) on Redmi 7a

Hello,
I know that ROM developement on redmi 7a has been extreemly slow, but we all know that redmi 7a is a treble enabled device and therefore we can install every android GSI as long as it is ARM32-BINDER64-AB, yes and i wouldn't explain it here you can read it over here here.
So i thought that i should give you guys a little guide on how to install GSIs and custom ROMs and yeah with volte fix too
NOTE - I AM NOT RESPNSIBLE IF YOUR DEVICE GETS BRICKED OR THERMONUCLEAR WAR TAKES PLACE, YOUR WARRANTY IS VOID FROM THIS STEP ON, I AM NOT RESPONSIBLE IF YOUR DEVICE GETS BRICKED MAKE SURE YOU HAVE MOVED YOUR DOWNLOADED ROMS AND GAPPS TO A PC OR A SD CARD I AM NOT RESPONSIBLE FOR ANYTHING
1] The very important first step is to unlock your bootloader.
2]The second step is to patch your boot image (if you want to root it with magisk)
3] Install the custom recovery of your choice
Download the TWRP file from here
you also can install TWRP forks like
PICTHBLACK RECOVERY PROJECT or PBRP from here
SHRP RECOVERY from here (i wouldn't recommend this one if you are flashing this for the first time)
If you have your device drivers installed but you dont have adb installed then please download this file and extract it to a suitable folder where your downloaded recovery is extracted and run cmd-here and follow these steps given below
Code:
fastboot devices
this will show you if your device is connected or not.
Code:
fastboot flash recovery (your recovery name.img)
Code:
fastboot reboot
you have to keep pressing you volume increase button to reboot to recovery
4] You have to wipe DATA first then, reboot to recovery and go to mount select system (if it's unchecked)
5] Go to WIPE -> ADVANCED WIPE -> Select SYSTEM - DALVIK CACHE - CACHE - INTERNAL STORAGE
6] The list for the available GSIs or ROMs is ----
1) LineageOS thanks to ExpressLuke (GSI) (You might have to downgrade your miui to be able to boot)
2) HavocOS thanks to Skulshady (GSI) (Boots just fine with any version of miui volte patch is needed)
3) Mokee thanks to GuaiYiHu (ROM) (No worries about anything)
4) AOSP Special thanks to Phhusson (GSI) (Boots just fine without any hiccups volte patch is needed)
5) CAOS by Erenmitein (GSI) (Not tested)
6) CrDroid By Erenmitein (GSI) (tested needs the bolte fix patch. please follow the steps given below)
7] Move your GSI img (extract the .xz file) the extension is going to be .img and will not visible in TWRP or it's forks unless you select the INSTALL IMAGE option in the FLASH section and GAPPs
8] Flash your GSI as a System Image
9] Reboot to recovery again and flash your GAPPS ignore if it says no OS installed when rebooting to recovery
10] The fix for VOLTE is here thanks to Khushraj Rathod
you just have to flash it from TWRP or its forks
11] The first reboot will take some time and voila your GSI has been installed (flashed).
12] For Mokee, personaly i love Mokee rom with its boot animation, you can just flash your zip through twrp with gapps.

Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?

kra_ppo said:
Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?
Click to expand...
Click to collapse
No.

A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.

Havoc (an Mokee - but I dont like it) was finally successfull, but only by formating Data and not to wipe internal Storage....

kra_ppo said:
A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.
Click to expand...
Click to collapse
Flash vbmeta

Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work

how to get back to stock ROM ?

idcamper said:
Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work
Click to expand...
Click to collapse
You flashed floor miui 10.0.2.5.?

can't i do this with twrp? Tutorial ?

Flammenschwert1337 said:
Flash vbmeta
Click to expand...
Click to collapse
Did you find solution?

lslayer4231 said:
Did you find solution?
Click to expand...
Click to collapse
Start with miui 10.0.2.5.
Then go on.

My phone bootloops to redmi logo and recovery after flashing, any help from this?

After installing latest havoc 3.7 gsi the call recording feature not working though normal sound recording works... Any fix?

Hey, guys!
Havoc OS GSI is selinux permissive or enforced?
Is it possible to go back to stock rom by doing a backup using twrp?
I'm sorry if I'm being dumb, but as you already noticed, I'm newbie.

MEMO#22 said:
My phone bootloops to redmi logo and recovery after flashing, any help from this?
Click to expand...
Click to collapse
Switch back to miui 10 global version and install twrp

Has anyone else got media playout over bluetooth OK and if so, which GSI or ROM and which base firmware, please? It does not work for me with AOSP on latest EU firmware. Only calls go to BT.