[ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post Reply
User avatar
voodik
Posts: 1807
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 33 times
Been thanked: 200 times
Contact:

[ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik » Wed May 13, 2020 8:55 pm

Call for beta test : LineageOS-17.1 Android 10 for Odroid-C4

Avoid using Android on MicroSD cards!

android-10-logo.jpg
android-10-logo.jpg (24.98 KiB) Viewed 1206 times

How to install.
For first time you need prepare your emmc/sd with spercial selfinstall image.

Selfinstall Images with preinstalled Gapps
64bit You can find latest version here

Selfinstall Images without preinstalled Gapps
64bit You can find latest version here

Image flashing guide.
https://wiki.odroid.com/troubleshooting ... hing_tools

For Google apps please read this.
https://www.google.com/android/uncertified/
Also after you register your Android framework ID, please wait some time (30-60 minutes) then reboot Odroid and try to add Google Account.

Extra:
  • tvheadend
  • androidvnc server
  • aptX aptXHD ldac Bluetooth codecs
Changelog:

Code: Select all

20200513 Alpha-v0.1
* first alpha release

Last edited by voodik on Wed May 20, 2020 10:28 pm, edited 3 times in total.
These users thanked the author voodik for the post (total 3):
joerg (Wed May 13, 2020 9:41 pm) • mad_ady (Thu May 14, 2020 12:45 am) • odroid (Thu May 14, 2020 1:20 pm)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
voodik
Posts: 1807
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 33 times
Been thanked: 200 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik » Wed May 13, 2020 8:55 pm

Tips:

Root Access
The fix to support Odroid-N2/C4 has already merged on Magisk repo.
So Magisk should be work starting next Magisk release.
I create fixed version based on 20.4, so use it till new Magisk will be released.
Magisk-20.4

To enable GPS support

Code: Select all

Odroid Settings> Misc settings> Enable GPS (Most of USB GPS modules is Plug and Play)
If your GPS is connected to UART or not detected you need set proper GPS serial node manually.
Change this lines according your GPS dongle in /vendor/build.prop (adb remount)

Code: Select all

ro.kernel.android.gps=ttyS1
ro.kernel.android.gps.speed=9600
How to configure usb_modeswitch
You can find usb_modeswitch.conf sample config file in /odm/ partition.
Change this file depending your hardware, run usb_modeswitch and check logcat is everything ok

Code: Select all

usb_modeswitch -c /odm/usb_modeswitch.conf
If configuration working lets enable auto trigger usb_modeswitch via prop

Code: Select all

setprop persist.usbmodem_vidpid 12d1:1f01
Value 12d1:1f01 is VID/PID of device which need monitored.
If your device after switching return with ssame VID/PID to avoid loop set

Code: Select all

setprop persist.usbmodem_vidpid_same true
In this case every second device attach event will be ignored .


List of custom properties introduced by me

Disable Bluetooth service globally. If you don't have a compatible USB Bluetooth dongle BT service keep crashing.
So disable it by default.

Code: Select all

persist.disable_bluetooth true|false default:true
Enable/Disable Bluetooth A2DP Sink support

Code: Select all

persist.service.bt.a2dp.sink true|false default:false
Enable/Disable GPS support

Code: Select all

persist.disable_location true|false default:false
Enable/Disable WiFi power saving. Most of USB WiFi modules have a problems with power saving mode.
So Disable it by default.

Code: Select all

persist.enable_wlan_ps true|false default:false
Some AP have a wrong timestamp and Android framework filter out this AP.
If You don't see your AP in WiFi scan results set this property true.

Code: Select all

persist.wifi_fixts true|false default:false
WiFi Linkstats is feature depending driver implementation, at this moment almost all USB drivers does not implement this feature.
Some of them have Linkstats support but it working wrong and crash whole WiFi service.
So i disable it by default.

Code: Select all

persist.disable_wifi_linkstats true|false default:true
Enable/Disable Shutdown without confirmation feature.
Set it true if you want shutdown your Board without confirmation by POWER button long press.

Code: Select all

persist.pwbtn.shutdown true|false default:false
Device tree tricks
We can modify our dtbs from bootloader to Enable/Disable or change configuration of dtb nodes.
We can add those commands to boot.ini before bootm command.

Enable UART_EE_A(ttyS1) port on 40Pin Header (disabled by default)

Code: Select all

fdt set /serial@ffd24000 status "okay"
Enable GPIO Buttons (by default 4 GPIO keys konfigured as F7-F10 keys)
You can remap them at boot stage by changing "linux,code" value.
In this example we are change Button1 and Button2 to function as Volume UP/DOWN.
And at the last line we need Enable GPIO buttons (disabled by default)

Code: Select all

fdt set /gpio_keys_polled/button@1 "linux,code" "<115>"
fdt set /gpio_keys_polled/button@2 "linux,code" "<114>"
fdt set /gpio_keys_polled status "okay"
List of Linux keycodes
https://github.com/hardkernel/linux/blo ... des.h#L189

Google Services Framework Android ID
You can get it from Odroid Settings> Misc > GSF ID
To get GSF Android ID from cmd use this commands

Windows command line

Code: Select all

adb shell sqlite3 /data/data/com.google.android.gsf/databases/gservices.db 'select * from main where name = \"android_id\";'
Terminal app

Code: Select all

sqlite3 /data/data/com.google.android.gsf/databases/gservices.db 'select * from main where name = "android_id";'
Last edited by voodik on Thu May 14, 2020 1:18 pm, edited 7 times in total.
These users thanked the author voodik for the post:
joerg (Thu May 14, 2020 2:43 pm)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Wed May 13, 2020 9:37 pm

I definitely will install and check if all my apps do work on Android 10! For me first time for an Odroid device! :)

User avatar
voodik
Posts: 1807
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 33 times
Been thanked: 200 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik » Wed May 13, 2020 9:50 pm

joerg wrote:
Wed May 13, 2020 9:37 pm
I definitely will install and check if all my apps do work on Android 10! For me first time for an Odroid device! :)
Gapps included selfinstall ready ;)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Thu May 14, 2020 3:12 am

I was searching to enable root, but then I learned that LineageOS has dropped this and users must install by them self some su binary like Magisk.
I tried now to install Magisk, but without success. After reboot, it shows Magisk not installed. I used the latest Version 20.4. I have tried to install the zip like I published in How to.. thread and also with adb sideload in recovery mode. With both methods I haven't seen errors, but the Magisk Manager shows that Magisk is not installed.

User avatar
mad_ady
Posts: 7898
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 498 times
Been thanked: 348 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady » Thu May 14, 2020 3:24 am

You can enable root from Developer Tools, though you need to make that visible first.

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Thu May 14, 2020 3:31 am


User avatar
voodik
Posts: 1807
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 33 times
Been thanked: 200 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik » Thu May 14, 2020 12:24 pm

joerg wrote:
Thu May 14, 2020 3:12 am
I was searching to enable root, but then I learned that LineageOS has dropped this and users must install by them self some su binary like Magisk.
I tried now to install Magisk, but without success. After reboot, it shows Magisk not installed. I used the latest Version 20.4. I have tried to install the zip like I published in How to.. thread and also with adb sideload in recovery mode. With both methods I haven't seen errors, but the Magisk Manager shows that Magisk is not installed.
viewtopic.php?f=178&t=35690&p=290940#p290940
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Thu May 14, 2020 2:48 pm

This is really outstanding. I myself was thinking last days about how fdt can be used on Android. Now it's there. It's magic.

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Mon May 18, 2020 3:58 am

Hello voodik, I haven't yet tested all, but my App GpioShutdownService is working so far. Setting account is also working. Hearing music via usb audio adapter is working.
One thing that I had also with Lineage 16 is a gray background behind the clock widget. On LOS 16 I was able to make some settings for the widget and suddenly this grey background went away. If I put other widget to the home screen than ether this other widget or the clock have this grey background. Normally it should be transparent. This seems an issue with the launcher than with the widget it self. Here is an example:
Screenshot_20200517-210022_Trebuchet.png
Screenshot_20200517-210022_Trebuchet.png (926.33 KiB) Viewed 1059 times

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Mon May 18, 2020 9:08 pm

After booting several times this is looking normal now. The gray background rect went away... :o

User avatar
voodik
Posts: 1807
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 33 times
Been thanked: 200 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik » Mon May 18, 2020 9:42 pm

joerg wrote:
Mon May 18, 2020 9:08 pm
After booting several times this is looking normal now. The gray background rect went away... :o
In any case i am also take a look for this issue.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Thu May 28, 2020 8:44 pm

Hello voodik, I try to flash a new kernel and dtc, but when I use the one from hardkernel repo I get FDT_ERR_BADMAGIC and it stays at the u-boot prompt. Or do I have to use a kernel from your repo?

Code: Select all

sudo fastboot flash dtbs ../kernel/android/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dtb
target reported max download size of 134217728 bytes
sending 'dtbs' (69 KB)...
OKAY [  0.013s]
writing 'dtbs'...
OKAY [  0.026s]
finished. total time: 0.039s

User avatar
voodik
Posts: 1807
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 33 times
Been thanked: 200 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik » Thu May 28, 2020 11:10 pm

joerg wrote:
Thu May 28, 2020 8:44 pm
Hello voodik, I try to flash a new kernel and dtc, but when I use the one from hardkernel repo I get FDT_ERR_BADMAGIC and it stays at the u-boot prompt. Or do I have to use a kernel from your repo?

Code: Select all

sudo fastboot flash dtbs ../kernel/android/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dtb
target reported max download size of 134217728 bytes
sending 'dtbs' (69 KB)...
OKAY [  0.013s]
writing 'dtbs'...
OKAY [  0.026s]
finished. total time: 0.039s
In general i recommend use my kernel branch.
BTW
you flash wrong dtb. Right one is meson64_odroidc4_android.dtb
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Thu May 28, 2020 11:25 pm

Hello voodik, I tried this dtb also before I asked. But I will try again with your kernel branch.

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Fri May 29, 2020 12:21 am

I have the same with your branch. I found only: lineage-16.0_odroidg12_64. Or do you use another branch for Lineage17, that I haven't found?
When I fdtdump the generated devicetree I get:

Code: Select all

fdtdump ../kernel/android/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4_android.dtb

**** fdtdump is a low-level debugging tool, not meant for general use.
**** If you want to decompile a dtb, you probably want
****     dtc -I dtb -O dts <filename>

/dts-v1/;
// magic:		0xd00dfeed
// totalsize:		0x11be2 (72674)
// off_dt_struct:	0x38
// off_dt_strings:	0xfd60
// off_mem_rsvmap:	0x28
// version:		17
// last_comp_version:	16
// boot_cpuid_phys:	0x0
// size_dt_strings:	0x1e82
// size_dt_struct:	0xfd28

/ {
    model = "Hardkernel ODROID-C4";
    compatible = "amlogic, g12a";
    interrupt-parent = <0x00000001>;
    #address-cells = <0x00000002>;
    #size-cells = <0x00000002>;
    bifrost {
        compatible = "arm,malit60x", "arm,malit6xx", "arm,mali-midgard";
        #cooling-cells = <0x00000002>;
...
Can you compare it with yours?

User avatar
OldGaf
Posts: 109
Joined: Fri Sep 25, 2015 11:06 pm
languages_spoken: english
ODROIDs: U3 C2 C4
Has thanked: 5 times
Been thanked: 3 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by OldGaf » Fri May 29, 2020 1:28 am

Can I get away with an 8 Gig eMMC for this (at least for testing)?
Thanks,
-OG-

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Fri May 29, 2020 1:39 am

I use a 8 Gig eMMC. Everything was working until I tried to flash a new dtc.

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Fri May 29, 2020 3:20 am

-Compiled the kernel from your repo.

-Flashed new LineageOS17.1 image to emmc.

-Booting up.

-Backup of dtbs.img.

-Flashed dtb from compiled kernel.

Code: Select all

sudo fastboot flash dtbs ../kernel/lineage/linux/arch/arm64/boot/dts/amlogic/meson64_odroidc4_android.dtb

Code: Select all

Starting download of 72738 bytes

downloading of 72738 bytes finished
cmd cb_flash is flash:dtbs
lock state is NULL 
Writing to MMC(0)... done
lock state: 10000000
info->version_major = 1
info->version_minor = 0
info->lock_state = 0
info->lock_critical_state = 0
info->lock_bootloader = 0
partition is dtbs
Flashing Raw Image
........ wrote 73216 bytes to 'dtbs'
-Rebooted - FDT_ERR_BADMAGIC, stuck on u-boot prompt

Code: Select all

U-Boot 2015.01-00002-ge7e6aa702a-dirty (May 09 2020 - 12:52:02)

DRAM:  3.5 GiB
Relocation Offset is: d6ef1000
spi_post_bind(spifc): req_seq = 0
register usb cfg[0][1] = 00000000d7f84588
MMC:   aml_priv->desc_buf = 0x00000000d3ee17c0
aml_priv->desc_buf = 0x00000000d3ee3b00
SDIO Port C: 0, SDIO Port B: 1
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x172000
[mmc_startup] mmc refix success
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: driver version: v20190313
vpu: detect chip type: 12
vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz)
vpu: clk_level = 7
vpu: vpu_power_on
vpu: set_vpu_clk
vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100)
vpu: set_vpu_clk finish
vpu: vpu_module_init_config
vpp: vpp_init
vpp: g12a/b osd1 matrix rgb2yuv ..............
vpp: g12a/b osd2 matrix rgb2yuv..............
vpp: g12a/b osd3 matrix rgb2yuv..............
cvbs: cpuid:0x2b
cvbs_config_hdmipll_g12a
cvbs_set_vid2_clk
reading boot-logo.bmp.gz
27178 bytes read in 4 ms (6.5 MiB/s)
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]set initrd_high: 0x3d800000
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]VPP_OFIFO_SIZE:0xfff01fff
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=3840, height=1440
cvbs: outputmode[1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
[OSD]osd_hw.free_dst_data: 0,1919,0,1079
USB3.0 XHCI init start
Net:   dwmac.ff3f0000
odroidc4#
-Flashed back the former backup (original dtbs.img) with fastboot.

-Rebooted - FDT_ERR_BADMAGIC, stuck on u-boot prompt.

-Need to reflash the image :(

[edit]
Does fastboot something wrong?
The same happens if I flash a new boot.img with fastboot, stuck on u-boot prompt.

[edit]
When I flash the boot.img from adb console with dd if=newboot.img of=/dev/block/boot then it works.
I guess fastboot is writing to false address. Is the partition table different on LineageOS17 / Android 10?

User avatar
joerg
Posts: 1043
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 33 times
Been thanked: 73 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg » Fri May 29, 2020 4:35 am

Yes, and also flashing dtb this way is working: dd if=meson64_odroidc4_android.dtb of=/dev/block/dtbs

User avatar
voodik
Posts: 1807
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 33 times
Been thanked: 200 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik » Sat May 30, 2020 2:36 am

joerg wrote:
Fri May 29, 2020 4:35 am
Yes, and also flashing dtb this way is working: dd if=meson64_odroidc4_android.dtb of=/dev/block/dtbs
Its strange, Lineage-OS 17.1 use prebuilt u-boot from Lineage-16.0 . Thanks for report, i will check fastboot on Lineage-17.1 and let you know.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

Post Reply

Return to “Android”

Who is online

Users browsing this forum: No registered users and 0 guests