[RECOVERY][ROOT] TWRP 3.1.1 for Lenovo Vibe K5, K5 Plus, Lemon 3 - Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is TWRP 3 for the Lenovo Vibe K5
Fully tested on the A6020a40 version (European Variant)
Confirmed compatible by the community for those variants:
A6020a40 (S415)
A6020a40 (S616 H39)
A6020a41
A6020l36
A6020l37
A6020a46 (2GB RAM)
A6020a46 (3GB RAM)
K32C36 (Lemon 3), see http://forum.xda-developers.com/showpost.php?p=67546530&postcount=140 for more informations
It should work when you flash it, but using it is still a try at your own risk procedure.
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
TWRP is now official, detailed information are available on the TWRP website.
Unnoficial download is up on the downloads tab.
Also mirror available on my website: moto.shreps.fr
Changelog:
twrp-k5-3.1.1-Oreo_shreps.img
- Based on Android 8.0 branch
twrp-k5-3.1.1_shreps.img
- Updated to TWRP 3.1
- Based on Android 7.1.2 branch
twrp-k5-3.1.0_shreps.img
- Updated to TWRP 3.1 (more infos here: https://www.xda-developers.com/twrp-v3-1-0-is-now-rolling-out-with-support-for-adb-backup-ab-ota-zips-and-more/)
twrp-k5-3.0.3-n4_shreps.img
- Back to original TWRP theme
- Compiled using official LineageOS env
- Using latest LineageOS Kernel
- Everything in sync with Android 7.1.1
twrp-k5-3.0.3-n3_shreps.img
- Added more partitions available for backup
twrp-k5-3.0.3-n2_shreps.img
- Support of A6020a40 S616 H39 variant (new DTB in Kernel)
twrp-k5-3.0.3-n1_shreps.img
- Fully rebased on AOSP Recovery 7.1
- TWRP bump to 3.0.3, with a lot of fixes
- Dark Material Theme
- F2FS fixes
- Removed cursor pointer
twrp-k5-3.0.2-r3_scritch007.img
- F2FS Support
- Encryption support (for both userdata and SD Card formatted as internal storage), for both EXT4 or F2FS
twrp-k5-3.0.2-r2_shreps.img
- Updated to custom Kernel compiled from sources, used in PAC & CM
twrp-k5-3.0.2-r1_shreps.img
- Initial Release, using Lenovo Stock Prebuilt Kernel
XDA:DevDB Information
[RECOVERY][ROOT] TWRP 3.1.1 for Lenovo Vibe K5, K5 Plus, Lemon 3, Tool/Utility for all devices (see above for details)
Contributors
Shreps
Source Code: https://github.com/boulzordev/android_device_lenovo_A6020
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-03-11
Current Beta Version: 3.0.2.0-r1
Beta Release Date: 2016-06-01
Created 2016-06-02
Last Updated 2017-11-28

Root & Tutorials
ROOT:
Flashing SuperSU ZIP v2.46 with TWRP is working fine to get Root on your device.
[TUTO] Steps to Install TWRP and make root in the K5 / K5 plus (for noobs) thx to @samuro625
Combo Key:
To reboot in Recovery with hardware keys:
- Power off your device
- Press and hold Vol+ + Vol- + Power until TWRP boots.
TWRP and Internal Memory:
The Lenovo ROM mounts internal memory directly from "/data/media".
But on TWRP, it uses the "emulated" mount option, meaning internal memory is mounted as "/data/media/0". It's also true for custom ROMs which are using the same built Kernel as TWRP.
That means:
- Every files generated by TWRP (like backups) are visible in the "0" directory when you're in OS Mode
- If you need to see files from your OS Internal Memory, you can open and browse manually "/data/media" or just simply connect your USB and copy files to your phone, TWRP will put them in the accessible Internal Memory (ie /data/media/0) and your files will be directly visible.

Firmwares & Backups
Stock Firmwares:
Firmware collection Thanks to @vache
Firmware collection, 2nd Mirror by @Shreps
TWRP Backups of Stock ROM:
A6020a40 - S027_160519_ROW
A6020l36 - S032_160401_LAS
Custom ROMS
PAC-ROM MM by @Shreps
CyanogenMod 13 by @scritch007
AOKP Nougat by @Shreps
CyanogenMod 14.1 by @scritch007

I just flashed your recovery and the SuperSU zip, and all worked perfect! You are the Master. You enlight us our life with this! Thanks you!
Enviado desde mi Lenovo A6020a46 mediante Tapatalk

help ta giving error here not loaded image must unlock

Thank You, Now the door is open for Custom ROMs [emoji2]

I tried on A601020l36 model and it failed to mount /cache partition, does it means that is not compatible?

noob guide needed!

!! AVOID ANY OTA UPDATES WHILE ON ROOT ACCESS !!
Unroot before OTA Update is recommended, you may encounter any false positive.
idk if TWRP too.
but i request Dev to reply few suggestion on this matter.
Thankyou....

bik95122 said:
!! AVOID ANY OTA UPDATES WHILE ON ROOT ACCESS !!
Unroot before OTA Update is recommended, you may encounter any false positive.
idk if TWRP too.
but i request Dev to reply few suggestion on this matter.
Thankyou....
Click to expand...
Click to collapse
That obvious , device should be Unrooted and should have STOCK recovery for OTA updates.

Shreps said:
Here is TWRP 3 for the Lenovo Vibe K5
Fully tested on the A6020a40 version (European Variant)
It should work when you flash it, but using it is still a try at your own risk procedure.
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the downloads tab.
XDA:DevDB Information
[RECOVERY][ROOT] TWRP 3.0.2.0 for Lenovo Vibe K5, Tool/Utility for all devices (see above for details)
Contributors
Shreps
Version Information
Status: Beta
Current Beta Version: 3.0.2.0-prebuilt
Beta Release Date: 2016-06-01
Created 2016-06-02
Last Updated 2016-06-02
Click to expand...
Click to collapse
Thank you so much for this bro! It was only because of your effort that we finally have root access on our phone. Can you now try compiling cyanogenmod 12.1 for our phone? It will be appreciated a lot. Thank you again

bittooshubham said:
Thank you so much for this bro! It was only because of your effort that we finally have root access on our phone. Can you now try compiling cyanogenmod 12.1 for our phone? It will be appreciated a lot. Thank you again
Click to expand...
Click to collapse
It's already in progress with others dev, but requires lot of works.
Be patient. Thx

Shreps said:
It's already in progress with others dev, but requires lot of works.
Be patient. Thx
Click to expand...
Click to collapse
Ok bro. Thanks again for the recovery

Hi, @Shreps
I wonder if you compiled this from source and if you will, can I learn how to compile it?
I'm currently on K32c36 and I've done pre-root stock firmware, but I wonder if I can compile a TWRP for Chinese user to backup and restore their data and system easily?

jwchen119 said:
Hi, @Shreps
I wonder if you compiled this from source and if you will, can I learn how to compile it?
I'm currently on K32c36 and I've done pre-root stock firmware, but I wonder if I can compile a TWRP for Chinese user to backup and restore their data and system easily?
Click to expand...
Click to collapse
I'm using a prebuilt Kernel if what you're asking.
Device tree for the device is in progress.

Shreps said:
I'm using a prebuilt Kernel if what you're asking.
Device tree for the device is in progress.
Click to expand...
Click to collapse
I wonder why this is working on locked bootloader devices?
I tried to flash on my K32c36(Chinese vibe k5 plus), but it failed because it detect bootloader is locked
Edit: Tried to flash this recovery via FlashFire, but failed. If this is also for Vibe K5 plus?

What about Lenovo K5 plus (indian units)
Shreps said:
It's already in progress with others dev, but requires lot of works.
Be patient. Thx
Click to expand...
Click to collapse
Hey,first of all, thanks a lot for your effort in making the TWRP recovery for the phone. I wish to know whether this works on the Indian retail units of K5 Plus (A6020a46)? Can anyone confirm on this?
Every single day I open xda forum to check the latest updates on K5 plus, and this is a huge news for the users! Thanks again mate

Steps to Install TWRP and make root in the K5 / K5 plus (for noobs)
axal said:
noob guide needed!
Click to expand...
Click to collapse
TWRP:
1. Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Connect the phone with the USB cable to the computer
5. Install the drivers that come on the CD cell partition.
6. Install "Minimal adb and FlashBoot" (if not already installed).
7. Download the TWRP recovery created by @Shreps, and copy it to the folder where abd is installed.
8. Run the Minimal adb and FlashBoot program or open the command line in the folder where the abd installed.
9. Run the command "adb devices" to confirm the connection. If you have never done before in this cell, the cell must confirm the adb connection.
10. When the adb confirm the connection, run the "adb reboot bootloader" Fastboot command to enable the functionality.
11. If you want a temporary recovery run the "fastboot boot TWRP-k5-3.0.2-r1_shreps.img" command. If you want to permanently run the "fastboot flash recovery TWRP-k5-3.0.2-r1_shreps.img" command.
12. You can now use the TWRP recovery in the K5 / K5 plus!
root:
1. Download the ZIP file SuperSU v2.46 and save it in the micro SD card.
2. Restart the phone in recovery mode: Turn off the phone, then turn it on while pressing the volume up button. a screen appears with various options and choose "recovery". When opening the recovery, select Install and locate the file you downloaded just now.
3. Confirm execution flashing, restart the phone and voila!

samuro625 said:
TWRP:
1. Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Connect the phone with the USB cable to the computer
5. Install the drivers that come on the CD cell partition.
6. Install "Minimal adb and FlashBoot" (if not already installed).
7. Download the TWRP recovery created by @Shreps, and copy it to the folder where abd is installed.
8. Run the Minimal adb and FlashBoot program or open the command line in the folder where the abd installed.
9. Run the command "adb devices" to confirm the connection. If you have never done before in this cell, the cell must confirm the adb connection.
10. When the adb confirm the connection, run the "adb reboot bootloader" Fastboot command to enable the functionality.
11. If you want a temporary recovery run the "fastboot boot TWRP-k5-3.0.2-r1_shreps.img" command. If you want to permanently run the "fastboot flash recovery TWRP-k5-3.0.2-r1_shreps.img" command.
12. You can now use the TWRP recovery in the K5 / K5 plus!
root:
1. Download the ZIP file SuperSU v2.46 and save it in the micro SD card.
2. Restart the phone in recovery mode: Turn off the phone, then turn it on while pressing the volume up button. a screen appears with various options and choose "recovery". When opening the recovery, select Install and locate the file you downloaded just now.
3. Confirm execution flashing, restart the phone and voila!
Click to expand...
Click to collapse
thank you for the help!

how to extract our stack rom? and flash when false positive while moding

Related

[RECOVERY][2019-06-09] UNOFFICIAL TWRP 3.3.1 for ASUS MeMO Pad 7 (ME176C(X))

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.
*
*/
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
This port of TWRP is built alongside the LineageOS ROM using the same kernel. It's the recommended recovery if you want to use the LineageOS ROM (or another ROM based on it).
Features
TWRP 3.3.1 (built in LineageOS 16.0 tree)
F2FS
USB OTG
Full disk encryption
Installation
Install ADB and Fastboot on your PC. There are guides available online for this, for example on the LineageOS wiki.
Make sure you are running Android Lollipop (5.0).
You need an unlocked bootloader. TWRP 3.3.1 requires me176c-bootstrap 0.3.0, included in me176c-boot 0.3.0. (The old "Intel" bootloader is no longer supported.)
Boot into Fastboot mode: Press Volume Down + Power to turn the tablet on and select Fastboot mode in the menu.
Flash the downloaded TWRP recovery image using Fastboot:
Code:
fastboot flash recovery twrp-recovery-3.3.1-20190609-UNOFFICIAL-me176c.img
Usage
Before you start flashing ROMs I recommend making a backup of your system, especially of the Factory and Vendor Data partition. These tend to get corrupted for unknown reasons, so it's good to have a backup.
Download
Recovery image: twrp-recovery-3.3.1-20190609-UNOFFICIAL-me176c.img
XDA:DevDB Information
Unofficial TWRP for ASUS MeMO Pad 7 (ME176C(X)), Tool/Utility for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev
Version Information
Status: Stable
Created 2018-02-05
Last Updated 2019-06-10
Version History
TWRP 3.3.1 (2019-06-09)
lambdadroid said:
Updates
TWRP 3.3.1
Linux (4.19.42 -> 4.19.49)
CPU Microcode (version 838)
Download
Recovery image: twrp-recovery-3.3.1-20190609-UNOFFICIAL-me176c.img
Click to expand...
Click to collapse
TWRP 3.3.0 (2019-05-12)
lambdadroid said:
New installation instructions
TWRP 3.3.0 requires me176c-bootstrap 0.3.0, included in me176c-boot 0.3.0. The old ("Intel") bootloader is no longer supported.
Major changes
Update to TWRP 3.3.0, build on LineageOS 16.0 (Android 9.0 Pie)
Update Linux kernel to 4.19 (4.14.72 -> 4.19.42)
Fixes
MTP
Download
Recovery image: twrp-recovery-3.3.0-20190512-UNOFFICIAL-me176c.img
Click to expand...
Click to collapse
TWRP 3.2.1 (2018-09-26)
lambdadroid said:
New features
Added Backup/Wipe functionality for "ASUS Product Demo (APD)" partiton.
This partition only contains some product images/videos about the tablet and is likely only relevant for the stock ROM (if at all). It has ~300 MB of space available so it works great as additional partition to place boot images/kernels on when using dualboot.
Other changes
Updates: Linux (4.14.42 -> 4.14.72)
Download
Recovery image: twrp-recovery-3.2.1-20180926-UNOFFICIAL-me176c.img
Click to expand...
Click to collapse
TWRP 3.2.1 (2018-05-22)
lambdadroid said:
New features
Added USB OTG support: You can now connect USB devices (e.g. USB keyboards or USB flash drives) to the tablet using USB OTG adapters.
Improvements
Minor power management improvements: Put more devices into suspend when not used (ported from LineageOS ROM)
Other changes
Updates: Linux (4.14.19 -> 4.14.42)
Updated CPU microcode to 836 (2018-01-10) - includes Spectre-related fixes
Download
Recovery image: twrp-recovery-3.2.1-20180522-UNOFFICIAL-me176c.img
Click to expand...
Click to collapse
TWRP 3.2.1 (2018-02-16)
lambdadroid said:
Announcements
TWRP is now available in a separate thread on XDA.
Major changes
Kernel upgrade to Linux 4.14: Experimental, might break things. More improvements and optimizations coming soon.
New features
Support for full disk encryption
Fixed USB mass storage mode for file transfer
Known problems
MTP support is disabled. However, given that file transfers were already broken before I don’t consider this as a regression. You can use ADB to transfer files.
Download
Recovery image: twrp-recovery-3.2.1-20180216-UNOFFICIAL-me176c.img
Click to expand...
Click to collapse
TWRP 3.2.1 (2018-02-16) now available
Announcements
TWRP is now available in a separate thread on XDA.
Major changes
Kernel upgrade to Linux 4.14: Experimental, might break things. More improvements and optimizations coming soon.
New features
Support for full disk encryption
Fixed USB mass storage mode for file transfer
Known problems
MTP support is disabled. However, given that file transfers were already broken before I don’t consider this as a regression. You can use ADB to transfer files.
Download
Recovery image: twrp-recovery-3.2.1-20180216-UNOFFICIAL-me176c.img
Is this compatible with the MeMO Pad 8? (ME181C)
ChazyTheBest said:
Is this compatible with the MeMO Pad 8? (ME181C)
Click to expand...
Click to collapse
No, the ME181C never got the Lollipop (and as such, the UEFI) update, so you're stuck with the stock ROM and tethered TWRP unfortunately.
TWRP 3.2.1 (2018-05-22) now available
New features
Added USB OTG support: You can now connect USB devices (e.g. USB keyboards or USB flash drives) to the tablet using USB OTG adapters.
Improvements
Minor power management improvements: Put more devices into suspend when not used (ported from LineageOS ROM)
Other changes
Updates: Linux (4.14.19 -> 4.14.42)
Updated CPU microcode to 836 (2018-01-10) - includes Spectre-related fixes
Download
Recovery image: twrp-recovery-3.2.1-20180522-UNOFFICIAL-me176c.img
Quick question: can this image be safely flashed with the 'Flashify' app? Thought I'd ask before I attempted it. ?
seamo123 said:
Quick question: can this image be safely flashed with the 'Flashify' app? Thought I'd ask before I attempted it. ?
Click to expand...
Click to collapse
Well, you still need the unlocked bootloader, which is probably something that app cannot do. Otherwise, I see no reason why it wouldn't work for flashing new recovery images. It's really hard to break this tablet completely so you can just try it.
Unfortunately every ROM I try to flash with this TWRP version results in error signal 7. Tried removing the assert command of the roms I try to flash (lineage and the custom rom) but no success.
I do have model K013
TWRP 3.2.1 (2018-09-26) now available
New features
Added Backup/Wipe functionality for "ASUS Product Demo (APD)" partiton.
This partition only contains some product images/videos about the tablet and is likely only relevant for the stock ROM (if at all). It has ~300 MB of space available so it works great as additional partition to place boot images/kernels on when using dualboot.
Other changes
Updates: Linux (4.14.42 -> 4.14.72)
Download
Recovery image: twrp-recovery-3.2.1-20180926-UNOFFICIAL-me176c.img
Twrp 3.3.0 (2019-05-12)
New installation instructions
TWRP 3.3.0 requires me176c-bootstrap 0.3.0, included in me176c-boot 0.3.0. The old ("Intel") bootloader is no longer supported.
Major changes
Update to TWRP 3.3.0, build on LineageOS 16.0 (Android 9.0 Pie)
Update Linux kernel to 4.19 (4.14.72 -> 4.19.42)
Fixes
MTP
Download
Recovery image: twrp-recovery-3.3.0-20190512-UNOFFICIAL-me176c.img
Does this work with the ME375CL (ATT Koox version) of this tablet Trying to root this pig and I'm having problems.
pwag said:
Does this work with the me176cl (ATT Koox version) of this tablet Trying to root this pig and I'm having problems.
Click to expand...
Click to collapse
You may be able to launch a temporary recovery session using https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
But considering https://forum.xda-developers.com/showpost.php?p=79554718&postcount=47, I'm guessing you do not have a ME176CL but a ME375CL (K00X). Unfortunately, those have nothing in common with the ME176C, it has a completely different GPU and SoC. TWRP/LineageOS won't work at all for it.
lambdadroid said:
You may be able to launch a temporary recovery session using https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
But considering https://forum.xda-developers.com/showpost.php?p=79554718&postcount=47, I'm guessing you do not have a ME176CL but a ME375CL (K00X). Unfortunately, those have nothing in common with the ME176C, it has a completely different GPU and SoC. TWRP/LineageOS won't work at all for it.
Click to expand...
Click to collapse
You are correct, that was my mistake. It's the Asus Memo Pad 7 LTE.
Trying to root this damn thing. I managed to get lolipop on it. So taht's some progress
Twrp 3.3.1 (2019-06-09)
Updates
TWRP 3.3.1
Linux (4.19.42 -> 4.19.49)
CPU Microcode (version 838)
Download
Recovery image: twrp-recovery-3.3.1-20190609-UNOFFICIAL-me176c.img
@ChazyTheBest This TWRP is compatible with k011 https://drive.google.com/open?id=1BiSPms0AsYsEis-sUvKQIX-siyagb-Dq
enable debugging option
connect your tab with a pc
start launcher.bat
ME572CL
PLease Help Instal it ASUS ME572CL, HOW I Can Do It? Thx
MrZlobnyj said:
PLease Help Instal it ASUS ME572CL, HOW I Can Do It? Thx
Click to expand...
Click to collapse
Unfortunately, this version of TWRP is not compatible with your ME572CL. Sorry!
An additional note for newcomers
Hi,
Thanks for this, it helped a lot as I'm completely new to this and really want to replace the old android 5.0 with something from this century.
One issue I kept bumping my head into was that after following the steps above, I could not get TWRP to work.
First installing adb on a PC, (ok)
then installing the new unlocked bootloader (ok)
and finally installing TWRP, (not ok)
after trying to boot into recovery it always ended up with "Error".
A cute little robot laying on its back with the message "error" ... No details beyond that.
Tried reflashing the bootloader and TWRP many times, including different versions of TWRP, but it would not matter.
No recovery for me.
But I'm a tad stubborn, so eventually it dawned on me to try and install the first TWRP from the list (3.2.1) and after that it booted into recovery OK and I was able to update to TWRP 3.3.3.
Now TWRP works OK (well it boots into TWRP, so I think it is now fine).
cheers!
Strangely I tried all 3.2.1 versions from that list but always got the error.
Chimay said:
Hi,
Thanks for this, it helped a lot as I'm completely new to this and really want to replace the old android 5.0 with something from this century.
One issue I kept bumping my head into was that after following the steps above, I could not get TWRP to work.
First installing adb on a PC, (ok)
then installing the new unlocked bootloader (ok)
and finally installing TWRP, (not ok)
after trying to boot into recovery it always ended up with "Error".
A cute little robot laying on its back with the message "error" ... No details beyond that.
Tried reflashing the bootloader and TWRP many times, including different versions of TWRP, but it would not matter.
No recovery for me.
But I'm a tad stubborn, so eventually it dawned on me to try and install the first TWRP from the list (3.2.1) and after that it booted into recovery OK and I was able to update to TWRP 3.3.3.
Now TWRP works OK (well it boots into TWRP, so I think it is now fine).
cheers!
Click to expand...
Click to collapse

12-19 - ViperExperience Beta 14 | Android 13 | November 2022 Security Patch |GSI

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ViperExperience 12L GSI for U12+
"Choose your flavor! - The next Generation Viper ROM"
Dear Community,
Venom ROMs takes the next big step for your HTC, as well as other Treble A/B devices out there! You want Android 11, but don't want to miss out on the hardware benefits of your HTC U12+? Or you want to enjoy all of your beloved HTC Apps on another OEM? Then we have the best of both worlds for you today (or very soon)! Decide for yourself between an Android Stock Experience, or an HTC Sense Experience by choosing between Pixel Launcher and HTC Sense 10 UI Launcher. On your HTC U12+ you can in addition continue to use your popular HTC features like HTC Edge Sense, HTC FaceUnlock and the HTC Camera!
We at Venom ROMs are using the AOSP GSI based on Android 11 to bring you the best HTC features paired with the latest Android AND Pixel experience from Android 10.
Thanks to @phhusson for his Treble experimentations repos, @JEANFRIVERA, @5m4r7ph0n36uru, @Captain_Throwback, @MassStash, @donmarkoni for all tests you did for me to make this ROM.
mikalovtch
Must have unlocked bootloader from htcdev.com or factory S-OFF
Download Viper Experience 11 GSI from Androidfilehost.com
Download „vbmeta_noverity.zip“ from Androidfilehost.com
Download latest TWRP from #2 post or Download latest PBRP from here: PBRP
Boot your Device in Bootloader Mode
Boot to TWRP or PBRP, using the following command:
Code:
fastboot boot nameoftwrpimage.img
Rename „vbmeta_noverity.zip“ to „update.zip“ and place it inside your adb/fastboot folder
Push „update.zip“ to your device, using the following command:
Code:
adb push update.zip /update.zip
Make sure you are on slot A on reboot page of TWRP or PBRP if not switch to slot A and fasboot boot twrp.img again
Flash „update.zip“ from recovery UI
Reboot to Download from recovery UI
Erase userdata and system using the following commands: (THIS WILL FORMAT INTERNAL STORAGE!)
Code:
fastboot erase userdata
and:
Code:
fastboot erase system
Flash Viper Experience 10 GSI, using the command:
Code:
fastboot flash system nameofimage.img
Rebootyour device, using the command
Code:
fastboot reboot
Setup and enjoy an mew ROM on your HTC U12+!
​
XDA:DevDB Information
12-04 - ViperExperience Beta 12 | Android 12L | April 2022 Security Patch |GSI , ROM for the HTC U12+
Contributors
mikalovtch, JEANRIVERA
Source Code: https://github.com/phhusson/treble_experimentations
ROM OS Version: Android 12L
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 Pie
Based On: AOSP HTC Sense
Version Information
Status: Beta
Beta Release Date: 2020-12-22
Created 2020-03-07
Last Updated 2020-12-22
​
Prerequisites
PIE_noverity_vbmeta_both_slots-TWP.zip: This zip patches the stock vbmeta for BOTH slots to ensure the device will boot after flashing the GSI. The zip in the OP only patches slot A, so you would have to ensure you are on slot A when flashing the system image. This zip allows either slot to be used. Thanks @The_Walking_Playground for posting the updated zip!
Fixes
UPDATE-BeyondStock™_U12+_Exodus_Vendor_Fixes-CPTB-signed.zip: This zip patches the vendor partition on U12+ and Exodus devices to fix Bluetooth streaming/headset compatibility, and enables exFAT support with the stock and BeyondStock™ kernels (NOTE: The exFAT portion of this fix is no longer needed, but has no negative side effects).
Patches
UPDATE-BeyondStock™_Header_Patch_U12+_Exodus-CPTB-signed.zip: This zip patches the boot.img header of the installed kernel so that decryption will work in permanently installed TWRP. This zip should be used if you're using a custom kernel that doesn't require patching for touch.
UPDATE_BeyondStock™_U12+_Exodus_Remove_Forced_Encryption_CPTB_signed.zip: This zip disables forced encryption on the device so that it doesn't automatically get encrypted after Formatting Data in TWRP.
Custom Recovery
Official TWRP for U12+: This is the recommended TWRP version to use with the ROM, with full Android 11/12 decryption support.
Kernels
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus-signed.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP older than 3.4.0, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus_TWRP_3_4_0_CPTB.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP 3.4.0 (and higher), and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
[MANUAL] Fix CTS Profile Mismatch
Initial situation: most GSIs are rooted to a certain extent. This also applies to the AOSP GSI, which is the basis of our ViperExerience ROM.
Precondition: To correct the CTS mismatch, it is necessary that Magisk is installed.
If the precondition is fulfilled, proceed as follows:
Install the Magisk modules "Busybox" from Osmosis, and "MagiskHide Propst Config" from Didgeridoohan
After a device restart, open a Terminal App on your HTC U12+ and go through the following steps
Request root privileges by typing
Code:
su
Start the Props module by typing
Code:
props
Type
Code:
1
to set a new fingerprint for the device
Follow the instructions in order by selecting
Code:
f
and
Code:
7
(for HTC).
finally type
Code:
4
(for U12+ Pie).
How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from here: https://github.com/CaptainThrowback/android_device_htc_ime/releases
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either
4. Download BeyondStock™-Kernel This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
5a. If you want to be rooted flash the magisk.zip
5b. If you don't want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
Thanks to @JEANRIVERA
reserved
reserved3
reserved4
reserved5
reserved6
Support
Hi users, I was a noob once too, believe it or not I had questions & stupid questions too but I was never afraid to ask, in my way to be part of this amazing team I have known all kind of Devs, with different levels of friendliness , but being honest in some way or another I have learned from all of them a little something, Now I want to give back to the community as much as I can, I am no Dev, but I do know a trick or two, if I don't know the answer to your questions, I will try my best to get an answer for you from the Team.
The instructions in the OP have been updated for better understanding and corrected some points, if anyone has tried unsuccessfully to flash this ROM please follow the updated instructions, if anyone have trouble or not booting device please feel free to ask, I will try to guide anyone as much as I can and as friendly as possible. I see there is 73 downloads on AFH of the ROM but only few users reported their experience here, maybe if you are afraid to ask, don't be, if you navigate through the thread you will see only friendly responses, and I will try my best to keep it that way, don't be afraid to tag me for support
And I'll take this one, just for the kicks.
I am running android 8 with viper 2.0 and i tried to update to this but ADB says that my file system is read-only. What is the recommended course of action?
Code:
adb: error: failed to copy 'update.zip' to '/update.zip': couldn't create file: Read-only file system
I read elsewhere that 'adb root' would be needed but i figured it would be better to ask here instead of following some random post about a somewhat similar situation.
First off: don't install this ROM on Android 8 firmware. It's an Android 10 GSI and all development an testing has been done on the latest EMEA firmware.
So the way to go from ViperU12+ would be to go back to full stock unsung a RUU and upgrade to Android Pie. This is to make sure you start from the correct base and environment. Then boot the device and copy the vbmeta zip onto /sdcard. Then reboot to bootloader and boot to TWRP, and follow the instructions from post #1 to the point.
Use the latest TWRP from @Captain_Throwback, found here: https://github.com/CaptainThrowback/android_device_htc_ime/releases/tag/3.3.1-2
Sent from my Pixel 4 XL using XDA Labs
it should be: 9 Reboot to Download from TWRP UI not
9 Reboot to bootloader from TWRP UI
on Production Units in Bootloader you get an error:
FAILED (remote: Erase is not allowed on PRODUCTION device)
This ROM is been running quite fantastic for me, I am so excited to help test and get this released for everybody to use! Can't believe we have Android 10 on this u12 plus Beast, it's so amazing! LOL thank you so much @mikalovtch, @JEANRIVERA, @Captain_Throwback, &
Sent from my HTC U12+ using Tapatalk
Oh man, you`ve done brilliant work:highfive::good:
it is almost perfect, butter smooth and fully functional except few bugs.
some issues are:
1. time and date automatically reset to 2020.03.07 4:47 after reboot, which can be quite annoying.
2. edgesense squeeze gesture feedback is weird. it`s not like the feedback of power btn but vibrating.
3. edgesense setting does not show in the settings.
some Pro tips:
1. flash system.img via twrp or via usb under DOWNLOAD mode. you can not flash it under BOOTLOADER mode.
2. you can access edgesense settings by this method:
goto Setting.Apps, show all system Apps and find out edgesense service app. In the detail screen(where you can clear the cache and force stop, idk the exact term), tap Advanced, Additional settings in the app.
3.kirisakura kernel tested, all good.
btw i use China version u12+, hope this will help you.
Thanks you bro!
issue has been fixed
JEANRIVERA said:
without the vbmeta.zip the ROM will not boot at all, the instructions fail to specify you must be on slot A to flash the vbmeta.zip and ROM, instructions will be updated soon, if you are on slot B another vbmeta zip should be used.
Click to expand...
Click to collapse
thank you! but i still boot without flashing vbmeta.
neoncloud4399 said:
thank you! but i still boot without flashing vbmeta.
Click to expand...
Click to collapse
is your device S-OFF? that would be the only possible reason it boots
JEANRIVERA said:
is your device S-OFF? that would be the only possible reason it boots
Click to expand...
Click to collapse
no, it still s-on.
i followed this procedure:
clear system, flash system, clear userdata under twrp
flash vbmeta.zip under twrp By sideload
reboot, failed to boot, show warning messages.
run fastboot oem rebootRUU to ruu flash mode and downgrade to 1.21
fastboot erase persist
boot to 1.21 China then upgrade to PIE.
boot to DOWNLOAD, erase system, userdata, flash system both system_a and system_b and it boots.

[ROM][Official] Kali NetHunter for the Nokia 6.1 LOS17.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE THE LATEST VERSION CAN BE FOUND HERE https://forum.xda-developers.com/t/rom-official-kali-nethunter-for-the-nokia-6-1-los18-1.4330657/​
I present to you: Kali NetHunter for the Nokia 6.1 LOS17.1
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
~ Prerequisites ~
- Lineage 17.1 March build - https://androidfilehost.com/?fid=4349826312261740562
- TWRP 3.3.1 unofficial - https://www.androidfilehost.com/?fid=8889791610682920237
- Universal Force Encryption Disabler for Treble - https://www.androidfilehost.com/?fid=8889791610682920239
- Magisk – https://forum.xda-developers.com/apps/magisk
- Unlocked bootloader by Hikari Calyx - https://t.me/HikariCalyxFIH
- Stock Pie, as sometimes Q doesn't let you boot into TWRP (can be downgraded using OSTLA after unlocked bootloader) - https://fih-firmware.hikaricalyx.com/hmd_en.html - Download the appropriate region
- OSTLA - https://www.androidfilehost.com/?fid=8889791610682920445
- Community Vendor - https://androidfilehost.com/?fid=4349826312261717564
~~ Downloads ~~
- NetHunter installer: https://www.androidfilehost.com/?fid=8889791610682934616
~~ How to Install ~~
Assuming you have unlocked bootloader, stock Pie.
To install LineageOS with encryption disabled, follow these steps:
- Copy Lineage, Vendor, Gapps, NetHunter, ForceEncryption Disabler, Magisk onto OTG USB medium
- Boot into TWRP linked above using the 'fastboot boot' command
- Wipe system, cache partitions and format data as well
- Reboot to bootloader
- Boot into TWRP again
- Install LineageOS, Community Vendor - on both slots (Reboot to bootloader, fastboot --set-active command to change slots, reboot into bootloader and boot into TWRP again - wipe system, cache on the second slot, install Lineage, Vendor. Then reboot to bootloader to switch back to active slot with fastboot command)
- Boot into TWRP again via fastboot.
- Install TWRP recovery ramdisk (in advanced menu), format data, reboot into recovery you installed.
- Flash Gapps, Disabler, Magisk. Wipe cache, and reboot into system
- Do initial setup
- Reboot to TWRP
- Flash NetHunter
- Flash Magisk
- Reboot into system, setup Nethunter and do a final reboot
- To upgrade to full Kali fs, do
Code:
apt-get update && apt-get install kali-linux-nethunter -y
~~~ Notes & Updates ~~~
RNDIS is also working (didn't work on devices with kernel above 4.x), thanks to @Thiviyan
Credits: The Offensive Security Team and the NetHunter community
Android Version: 10.0
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the Nokia 6.1
Contributors
@yesimxev
For LineageOS: @theimpulson
For bootloader unlock and general Nokia support: @hikari_calyx
Huge thanks for both as this project would not be possible without them!
Source Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/yesimxev/android_kernel_nokia_sdm660
Follow me on Twitter!
Reserved
Reserved #2
Cool!
I just noticed that yesterday
i can install this on pixel experience rom ? if i built my own kernel right?
something like
install rom pixel
install custom kernel and magisk
install nethunter pl2
would it work?
Tsuragi said:
i can install this on pixel experience rom ? if i built my own kernel right?
something like
install rom pixel
install custom kernel and magisk
install nethunter pl2
would it work?
Click to expand...
Click to collapse
Good point to test out. Make sure you have encryption disabled otherwise it can cause issues. Just flash your Pixel rom instead of my Linage step. Kernel should be fine as long as it's Android 10. Please let me know how was it.
Hello,
Is there a way to unlock the bootloader on a TA-1043 running android 10?
Regards,
SHUHADAKU
SHUHADAKU said:
Hello,
Is there a way to unlock the bootloader on a TA-1043 running android 10?
Regards,
SHUHADAKU
Click to expand...
Click to collapse
Please refer to https://t.me/HikariCalyxFIH @hikari_calyx
now we have badusb in kernel 4.X phone yeahhhhhh...
Hello,
Does this guide work for Nokia 6.1 plus TA-1116?
Thank,
rubick0x100 said:
Hello,
Does this guide work for Nokia 6.1 plus TA-1116?
Thank,
Click to expand...
Click to collapse
Unfortunately not, but support for that could come soon as it's similar. I'm too busy right now so it could be a few months unless you want to prepare same as above, but use generic arm64 nethunter zip from next release. (sometime in November) and I might be able to send you a test kernel by that time
yesimxev said:
- Copy Lineage, Vendor, Gapps, NetHunter, ForceEncryption Disabler, Magisk onto OTG USB medium
Click to expand...
Click to collapse
How are you using a USB thumb drive while also connecting for fastboot?
kazumawasd said:
How are you using a USB thumb drive while also connecting for fastboot?
Click to expand...
Click to collapse
You unplug the USB drive and plug into PC for fastboot commands :highfive:
yesimxev said:
You unplug the USB drive and plug into PC for fastboot commands :highfive:
Click to expand...
Click to collapse
Haha thanks, easy enough
So my bootloader is unlocked and I used the recommended OSTLA to flash "PL2-351F-0-00WW-B04.full.zip" from "https://fih-firmware.hikaricalyx.com/hmd_en.html". I used "Normal Download" and "Check System AP Status" default options. Once flashed, I got a factory reset menu, selected yes and was able to boot into the stock android 9 - March 1, 2019 security patch level. Now when trying to boot into TWRP to really get started I get stuck at the TWRP splash screen. Can you provide any guidance on getting booted into TWRP properly?
kazumawasd said:
Haha thanks, easy enough
So my bootloader is unlocked and I used the recommended OSTLA to flash "PL2-351F-0-00WW-B04.full.zip" from "https://fih-firmware.hikaricalyx.com/hmd_en.html". I used "Normal Download" and "Check System AP Status" default options. Once flashed, I got a factory reset menu, selected yes and was able to boot into the stock android 9 - March 1, 2019 security patch level. Now when trying to boot into TWRP to really get started I get stuck at the TWRP splash screen. Can you provide any guidance on getting booted into TWRP properly?
Click to expand...
Click to collapse
Are you booting into TWRP via 'fastboot boot'? And not trying to flash rightaway yes?
yesimxev said:
Are you booting into TWRP via 'fastboot boot'? And not trying to flash rightaway yes?
Click to expand...
Click to collapse
Yes, I'm not trying to flash right away.
I'm doing this:
Code:
fastboot reboot-bootloader
fastboot boot twrp-3.3.1-PL2.img
Then it just gets stuck at the TWRP splash screen
kazumawasd said:
Yes, I'm not trying to flash right away.
I'm doing this:
Code:
fastboot reboot-bootloader
fastboot boot twrp-3.3.1-PL2.img
Then it just gets stuck at the TWRP splash screen
Click to expand...
Click to collapse
Strange, can you try to flash the oreo stock and then repeat the process please?
yesimxev said:
Strange, can you try to flash the oreo stock and then repeat the process please?
Click to expand...
Click to collapse
I ended up fixing it by running this before booting into TWRP:
Code:
fastboot erase userdata
But unfortunately it looks like the android 9 flash I did locked my bootloader on slot b
kazumawasd said:
I ended up fixing it by running this before booting into TWRP:
Code:
fastboot erase userdata
But unfortunately it looks like the android 9 flash I did locked my bootloader on slot b
Click to expand...
Click to collapse
Simply set A as active with
Code:
fastboot --set-active a
. Btw TWRP should boot without that, as you would format data later 2x (before and after LOS17 flashing)
Waiting for my Nokia to get through customs... It was a cheap replacement for my overly abused Mi 9T. I was wondering if we get monitor mode on the internal with this latest release. I loved that the Xiaomi didn't need an external... Keeping my fingers crossed.

[ROM][UNOFFICIAL][G770F/FD][11] LineageOS 18.1 S10 Lite

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the changelog for a full list of changes & features.
DISCLAIMER: LineageOS Legal
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Notes:
VoLTE, IMS, and other samsung specific stock rom features wont be ported or fixed.
Download:
r5q 18.1
r5q recovery
Support Group: Telegram
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
I do this kind of stuff on my free time. If you like my work, please consider buying me a drink (donation) by clicking the link below.
Paypal
Archive link: Github Releases
Kernel source: Github
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
I think i had to mention this, booting recovery now requires you to have usb plugged in while you're punching the recovery combo to enter recovery.
Also, i've fixed the lineage recovery yesterday, sorry for the hassle.
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Ok, I found the instructions for patching boot.img:
[HOW-TO-ROOT] [G770F/DS] Galaxy S10 Lite International Model
Models: SM-G770F or SM-G770F/DS Frequently used key combinations keys: FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button. DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via...
forum.xda-developers.com
darth.cabs said:
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
Click to expand...
Click to collapse
Got new account nice to be here too..
Vaughnn said:
我想我不得不提一下,启动恢复现在需要您在插入恢复组合以进入恢复时插入USB。
另外,我昨天修复了血统恢复,很抱歉给您带来麻烦。
Click to expand...
Click to collapse
Vaughnn said:
LineageOS是免费的,社区构建的Android 11售后固件发行版,旨在提高设备的现有Android的性能和可靠性。
LineageOS基于Android开源项目,并得到了Android社区中许多人的额外贡献。无需安装任何Google应用程序即可使用它。下面链接的是一个来自另一个Android项目的程序包,这些程序可以还原Google部件。LineageOS仍然包含各种特定于硬件的代码,无论如何它们也正在缓慢地开源。
LineageOS的所有源代码都在LineageOS GitHub中提供。如果您想为LineageOS做出贡献,请访问Gerrit Code Review。您还可以查看更改日志以获取更改和功能的完整列表。
要求: Oneui 3.0(DTL1)。
指示:
Flash Lineage Recovery或从下面的下载文件中获取文件,然后使用此处的说明对其进行刷新
格式化数据/恢复出厂设置
刷新构建(使用adb侧载,或使用mtp将文件推送到sdcard)
重启
笔记:
请勿使GAPP闪烁,这包括最小的GAPP。我将发布带有gapps的版本,直到gapps程序包足够适合我的需求为止。
VoLTE,IMS和其他三星特定的rom功能将不会移植或修复。
在使用指纹之后或之前,屏幕有时会闪烁,这只是免责声明,如果有人使用此版本的癫痫病患者,我将不承担任何责任
错误:
接近度(可能无法在某些应用程序上运行)
5Ghz热点
下载:
r5q 18.1
r5q恢复
支持小组: 电报
报告错误
如果您正在运行自定义内核或已安装Xposed,请不要报告错误
问题发生后立即拿起logcat。(除非您知道自己在做什么,否则请至少包括日志的几页,而不仅仅是最后几行。)
如果是随机重新引导,请抓住/ proc / last_kmsg。(除非您在重新启动之前就可以获取它,否则不要费心获取一个logcat。重新启动之后的logcat是没有用的)
如果从根shell运行“ setenforce 0”后问题消失了,请抓住/data/misc/audit/audit.log
Code:
您的-
LineageOS版本:
LineageOS下载网址:
Gapps版本:
你是否 -
擦拭:
使用钛备份还原:
出现问题后重新启动:
你正在用吗 -
任务杀手:
非库存内核:
其他修改:
根据需要提供任何其他信息(观察/问题发生的频率/它工作的最新版本/等):[/ CODE]
[B]我会在业余时间做这种事情。如果您喜欢我的工作,请考虑通过单击下面的链接为我买一杯饮料(捐赠)。[/B]
[URL='https://www.paypal.com/donate/?cmd=_donations&[email protected]']贝宝[/URL]
存档链接:[URL='https://github.com/mainey/release-r5q/releases']Github版本[/URL]
内核来源:[URL='https://github.com/mainey/android_kernel_samsung_r5q']Github[/URL]
[/QUOTE]
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
[/QUOTE]
Click to expand...
Click to collapse
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
Rom is fine. There's simply not much to tell about. It runs runs runs. No problems at all. Twrp or lineageos recovery....whatever. all good
Would it be possible to have a version without Gapps?
Vaughnn said:
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
Click to expand...
Click to collapse
Is your lineageos 19 beta google-free?
Hi. Can anyone confirm if [BETA] Lineage 19 20220307 Beta 4 is stable enough as daily ROM?
Banking apps work? OIS+EIS during video recording?
Thank you.
Vaughnn said:
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Click to expand...
Click to collapse
First of all thank you for your time and energy.
I'm having problem flashing latest beta 4.
I'm coming android 11 Oneui 3.1. My device is was rooted with unlocked bootloader.
1. I've flashed the lineage recovery via odin (Including vbmeta_disable) and upon reboot (it needed 2 boots to get into recovery) I chose factory reset of the device.
2. I've enabled developer options and saw my bootloader was unlocked.
3. I've booted into recovery
4. I've flashed the lienage os 19 beta 4 with google apps
I keep getting status error 2 and installation is aborted :O(

General [SHARED] LineageOS 19.1 | OFFICIAL | MicroG + MIUI Camera [23/04/16]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First I'm not the developper of this rom and just share it here
credits go to @NeoArian
Be aware that it's a provisory thread and the dev will create his own when he decide ....
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
​@NeoArian made a flashable zip for having MIUI camera on LOS​Here is the camera..I repeat Im not the creator of this file, you must thank @NeoArian for this and his perfect rom​
LineageOS 19.1 for Xiaomi M2101K9G (renoir)
Build date: 2022-11-01
Security patch: 2022-10-05
Variant: GMS
Changelog (https://www.lineageoslog.com/19.1/renoir)
Download
lineage-19.1 (https://download.lineageos.org/devices/renoir/builds)
lineage-19.1 MicroG (https://download.lineage.microg.org/renoir/renoir/)
⛭ GitHub release / additional files
Build date: 2022-09-27
Spoiler
Security patch: 2022-09-05
Variant: VANILLA
changelog
Download
lineage-19.1 (https://github.com/arian-ota/ota/re...f/lineage-19.1-20220927-UNOFFICIAL-renoir.zip)
⛭ GitHub release / additional files (https://github.com/arian-ota/ota/releases/tag/19.1-renoir-3746432f)
SHA-256 checksum
3746432fe6134e94aabfb1efad645aec882da1ddba48b39c70b5548a0abd3120
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++===========================================================================================
Build date: 2022-09-25
Security patch: 2022-09-05
Variant: GMS
changelog
Download
lineage-19.1 (https://github.com/arian-ota/ota/re...neage-19.1-20220925-UNOFFICIAL-GMS-renoir.zip)
⛭ GitHub release / additional files (https://github.com/arian-ota/ota/releases/tag/19.1-renoir_gms-4eab216d)
SHA-256 checksum
4eab216d294330b851005b8166d3e356e41e72729831b696d915f026027133e6
Spoiler: Earlier versions
Build date: 2022-08-29
Security patch: 2022-08-05
Variant: GMS
Changelog
Download
Lineage 19.1
⛭ Github release/additional files
SHA-256 checksum
b5b38148be07ed66d614dfada0acc2587420f2a763c36fd6d8647db6eb0c903f
Credits and thanks to @NeoArian
Installation Instructions:
Lineage Os Installation:
1- Install LOS Recovery: With the phone in FASTBOOT mode in the Platform-tool folder and the necessary files, open the CMD
2- Next we place in the window: fastboot flash boot_ab boot.img and then fastboot flash vendor_boot_ab vendor_boot.img to finish fastboot reboot recovery
3- The cell phone will restart in recovery mode with LOS recovery already installed (it is managed with the volume and power keys)
4- Perform Format Data (do not restart again)
5- Give Apply Update and then Apply Update from SDcard1 and look for the ROM
6- Then Reboot System Now (WILL INITIATE THE ROM)
7- Force restart in recovery to install Gapps (PICO Recommended)
8- Apply Update, Apply update from SDcard1 choose the gapps
9 Reboot System Now and enjoy XD
ALTERNATIVE WAY OF FLASHING THE ROM see post 2
ALTERNATIVE WAY OF FLASHING THE ROM
For those like me who have issue with flashing this rom here i what I do to bypass recovery issue..
after flash boot+vendor and start on LOS recovery and format data, I click update but I haven' apply update from sdcard1 but justapply from ADB..in advanced settings, there isn't such option....so I installed with ADB sideload
that what I do, and after 1 error I tried again and got error when I command adb reboot that system was not installed but I'm now on your rom....only issue is with my sdcard not recognized...have to backup on pc, format and recopy back, but certainly error on my side when I flash back miui rom.......
Install Custom ROM with ADB sideload
What is Android Debug Bridge?
ADB is a command-line tool included in the Android SDK development kit. It is used to communicate with any device that runs the Android operating system. You can use the ADB commands to perform various operations on your Android device.
With the help of the Android Debug bridge, you can install custom ROMs, mods, GApps, backup Android, flash official stock firmware, and install Android apps. Besides, you can also use ADB to uninstall bloatware without Root, downgrade an app, etc.
What is ADB Sideload?
ADB sideload, a command that transfer and install a zip file on an Android device from the PC. This command is handy for a custom ROM developer to push and install any installation zip file directly on a device.
The sideload feature was introduced with the Android Jelly bean recovery. Most importantly, this sideload mode requires a TWRP recovery version 2.3 or higher. Besides, it is also essential to install the latest ADB binaries on your PC.
How to Flash Custom ROM using ADB and Fastboot
Are you ready to use ADB and Fastboot for flashing custom firmware on your Android phone? Then let’s get started.
Warning
Ensure to install the right custom ROM on your Android phone. Do NOT proceed if the firmware is incompatible with your phone model number.
Requirements
A Windows PC and a standard USB cable.
Charge your device to a minimum of 50%.
Install mobile USB drivers on your computer.
Enable USB Debugging mode from your device settings.
Also, enable the OEM unlocking and Advance reboot mode.
Moreover, unlock your device bootloader.
Install TWRP 2.3 or higher on your Android device.
(Optional) Temporarily disable antivirus and firewall on your PC.
Steps to Install Custom ROM using ADB Sideload
Follow these step-by-step instructions to sideload the zip file on your Android phone.
1. Download Custom ROM
At first, download the mobile-specific Android custom ROM on your PC.
Ensure that the ROM file is in zip format.
Also, download the correct firmware that is compatible with your device’s model number.
2. Install ADB and Fastboot drivers
Download and install the latest ADB drivers on your computer.
Make sure that the ADB version is 1.0.29 or higher.
3. Transfer Custom ROM to ADB folder
Copy the downloaded custom ROM and paste it into the ADB folder.
The folder default location will be C:\Program Files\Minimal ADB and Fastboot.
4. Boot Android phone into Recovery mode
Switch off your Android phone.
Now, restart it into recovery mode.
Every device has different methods to boot into recovery.
You can either Google it or use the Recovery reboot app from Play Store.
5. Set the device into ADB sideload mode
As soon as you enter the recovery mode, click on the Advanced button.
On the next screen, click on the ADB sideload option.
6. Connect Android phone to PC
Now, connect your Android device to the computer using a USB cable.
Keep the device as it is in sideload mode.
After a successful connection, tick the Wipe Davik Cache and Wipe Cache options.
Then, swipe right on your device to start sideload.
7. Launch CMD window
Open the ADB folder, hold your keyboard’s Shift button, and right-click.
From the list of options, tap on the Open command window here option.
This will open the command prompt window on your PC.
8. Confirm the ADB connection
Furthermore, type the below command in the cmd window and press the enter key:
adb devices
You’ll see some random numbers with a ‘List of devices attached’ message.
This will confirm that your Android device is successfully connected to the PC.
9. Flash Custom ROM with ADB sideload command
To flash the custom ROM zip package file, enter the below command in the CMD:
adb sideload LineageOS18.zip
Make sure to type the exact name of the custom ROM file.
Also, don’t forget to add the zip extension at the end.
Here, I’m flashing LineageOS18 custom ROM.
Finally, hit the enter key to begin the ROM flashing process.
10. Reboot Android phone
On the installation finishes, your device will show a message saying, ‘ADB sideload complete.’
Tap on the Reboot System option to restart your device.
or those who don't know how to use ADB sideload here is a tuto you can read
How to Flash Custom ROM using ADB sideload [Easy Steps] ​
Flash Custom ROM zip file with ADB and Fastboot commands on any Android phone. Install Custom Firmware without TWRP recovery using CMD.
How to use adb
Attachments​
Mind sharing the device, kernel and vendor trees used to build this ROM? I want to build and try it out myself. Thank you and @NeoArian for the hard work btw.
calputer said:
Mind sharing the device, kernel and vendor trees used to build this ROM? I want to build and try it out myself. Thank you and @NeoArian for the hard work btw.
Click to expand...
Click to collapse
The trees and kernel are available on GitHub.com/renoir-development
The vendor repository can be extracted with extract-files.sh from the renoir tree. To do so, download the lineage zip, then cd to device/xiaomi/renoir and run "./extract-files.sh /path/to/lineage.zip".
I don't see a vendor_boot.img in the github release page but there's a dtbo.img file. What do we do with this file? Also I don't think TWRP for renoir is working with Android 12 am I right?
Sa
calputer said:
I don't see a vendor_boot.img in the github release page but there's a dtbo.img file. What do we do with this file? Also I don't think TWRP for renoir is working with Android 12 am I right?
Click to expand...
Click to collapse
Same here. Where can i download boot_ab boot.img and vendor_boot_ab vendor_boot.img ?
I tested the rom and managed to install. attached image with the command needed. It work after I tried to puzzle the correct way to install. PS (if don't work try install LineageOS 18 as base to start, this is how I done). [after <<fastboot reboot recovery>> command, your smartphone will go in recovery mode from that -reset data- and -apply update-].
source of files used <<github.com/ arian-ota/ota/releases/tag/19.1-renoir_gms-b5b38148>>
wanna ask to dev or expert: if this change about use of -dtbo- instead -vendor_boot- is android 12 new design fault (google)?
PS: the devs have some grudge against users for lacking info about rom installation? This is my first LineageOS custom rom, kinda hard to install.
So I flashed the rom using files from the git release and vendor_boot.img from MIUI13. And one problem is that the wallpaper preference in setting is not working. So I just decided to go back to MIUI 13 global and somehow twitter and reddit scrolling is smooth and does not stutter anymore. Interesting cause it was stuttering on every AOSP I've tried.
calputer said:
So I flashed the rom using files from the git release and vendor_boot.img from MIUI13. And one problem is that the wallpaper preference in setting is not working. So I just decided to go back to MIUI 13 global and somehow twitter and reddit scrolling is smooth and does not stutter anymore. Interesting cause it was stuttering on every AOSP I've tried.
Click to expand...
Click to collapse
vendor_boot from MIUI13 OTA or FASTBOOT? for odd reason my LIneage os 19 work even without installing it
Testing the ROM, it cannot read sd card in exfat, ntfs or ext3 file system, it always ask me to format in fat32. there's a workaroud? fat32 limit is annoying, and pretty sure original MIUI have support for exfat.
Ranball said:
vendor_boot from MIUI13 OTA or FASTBOOT? for odd reason my LIneage os 19 work even without installing it
Click to expand...
Click to collapse
From Fastboot zip. And the vendor_boot.img from Pixel Experience site also has the same size (98,304 KB), so I figured I could use it without any modifications.
Any news about update??
jellybean 4.1 said:
Any news about update??
Click to expand...
Click to collapse
no, not yet
I bought my mom a new Xiaomi Redmi Note 11 lite 5G. Before she has used the Xiaomi Redmi Note 8T, which now will be dedicated for banking apps or as Navigation device.
The Xiaomi RN 8T had some issues on a custom Rom, especially with the microphone on some Apps.
Now i consider to let the Xiaomi RN 11L on Stock ROM, to not disturb her phone experience. I'm a fan of the work of all the Custom ROM Creators and use it on all my own devices. But which one of the Custom ROMs does work properly and would you prefer, for daily use and a bigger amount of Gapps?
MonoPro9 said:
I bought my mom a new Xiaomi Redmi Note 11 lite 5G. Before she has used the Xiaomi Redmi Note 8T, which now will be dedicated for banking apps or as Navigation device.
The Xiaomi RN 8T had some issues on a custom Rom, especially with the microphone on some Apps.
Now i consider to let the Xiaomi RN 11L on Stock ROM, to not disturb her phone experience. I'm a fan of the work of all the Custom ROM Creators and use it on all my own devices. But which one of the Custom ROMs does work properly and would you prefer, for daily use and a bigger amount of Gapps?
Click to expand...
Click to collapse
Pixel Experience best stability for now, then this Lineage 19.1.
razor_1911 said:
Pixel Experience best stability for now, then this Lineage 19.1.
Click to expand...
Click to collapse
Thank you for the conclusion.
She want to stay with MIUI at least till the guarantee.
The Redmi Note 8T will be my next Toy
razor_1911 said:
Pixel Experience best stability for now, then this Lineage 19.1.
Click to expand...
Click to collapse
For renoir is the rom discontinued =(
@NeoArian made an update of his LOS with Gapps and Vanilla version.....I have flashed both and its working great....
thanks to him

Categories

Resources