[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

[psi78]

I think they need to patch these tablets... all of them, so you can see the boot process happening and not stamp an image at boot. That way when something bombs out, there is some breadcrumbs as to what tanked.

Glad you know about this! I had no idea how this stuff works behind the scenes.

Yeah, i agree. It sucks when you can't see what 's happening during the boot process.

if you wanna read something more, these articles may shed some.light:

What the Zygote!?

Android OS boot process explained with focus on Zygote

medium.com

Difference between dexopt and dex2oat?

Google is moving from Dalvik to ART(Android Runtime). I was trying to understand, how it is going to improve the performance. The best explanation I found is the below image: One of the main com...

stackoverflow.com

Android Runtime - Wikipedia

en.wikipedia.org

 

[shaunblyde]

Not sure what you did to cause it to get into this condition.

If you have TWRP on it, wipe the device within TRWP and give it another go.

If you don't have TWRP on it, Try flashing the OEM binary again with fastboot. Then once its flashed and boots up, root it and try again with the lineage rom.

If someone can correct me on this, I think that is soft bricked. You might want to search around for what that is and how to solve it unless my attempt at help is indeed help and not a rabbit hole.

Good luck.
Take care,

I have this problem when flashing a stock image (.bin renamed to .zip) - except I don't get the "optimizing" message, only that I am stuck on the fire logo screen for hours on end. I have TWRP installed and have tried wiping system (and other partitions), many different stock roms from the Amazon website and XDA. Unfortunately no luck with any of this.

Anyone have suggestions on what to flash or what I'm doing wrong to get back to stock FireOS with TWRP installed?

 

[psi78]

I have this problem when flashing a stock image (.bin renamed to .zip) - except I don't get the "optimizing" message, only that I am stuck on the fire logo screen for hours on end. I have TWRP installed and have tried wiping system (and other partitions), many different stock roms from the Amazon website and XDA. Unfortunately no luck with any of this.

Anyone have suggestions on what to flash or what I'm doing wrong to get back to stock FireOS with TWRP installed?

Did you format Data partition too (not only wipe it)? Then power off/reboot to recovery before you flash.

 

[shaunblyde]

Did you format Data partition too (not only wipe it)? Then power off/reboot to recovery before you flash.

Just tried this - explicitly formatted Data (then typed "yes"). Shut down, then booted into recovery again to flash stock zip, with no luck unfortunately. Still sitting on Fire screen 10 minutes later.

 

[psi78]

Just tried this - explicitly formatted Data (then typed "yes"). Shut down, then booted into recovery again to flash stock zip, with no luck unfortunately. Still sitting on Fire screen 10 minutes later.

Hmm, just tried it, worked perfectly in one go for me.
Did you use the correct file for your device?
I wiped everything besides Micro SD card, i.e. Dalvik / ART cache, System, Data, Internal Storage, Cache.
Then i formatted Data partition.
Then power off and boot to TWRP again.
Then installed the renamed .zip file, didn't wipe Dalvik/ ART cache or cache at this point.
Then rebooted, FireOS taking like 2 mins to optimize the apps (there was visible progress at the progress bar), then i was in.

 

[shaunblyde]

Hmm, just tried it, worked perfectly in one go for me.
Did you use the correct file for your device?
I wiped everything besides Micro SD card, i.e. Dalvik / ART cache, System, Data, Internal Storage, Cache.
Then i formatted Data partition.
Then power off and boot to TWRP again.
Then installed the renamed .zip file, didn't wipe Dalvik at this point.
Then rebooted, FireOS taking like 2 mins to optimize the apps (there was visible progress at the progress bar), then i was in.

Thanks for testing it out. To confirm, I have the 7 Generation Fire HD 10 (Suez) and am following the method you advise, and am using the file from this link (renamed as .zip) for the stock image: https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE

Fire HD 10 (7th Generation)​

FireOS 5 | FireOS 5.3.7.3
Download Software Update

Is this the same stock image you are using? I am only installing the single zip/image, nothing additional (root, Magisk, Gapps etc), I assume this is the same under your testing?
I am wondering if perhaps my partition table or boot image needs manual intervention after the custom rom installations?

 

[psi78]

Thanks for testing it out. To confirm, I have the 7 Generation Fire HD 10 (Suez) and am following the method you advise, and am using the file from this link (renamed as .zip) for the stock image: https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE

Fire HD 10 (7th Generation)​

FireOS 5 | FireOS 5.3.7.3
Download Software Update

Is this the same stock image you are using? I am only installing the single zip/image, nothing additional (root, Magisk, Gapps etc), I assume this is the same under your testing?
I am wondering if perhaps my partition table or boot image needs manual intervention after the custom rom installations?

Yeah, that one. There's a boot.img inside the zip, so it will flash boot image just like other ROMs. If it doesn't boot probably you haven't wiped/formatted everything. You could also use the repair partition function of TWRP on Cache, System, Data partitions or reformat these with ext4 filesystem. Unless you didn't repartition the device or messed up something with adb there shouldn't be any more interventions needed than that. Edit: Maybe it's the TWRP version, i'm using not the latest one, but 3.6.1-9.0

 

[shaunblyde]

Yeah, that one. There's a boot.img inside the zip, so it will flash boot image just like other ROMs. If it doesn't boot probably you haven't wiped/formatted everything. You could also use the repair partition function of TWRP on Cache, System, Data partitions or reformat these with ext4 filesystem. Unless you didn't repartition the device or messed up something with adb there shouldn't be any more interventions needed than that. Edit: Maybe it's the TWRP version, i'm using not the latest one, but 3.6.1-9.0

Thanks, still no luck unfortunately. Seems I am following the same process as you. I just updated to 3.6.1-9.2 yesterday, but before that was using 3.6.1-9.0, and still no result, so I think that is unlikely to be the problem, but can roll back TWRP and try.

 

[psi78]

Thanks, still no luck unfortunately. Seems I am following the same process as you. I just updated to 3.6.1-9.2 yesterday, but before that was using 3.6.1-9.0, and still no result, so I think that is unlikely to be the problem, but can roll back TWRP and try.

I'd try to wipe everything possible (just not Micro SD card if you have an external sd card inserted) + format data, then also use the repair partition function (in the wipe section of TWRP) on every possible partition.
I had it once or twice when i did stuff with adb that for example the cache partition was broken.

 

[shaunblyde]

I'd try to wipe everything possible (just not Micro SD card if you have an external sd card inserted) + format data, then also use the repair partition function (in the wipe section of TWRP) on every possible partition.
I had it once or twice when i did stuff with adb that for example the cache partition was broken.

Still no success I've tried all you've mentioned, so really not sure what to try next.

Just to confirm, your partitions are all ext4 and match the sizes below? I have tried to repair, "change file system" to ext4 (which they already were, I was just hoping to refresh the partitions) and wipe them all - besides for the system partition, which I could only wipe, not repair or "change file system".

/system ext4 1557MB (No repair option, only Change File System)
/data ext4 26899MB
/cache ext4 394MB

 

[psi78]

Cool you tested it. Did you try the other app alternatives too? I'm on LOS12.1 atm and can't test it.

@ggow you used some of those ibilux patches for the mediatek chipset and omx. There is one patch which fixes the zoomed in videos too apparently, maybe that's the fitting fix for the zoomed in videos on yt app on this rom?

See https://github.com/ibilux/android_d...x-video-autoscaling-on-old-OMX-decoders.patch

@ggow As it turns out the contents of this patch are already in the LOS16 source code of
frameworks/av/media/libstagefright/ACodec.cpp

Just the define is missing, so this entry in the same file is needed to enable the legacy rescaling:
#define USE_LEGACY_RESCALING

 

[psi78]

Still no success I've tried all you've mentioned, so really not sure what to try next.

Just to confirm, your partitions are all ext4 and match the sizes below? I have tried to repair, "change file system" to ext4 (which they already were, I was just hoping to refresh the partitions) and wipe them all - besides for the system partition, which I could only wipe, not repair or "change file system".

/system ext4 1557MB (No repair option, only Change File System)
/data ext4 26899MB
/cache ext4 394MB

Hmm, something seems wrong with your system partition then, you should be able to wipe it, which means it would be reformatted.
Can you use repair partition on it and format it as ext4?
Edit: Oh you said, you can't, well i guess try to remember what you did with it, or switch the deivce off, then go to recovery and format it, maybe unmount it first?
Or maybe you have to reconstruct the system partition.
You could also try to do this what @Kate6 suggested:

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * 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 the products you find...

forum.xda-developers.com

Yeah all partitions are ext4, and i think they have the same size as yours

 

[shaunblyde]

Hmm, something seems wrong with your system partition then, you should be able to wipe it, which means it would be reformatted.
Can you use repair partition on it and format it as ext4?
Edit: Oh you said, you can't, well i guess try to remember what you did with it, or switch the deivce off, then go to recovery and format it, maybe unmount it first?
Or maybe you have to reconstruct the system partition.
You could also try to do this what @Kate6 suggested:

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * 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 the products you find...

forum.xda-developers.com

Yeah all partitions are ext4, and i think they have the same size as yours

Managed to wipe and repair system partition, it was not mounted by default. Once I mounted it, it was treated the same as the others. But still nothing sadly. Thanks for your help though.

 

[psi78]

@ggow As it turns out the contents of this patch are already in the LOS16 source code of
frameworks/av/media/libstagefright/ACodec.cpp

Just the define is missing, so this entry in the same file is needed to enable the legacy rescaling:
#define USE_LEGACY_RESCALING

Tried to rebuild the ROM with ggow's sources, this fix and booting with only the little cpus 0-1. At one point i was able to build the kernel/boot.img, but for the rest of the ROM the build seems to be missing/dependent on libnvram sources. Don't really have a clue where to get that or what i'm missing there. Anyone got an idea?

 

[Syco54645]

So I am a bit confused, is the camera working at all in this rom? It seems like the camera may be fine but cannot do video.

 

[_ck_]

I think they need to patch these tablets... all of them, so you can see the boot process happening and not stamp an image at boot. That way when something bombs out, there is some breadcrumbs as to what tanked.

Install LiveBoot app by Chainfire

Way, way too much info on default settings but can be tuned very well

You'll be amazed how many typical errors occur on every rom boot

 

[likwidchz]

Install LiveBoot app by Chainfire

Way, way too much info on default settings but can be tuned very well

You'll be amazed how many typical errors occur on every rom boot

I'll check that out! thank you. I had no idea there was a method to do this.

 

[_ck_]

If this helps anyone, don't try to flash this rom and magisk at the same time.

First do the rom. Then reboot and let it config. Then go back into twrp and do magisk. Otherwise bootloop with rainbow stripe across the screen.

Thank you so much ggow for all your work, this tablet was all I could afford right now and you made it usable.

 

[_ck_]

Okay magisk just messes up my install every time so skipping it for now until I have time, don't really need root on twrp+lineage anyway

Hidden wifi SSID is broken on this build, has to be visible or never works (also oddly saved networks cannot be edited unless connected)

Solving the free space for gapps was done using "NikGapps-core-arm64-9" which is an old but well maintained project, super tiny and uses real play store and then google just updates the store app anyway

This tablet is fantastic for bad eyes, just set font and display to "larger" and so easy to read.

 

[psi78]

Okay magisk just messes up my install every time so skipping it for now until I have time, don't really need root on twrp+lineage anyway

Hidden wifi SSID is broken on this build, has to be visible or never works (also oddly saved networks cannot be edited unless connected)

Solving the free space for gapps was done using "NikGapps-core-arm64-9" which is an old but well maintained project, super tiny and uses real play store and then google just updates the store app anyway

This tablet is fantastic for bad eyes, just set font and display to "larger" and so easy to read.

There is an su version included in the ROM which also works for giving apps root rights (as alternative to magisk). I think it may be the LineageOS addon su from here https://download.lineageos.org/extras (but you'd have to ask ggow for that i guess).
You can enable/disable it in developer options.

If you wanna use magisk you could revert back to previous TWRP version 3.6.1-9.0, magisk works fine with it/no bootloop of LOS with this TWRP version and magisk. Somebody described also a way to make magisk work with the newest TWRP for suez, it's somewhere in the last pages of this thread.

Edit: See this post of droidjunkie for example

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * 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 the products you find...

forum.xda-developers.com

Or this by Creeju

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * 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 the products you find...

forum.xda-developers.com

Or also this by MarvinMod

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * 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 the products you find...

forum.xda-developers.com