Related
Enhanced twrp for op3 and op3t
Download from official server:
Download for oxygenos and other non-treble ROMs: https://glassrom.pw/op3_recovery.img
Download for treble ROMs: https://glassrom.pw/op3_recovery-treble.img
Download from CDN:
Download for oxygenos and other non-treble ROMs: https://cdn.glassrom.pw/op3_recovery.img
Download for treble ROMs: https://cdn.glassrom.pw/op3_recovery-treble.img
Unofficial mirrors:
Hosted by @Sytis https://storage.ceres-sys.de/glassrom
Don't ask these questions. Seriously:
Features: none. It's a recovery. It should be as simple as possible because you rely on this stuff to recover your device in case something goes wrong
Seriously. Were you expecting features from a custom recovery?
Screenshots: it looks like TWRP
Important. There is a blank option and a system_root option in the mounts section. These are only for compatibility with scripts. Do not try to tick them yourself
Some scripts may throw a "failed to umount /system_root" message. This is fine
Important: why do some ROMs refuse to flash?
Some ROMs like oxygenos and glassrom use a feature called "downgrade attack prevention". If TWRP's build date is higher than the build date of the ROM the installation script assumes a downgrade attack is happening and the flashing fails
System nandroid restore fails:
You are not supposed to be restoring file-based backups of the system partition on a device with dm-verity in the first place. Backup and restore system image backups.
Glassrom users: if this is your first time flashing glassrom remember that the current enhanced twrp will always have a build date higher than the current glassrom build. In other words you can only flash a newer glassrom build as long as your enhanced twrp build is older or in other words:
Switching to glassrom: use official twrp, flash glassrom and then flash enhanced TWRP to enforce downgrade attack prevention
Updating glassrom: no need to switch to official. Always update glassrom before you update enhanced twrp
This was intentionally done to prevent downgrade attacks on glassrom. Using enhanced twrp with glassrom is recommended
This TWRP addresses a number of issues that have been plaguing the op3:
Uses a backported F2FS driver (5.1-rc1-3.18) that fixes an issue where TWRP would get stuck on the TWRP splash screen for a long time if the user was using F2FS
Uses an upstream kernel that was taken from lineage's common kernel https://github.com/LineageOS/android_kernel_qcom_msm8996
Added all crypto footer code back to resolve all encryption issues
Improved detection of device variant. Recovery now validly detects op3 and op3t
A full selinux policy so that files do not get labelled incorrectly. This resolves a bunch of issues like "device doesn't boot after restoring nandroid"
Built against full lineage source. No minimal manifest or any other nonsense
Upstreamed sdfat driver for better suppport for USB-OTG drives
No prebuilt kernels. Uses a fully source built kernel
Kernel built with a compatible GCC 8. No weird compiler optimisation
Ext4 is the default filesystem instead of f2fs
Current issues: even if the source code is out building TWRP against lineage is not something a beginner can do. If somebody is willing to contribute build documentation they are more than welcome
XDA:DevDB Information
Anupritaisno1's enhanced twrp builds, Tool/Utility for the OnePlus 3
Contributors
anupritaisno1, anupritaisno1, dianlujitao
Source Code: https://github.com/GlassROM-devices
https://bitbucket.org/anupritaisno1/aarch64-linux-gnu
Version Information
Status: Stable
Current Stable Version: 3.3.0
Stable Release Date: 2019-05-01
Created 2019-05-03
Last Updated 2019-05-02
A request to moderators:
People often ask "screenshots" and "features" while this really doesn't make much sense in the context of a recovery. It's a recovery
Please delete such posts to keep the thread clean
Reserved
Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.
aboodyaiman said:
Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.
Click to expand...
Click to collapse
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.
Dirk said:
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.
Click to expand...
Click to collapse
Have you tried this*? I'm waiting feedback :silly:
I'm not in a good time for messing around..
*i mean the recovery as general
aboodyaiman said:
Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.
Click to expand...
Click to collapse
Busybox is pretty terrible and most of it's executables aren't even compliant to standards
Please update your scripts to use toybox or ship the actual statically linked binaries
Dirk said:
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.
Click to expand...
Click to collapse
You should specify the "-o rw,remount" flag otherwise if mount system partition read-only is ticked there's a high chance system is mounted read-only and the script won't actually touch the system partition. This can be achieved by using a shell script instead of run_program()
Your command can also fail with "cannot find /system in the fstab". Instead of calling mount that way you should use this edify command and then call mount with run_program() to make sure it doesn't fail
Code:
mount(fs_type, partition_type, name, mount_point)
Please see https://source.android.com/devices/tech/ota/nonab/inside_packages
Toybox uses a slightly different mount command so merely replacing all instances of busybox with toybox will not work
anupritaisno1 said:
Busybox is pretty terrible and most of it's executables aren't even compliant to standards
Click to expand...
Click to collapse
IMHO bb is much more sophisticated then tb. If compiled with long options enabled bb is more posix compliant then any other multicall binary I know of.
The original decission to replace bb by tb by google was made because of license politics (bb: gnu copy left; tb: apache) - technically bb is superior to tb, for the amount of implememted commands as well as the posix compliance of the implemented commands (if configured correctly). I.e. parts of dns and resolver libs in tb are broken from the beginning of tb used in android (though this doesn't matter in recovery only use). fgrep/egrep are another broken/non-posix-compliant topic, which is solved by adding standalone binaries.
The claim you've made is at least questionable, and since you are publishing your sources (aka complying to gpl), the main reason for not using bb is not true for your twrp builds.
You may consider to put in bb additionally. For los integration, I've made a bb setup not overriding any tb links and installing bb as well as it's links to /system/xbin. With nearly no effort the installation target could be changed to i.e. /xbin or /bb/bin. If the installation dir is added in the path after the path to tb, you'll ship a recovery not only compatible with latest pie sources, but also with backward compatibility for flashable zips relying on bb.
https://github.com/nvertigo/android_external_busybox/tree/nlos-16.0
nvertigo67 said:
IMHO bb is much more sophisticated then tb. If compiled with long options enabled bb is more posix compliant then any other multicall binary I know of.
The original decission to replace bb by tb by google was made because of license politics (bb: gnu copy left; tb: apache) - technically bb is superior to tb, for the amount of implememted commands as well as the posix compliance of the implemented commands (if configured correctly). I.e. parts of dns and resolver libs in tb are broken from the beginning of tb used in android (though this doesn't matter in recovery only use). fgrep/egrep are another broken/non-posix-compliant topic, which is solved by adding standalone binaries.
The claim you've made is at least questionable, and since you are publishing your sources (aka complying to gpl), the main reason for not using bb is not true for your twrp builds.
You may consider to put in bb additionally. For los integration, I've made a bb setup not overriding any tb links and installing bb as well as it's links to /system/xbin. With nearly no effort the installation target could be changed to i.e. /xbin or /bb/bin. If the installation dir is added in the path after the path to tb, you'll ship a recovery not only compatible with latest pie sources, but also with backward compatibility for flashable zips relying on bb.
https://github.com/nvertigo/android_external_busybox/tree/nlos-16.0
Click to expand...
Click to collapse
Thanks. I guess I was wrong about busybox
I'm still not considering shipping busybox. Whenever I've tried it something broke so I'll just be sticking with toybox on that part
What I might be able to do is make a zip that copies busybox to /sbin/busybox and since it's just copying in ram there shouldn't be much of a problem. Users can flash this zip as a way to have backward compatibility with older zips. That sounds like a much better option honestly as then the fix is not just tied to my recovery but can be used on every recovery that doesn't have busybox on the op3
Edit: I also do not think shipping your busybox is a very good idea. You're compiling busybox with this
-Wno-error=implicit-function-declaration -Wno-implicit-function-declaration
Click to expand...
Click to collapse
I don't even know why this is a compiler warning. This should be an error but if you're shipping busybox with that warning disabled instead of fixing it that's just asking for trouble
anupritaisno1 said:
What I might be able to do is make a zip that copies busybox to /sbin/busybox and since it's just copying in ram there shouldn't be much of a problem.
Click to expand...
Click to collapse
...and on every second page of this thread, you'll be asked, if flashing bb is necessary on each update. Then you'll need to answer every time: "no, you need to flash it prior to each flashing of a bb needing zip."
If you just say bb is droped upstream and you want to keep your twrp clean.
Anyway: I've fixed the static build target.
anupritaisno1 said:
Edit: I also do not think shipping your busybox is a very good idea. You're compiling busybox with this
Click to expand...
Click to collapse
Thanx for the heads up - you are absolutly right here! (This was on my todo list more then 2 years ago, then I fogot to do it... I don't like people pointing me to my old and forgotten todos... )
https://github.com/nvertigo/android_external_busybox/commit/f512d6cbb4181970b47383a6efe0c01f27a0d978
nvertigo67 said:
...and on every second page of this thread, you'll be asked, if flashing bb is necessary on each update. Then you'll need to answer every time: "no, you need to flash it prior to each flashing of a bb needing zip."
If you just say bb is droped upstream and you want to keep your twrp clean.
Anyway: I've fixed the static build target.
Thanx for the heads up - you are absolutly right here! (This was on my todo list more then 2 years ago, then I fogot to do it... I don't like people pointing me to my old and forgotten todos... )
https://github.com/nvertigo/android_external_busybox/commit/f512d6cbb4181970b47383a6efe0c01f27a0d978
Click to expand...
Click to collapse
I haven't really checked the code but I'm not that sure about this part
Shouldn't it be like
Code:
#ifndef _GNU_SOURCE
#define _GNU_SOURCE
Idk just sounds more correct that we don't want a redefinition here
Is there any need for a manual mount of 'fakecache' like in Enhanced TWRP of OP2 ?
I hope not...
Thanks for the development !
gps3dx said:
Is there any need for a manual mount of 'fakecache' like in Enhanced TWRP of OP2 ?
I hope not...
Thanks for the development !
Click to expand...
Click to collapse
The entire fakecache experiment was me trying to port treble to the op2
That obviously failed and I'm in the process of removing that hack even from the op2
It's not there on this TWRP. That's for sure
F2FS 5.2-rc1-3.18 is out
The update will first arrive on glassrom and then on enhanced TWRP
anupritaisno1 said:
F2FS 5.2-rc1-3.18 is out
The update will first arrive on glassrom and then on enhanced TWRP
Click to expand...
Click to collapse
Glassrom is out but I've sadly not received any feedback from the twrp testers yet
The new release might be delayed and I'm also busy working on op2
It will definitely come in 1-2 days
Glad you made this twrp @anupritaisno1.
Working great here and happy to see all issues I had with other versions (some warnings on terminal, time issues etc...) are gone!
Keep up the good work
@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?
gps3dx said:
@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?
Click to expand...
Click to collapse
Please get me a copy of /sys/fs/pstore/console-ramoops-0 on the next boot after the crash
gps3dx said:
@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?
Click to expand...
Click to collapse
Hi I checked this myself
There seems to be absolutely no difference between drivers from 5.0.8 and 9.0.2
It feels as if oneplus simply took the drivers from 5.0.8 and smashed them onto 9.0.2 so I have no idea what crashes you're observing. Please submit logs
Did somebody try the Beta/Dev Rom for the Poco F2 Pro? How it is?
Looks like in 2 weeks Google will release stable Android 11.
about Android11
it is unstable for now,some bank apps are crashed,and system is constantly reboot itself,however,you can enjoy new GPU driver.
Using for a while on China Developer ROM. There are no crashes or performance issues, but for me biggest deal breaker is that DJI Go 4 app isn't working at the moment. I hope they update it soon to work with Android 11.
Does the beta come with A/B partition for seamless updates? I heard Android 11 will require devices to be in an A/B partition system, which would come handy for OTA updates on rooted devices.
(Currently, we're on an A-only partition with MIUI12 & Android 10)
You could easily answer my question by installing Treble Check (from KevinT.) on the Play Store. The app checks which partition system is used on the device (currently says "Seamless System Updates Unsupported" with Android 10).
Eidenz said:
Does the beta come with A/B partition for seamless updates? I heard Android 11 will require devices to be in an A/B partition system, which would come handy for OTA updates on rooted devices.
(Currently, we're on an A-only partition with MIUI12 & Android 10)
You could easily answer my question by installing Treble Check (from KevinT.) on the Play Store. The app checks which partition system is used on the device (currently says "Seamless System Updates Unsupported" with Android 10).
Click to expand...
Click to collapse
I have EU ROM Android 11 Beta weekly 20-08-20 installed. Treble Check says Only A partition, Seamless System updates Unsupported".
Alrighty, thank you.
I hope this will be in the first release of Android 11 in September. They are planning to make a virtual A/B partition for all devices.
Eidenz said:
I heard Android 11 will require devices to be in an A/B partition system, which would come handy for OTA updates on rooted devices.
Click to expand...
Click to collapse
AFAIK only devices launched with Android 11 are required to adopt it's new features like A/B partitions and enforced background processes handling.
Thats why we will not get it.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Whats works:
Booting
Audio
Graphics
RIL (calls, sms, mobile data)
Wi-Fi, Wi-Fi Direct
Bluetooth
GPS, GLONASS
FM Radio
Sensors
Camera
Face Unlock
Video recording
Screen cast
Offline charging
SELinux (enforcing)
SafetyNet (with hidden Magisk or without root)
Tell me, if something does not work.
FAQ
Q: Does this ROM supports double tap to wake? A: No. And will not in future.
Q: Cannot add widgets to home screen. Widgets is not supported? A: Widgets is not supported in builtin launcher. Download any third-party home app (like Nova Launcher) and enjoy!
Q: Why split screen mode is not available? How to enable? A: Due to Android Go limitations, all forms of multiwindowing is not available on this edition of Android.
Q: When my app "foo" asks permission to access to notifications or to run on top of other apps, I see "This feature is disabled"... A: This is limitations of Android Go to save memory.
Q: Cannot use my sdcard as primary storage! A: This feature is unstable and excluded from ROM.
Q: Flashed this ROM but phone don't booting! A1: Boot to recovery and wipe /data, then reboot. A2: If your /data is formatted to f2fs, format it to ext4 and boot your phone.
Q: What is "Gapps for Android Go"? A: This is Gapps set, extracted as-is from Nokia 1 Plus Android 11 Go firmware and packaged for Lenovo A6000. Nothing removed, just fixed some permissions and added Google Camera Go.
Installation
Flash latest recovery (if needed), based on TWRP >= 3.2
Reboot to recovery
Wipe /cache and /data. If your /data is formatted in f2fs, format it in ext4, otherwise OS will not boot.
Flash the rom
Flash Gapps (Gapps for Android Go or OpenGapps ARM/Android 11/pico or nano)
Flash Magisk (also if needed)
Reboot to ROM
Spoiler: Latest changes
Build 05.09:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
NOTE: Strongly not recommended "dirty" updating. If you want to do this anyway, flash migration script before flashing the ROM!
Migration script: https://drive.google.com/file/d/15hB63RkyRpCljho9jyFTHoYWvCl4cDWe/view?usp=drivesdk
Download ROM: https://drive.google.com/file/d/1vUHuS18vDowwCSIWl8Dl4xxRHR4EHir0/view?usp=drivesdk
Gapps: Gapps for Android Go(updated!) or OpenGapps (ARM, pico or nano)
Credits to:
twain55
Moto-M8916 guys
Teo Flo
dev_harsh1998
SkepticOne
Nitrogradient
IvanHephaestus
Our Telegram discussion group: Lenovo A6000/Plus Community Discussions
Contributors
acroreiser
dev_harsh1998
Source code
Device tree: https://github.com/acroreiser/android_device_lenovo_a6000
Kernel tree: https://github.com/acroreiser/android_kernel_lenovo_a6000
Vendor tree: https://github.com/acroreiser/android_vendor_lenovo_a6000
ROM OS Version: Android 11 Go
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Hex Firmware Patch, TWRP >= 3.2
Based On: LineageOS
Version Information
Status: Stable
Created 2021-05-12
Last Updated 2021-09-13
Finally android 11 for a6000 thank you
Wow, I thought the previous version (17.1) is the last one for this device.
I am really happy I was wrong!
Thank you so much for your work acroreiser and dev_harsh1998. Also thanks to everyone who is credited!
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
[email protected] said:
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
Click to expand...
Click to collapse
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Teo Flo said:
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Click to expand...
Click to collapse
Thanks for the info, I will try that for sure...
Hey devs,
Thanks for this brand new ROM! I use this phone as a daily driver and wanted your advice on this version or the 17.1 version. Which one is likely to be maintained in the future? I understand that 17.1 is stable but will it still get more updates or security patches or should I go ahead with this 18.1 version, please?
Thank you for your help and also for keeping this phone alive in 2021.
Cheers,
S
santoshwins said:
Which one is likely to be maintained in the future?
Click to expand...
Click to collapse
Currently Lineage OS 18.1 is maintained.
Both 17.1 and 18.1 is based on my Go device tree (forked from @dev_harsh1998 lineage-16.0 tree) but lineage-17.1 branch is not maintained since february 2021.
I don't know is @twain55 can maintain 17.1 builds for a long time (better ask him).
Lineage OS 18.1 is pretty stable for daily usage by user reports and my experience with a6010 (I don't have a6000 and primarily maintaining a6010 with merging stable changes to a6000 tree).
Can a dirty flash be done from 17.1 ?
Zack316 said:
Can a dirty flash be done from 17.1 ?
Click to expand...
Click to collapse
Of course no.
New build is up!
Changes:
June security patch level
Updates from Lineage OS team
Memory and performance optimizations for 1/8 devices
Forward-ported qcom memory optimizations (frameworks/base)
Updated Binder driver (kernel)
Implemented automatic background apps memory reclaim (kernel)
Restored Qualcomm VP8 and HEVC codecs
Updated Bluetooth HAL from Nokia 1.3
Updated some media blobs
Some kernel tweaks from other low ram devices (Redmi Go, Nokia 1.3)
Workaround for broken video recording in recent versions of Google Camera Go
Recent apps screen is limited to 5 apps to save memory
Killed multiuser support - Go devices should not have this. Also this feature is pointless in our ancient phones...
Download: https://drive.google.com/file/d/1IqRTbY9CYH9Je3bmqaavjQHnn-763bx5/view?usp=drivesdk
Wow, thank you so much for the android 11 version. It is minimalistic and smooth. Loved the rom. Also thank you devs for keeping this device alive.
Needs Undervolting.
Even the standby drain is around 600ma.
Also I've bought a new battery for this, even that cannot survive more than an hour of SOT.
Please optimised the kernel or just undervolt it a bit.
Also only one of the back speaker is working,
Hi , Dear
Thank you for your your creativity
For Lenovo A6000 1G Ram & 8Gb Rom
Which version is the best 17.1 or 18.1 ??
Can i flash Twrp 3.2 on kitkat or must to be on Lolipop ??
Cheers ^_^
so this rom i cannot use my sd card right? that's super bad for me!
-ARiCK- said:
so this rom i cannot use my sd card right? that's super bad for me!
Click to expand...
Click to collapse
There is no problem with the firmware for using the SD card
I keep getting the "This build is signed with public key" error notification every time at startup.
New build us up!
Quick changelog:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
Read notes in OP before installing!
Installed the latest build. Thank you. Great work . Everything is working very good. Battery life is extremely good. Got 7-8 hours full HD youtube playback on 4g. Go version is working very smoothly ( previously was using android 5.0 stock )
...
I also have another device 10or.E which has similar SoC SD430. Can you tell me step by step instructions. Kernel source is available. ( I read about building but did not clearly understand various terms like vendor etc... Tried to create initial .mk files for the board but errors at luch command itself )
Automated GSI flashing tool for Redmi Note 11 (spes)
I WON'T GIVE SUPPORT TO THOSE WHO FACE ISSUES BY NOT READING THE STEPS BELOW CAREFULLY!
I will get right into the topic here, find the answers to your questions below at near the end.
What this tool does:
1. Flash a GSI to your Dynamic partitioned Note 11
2. Patch your Vbmeta
3. Patch Product for magisk flashing
How to use this tool:
0. Flash a rom (stock rom, MIUI EU, AOSP, ...) - IMPORTANT
1. Download your GSI and the tool, extract them
2. Copy your GSI image to the tool's folder, rename the GSI to system.img if you are using Windows
3. Boot your phone to fastboot mode and plug it in
4. Run the "windows.bat" or "macos.sh" script based on your os
5. Wait until the process finishes, your phone will automatically reboot
Download: See attached file
Extras:
A ROM collection Telegram channel of mine, you can see screenshots of GSIs I booted on Note 11 by searching it there
The original post on Telegram
Credit:
kusti420 for Product file
AnhNotAnh (me) for the tool ofc
Main Q&A:
Q: What is a Generic System Image, GSI?
A: A GSI is a prebuilt system image that can be booted on devices that support Project Treble. In short, this System Image is a custom ROM but it uses your Vendor, Kernel from your previous/stock ROM.
Q: Okay, but why I would like to flash it on my Redmi Note 11?
A: As we have already known, MIUI does not perform exactly well in the recent years, especially on such a low end and underpowered phone. GSI helps us getting a taste of AOSP's cleanliness and smoothness before the developers finish making actual custom ROMs. This is a temporary solution, good enough to use, please don't think or complain if your GSI perform badly, since it is not a ROM or trying to be one either.
Q: Why do we need a dedicated tool and such time wasting thing to do? Can't you just flash it in a custom recovery?
A; From Android 10, devices with it come equipped with a new partition scheme, as known as Dynamic Partition. It helps speeding up OTA updates and make the partitions more flexible in size. But also creates a huge difficulty in flashing those GSI, that is why you cannot flash the image in a custom recovery.
Q: My terminal window freezes at a certain progress for too long! What should I do?
A: This case often happens with Windows users. Everything is quite complicated BTS, but the workaround is just spamming Enter key several times every minute or two.
Q: What if I want to install a GSI on top of another one? I already flashed one, do I need to restore my MIUI or AOSP rom to flash GSI?
A: It is not necessary, you can flash a new GSI on top. The tool will clear your previous GSI without erasing required stuff from ROM.
Q: My GSI does not boot, what should I do??
A: I highly suggest using GSIs based on Phh's work. Those are often called Phh GSIs. Secondly I would highly suggest against using "Ported GSIs", those are often based on Erfan or Xiaoxindada's GSI tool, they are a port from a different device's ROM instead of directly built from source like Phh. Here is a list of GSIs based on the man himself, Phh.
Q: Bro my phone just boot to TWRP and nothing happens, computer still waits for my device??
A: Like I said before, you can try spamming Enter key. It is also likely that your TWRP does not support Fastbootd (Fastboot Dynamic) environment, an easy workaround for this is using MIUI's boot (kernel) image, stock Fastbootd mode will be used.
Q: Which Android version can I flash??
A: You can flash corresponding or NEWER Android version GSI with the ROM you are coming from/installing GSI on top, you cannot flash a lower version one. For example, you can flash Android 11, 12, 12.1, 13, bla bla GSIs when coming from stock Android 11 MIUI ROM (Android 11 Vendor for people who understands)
Q: Can I use this tool on another device?
A: Yes, with proper bringup and changes in the tool for it to compatible with your device and it will work. But I will not be responsible for bricks, which I always won't xD
More questions and answers will be updated later.
Reserved.
Thanks for this Awesome Tool. Quiet Simple and efficient.
@PingVN This script works on Xiaomi redmi note 11 4g codename selene?
So, I was testing various and came across the guide for installing LineageOS17 GSI in the guides section. The way mentioned seems to be working
Procedure-
Install TWRP with latest security patches according to this guide https://forum.xda-developers.com/t/updated-september-2022-how-to-root-a7-2018.4488289/
Now, download Latest LineageOS19.1 vndklite-secure GSI.
Make sure to have backup of your internal storage, it might need to be wiped.
Install this GSI and right after that install Quantum Kernel 2.5 GSI version(for mtp) (check in attachments, it has Magisk 25.2 instead of 20.4 as mentioned in verbose) and then Magisk. After boot, check if MTP works in system, if it reboots, force reboot to TWRP and format Data and then reboot. That should fix it.
Without the kernel, seems to be stuck at logo.
No critcial bugs I have seen till now.
PS: always maintain a backup, I am not responsble if something goes wrong, like data loss.
Now, haven't tested it, but seems to me that any version other than vndklite-secure will have the 'camera in use' problem. So, try and let me know if that's the case.
Note - TWRP used is from a telegram group, which I couldn't share without the permission of owner. Search for it and you'll find it in A7 2018 telegram support group. TWRP version is 3.6.2.
Dmverity-disabler is to be flashed according to how to root guide only.
Tested on SM-A750F/DS (INS).
The reason why GSIs later than android 11 have a lockscreen bug is due to a vendor issue, in which Android 10
vendor of A7 2018 is not compatible with these GSI's. Apart from some Android 10 GSIs (like Havoc), lockscreen and everything works on these.
Abridged from https://forum.xda-developers.com/t/sm-a750fn-ds-unofficial-lineageos-17-1-gsi.4195065/
The img file for TWRP 3.6.2 is https://sourceforge.net/projects/batuhan-s-builds/files/TWRP/a7y18lte/recovery.img/download
To flash it as tar, use 7zip or any alternative to arcive as tar with default options, just make sure the image file remains as recovery.img, because it is present in this form on the phone partition. Tar can have any file name.
Source Telegram group for TWRP img file is @Exynos7885Updates
No sources have been specified by the developer.
For Indian SM-A750F, BL FILE IS INCLUDED
Note: For Camera in use error, always try to use vndklite versions of GSI, they have specific patch to work with some specific types of vendors. Currently looking for lockscreen fix, most probably, it is also a vendor related problem.
All of these are android 12 or 13 ones.
Possibility of usage:
Works Complete with magisk (including working Lockscreen): FLOS19.1(https://github.com/ChonDoit/treble_flos_patches/releases) [use (VNDK)lite secure ones, stability check needed]
no lockscreen : AncientOS S,ProtonAOSP 12.4.1, ProjectBlaze12.1, LineageOS19.1, LineageOS 20.0 TD-based VNDKLite(no bluetooth), pHH A12.1 GSI (secure), OctaviOS(vndklite), Evolution X 13 vndklite (no bluetooth), Miku UI 13 (no bluetooth), Pixel Experience Plus 13 (VNDK)lite, (no bluetooth),
with 'camera in use': ArrowOS 12.1, CherishOS, DotOS, Pixel Extended 13, Pixel OS 13
Don't boot at all: CorvusOS, BlissOS, Crdroid, ProjectAwaken 415, DerpFest A13
Android 13 GSI's have a problem with bluetooth that allow connection but no audio to go to headset.
Downloads links: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-List
where can you get twrp 3.6.2 for a750?
I have the latest stock firmware. Do I have to downgrade?
Did your phone has the latest firmware when you installed GSI ROM? Did you downgrade the firmware?
Also are banking apps like GPay work on GSI ROMS?
blazzer12 said:
I have the latest stock firmware. Do I have to downgrade?
Did your phone has the latest firmware when you installed GSI ROM? Did you downgrade the firmware?
Also are banking apps like GPay work on GSI ROMS?
Click to expand...
Click to collapse
No you don’t have to downgrade, just use the older 2020 Update BL file.
You can use UPI if you can securize the gsi and follow the steps of fixing safetynet. Search them
Thank you for the response.
Can you update the BL file file from 2020?
blazzer12 said:
Thank you for the response.
Can you update the BL file file from 2020?
Click to expand...
Click to collapse
No, updating with later BL's can cause issue with custom recoveries.
Does anyone have issues with mobile hotspot in GSIs. In OneUI roms, mobile hotspot works normally, but on GSIs, it does turn on and discoverable, but without internet access. USB tethering works fine on all roms though.
My phone is SM-A750GN
VorzaCu said:
Does anyone have issues with mobile hotspot in GSIs. In OneUI roms, mobile hotspot works normally, but on GSIs, it does turn on and discoverable, but without internet access. USB tethering works fine on all roms though.
My phone is SM-A750GN
Click to expand...
Click to collapse
My 2.4Ghz hotspot work fine. SM-A750F/DS INS
Do sms and calls work properly in FLOS 19.1?