Database Info

What ROM to use?

I'm pretty happy with stock 5.0 but I miss OnmiRecents from OmniRom and xposed modules.
On my Note 3 I loved Temasek's CM12 because it included both of these, what ROM would you recommend if I want the bare minimum that supports Onmirecents and Xposed?
I tried useing xposed on stock without any FC's unsuccessfully.

if you are getting crashes with xposed then its likely the module might not be lollipop compatible, im running 5.0.2 with xposed and a few modules I use and its solid
you might be better off looking at some of the aosp/cm based roms in the dev section

I want to give aosp a shot since you recommended it and I think it's exactly what I'm looking for, but I'm having trouble flashing the zip I got from the Free Xperia Project site, I'm trying to flash AOPS_L_MR1_150312_leo.zip and all I'm getting is errors from all 3 custom recoveries, using an unlocked bootloader, the md5 is 2c4006757733d7a57997cfb31ba9efe but I can't find a hash on their site, the only error I have is "E: Installation aborted. press any key to continue". My internet is terribly slow and downloading a 200mb file takes hours, so I'll try re-downloading but I'd prefer not to.
Edit: I've tried 2 ROMs I've verified are downloaded correctly and they won't install, one with an unspecified error (AOSP) and the other will report wrong device saying "This rom is intended for D6603 z3, this device is 'leo'" (pac rom), I have no idea where the problem may be

well I never recommended it, I just said that you might be better off looking at aosp roms as that's clearly what you want rather than stock sony rom, what model is your device and are you flashing the boot.img from the rom and using that recovery?

Ok, I got a bit carried away I ment to say that you where right when saying that AOSP suited my needs.
Richy99 said:
what model is your device and are you flashing the boot.img from the rom and using that recovery?
Click to expand...
Click to collapse
I'm not flashing boot.img from the rom, I'm using CWM TeamWin and Philz recoveries I previously flashed while on stock to flash the zip files. Is this wrong? I've been doing this forever on other devices.
Do people that post ROMs provide boot.img to be flashed using flashtool previous to the flashing of their ROMs zip?

what device do you have? is it the 6603 or 6653? no its not wrong but sometimes the recovery is slightly different from the boot.img and I have seen it resolve the issue in the past, the installation aborted should give an error number after it, normally googling this can lead to why it failed

Richy99 said:
what device do you have? is it the 6603 or 6653?
Click to expand...
Click to collapse
I'm using 6603 and the error I get isn't very descriptive "E:Installation aborted" right after selecting the zip, nothing else.
Only in one isntance did I get something different and the error was something along the lines of "this rom is for 6603 and your device is leo".

which rom did you try? as it sounds like the rom isn't for the 6603

You must edit update.binary and erase z3 and replace it with Leo.
Then re-zip and flash it.

Richy99 said:
which rom did you try? as it sounds like the rom isn't for the 6603
Click to expand...
Click to collapse
This has happened with various ROMs that stated they where for 6603, could it be my recovery isn't playing nice with the zipped ROMs making them think my phone is a diferent model?
Edit:
I flashed bootZ3monxtest01.img with fastboot wich i TWRP and I'm getting nowhere
{
"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"
}

E-Chan42 said:
This has happened with various ROMs that stated they where for 6603, could it be my recovery isn't playing nice with the zipped ROMs making them think my phone is a diferent model?
Click to expand...
Click to collapse
LOL
Read my post.

TheTeslaCoil said:
You must edit update.binary and erase z3 and replace it with Leo.
Then re-zip and flash it.
Click to expand...
Click to collapse
For every .zip I try to flash? I'm not confident I could unzip, modify and re-zip without screwing up somehow, isn't there a specific recovery I can flash that will do this correctly?
UPDATE: using Z3_DooMLoRD_AdvStkKernel_v01_FW-93.img I was able to flash only cm-12.1-20150505-UNOFFICIAL-z3 (1).zip all other files gave me the same error, I'm now running Cyanogen but I still want to find a solution so I can flash other ROMs freely

E-Chan42 said:
For every .zip I try to flash? I'm not confident I could unzip, modify and re-zip without screwing up somehow, isn't there a specific recovery I can flash that will do this correctly?
Click to expand...
Click to collapse
Its not hard, open the zip using 7 zip or any winzip or WinRAR
Drag and drop the updater script out, modify it, drag and drop it back in.
Done

You can also flash CM by: flash boot.img from inside the firmware you want to flash. Unzip the CM ROM and extract boot.img and flash it. [via adb]
Then reboot into recovery.
It will bring you to CM recovery, from there apply update from sdcard1. [assuming that the ROM and gapps are there]
Flash CM
Again apply update and flash gapps.
Done.
After that you can flash another recovery if you want, or kernel, there is also a fota kernel, which updates only the recovery and keeps the kernel the same.
This method is without the need of editing update-binary.
Flash original firmware, [exactly as it is when downloaded] because the CM Recovery will check the signature.
Must have unlocked bootloader.
P.S.
If you edit update-binary do it with Notepad++

I had no idea I could extract boot.img from a ROM and flash it individualy using fastboot, this solved my problem 100%, thanks!

[ROM] [7.0] Optimized Stock Shield Tablet Original [5.2] & K1 [5.2] [14/08/17]

Optimized Stock Rom for Shield Tablet
{
"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"
}
Introduction:
I was missing a stock based rom for this device. So I took the nvidia recovery image and made it a flashable zip for TWRP. You cannot use ota to update though, wait for the new version from here if you want to update.
Also, don't flash wrong zip on the wrong Shield Tablet. It's your own responsibilty
Features:
- Latest Stock Factory Image
- Zipaligned apps
- Nothing more
Download:
K1: https://www.androidfilehost.com/?w=files&flid=93930
Original (Wifi & LTE): https://www.androidfilehost.com/?w=files&flid=94437
Also flash blob file of the same version
Enjoy!!

What to do with the blob zip:
Code:
1. Extract blob file from zip
2. Flash blob in fastboot with: fastboot flash staging "name of blob file"

Yup, I vote for original Shield ROM! Thanks!

Nice! Vulcan API goodness!

Zip for the original Shield Tablet (untested):
https://www.androidfilehost.com/?fid=24591000424954195

Thanks for this!
Is there any possibility you remove the Kill-Switch for users who have kept their tablet what has had to be replaced? I guess the Tegra Ota service must be disabled

Thanks! Made backup, flashed rom zip, flashed twrp, su, Xposed, nomoreota, and kernel. Wiped cache and booted system. Looks good so far... Not much immediate difference but we shall see over time. Came from stock so I did not wipe data and all is well.

teachmeluv said:
Thanks for this!
Is there any possibility you remove the Kill-Switch for users who have kept their tablet what has had to be replaced? I guess the Tegra Ota service must be disabled
Click to expand...
Click to collapse
Its better to do that yourself. There are tutorials on how here in the devices forum
Sent from my XT1562 using XDA Labs

GtrCraft said:
Its better to do that yourself. There are tutorials on how here in the devices forum
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
Ok thank you. Previous post says something about the nomoreota file, I remember that one now.
Anyway is this ROM pre-rooted? And is the file for the original tablet compatible with all three versions of it?

So after a few hours this ROM is smoother, cooler and faster then stock... Guess I'll be keeping it for awhile.

teachmeluv said:
Ok thank you. Previous post says something about the nomoreota file, I remember that one now.
Anyway is this ROM pre-rooted? And is the file for the original tablet compatible with all three versions of it?
Click to expand...
Click to collapse
The rom is not prerooted, also I only downloaded the wifi image. So that's the version for the original tablet

ok so after unlocking and rooting, I installed the bliss rom, but realized none of the nvidia apps were there And besides my Phantom I want this tablet for that.
so I wiped and installed this one, ran the nomoreota zip and everything is back to normal, but, I'm not longer rooted.
I just want this rom and rooted. I have twrp recovery and it works fine, but still not rooted.
anyhelp? thanks

Hello,
I tried to install K1 version using twrp, but i'm getting a blkdiscard failed: Invald argement,updater process ended with error 7. Image doesnot get installed.
Any ideas?
Regards,

Good Good! Working fine!!.Thanks.

fastfed said:
ok so after unlocking and rooting, I installed the bliss rom, but realized none of the nvidia apps were there And besides my Phantom I want this tablet for that.
so I wiped and installed this one, ran the nomoreota zip and everything is back to normal, but, I'm not longer rooted.
I just want this rom and rooted. I have twrp recovery and it works fine, but still not rooted.
anyhelp? thanks
Click to expand...
Click to collapse
Flash the latest su.zip in twrp.

rampa99 said:
Hello,
I tried to install K1 version using twrp, but i'm getting a blkdiscard failed: Invald argement,updater process ended with error 7. Image doesnot get installed.
Any ideas?
Regards,
Click to expand...
Click to collapse
Be sure to have the latest twrp and bootloader for K1

GtrCraft said:
Tell me if you guys want the same zip for the original shield tablet. Or a version without zipaligned apps
Click to expand...
Click to collapse
any chance for original 32GB European LTE flashable version, please?

SnowiiSnowii said:
any chance for original 32GB European LTE flashable version, please?
Click to expand...
Click to collapse
which recovery image is that?

That'd be LTE RoW 4.2... thank you!

SnowiiSnowii said:
That'd be LTE RoW 4.2... thank you!
Click to expand...
Click to collapse
Here you go:
https://www.androidfilehost.com/?fid=24591000424955372

Struck at Error:7 twrp "this package requires firmware from miui 9.5.14"

So I was initially on pixel experience 9.0 plus for my redmi note 7 pro and then decided to flash MIUI V11.0.5.0.PFHINXM via TWRP recovery. After flashing, the phone booted normally. Then I switched the rom to Pixel Experience 10. I didn't like the rom so thought of coming back to 9.0-pixel-experience but when I tried to do so, I got the error Error:7 twrp "this package requires firmware from miui 9.5.14" update your firmware. I tried updating the firmware too by flashing firmware from https://xiaomifirmwareupdater.com/firmware/violet/ but nothing seemed to work. Later I tried flashing pixel experience 10 and got the error. Now I am not able to flash any other rom other than Miui. Can someone help me to fix it, please?
ps: I have already tried flashing factory images of latest miui roms and that has not solved the problems.

which recovery are you using
try changing recovery
check with orangefox

I have tried switching recoveries too. Nothing seem to work.
gursewak.10 said:
which recovery are you using
try changing recovery
check with orangefox
Click to expand...
Click to collapse
I have tried changing the recovery too. Same error.

try flashing stable fastboot rom with option flash all.
then flash orangefox recovery with fastboot and then try.
flashing fastboot rom will undo anything happened to any partition

Seemed like it would have worked
gursewak.10 said:
try flashing stable fastboot rom with option flash all.
then flash orangefox recovery with fastboot and then try.
flashing fastboot rom will undo anything happened to any partition
Click to expand...
Click to collapse
I already tried flashing the latest Fastboot image and then tried flashing again. It still doesn't work.

are you formatting data before flashing??
when you format data there is no residue left of previous roms.
try format data then flash fastboot rom with "flash all" and then install recovery, try orangefox .

Yes
gursewak.10 said:
try flashing stable fastboot rom with option flash all.
then flash orangefox recovery with fastboot and then try.
flashing fastboot rom will undo anything happened to any partition
Click to expand...
Click to collapse
gursewak.10 said:
are you formatting data before flashing??
when you format data there is no residue left of previous roms.
try format data then flash fastboot rom with "flash all" and then install recovery, try orangefox .
Click to expand...
Click to collapse
I first erased everything from wipe and then even removed system,data,cache from advance wipe and then flashed. Whenever I try to flash any rom, it fails at the manifest check and gives the above said error. I even tried flashing the latest firmware. Nothing seem to work for me and now I am stuck at Miui?.

Starksm said:
I first erased everything from wipe and then even removed system,data,cache from advance wipe and then flashed. Whenever I try to flash any rom, it fails at the manifest check and gives the above said error. I even tried flashing the latest firmware. Nothing seem to work for me and now I am stuck at Miui.
Click to expand...
Click to collapse
i guess the rom file you are trying to install is either corrupted or checking for something.
could you upload updater-script file from meta-inf/com/google/Android folder from the rom you are trying to flash which is giving this error.

Please find the screenshot attached.
gursewak.10 said:
i guess the rom file you are trying to install is either corrupted or checking for something.
could you upload updater-script file from meta-inf/com/google/Android folder from the rom you are trying to flash which is giving this error.
Click to expand...
Click to collapse
Btw every rom has that updater line that I have highlighted. If I remove the assert function from the updater, the rom will get flashed but I just want to know why the issue is happening.
{
"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"
}
https://drive.google.com/file/d/1-7X0FyJH37mjOxVZcpdnb-STaxM2V_BO/view?usp=drivesdk

Please find the screenshot attached.
https://ibb.co/9gCg59f

its for checking, so you cannot flash the rom over a very old version of the stock rom which makes flashed rom not work properly or not booting at all.
they build roms over a specific version on which they test to have it working fine during all phases.
so thats why developers have it to keep a check over version of the rom you are installing upon. so that it has no conflicts between integration in future for running the rom.
moreover i see the version of your rom is old and may have a new version ,so try to have an updated version of the rom which may flash fine.

I tried flashing the lastest today's built of mokee and still the same error
gursewak.10 said:
its for checking, so you cannot flash the rom over a very old version of the stock rom which makes flashed rom not work properly or not booting at all.
they build roms over a specific version on which they test to have it working fine during all phases.
so thats why developers have it to keep a check over version of the rom you are installing upon. so that it has no conflicts between integration in future for running the rom.
moreover i see the version of your rom is old and may have a new version ,so try to have an updated version of the rom which may flash fine.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-EJlMd23ZJXa-Q_G9GCnkAN1oXTPxyGT/view?usp=drivesdk

Starksm said:
https://drive.google.com/file/d/1-EJlMd23ZJXa-Q_G9GCnkAN1oXTPxyGT/view?usp=drivesdk
Click to expand...
Click to collapse
from what i know, mokee rom has a patch for that.
you need to install that patch first.

This ought to be firmware bug. try fw 9.9.3 or the global 11.0.5.0 fw. Might work.....

I thought that too
Roshin1401 said:
This ought to be firmware bug. try fw 9.9.3 or the global 11.0.5.0 fw. Might work.....
Click to expand...
Click to collapse
I tried flashing the latest firmware too but it still doesn't want to work.

there is one simple and easy solution for this "delete that line" and then flash.

Xiaomi firmware update about 65mb
xiaomifirmwareupdater.com

I have tried that already
[email protected] said:
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
It didn't work

Hey! thanks for helping with your solutions. My issue was solved by flashing the latest INDIAN MIUI FIRMWARE. I can now easily flash any rom without any problems. Thanks

Please, can you explain the process, because even I'm getting firmware update error while flashing PE10 even after flashing latest Indian firmware before flashing Custom ROM, Tried Official TWRP, Peter TWRP booth. This started after update of MIUI-11, There was no such issue with MIUI10.

[ROM][STABLE]LineageOS 20 [Early Builds][Unofficial]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have finally been able to compile Android 13 for Mi Mix. I have been testing it for 3 days and no bugs found for now.
As if few of you are still using the phone as me, we deserve Android 13 so..here it is.
ROM LINK
ROM SOURCE
DEVICE TREE+KERNEL
Bugs:
*proximity sensor on calls , light sensor works perfect.​

Reserved for stuff

Thanks so much, i had already given up As I'm now away for christmas and new year i can only flash in january, but starting a new year with a new OS seems very promising

ducatisto said:
Thanks so much, i had already given up As I'm now away for christmas and new year i can only flash in january, but starting a new year with a new OS seems very promising
Click to expand...
Click to collapse
I will build pixel experience and few ROMS more, now that device tree is set up. I still remember the first ROM I built for this phone. I just had to change battery, phone is like new still.

ducatisto said:
Thanks so much, i had already given up As I'm now away for christmas and new year i can only flash in january, but starting a new year with a new OS seems very promising
Click to expand...
Click to collapse
Pixel Experience build will be ready for weekend, probably. Will be last build for this year until I come back from New York for holidays. I have a threadripper so builds finish within 1:10 hours.

I like it so far. I notice a bit of a battery drain. Could just be my device.

FateZero said:
I like it so far. I notice a bit of a battery drain. Could just be my device.
Click to expand...
Click to collapse
Kernel needs some adjustments still.

I think it might be the G apps as part of the issues. I am now using NikGapps core and the drain is not as bad.
The rom by itself is not too bad on the battery.

I got trouble installation failure.
E1001: Failed to update system image.
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
Before instllation it have LineageOS 17.
My twrp version is 3.5.2 fbe.
I tried to flash PixelExperience and DotOS, it worked.
Does someone have any idea?

Just out of curiosity gave it a try today: same twrp, same error msg, twice. Formatting data etc...nothing works. What's going on?

ducatisto said:
Just out of curiosity gave it a try today: same twrp, same error msg, twice. Formatting data etc...nothing works. What's going on?
Click to expand...
Click to collapse
Use recovery.img and adb sideload. Our twrp is outdated for Android 13.

YazumiWuHung said:
Use recovery.img and adb sideload. Our twrp is outdated for Android 13.
Click to expand...
Click to collapse
Thanks, that did it with the OS. What's strange is that after rebooting I don't succeed in adb sideloading any v13 Gapps package, i tried 5 different versions and after adb sideload starts sending the package and does start on the phone there's always "Error: recovery error in package..." Any ideas?

For gapps use twrp, its a bit messy having to change but it works.

YazumiWuHung said:
For gapps use twrp, its a bit messy having to change but it works.
Click to expand...
Click to collapse
after installing the rom, I flashed recovery back to official Twrp 3.2.1 to install gapps but when I boot to Twrp the touchscreen doesn't work. Which twrp do you use?

furiseto said:
after installing the rom, I flashed recovery back to official Twrp 3.2.1 to install gapps but when I boot to Twrp the touchscreen doesn't work. Which twrp do you use?
Click to expand...
Click to collapse
Use this one

YazumiWuHung said:
Use this one
Click to expand...
Click to collapse
thank you so much. you breathed new life to my old pal.
I've spent 1 hour with it and so far so good. Only bug I found is Night Light being glitchy but very minor.

Hello, where can I download the boot.img to root with magisk? I copy the one that is in the zip of the rom but it gives me a corrupt message. Thanks a lot!

fredferrer said:
Hello, where can I download the boot.img to root with magisk? I copy the one that is in the zip of the rom but it gives me a corrupt message. Thanks a lot!
Click to expand...
Click to collapse
It's in the sourceforge folder

Can anyone help me how to install this custom ROM on my Xiaomi Mix? This is my very first time on how to install a custom ROM. What are the basic things to do? What to download, where to download and how to download and install.
Thank you very much.

LineageOS 20.0 for Lenovo Xiaoxin Pad 2022 (China) (4/64 and 6/128)

{
"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"
}
OS:
LineageOS 20.0
Devices supported:
Lenovo Xiaoxin Pad 2022 (China) (4/64 and 6/128)
Means no radio support and no haptics.
Kernel:
4.19.275, Source @ GitHub
Bugs:
Not found
Installation:
Flash via TWRP as zip, if any troubles with installation, please format super and flash super_1.img from ZUI firmware to super partition.
FLASH ON YOUR RISK!!!
lineage-20.0-20230521-UNOFFICIAL-tb128fu.zip
Please donate if you want to support my work.

Can you provide kernel source, device trees and vendor trees?

after flashing and testing for a bit i noticed that Shim level is way higher than on stock or any gsi i have used
the higher the brightness, the worse the situation is.
after opening and closing any app, its back to normal a bit better but shim is still very high and noticable compared to any gsi or stock
turned off the device (didnt shutdown) after a minute or so, turned on, it flickered and shim is back until opening any app
if you are interested in more details or logs, let me know
i will have this build flashed for at least few days to test

hi! thank you for feed back.
brightness value are default. not device related. pls check vendor overlay.
Atm dont have pbty to share device/vendor.
Kernel is here https://forum.xda-developers.com/t/...tb128xu-kernel-sources.4583191/#post-88570739 dtb and dtbo are used from stock.

you may want to add direct github kernel link to main post since its required by xda gpl rules, your post may get banned and we definately dont want that xD

heineken78 said:
Kernel is here https://forum.xda-developers.com/t/...tb128xu-kernel-sources.4583191/#post-88570739 dtb and dtbo are used from stock.
Click to expand...
Click to collapse
Hi! Thanks for sharing your work on the forum. As per the post above, we require a direct link to the kernel source in the first post to ensure GPL compliance. As a courtesy, I've edited the first post and added that for you (from the source link you have mentioned in your other thread), so you're good to go. But please remember to do so in the future whenever you're creating threads sharing your development work.
Regards,
shadowstep
Senior Moderator

any updates?

LOS-20.0-20230611v2-UNOFFICIAL-tb128fu.zip

uhhhh
Psyl0w said:
LOS-20.0-20230611v2-UNOFFICIAL-tb128fu.zip
Click to expand...
Click to collapse
i kinda "semi-hard bricked" the tablet... not with the ROM, but in some other way, can you pm me on telegram if you could help?...

and i cant properly flash lineage now, it crashes the moment i start flashing it.., flashing super_1 to super doesnt fix it

welp, after flashing all the partitions manually, i ended up in crashdump, thats my "semi-hard brick", only stock flobal fw kernel works, any other kernel, zui, CAF, crashdump...

flashed stock kernel from global fw and lineage booted, everything is laggy (also thanks to my semi-hard brick), i guess this tablet can just go to the shelf...

oh **** and i dont have wifi unless i flash stock vendor with stock kernel :| and the display doesnt rotate at all, even if i force landscape, it stays in portrait.. bug of stock kernel. please help, i just dont know what to do, flashing zui from qfil doesnt help too...

tqmatvey said:
flashed stock kernel from global fw and lineage booted, everything is laggy (also thanks to my semi-hard brick), i guess this tablet can just go to the shelf...
Click to expand...
Click to collapse
actually before flashing stock vendor, it doesnt lag

Hi!
Thank you for your work! I wanna flash Lineage OS in this tablet but I dont know how to do it. Can someone tell me where I can find TWRP and how to flash it?
Thanks

Hi everyone! Hope you are fine
I tried to flash Lineage OS today and I couldnt do it. I flashed TWRP (no root) but it couldnt flash zip. It just said It couldnt do it.
I tried to flash super.img but i dont know where are the super partition to format. I went to wipe menu of twrp and there wasnt a super partition, just “ART/Dalvik”, “SD card”, etc, but nothing called “Super”.
Anyway I tried flash super1.img from original firmware with twrp flashing image menu and after reboot I saw black screen with Qualcomm Crashdump text. In flash menu I could see a “super_…” partition but there wasnt it in wipe menu.
After that I prayed to all Saints to restore global rom and I had good luck and thats all.
As can you see I need a little tutorial to do it, If any caritative person wanna share his knowledge please thank you
PD: i dont flash any rom since I had my last android device five years ago. I just used CWM, zip files and thats all. I see that this procedures are more difficult nowadays

@ajesushn use lineage recovery, unzip, flash to recovery, reboot to lineage recovery, fastboot mode > flash super_1.img, sideload latest lineage, reboot recovery so that it switches slots, flash other stuff you need (gapps, microg, magisk) you choose, format data , boot to system
for now quite sad that the device trees aren't public, would love to get crdroid working for the tb128fu

tqmatvey said:
@ajesushn use lineage recovery, unzip, flash to recovery, reboot to lineage recovery, fastboot mode > flash super_1.img, sideload latest lineage, reboot recovery so that it switches slots, flash other stuff you need (gapps, microg, magisk) you choose, format data , boot to system
for now quite sad that the device trees aren't public, would love to get crdroid working for the tb128fu
Click to expand...
Click to collapse
Thank you for the recovery. Just a doubt: there are 2 lineage20 zips. Which works better? I read your replies and the update seems that give more issues than fixes

ajesushn said:
Thank you for the recovery. Just a doubt: there are 2 lineage20 zips. Which works better? I read your replies and the update seems that give more issues than fixes
Click to expand...
Click to collapse
as i clearly mentioned, my issues were caused by another thing, not lineage related, latest lineage 20 works perfectly

Thank you. Install LineageOS successfully. Everything works great and very fluid. I haven't found any problem so far.