[UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices

[goapy]

thanks! just in case our models are different, mine's a "DT-ATV36" although i highly doubt they are different. i forgot the firmware i started with before i installed, but i later flashed the walmart firmware (from the factory images provided in this post), so thats what it is for me right now.

I checked another wade device. It had been in storage and had older firmware installed.

It did have problems running recovery, both by direct boot or if flashed. Best I could tell, it was the particular dtb installed that would allow recovery to boot/run or not

Better to just wait for the real build since it's being worked on presently.

 

[RDS5]

I checked another wade device. It had been in storage and had older firmware installed.

It did have problems running recovery, both by direct boot or if flashed. Best I could tell, it was the particular dtb installed that would allow recovery to boot/run or not

Better to just wait for the real build since it's being worked on presently.

oh alright! i think the dtb partition is flashable, no? although id prefer not to mess with it anyways since it'd probably brick the thing anyways.
but theoretically, you could probably flash an older dtb, although i think in the factory images, you do flash the dtb of the build (older walmart build on the original post). i had both the latest build (from amazon) and the older walmart build (from the original post) and both failed to launch the 19.1 recovery, so its safe to say that the 19.1 recovery for wade is practically cooked on most devices.
especially new ones.

 

[goapy]

I'd just leave the device alone. I tried the dtb from the build. It didn't work. Although, of course, recovery does work with that dtb if the build is successfully sideloaded. I then tried another dtb from one of the ota archives, and recovery would then directly boot. But I still had trouble with installation. I gave up and just pulled the super.img off my other wade device that had 19.1 installed already and installed the build with bootloader fastboot.

There is still the black screen issue with this xda build, which has been fixed but not in this build, so it's not really worth the time to finagle an installation of this build. The xda builds of 19.1 for the other devices have issues with the recovery as well.

 

[pddc]

for the life in me, I cannot get ethernet working on 18.1, OTG or powered HUB. anyone has this working and could share parts used? thanks

 

[TabascoJoe]

I see the new build is up...
Are we ok to flash and test it?

 

[npjohnson]

I see the new build is up...
Are we ok to flash and test it?

dopinder still isn't gonna boot, but others should be fine yeah

 

[TabascoJoe]

dopinder still isn't gonna boot, but others should be fine yeah

Figured that out the hard way, lol!

 

[goapy]

I see the new build is up...
Are we ok to flash and test it?

If you do, post your thoughts about any changes that you notice from the prior build.

 

[TabascoJoe]

If you do, post your thoughts about any changes that you notice from the prior build.

Without a working recovery I'm going to wait...
When I flashed a 19.1 image with the 18 bootloader it was broken beyond useable...
Images would crash and never load...
Not sure if it was due to the mismatched recovery, but I figured I'd wait.

 

[goapy]

19.1 on dopinder is broken - rest of devices are fine.

We know why. We know how to fix it.

dopinder still isn't gonna boot, but others should be fine yeah

Since you know why and how to fix it, what's the reason that dopinder won't boot, and what would it take to fix it?

Asking for a curious friend.

 

[npjohnson]

Since you know why and how to fix it, what's the reason that dopinder won't boot, and what would it take to fix it?

Asking for a curious friend.

What I initially suspected was wrong.

My dopinder is broken. It shot up blue smoke and won't shot any life.

I need to find time to debug it and get one of the lineage devs to get me a UART log.

 

[goapy]

Without a working recovery I'm going to wait...
When I flashed a 19.1 image with the 18 bootloader it was broken beyond useable...
Images would crash and never load...
Not sure if it was due to the mismatched recovery, but I figured I'd wait.

I'll guess I'll have to try it tonight then. I'm hesitant to tempt fate with a friday-the-13th build, but I won't be able to resist.

 

[goapy]

What I initially suspected was wrong.

My dopinder is broken. It shot up blue smoke and won't shot any life.

I need to find time to debug it and get one of the lineage devs to get me a UART log.

It's true that lineage-19.1-20220513-recovery-dopinder.img won't boot from a device that is otherwise stock.

But I installed the lineage-19.1-20220513-UNOFFICIAL-dopinder build by means other than by using the build's recovery installation method, and it boots fine.

I installed the com.netflix.ninja apk that I had pulled from the actively running dopinder stock system on the 19.1-20220513 build, and it installs and runs! Very exciting.

I didn't check if using the build's dtb/dtbo before attempting to boot the build's recovery would make any difference, because I didn't know if that could mess up the stock system before I'd even have a chance to try to boot the build's recovery.

 

[hp420]

Sorry to ask what's quite obviously somewhat answered somewhere, but I've read through and can't find how people are getting 18.1 running on dopinder if it's broken and reported to bootloop. is there some adp method or something i'm missing?

 

[goapy]

I didn't check if using the build's dtb/dtbo before attempting to boot the build's recovery would make any difference

I've found that by flashing dtb.img, dtbo.img, and boot.img from lineage-19.1-20220513-UNOFFICIAL-dopinder.zip, in addition to flashing the recovery image (lineage-19.1-20220513-recovery-dopinder.img), the lineage-19.1-20220513 recovery will boot on dopinder coming from a device that has a factory build installed.

However, when attempting to repeat these steps again from the beginning (after flashing back the factory firmware), I noticed that the dirty data partition flag got set, but when it got set, it did not boot to the lineage-19.1-20220513 recovery that was installed, it just didn't boot.

So, I rebooted and executed "fastboot erase data" and "fastboot erase cache", and then it functioned properly. These steps need to be inserted somewhere in order to have a reliably repeatable process.

Of course, it is fine just to use the 18.1 recovery (instead of the above steps) until this gets fixed, because the recovery partition will be overwritten to the 19.1 recovery as part of the installation anyway.

 

[kennkanniff]

If you're stuck in a recovery bootloop, you should first try writing back a misc partition that does not contain the recovery flag. If that doesn't work, try tricking the device by redirecting recovery to boot, i.e., build this u-boot:

run_command("mmc dev 1; setenv lock 10100000; setenv recovery_part boot; save", 0);

I still have one device that is stuck with bad recovery that was on unrooted stock. I cannot connect to the device over ADB and am unable to enable wireless ADB because it is unrooted.

Is there a 'run_command(...);' that boots straigth to bootloader? I can compile u-boot myself.

 

[retyre]

Is there a 'run_command' that boots straigth to bootloader? I can compile u-boot myself.

Try:

run_command("mmc dev 1; setenv lock 10100000; save; reboot bootloader", 0);

 

[kennkanniff]

Try:

run_command("mmc dev 1; setenv lock 10100000; save; reboot bootloader", 0);

Already tried that. Does not work. Thanks though.

 

[goapy]

I cannot connect to the device over ADB

Why is this the case? Is this inability particular to the version of the factory build that you have installed? Where is the failure? Are the dev options not available, or does adb over usb just not connect?

Already tried that. Does not work. Thanks though.

Since your device is exploitable and unlocked, have you considered installing fred's boot-from-usb ubuntu build?

Fred's ubuntu build preceded the unlock method release, and at the time of its release would have been of no use for a situation like yours because any attempt to modify the emmc system from the temporarily usb-booted system would cause avb to fail.

But since your device is unlocked and exploitable, you could use the temporarily usb-booted ubuntu system to dd a factory recovery image back to the emmc, and avb wouldn't be an issue. Fred's method also enables aml v2 factory burn via the reset button, which could give you another vector to write the recovery partition using the update utility via burn mode. The same methods could also be used to write a magisk-patched boot image to the boot partition.

Using an update command with burn mode may also provide a method to instantaneously boot to bootloader fastboot, without even rebooting the device.

The only issue you may run into when trying to do this is that the bootloader version may be stale relative to the bootloader that is currently installed on your device, so the bootloader used, or fred's method of disabling anti-rollback detection may need to be adjusted to take into account the bootloader version currently installed on your device. Also check if the temporary system uses its own environment.

 

[npjohnson]

Already tried that. Does not work. Thanks though.

Replace "reboot bootloader" with "fastboot"