Jump to content

nokirunner

Members
  • Posts

    69
  • Joined

  • Last visited

Posts posted by nokirunner

  1. 2 hours ago, jock said:

    Unfortunately the keep costs down, tv box makers use chips from unknown and unreliable sources, then happens that the vendor failed (at least rumors say so) leaving us with a very badly written driver. That is one of the reasons why I avoid cheap tv boxes when doing serious pet projects, a proper single-board-computer is much more suited.

    I can understand this reasoning ...
    But this makes me believe more firmly about the validity of the open source, if you have hardware working with opensoruce, even if the owner company is no longer available for any reason, the hardware always has the opportunity to improve ... I have become from my experience more convinced that it is better to invest in open source, I mean both in time and in money, especially if you are an end user, my experience is in the field of 3D in general, years ago there were many powerful and also expensive 3D applications, and people have invested a lot of time to grow on these applications .. over the years these have either failed or acquired from other competing houses and have been suppressed, some with very large communities that used that software, overnight the people who they invested in time and money on their growth around that software they found themselves "homeless".

    Fortunately today things are starting to change, because people are now accustomed to the traps of closed source .. I give a very obvious example, which I know well because of my field, and it is that of Blender , which in recent years, through online donations has grown a lot, because people, but also companies have understood that it is much more convenient to pay engineers who develop on opensoruce ...

    Moreover I am particularly enthusiastic because significant investments are also coming on the open-light hardware architecture ... in particular I am referring to the Risc - V ...
    the future will be interesting ..

    I apologize for the offtopic, now i return in the ranks.

    I expect in the future, projects with single board computer open source architecture, developed by the communities, where then the various farms print and distribute the hardware ... in the wake of how it happened with arduino and the whole world of electronics projects that are evolved more or less ..

  2. I answer a little to everyone to simplify ..
    Yes I was referring to the usb 3 of the pc,
    It is a pity that there are still companies reluctant to release the open source drivers and firmware of some hardware, yet they would all benefit us, the users who would have well-functioning hardware, and the farm maintainers who would have less time and money to invest to debug and operate at best their hardware ...
    stupidity take me away. 😁

    my only desire to have this tvbox operating with armbian is to set up an octoprint server so that I can remotely control my 3d printer while printing, so it is essential for me that wifi works, I only have two free usb ports , and in one I want to put a webcam and the other is connected to the 3d printer ...
    it is essential for me that it is always on, that  consume very little energy and so on ...
     

  3. @fabiobassa
    Probably it was usb 3, i don't know, for me this whole process was relatively new ..
    The strange thing to say, that the first backup I had done without any problems on a usb 3, so this is triggered me, it was also quite fortuitous to guess to try a usb 2.

    Back to normality , I can't activate the wi-fi on armbian, I removed it from the black list, and it shows the 2 famous wlan0 and p2p0 not activated
    Is there a possibility to bypass this problem or do i have to give up for the internal wifi  and using a usb wi-fi ??

    Do you think this problem is permanent, or is there a good chance that it will be fixed in future driver releases fot this wi-fi?

  4. @jock @fabiobassa Success!
    First of all I want to thank the two of you guys, and all the others too ..
    without you, I would not have experienced this new adventure, I certainly would not have got bogged down and I would not have come out of the sand afterwards .. certainly I have acquired a lot of important experience.
    now I will tell you how I managed to resurrect something apparently dead ..
     You already know the first part of the story ..
    I was about to give up, until I read the last suggestion of fabiobassa, to flash the original rom ... which in reality I had already downloaded and tried to flash without success with the first tool on windows, the rkandroid tool ... then going to check if the rom I had already found and downloaded was the same as the one suggested, I realized that inside the rar file there was another tool called factoryTool ... so, since I had tried them I have tried all this too .. this tool has the particularity of being a little more aggressive, it mounts and unmount the USB port where the device is attached until it can upload the various binary files and every time it used "wait mask rom" and I had to unplug the usb port and redo the clock short operation and I noticed that some times it failed and a couple of times for the first two small binary files, now I don't remember well it did "the ibl" and the loader I don't know .. but then the flash attempts kept failing, and asked me to unplug and replug the usb and do the mask mode ... until seeing that something was progressing, I decided not to un-plug on the usb 3 port that I had used so far, and to plug on the usb 2 port, and just I inserted the plug in usb 2 the rom flash started and it ended successfully ..

    Now what is the synthesis of all this? that after all the failures that I have had so far, just that it showed no signs of life beyond the mask mode, trying with this tool and changing using a usb 2 port I got immediate success, now I have no idea if the problem was due to the usb 3 or some "out of the ordinary" problems that really didn't allow me to restore the device had emerged ..
    Of course I was lucky and unfortunate at the same time, not that it was too serious .. in the end I would have lost 25 buks was something that I could let go ..

    the master of the tools that saved me
    uCYsIcL.jpg

  5. @jock
    apparently I can't flash from windows with that tool, it was the tool I used to make backups, and for some reason even if it see the mask rom mode it doesn't work as it should,  (I saw some demonstration videos) I'm afraid I did some hardware damage yesterday making random attempts to find the clock pin ... now I'm trying from linux with your instructions ....
    from linux the first thing i noticed, is that now the usb port is seen as 2207: 320b and it is like all the other rk2329 ... while before it was seen as 2207: 0002 ... now i am crossing my fingers hoping to have more luck ...

  6. fantastico...  
    I presume by the name that you are Italian  aren't you?
    Well thank you ... now I see to resurrect ..
    from stables to stars alle stalle  alle stelle again

    the fact is that this is also the first arm board for me .. and i didn't know that i had to be more careful ... the world of x86 and  android recovery of the phones got me used to it

  7. 23 minutes ago, jock said:

    @nokirunner

    I'm really sorry this happened :unsure:

    Everything seems odd to me, beginning from the unusual USB device ID, sdcard allocated to mmcblk1 (it should be mmcblk0) and now this unexpected brick.


    maybe it was mmcblk0, I don't remember well

    I installed from armbian-config
    I prepared the rom from your first page with the method of starting directly from sdcard suggested in the comments below.

     I had performed the hexdump before launching the installation but nothing had come out, it could not find the path of the file, there were subfolders, I promised myself to investigate better after the installation and instead I found the surprise.

    what do you think prevents the sdcard from starting now?

    @jock
    I got an idea, I have another identical engine, which I have for the other TV ... I'm thinking about it now, I try to start armbian on sdcard on that other machine and I tell you all the precise information, (of course I don't install anything on that tvbox)
    tell me if you need other precise information

  8. well .. my journey was intense but short, with your advice I managed to backup the rom, using the method suggested by @MFaust
    so sure that everything went smoothly, I started armbian from sdcard and I tried an installation on mmcblk2 ... I restarted and end of the race, the device does not start anymore, neither from nand that from sdcard.

    the strange thing is that it fooled me is that since the sdcard turned out to be like mmcblk1  and  the internal memory as mmcblk2  I didn't think it would even ruin the boot from sdcard.

    after which I spent all afternoon trying to debrick the device via mask rom, unfortunately my device is quite unknown and there are no examples on how it can be restored ... and those that seemed more similar to me, trying to create a short circuit between clk and grd on the nand memory, they did not work.

    my tv box is an  andowl q-m6 

    Spoiler

     

     

     


    the nand memory is a 16gb
    Samsung 641
    KVMTU000LM-B503
    GS062C9Z8EM

     

    I searched the in the internet, but I couldn't find the clk pin of this memory ..
    6OqzDGW.jpgTvwlb5u.jpg3cNyj7j.jpg

    looking better is an identical to this:
    https://forum.freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3229-devices/750159-scishion-model-x-android-8-1-rk-3229-2-16gb-5g-wifi-fast-lan

    https://forum.freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3229-devices/firmware-roms-tools-bg/754403-need-to-identify-my-android-box-and-find-firmware

  9. hello everyone, it is the first time I write in this forum, I have a tvbox based on rk3229 and I happily managed to boot armbian on sdcard, thanks to your advice, now I would like to install on internal memory but to do this I would first like to do a bakup  of android and here my problem arises .. first of all my device is an rk3229 with 2 gb of ram and 16 days of mmc memory m but when I went to try the rockchip tool to make the backup it tells me that it cannot find the device .. and in fact instead  of 2207:320b it is  2207:0006 ...  so I did a quick google search to see what it was and I arrived on the rockchip website which tells me that shoudl be an rk3066 (but is not)  and that flashes through fastboot, well it would not be a problem if it were not that after several attempts I could not get anything (I wanted to install the recovery twrp to make a backup etc) .. and I found that the bootloader is in security on, and I have no possibility to install custom recovery or different boot ..
    The even more odd thing is that I can access adb as root and write the android 8 filesystem via adb does anyone know how i can unlock the bootloader? or in extremis an alternative method to backup android in order to then install armbian in memory?
    the problem in what I fear is that I cannot write the recovery partition (I have not tried with the boot partition) I had also tried using dd to write on the recovery partition from armbian, but it does not give me write permission in any way, I did the same thing entering through adb shell by mounting in rw the android system, but nothing, I have no possibility to write the recovery partition.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines