Database Info

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.

OxygenOS C.36 out but DON'T INSTALL THIS UPDATE FOR NOW!

I got a KB2003 - ONeplus 8T EU
Oxygen Updater told me today there's an update avaliable, version C.36.
I donloaded it via the app and updated manually.
Phone did not boot up.
I was able to boot into recovery once where it said the system is corrupt.
I managed to enter fastboot mode. It was recognised on my PC by fastboot but no fastboot command are not accepted. I couldn't even turn it off again.
About 2 hours passed.
Then I managed to turn it off and it booted up like nothing happened, but I cannot download the data from it. Nothing is showing up in my browser via cable connection.
I am not feeling safe anymore ... I think I will roll back to C.35 if possible ASAP.

You need to keep an eye on https://community.oneplus.com/wap/circleDetail?id=1034260458221338626
C.36 is an IN only version at the moment of OOS 12
Update: since I first wrote this post there have been reports of C.36 being available now for both EU and NA.

Thanks.
Can I download C.35 and install simply install it?

The C36 is rolling out to other versions now. See https://forum.xda-developers.com/t/updates-thread.4188149/
I've just received the KB2005 (NA/global) version when I checked in Settings>About device. Normally the EU version takes longer to roll out.
I don't think the system updater will let you downgrade to C35, but you can try.

After 1 night everything seems to work well. I did not try to Rollback or did anything.
Fastboot is back.
Still do not understand the issue. LOL

I updated it earlier. Now it's stuck on reboot loop :/

VarunAgw said:
I updated it earlier. Now it's stuck on reboot loop :/
Click to expand...
Click to collapse
You updated via OTA or Oxygen Updater app ?

neopbm said:
You updated via OTA or Oxygen Updater app ?
Click to expand...
Click to collapse
Oxygen Updater
Long story, I have reset my phone (I was planning to anyway), so all good now.

VarunAgw said:
Oxygen Updater
Long story, I have reset my phone (I was planning to anyway), so all good now.
Click to expand...
Click to collapse
Oh ! Even if formating is a good thing sometime to restart from scratch, i hope you didnt lost any important data

neopbm said:
Oh ! Even if formating is a good thing sometime to restart from scratch, i hope you didnt lost any important data
Click to expand...
Click to collapse
Yeah, I was able to fix the boot loop temporarily and was able to boot once. It gave me enough time to retrieve all the important data

i have 36 working just doesn't boot magisk boot i pulled myself and booted. i just tried with canary build and everything works great

ecompton59 said:
i have 36 working just doesn't boot magisk boot i pulled myself and booted. i just tried with canary build and everything works great
Click to expand...
Click to collapse
how did you get the boot.img ?
i cant because i cant find the stock flash file for C.36
build number : KB2005_11_C.36

oxygen updater
{
"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"
}
dont forget disable magisk mods

ecompton59 said:
oxygen updater
dont forget disable magisk mods
Click to expand...
Click to collapse
i am on c.36 , and on oxygen updater , i can only download flash file for c.33 , can i extract the boot img from it and root ? sorry for bad english

yes its in the 8t threads. payload dumper is what i use on pc its easy

ecompton59 said:
yes its in the 8t threads. payload dumper is what i use on pc its easy
Click to expand...
Click to collapse
so to be precise , i can extract boot.img from c.33 file and root my c.36 , right? ty btw

MevishL said:
so to be precise , i can extract boot.img from c.33 file and root my c.36 , right? ty btw
Click to expand...
Click to collapse
ecompton59 said:
i have 36 working just doesn't boot magisk boot i pulled myself and booted. i just tried with canary build and everything works great
Click to expand...
Click to collapse
sorry to bother, can you please tell me what are the exact steps to root it. im afraid i might brick my phone.

MevishL said:
sorry to bother, can you please tell me what are the exact steps to root it. im afraid i might brick my phone.
Click to expand...
Click to collapse
Look at this great guide.

Rootk1t said:
Look at this great guide.
Click to expand...
Click to collapse
thnks !

MevishL said:
sorry to bother, can you please tell me what are the exact steps to root it. im afraid i might brick my phone.
Click to expand...
Click to collapse
long as you know how to recover from brick with msm tool. but steps i use is oxygen updater to download full ota. (not incremental update) .put the 3gb zip on pc. use payload dumper to dump the zip (only for boot.img) take boot put on phone use magisk Canary to patch that boot. put boot on pc, reboot to recovery and fastboot boot magisk.img. once phone boots use magisk to directly patch boot and its rooted

General F-16/A13 oxygen os for LE2115 Na op9

Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here

mattie_49 said:
Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here
Click to expand...
Click to collapse
Do you have boot.img? i don't have good internet for download full ota and extract it :/

franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
Do you have full ota link?

franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot flash this then go into magisk let it reboot if it asks to continue setup. Rooted an A13 stock

mattie_49 said:
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot boot this then go into magisk and direct install to backup stock for you.
Click to expand...
Click to collapse
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd

@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66

AxelM said:
@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66
Click to expand...
Click to collapse
Oxygen updater

mh, I only receive 11_C.66 maybe I have to wait

after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?

franko_m19 said:
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd
Click to expand...
Click to collapse
{
"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"
}
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.

fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
It's the official 16 patched. Just fastboot flash it or ask guy above . He got working with it.

AxelM said:
after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?
Click to expand...
Click to collapse
No sir I carried it over with magisk from 11 originally. MSM,unlock bl. Patch boot . Then disable modules and carry from A11 to A12 then so on.

fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
fastboot flash boot *boot_name*.img

franko_m19 said:
fastboot flash boot *boot_name*.img
Click to expand...
Click to collapse
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool

_MartyMan_ said:
Do you have full ota link?
Click to expand...
Click to collapse
No but flash one of the open betas. That's how I received so fast. Was on ob2 and it's getting it first.

fhedeitx said:
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool
Click to expand...
Click to collapse
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?

franko_m19 said:
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?
Click to expand...
Click to collapse
Global (I believe) LE2115 in US

mattie_49 said:
Oxygen updater
Click to expand...
Click to collapse
I was on open beta 2 is why I received very first. That's the order they put rollout in. To ob 1& 2 before stock devices.

Install in inactive slot (after ota) in magisk is working for upgrading from android 12 to 13 (using oxygen updater zip file) ?Edit: this doesn't work because the device reboots when the installation starts.
Remove magisk boot image from magisk app, update and turn off the device...boot to fastboot and do a fastboot boot magisk_patched.img (you have to extract the boot image with payload dumper and patch it before or after the installation with magisk. Then do a direct install from magisk (on the temp root boot image).
On android 13 you will have this warning on every reboot: Orange state, Your device has been uplocked and can't be trusted.

Thanks for this! I have not had root on my Oneplus 9 for a while and it was driving my _crazy_. Had to do fastboot flash boot boot.img instead of fastboot boot boot.img to get magisk to work properly.
I had to jump through some extraordinary hoops to get it done including breaking out an old Win10 laptop since I could never get my new Win11 laptop to recognize my phone in fastboot, despite hours of work trying to install the drivers to no success.

[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.