Not sure why nobody replied to this. It's completely safe. Your device will downregulate it's charge to match what it was designed to accept.Can anyone tell if the discussed devices have any problems with chargers more powerful than recommended 1000mA?
The power supply for dopinder is piece of garbage, but nowadays it's not too easy to find a high-quality replacement with equal power, so I would like to power it with 2.4A, but still afraid to burn something.
Thank you! I really still waited for any response, but was afraid to force my inquiry too much. Now I can
After reading #853, and @kennkanniff 's advice, I was able to upload 18.1 recovery again without error. Going to order a usb-c adapter, to boot ubuntu and try to dd the factory recovery.
./update partition recovery lineage-18.1-20220324-recovery-sabrina.img
Flashed recovery without errors.
That makes sense. Good to know.
When in USB Burnmode, I get errors while trying to use fastboot;With the exploit that you reference above, you can also use the update utility to start bootloader fastboot directly.
./update bulkcmd fastboot
You could try erasing the data and cache partitions (using bootloader fastboot) to see if the 18.1 recovery (that is already flashed) will then be able to load. That has worked for me before.
./update bulkcmd fastboot AmlUsbBulkCmd[fastboot] [AmlUsbRom]Inf:bulkInReply failed: ERR: AmlUsbBulkCmd failed!
./update bulkcmd fastboot AmlUsbBulkCmd[fastboot] AM_REQ_BULK_CMD_Handler ret=-110,blkcmd=fastboot error_msg=error sending control message: Connection timed out [AmlUsbRom]Err:rettemp = 0 buffer = [fastboot] ERR: AmlUsbBulkCmd failed!
Device was new out of box (MFG 09/2020) with factory os installed.
fastboot oem unlock
That is the expected normal response when "./update bulkcmd fastboot" is executed successfully, the "failed!" notice notwithstanding.
That part of the instructions is sort of a generic instruction that doesn't really apply to sabrina or any of the supported devices.
Even though it's not possible to execute any fastboot commads. You talk about executing them through "bulkcmd fastboot" right?That is the expected normal response when "./update bulkcmd fastboot" is executed successfully, the "failed!" notice notwithstanding.
After executing the above, you should immediately be able to use bootloader fastboot, without doing anything else at all whatsoever. You just use it right then, after the result above is displayed, without touching the device or rebooting.
./update bulkcmd fastboot getvar unlocked AmlUsbBulkCmd[unlocked] [AmlUsbRom]Inf:bulkInReply failed: ERR: AmlUsbBulkCmd failed!
Thank you. Yes. I'm pretty sure the exploit worked and the device was successfully unlocked. I flashed Lineage 19.1 using adb through Lineage recovery.
Aight. Thatnks for clarification.
No, the fastboot commands are not executed through the update utility.
I've had one of these Fios Stream TV Gen2 sitting around for a while- now that Coreelec supports S905x4 devices I'm wondering if you've gotten anywhere with it? You should at least be able to boot off a USB flashdrive- I'm not even talking about rooting it. I can't even figure out how to get into recovery mode reliably.Thanks! It's too bad that usb burning mode is increasingly being disabled in new model devices. The askey ASK-STI6220 (S905X4) doesn't have it. The uboot menu is missing "update - Enter v2 usbburning mode". They've replaced it with a distinct version of fastboot (different than bootloader fastboot and fastbootd). Even masking the rom brings up only this mini version of fastboot. And it is no where near as capable as usb burning mode.
This should probably be discussed in a different thread. But to answer briefly, the post to which you responded was merely about modern amlogic SoCs (such as the X4, Y4 and others) replacing "v2 usbburning mode" with "Amlogic DNL protocol". Askey's sti6220d315 (verizon stream tv v2) is one device to which this applies. I describe this slightly more thoroughly in this thread.I've had one of these Fios Stream TV Gen2 sitting around for a while- now that Coreelec supports S905x4 devices I'm wondering if you've gotten anywhere with it? You should at least be able to boot off a USB flashdrive- I'm not even talking about rooting it. I can't even figure out how to get into recovery mode reliably.
I think it is...
Update to newest build on stock.Just got a dopinder from Walmart and read through all 48+ pages of this thread -- thanks everyone for all your contributions.
Before flashing the latest 19.1 LineageOS build, is there anything I should (or shouldn't) do with the device? Should I plug it in and let it update to the latest update (if one is available, depending what build it shipped with)? Or does it really not matter one way or another if I'm going to flash LineageOS?
Just want to make sure they didn't do something screwy like lock the bootloader and/or disable unlocking, etc.
Thanks in advance.
Yup, give it 2 days. TVs lastBuilds still in progress by chance? Just checked and the folder still looks empty here: https://download.ods.ninja/Android/lineage/dopinder/
I cannot thank you enough for supporting all of these devices! Greatly appreciated!
- Your warranty is now void. - You have been warned. - Use at your own risk.
adb reboot bootloader fastboot flash recovery lineage-18.1-20210805-recovery-dopinder.img fastboot boot lineage-18.1-20210805-recovery-dopinder.img adb reboot sideload adb sideload lineage-18.1-20210805-UNOFFICIAL-dopinder.zip # if successful then load bootloader and factory reset adb reboot bootloader fastboot -w fastboot reboot
this ended up being _wayyyyy_ to much, as this is the full value of the partition vs just the space to reserve, both will work, but we want to split it amongst partitions. One of our guys recalculated it and got it working.
Eh, soon, sure.It's been a month and a half since we discussed the possibility of the tablet-flavored (non-TV) release. It seems that the number of complaints has decreased and the basic quality of builds has improved enough to bother you again in this regard: are there any positive changes in this direction, or it is not worth expecting to get a full-featured Android on dopinder? (I'm still following this thread carefully to make a buying decision.)