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

Search This thread

psi78

Senior Member
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:
 

shaunblyde

Member
Jan 3, 2011
16
3
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

Senior Member
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

Member
Jan 3, 2011
16
3
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

Senior Member
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.
 
Last edited:

shaunblyde

Member
Jan 3, 2011
16
3
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

Senior Member
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
 
Last edited:

shaunblyde

Member
Jan 3, 2011
16
3
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

Senior Member
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

Member
Jan 3, 2011
16
3
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

Senior Member
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

Senior Member
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:

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

shaunblyde

Member
Jan 3, 2011
16
3
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:

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

Senior Member
@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?
 

_ck_

Senior Member
Apr 9, 2011
383
55
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
 

_ck_

Senior Member
Apr 9, 2011
383
55
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.
 
  • Like
Reactions: Kramar111

_ck_

Senior Member
Apr 9, 2011
383
55
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

Senior Member
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

Or this by Creeju

Or also this by MarvinMod
 
Last edited:
  • Like
Reactions: _ck_

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    @chairmanmiaow, if copying the working recovery and recovery_x files to your other device fixes it I'd greatly appreciate a copy! ;⁠-⁠)

    If I could flash stock recovery and get back to original firmware I might do the bootloader hack and get lineage 16 on there. But with the modified gpt on lineage 14.1 I don't know if it will break it.

    Well I've had a good poke around the partitioning and setup of mmcblk0 on a "good" and "bad" suez tablet for comparison and it looks like - unsurprisingly - there's probably considerably more to it than just dd'ing a recovery partition or two. For example:

    "good" suez 😇

    suez:/ # ls -alh /dev/block/platform/soc/11230000.mmc/by-name/ | tail -n +4 | awk '{print $8,$9,$10}' MISC -> /dev/block/mmcblk0p9 PMT -> /dev/block/mmcblk0p2 boot -> /dev/block/mmcblk0p11 boot0hdr0 -> /dev/null boot0hdr0_real -> /dev/block/mmcblk0boot0p1 boot0hdr1 -> /dev/null boot0hdr1_real -> /dev/block/mmcblk0boot0p2 boot0img0 -> /dev/null boot0img0_real -> /dev/block/mmcblk0boot0p3 boot0img1 -> /dev/null boot0img1_real -> /dev/block/mmcblk0boot0p4 boot_amonet -> /dev/block/mmcblk0p16 boot_x -> /dev/block/mmcblk0p11 cache -> /dev/block/mmcblk0p14 dkb -> /dev/block/mmcblk0p4 kb -> /dev/block/mmcblk0p3 lk -> /dev/null lk_real -> /dev/block/mmcblk0p5 metadata -> /dev/block/mmcblk0p8 proinfo -> /dev/block/mmcblk0p1 recovery -> /dev/block/mmcblk0p12 recovery_amonet -> /dev/block/mmcblk0p17 recovery_x -> /dev/block/mmcblk0p12 reserved -> /dev/block/mmcblk0p10 system -> /dev/block/mmcblk0p13 tee1 -> /dev/null tee1_real -> /dev/block/mmcblk0p6 tee2 -> /dev/null tee2_real -> /dev/block/mmcblk0p7 userdata -> /dev/block/mmcblk0p15

    "bad" suez 🤕

    suez:/storage/93CF-1B05/fireN # ls -alh /dev/block/platform/soc/11230000.mmc/by-name/ | tail -n +4 | awk '{print $8,$9,$10}' MISC -> /dev/block/mmcblk0p9 PMT -> /dev/block/mmcblk0p2 boot -> /dev/block/mmcblk0p16 boot0hdr0 -> /dev/block/mmcblk0boot0p1 boot0hdr1 -> /dev/block/mmcblk0boot0p2 boot0img0 -> /dev/block/mmcblk0boot0p3 boot0img1 -> /dev/block/mmcblk0boot0p4 boot_x -> /dev/block/mmcblk0p11 cache -> /dev/block/mmcblk0p14 dkb -> /dev/block/mmcblk0p4 kb -> /dev/block/mmcblk0p3 lk -> /dev/block/mmcblk0p5 metadata -> /dev/block/mmcblk0p8 proinfo -> /dev/block/mmcblk0p1 recovery -> /dev/block/mmcblk0p17 recovery_x -> /dev/block/mmcblk0p12 reserved -> /dev/block/mmcblk0p10 system -> /dev/block/mmcblk0p13 tee1 -> /dev/block/mmcblk0p6 tee2 -> /dev/block/mmcblk0p7 userdata -> /dev/block/mmcblk0p15

    I think at this point just to save time/effort it's time to reset back to stock and redo unlocking the bootloader from scratch again. It's worth double checking first of course but it does seem that it's still possible to unlock even the latest official Amazon suez firmware. Bit of a pain in the ass but it's entirely my fault - I know how fragile these things are but still half-arsed the TWRP upgrade even though I had misgivings at the time.

    @8bitword - if you just want to get back to stock you can indeed just flash straight over the top of your existing system and basically fully recover. In your case you didn't even have the unlocked bootloader status or custom recovery setup to lose in the first place so you're just replacing a lightly mangled stock os with a fresh minty stock os. I need to comb through the other suez threads first just to refresh my memory on how to reflash stock though - I think you just put it in fastboot mode and then you can send the stock bin from a PC via adb or odin/fastboot.

    Can anyone save me the effort and remind me?
  • 54
    Disclaimer
    Code:
    /*
    * 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 here before flashing it!
    * YOU are choosing to make these modifications.
    */

    - EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.

    - IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required). This will be fixed in a later update.

    Rules
    - Please search the thread before asking questions
    - Please try to stay on topic, I know it's not always possible
    - When reporting bugs please post a logcat and/or dmesg where possible

    Lastest TWRP version
    - 3.6.1-9.2

    Downloads

    - Google Drive

    Source Code

    Thanks
    - @k4y0z and @xyz` for the bootloader hack
    - @k4y0z for the initial kernel
    - LineageOS
    18
    🛠 Worklist / Tasks

    - [fixed] Bluetooth works
    - [fixed] Audio works
    - [fixed] Internal storage isn't accessible from any app
    - [done] Sensors working
    - [fixed] Touch sounds are working
    - [done] Test audio format playback - mp3 working
    - [done] Tested video playback with NewPipe which is working
    - [fixed] WiFi signal strength not working
    - [done] Support aptX-HD encoder for bluetooth
    - [fixed] No adb during boot
    - [fixed] WiFi working
    - [fixed] Navbar icon corruption
    - [fixed] Wallpaper corruption
    - [fixed] Laggy graphics
    - [fixed] High cpu usage
    - [fixed] DRM not working
    - [fixed] Hardware OMX (for the most part)
    - [fixed] Wired headphones not working
    - [done] Enable OTG USB for ethernet
    - [fixed] Youtube black screen with audio
    - [fixed] MtkOmxCore crash
    - [fixed] Battery showing wrong capacity - reported here
    - [fixed] "There's an internal problem with your device." dialog
    - [fixed] SIM card prompt
    - [fixed] Chrome cannot access internal storage
    - [fixed] Poor WiFi throughput (potential cause of choppy video playback)
    - [fixed] Disney app crashing (more info here)
    - [fixed] Speakers continuing to play while headphones are plugged in
    - [fixed] Cannot switch wifi on after storage encryption enabled
    - [hold] Bluetooth not working properly - can't see issue here
    - [fixed] Magisk update by app
    - [fixed] Storage permission issues (cause of some apps crashing)
    - [done] Upstreamed kernel
    - [todo] TWRP: USB-OTG not working
    - [fixed] USB-OTG Ethernet
    - [fixed] TWRP: MTP access
    - [todo] Voice assist MIC not working
    - [done] Added android.hardware.opengles.aep.xml permissions
    - [fixed] LiveDisplay not working
    - [fixed] Backlight HAL Errors

    - [todo] Shutdown after entering sleep mode (suspect cpu/gpu coming up in the wrong state -> overheating)
    - [todo] Gapps > pico causing not enough space error
    - [todo] Youtube black screen with audio
    - [todo] Mirrorcast not working
    - [todo] Multi-user not working
    - [todo] Navbar problem when keyboard is in horizontal mode
    - [todo] Playing videos over SMB failure after 30 min (more info here)
    - [todo] Can't connect to hidden WiFi networks
    - [todo] Lego app not working (more info here)
    - [todo] Cameras not working (more info here)
    - [todo] SELinux
    - [todo] Intermittent high idle cpu usage
    - [todo] Investigate L1 widevine support (L3 currently)
    - [todo] Pass safetynet
    - [todo] Device build fingerprinting
    - [todo] Enable zram?
    - [todo] Device encryption (TWRP)
    - [todo] Battery idle mode
    - [todo] Offline charging mode
    - [todo] Low speaker volume
    - [todo] Thermal Shutoff, overheating
    - [todo] System partition needs to be increased in size to accomodate gapps
    13
    ⏱ Change log / Release Notes

    05 July 2022

    - [fixed] Backlight HAL Errors
    - [fixed] LiveDisplay not working

    06 May 2022
    - [fixed] Voice assist MIC not working
    - [fixed] USB-OTG Ethernet
    - [fixed] TWRP: MTP access
    - [fixed] TWRP: Fixed USB-OTG
    - [info] Added android.hardware.opengles.aep.xml permissions

    13 April 2022
    - [fixed] Terminal input via apps and adb shell

    12 April 2022
    - [kernel] Up-streamed to 3.18.140
    - [kernel] Enable per user storage quota
    - [kernel] Optimized build flags for Cortex-a53
    - [kernel] Boeffla Wakelock Blocker Driver v1.1.0
    - [kernel] Enable some TCP congestion algorithms
    - [kernel] Westwood Default TCP congestion algorithm
    - [kernel] Sdcardfs v2.0
    - [info] Remove aptX bluetooth libraries for now
    - [info] Mount /system partition early-mount style
    - [info] Add vendor security patch

    06 April 2022
    - [fixed] Fix KernelUidCpuTimeReader errors
    - [info] Revert audio HIDL from 2.0 to 4.0 back to 2.0 - our drivers aren't ready for this
    - [info] Put storage permissions force close on the todo list
    - [info] Chrome browser works
    - [info] Jelly browser works
    - [info] WeDo lego app works

    Show Further History

    03 April 2022
    - [fixed] Magisk update by app
    - [fixed] Storage permission issues (cause of some apps crashing)
    - [fixed] Lego app not working (more info here)
    - [fixed] Cannot switch wifi on after storage encryption enabled
    - [info] Update suez defconfig in kernel to be more inline with aosp
    - [info] TWRP 3.6.1-9.0 available from Google Drive (no encryption support)
    - [info] Up-rev audio HIDL from 2.0 to 4.0
    - [info] Disabled amazon logging functions in kernel
    - [info] Disabled unused squashfs in kernel
    - [info] Conditionally compile MTK_M4U in the ion kernel driver as our device doesn't use it

    27 March 2022
    - [reverted] WiFi changes from previous build
    - [removed] 26 March Build

    26 March 2022
    - [fixed] Speakers continuing to play while headphones are plugged in
    - [fixed] Disney+ crashing
    - [didn't work for everyone] Slow WiFi throughtput
    - [didn't work for everyone] 5GHz connectivity to AX-88U router and in general
    - [didn't work for everyone] 5GHz connectivity to across all channels
    - [info] Include Bromite Webview
    - [request] WiFi: Can someone test connecting to hidden SSID's and report back?
    - [request] Magisk: Can someone test whether updating through the application works and report back?

    16 March 2022
    - [fixed] MtkOmxCore crash
    - [fixed] Better auto adjust on backlight
    - [fixed] SIM card prompt
    - [fixed] Changed battery capacity to 6300mAh
    - [fixed] sdcard access for chrome and other apps
    - [fixed] "There's an internal problem with your device." dialog
    - [info] Explicitly enable sdcardfs
    - [info] Refactor root init scripts
    - [info] Remove deprecated storage_list.xml
    - [info] Clean-up build.prop

    01 March 2022
    - [info] Re-build of 28 February version

    28 February 2022
    - [fixed] DRM Widevine L3 support
    - [new] Signature spoofing (enable and disable via developer options)
    - [fixed] Wired headphones not working
    - [fixed] Backlight HAL crashing
    - [fixed] Hardware OMX (MTK codecs now been used)
    - [info] Disable camera completely until fully investigated to stop logcat spam
    - [info] Enable OTG for ethernet in kernel

    07 February 2022
    - [fixed] OMX regression was breaking NewPipe and local video file playback
    - [info] Clean-up amazon binaries - media playback should be better - config file mess


    05 February 2022
    - [fixed] Navbar icon corruption
    - [fixed] Wallpaper corruption
    - [fixed] Laggy graphics
    - [fixed] High idle cpu usage
    - [info] Updated amazon binaries to fireos 5.6.9.0

    12 February 2021
    - Initial Release
    12
    But why OP decided to go back to 14.1?

    Never said for suez I was going back to 14.1.
    I will be continuing with lineage-16.0 for suez.
    12
    ℹ️ New Build is Up

    Dated: 16 March 2022

    - [fixed] MtkOmxCore crash
    - [fixed] Better auto adjust on backlight
    - [fixed] SIM card prompt
    - [fixed] Changed battery capacity to 6300mAh
    - [fixed] sdcard access for chrome and other apps
    - [fixed] "There's an internal problem with your device." dialog
    - [info] Explicitly enable sdcardfs
    - [info] Refactor root init scripts
    - [info] Remove deprecated storage_list.xml
    - [info] Clean-up build.prop

    Download from Google Drive link on OP.