After having tried several times to follow the guide for dopinder, now my device is stuck at boot screen.
Fastboot doesnt see the device.
What are my options?
Fastboot doesnt see the device.
What are my options?
Driver signing? What driver are you using?This thread has 84 pages and at least a handful of people have had the exact same issue as you, with others posting the solutions. It also doesnt help most lineageOS install guides are incorrect and assume everyone knows about driver signing on windows 10+ or needing to run fastboot with elevated privs. Then there's the "i dont want to read 84 pages to find the answers already posted" and i don't blame people, who has time for that.
Hold the button on the side of the device down, and plug the usb A male connector slowly into your PC until just the power pins make contact, then release the button. This will change how the device boots. After you do so, plug the usb A male connector fully into the port to allow a data connection. Your windows pc should make a "do doop" noise. Now see if you can get somewhere.
For future reference for Anyone flashing their android devices (outside of samsung devices). Linux is much easier to do it from and most linux distros can boot to a live CD without needing to install. All functionality of downloading files from firefox and installing the adb fastboot tools are available without installing linux. Both Ubuntu & Mint (debian based) and EndeavourOS (arch based) work great for this.
Google "Ventoy" for making a usb boot drive that you can use for multiple ISOs at the same time. You can partition space to allow a "permanent" storage area for said ISOs to write downloaded files to when booted into the live environments.
So, running them separately doesn't make much sense. `&&` says "run this after that if it succeeds" - this is on linux?Searching 84 pages is daunting! Although I only needed to read page 1 and page 84.
There are a few steps in the wiki linked on page 1 for Dopinger - Walmart Onn UHD Box that WOULD NOT WORK.
On this page https://wiki.oddsolutions.us/devices/dopinder/install under Unlocking the Bootloader < Step 5. It states to enter this command
fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock
The only way I could get it to work was typing each command separately
fastboot oem 'setenv lock 10101000;save'
fastboot reboot bootloader
fastboot flashing unlock
Then under Flashing the dtb and dtbo partitions it has 2 links for the required files...and one link is DEAD! The real place to find those 2 files is INSIDE the LineageOS zip that you download (the OS Install file. It's over 700MB) kudos @XDA-DB
Finally on Step 6 of Installing a Custom Recovery using fastboot. It states to type "fastboot reboot-recovery" but it never boots Recovery.
Power cycling the device then puts it in a state with NO fastboot or adb connection!
Unplug device. Hold button on device and slightly plug into PC until it powers on. When you see the Onn splash screen. Let go of button and fully plug in. You're now in Lineage Recovery that you installed. Again kudos @XDA-DB
fastboot - does not need root/sudo at all - it needs proper u-dev which is detailed on the wiki. You don't need to set MTP - ADB works just fine? I'm using it now.some special notes that could be added to the dopinder wiki as well.
Fastboot needs to be run as root (or sudo / doas) on linux
In order for dopinder to show up in adb, under developer options, set MPT on but turn off usb debug first or the stock OS crashes (does not occur under LOS). once MPT is enabled, re-enable usb debugging.
Onn's booting into another mode when detecting data causes trouble for quite a few.
And some advice for anyone looking to buy one of the devices: just buy a wade. dopinder has so many little issues (emmc burning out, overheating and freezing, the mtp slider crashing the OS, not booting recovery when connected to a pc). The only redeeming quality of dopinder is the remote (and the price).
You don't need to give me credit for anything, jim. I don't help others for e-clout.
Not everyone will read, not everyones native language is english, not everyone has the foundational knowledge. All we can do is try to make it as easy as possible. If those "who know" can offload the burden of the devs, they can focus on doing what they like to do best (unless you like herding cats then who am I to judge).
If you’re successfully in Lineage, just like with regular Android after turning on USB debugging, you can use adb to install any apk - “adb install <f-droid.apk>“Thanks to all of the helpful comments here in the forum. I thought I bricked two devices, but I was able to unbrick them through the usb trick given by XDA-DB given here in the forums. Very appreciative. I successfully got lineage os to boot, but there are no apps. Only "Settings." I saw the lineage directions to load the GAPPS on first boot, but I was not planning to use GAPPS, so I did not think it applied to my situation. I was planning to sideload F-Droid. I have attempted several times to sideload the F-Droid apk now and I'm being given an error "E: Failed to find binary META-INF/com/google/android/update-binary." I'm assuming I should have sideloaded F-Droid before first boot. Is it going to be possible to sideload the F-Droid apk or do I need to start over from scratch?
The compleate readout is:
Verifying update package...
E: footer is wrong
Update package verification took 0.1 s (result 1).
E: Signature verification failed (I click "yes proceed with the installation" here)
E: error: 21
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Install from ADB complete (status 2).
After this, I "Apply updates" and "Reboot System now," but there is no F-Droid app and nothing in the downloads folder. Any help would be appreciated. Thank you.
Wow, that was easy and yes it worked. For some reason I thought I had to sideload it. Thank you very much.If you’re successfully in Lineage, just like with regular Android after turning on USB debugging, you can use adb to install any apk - “adb install <f-droid.apk>“
You can also toggle on adb over wifi in the developer options, after which you’ll need to “adb connect <IP address>”
Adding to this:I just installed the newest nightly on a freshly bought wade.
Some notes:
- thanks for the hint with the button and usb cable to access recovery after the fastboot reboot-recovery not worked.
- don't use the included usb cable as it seems to not have data pins (at least eu version sold at amazon.de).
Sadly I cant activate Wifi. This seems to have been a bug in an older release. Any help on this?
thanks
lineage-19.1-20221113-nightly-wade-signed.zip fixed itI just installed the newest nightly on a freshly bought wade.
Some notes:
- thanks for the hint with the button and usb cable to access recovery after the fastboot reboot-recovery not worked.
- don't use the included usb cable as it seems to not have data pins (at least eu version sold at amazon.de).
Sadly I cant activate Wifi. This seems to have been a bug in an older release. Any help on this?
thanks
use the power button to select stuff in recoveryI just bought a dynalink (wade) device and trying to flash the LOS unofficial 20 on it. I followed the instructions as I have done also on 2 dopinder (ONN) devices. I can get into the LineageOS recovery fine but after following I cannot navigate using the button. I can only press and hold the button down which highlights "Reboot system now" by turning the selection green but nothing happens. Suprisingly I can use the remote control to navigate up and down on the LOS recovery, but when I hold down the circle (o) button, it does the same - just highlights the command green and thats it. So I cannot do `adb sideload` because in recovery I cannot select "Apply Update". I can only highlight it. I then tried to do the same with LOS19 recovery, but its doing the same thing. Am I missing sometime? The button appears to be working fine as it allows me to get into fastboot mode and reboot fine.
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Yeah, you used the stock recovery. You need to fastboot flash, then fastboot boot recovery, I'll update the docs.
For dopinder, it's needed right now.
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