• Content Count

  • Joined

  • Last visited

About Ztrawberry

  • Rank

Profile Information

  • Gender
  • Location
    Dubai, UAE

Recent Profile Visitors

203 profile views
  1. Welcome back sir! I was about to send a message asking if you are okay due to the silence since 25-Jul :-)
  2. I installed the latest focal current 20200723 image and the new locale settings are a disaster. Just because my IP address is from an arabic country all my default locale settings are changed... On this image, you boot straight into root password change. This is a regressive move in my view, just because as an example your IP is from France doesn't mean you speak French etc etc etc. This is almost like websites where you cannot find the option to change your language... armbian-config should be used for this type of change, not a default change you cannot override at 1s
  3. Hi @DaviMesquita, yes with these boxes it is quite random due to all the hardware differences on the "same models". Personally I have found that looking at the various DTB files help (once you have converted them to DTS) and even managed to solve a few small issues for my boxes. BTW my SSV6051 loads perfectly and works on 2.4Ghz, which as far as I recall is correct since it doesn't support 5Ghz on the CSC RK322x image. You might want to test this one as well just to be sure. Here is my mntui output: One thing you can try is the DTB file c
  4. Ztrawberry


  5. Hi @moshem, I think something changed in the latest kernel. Mine was working fine a while ago with meson-gxm-q200.dtb. Then it got unstable and I even tried building my own images with no luck. I read somewhere that there is a timing change which was affecting some boards. This I believe introduced this instability. Some observations: 1) Sometimes eth0 would come up, work for a short while and then stop. Not even rebooting works and it remains hard down 2) I can see on my router that auto negotiation goes for 1Gbps, but my board is only 100Mbps. Did not find a place wher
  6. Not sure if this is related... Today I cloned the build scripts from https://github.com/armbian/build and created a legacy Ubuntu desktop image for CSC RK322x. Everything worked well and I only had to use Multitool again to install the NAND bootloader (previously I had the Debian test image from 2 days ago installed via StepNAND). After the bootloader reinstall it booted straight from the sdcard. Armbian-config works etc... I have to say this is a major milestone and well done @jock and team!
  7. I started from scratch and tried again on both Ubuntu and the Debian test images. Good news is that is worked. Only differences were I first erased flash, installed the bootloader and then the StepNAND image transfer. This may have made a difference since I had the Ubuntu desktop image installed previously or maybe not. Please note that I did not previously or today installed the original Android image first. General observations: * WiFi was not detected. I am not 100% sure, but I thought this worked in images from earlier this year when I selected the Generic option in rk322x
  8. Hi @jock, I gave this a go and unfortunately it failed and dropped to the busybox shell... The drop https://pasteboard.co/JdvdOY2.jpg Tried fsck https://pasteboard.co/JdvegbK.jpg Steps I took: 1) Used a know good multitool sd card (used it today to install the legacy image as well) 2) Simply booted and installed the image linked above via StepNAND Let me know if anything else you would like to test...
  9. Hi @jock, seems the download link is broken, it only links back to this forum...
  10. Hi all, Since the previous thread got closed due to not sticking to the topic box, I thought I will start a new thread. Let's try and avoid this turning into a general discussion... I have noticed that the price for X88 King (and variants like Pro) have significantly dropped. This intrigued me so I spend a few hours reading the thread over at 4pda.ru via Google Translate and it seems the stock firmware was very buggy initially. Over the last couple of months some OTA upgrades and custom firmware managed to greatly improve stability. Some questions remain as to whether
  11. Hi @Mark Khevin Rogacion, what worked for me multiple times from complete soft bricked state (once I did rkdeveloptool ef and the other time was when I wrote a legacy image to my NAND) was with AndroidTool 2.51 and a copy of the original firmware. Key is the workable firmware and watch out for whether it is NAND or eMMC. As long as you can get the device to be USB recognized you should be fine. In some cases you would need to press the reset switch inside the AV port, but in a worst case scenario you would need to short the NAND or eMMC pin. I found a picture on which chip and pin