Dear after loging to box , what command i need to type , pls confirm , hope i am not irritating u
mount
and then
df -h
Posts by oottppxx
-
-
Many thx for reply dear , kindly explain in simple terms file attached herewith , 55b4eb74d9c8ffd6.jpg
How to unmount and mount
You need to telnet and login to the box: the username is "root", without the quotes... not sure what the default password is for openblackhole, if any... Try and search for it.
Once you're able to login to the box and get a prompt of "root#" (or very similar, ending in #), you can input commands.
To start without making any damage it's probably better if you collect the output of the "mount" and "df -h" commands, then paste it here, and we can take it from there... (use "exit" or "logout" commands to terminate the session or close it from your telnet client side).
-
Hi Friend , i have an issue with h7 as i was using internal flash pation and had installed 4 different images on it and every thing was fine as i was using multiboot image selector to switch between images , now recently i installed open black hole image in one of the internal flash partion , no issue is i am unable to switch other images which r installed on flash , is there any plugin / solution available to switch to other images which r installed other than black hole , pls reply thx
If you're hand with the terminal, login to the box, check if /dev/mmcblk0p1 (the boot partition) is mounted (but probably not), then copy the relevant STARTUP_1 (or _2, _3, _4) over the STARTUP file there, unmount, then do a "sync && reboot" - fingers crossed.
-
'Cept, it doesn't work in my case, hence xml.... But OK...
You mentioned your hardware (RAM) may be broken, XML isn't going to provide a miracle and fix it... Also, did you even try the XML I posted? That had 2 files, one of which was the fastboot...
-
That's an excellent tutorial, thanks Mahdi-Dz. I also see, from the pics, there's a tab in HiTool called "Burn Fastboot", which is probably all one needs to then do the rest via USB (and probably doesn't need any xml file to do it :-)
-
But, as I said, Combo/Twin/Maxytec are very different from H9s...
P.S. I think @baps said my RAM is actually screwed... which in English means "give it up - nothing you can do there..."??
Yes, we know those boxes are different than H9S, but they're similar to each other which was the point.
In English, that means "sell it for parts or give it away to someone with the tools and the inclination to replace the necessary components to fix it".
-
You probably don't even need an XML file, re-reading your opening post and the quote from some guy that puts only fastboot.bin on hiburn (which I presume is some section of hitool) you can probably just burn the bootloader directly to the chip then use the USB to load all the other files, as I suggested.
-
Display More
I don't get you now: we need H9S xml, not Combo/Twin.
We have Maxytec xml example in this thread.
Now, all you need to do is to DL and unpack H9S image, as you said it yourself, from OpenATV - yes?
Then, as you explained, when you unpack it, check the bootargs, was it? And so on... Well, you know what to do, why do you need me?
I mean, I do not have the box functional, I can not get in, that's the whole point, isn't it.... That is why I need the xml file for H9S...
I've checked the Combo/Twin because it's a very similar box, apparently, and I already had images around from when I was looking at something completely unrelated. The bootargs for the latter don't exactly match the XML (namely the order, the sizes actually might match), so now I went and checked the MaxytecMulti4k image and got the relevant bootargs line from there:
blkdevparts=mmcblk0:1M(fastboot),1M(bootargs),18M(recovery),2M(bootoptions),2M(deviceinfo),4M(baseparam),4M(pqparam),4M(logo),40M(fastplay),20M(kernel),20M(trustedcore),4M(misc),1024M(system),150M(vendor),306M(e2tv),256M(cache),50M(private),8M(securestore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) hbcomp=/dev/block/mmcblk0p13
This is pretty spot on with the XML, except for the name of the dvb partition (XML) which is named e2tv on the bootargs.
The 5 line XML I posted was from checking the bootargs from H9S, which is:
mtdparts=hinand:1M(boot),1M(bootargs),1M(baseparam),1M(pqparam),1M(logo),1M(deviceinfo),16M(kernel),234M(rootfs),-(others)
It's just that in the XML I only put the lines for the first 2 sections, boot & bootargs... As that's what I thought it was relevant... We can easily add the lines for the rest, taking the sizes from there, and the offsets is basically just starting at 0 and adding the size of all the previous sections/files (in this case offsets would be 0, 1M, 2M, 3M, 4M, 5M, 6M, 22M). We're left with the flash type parameter, which I guess it's "nand" instead of "emmc", and if hitool really supports this particular box.
-
I've looked at the h9combo/twin openatv image vs the xml, and that's why I'm stating the order isn't linear (or at least doesn't match up); where's this Maxytec image that should match up to the xml so I can take a look?
Edit: also, again, someone with a box and hitool needs to test all this, you can't have omelettes without eggs (and I don't have any eggs, nor chicken :-)
-
Define "not usable"?
The only thing that xml file is telling hitool is to read a couple of files from the file system (make sure to use the right ones for your box) and load them in the flash where the bootloader should go. The sizes are taken from checking the bootargs file for the h9s box under that openatv6.4 image I posted (and the files should be taken from there, too, or somewhere similar), the offsets are pretty straightforward for the bootloader as well. The only thing that changes is actually the partition name (again, taken from the bootargs file for h9s, but really not sure how important that is in the grand scheme of things).
After you, fingers crossed, recover the bootloader with hitool, supposedly you'd be able to flash a full image via USB, which is why I didn't bother trying to guess all the offsets (and order) of the remainder of the other files (sizes are easy because you just take them from bootargs, but the order not so much, although it _should_ be very similar to the h9combo/twin).
-
No, I can't do it because I don't have such box; I don't even have a windows computer to run HiTool, not that it matters because... I don't have such box.
Not sure what's your issue with the posted XML file... Your box is bricked, it can't really get much worse (pending catastrophic hardware issue).
I did post a XML file that might work; someone with HiTool should see what it says when it gets loaded (e.g., I'm not sure about the flash type value being "nand", but the rest should be pretty much on) - provided HiTool supports that box/the box supports HiTool.
No one is born knowing all this stuff, try and examine and ask questions to improve your knowledge. At some point you'll need to try something on your own box, using your own computer, and your own cable; if you need a step by step tutorial, just say so... Hopefully someone that can actually use HiTool steps up.
The XML is the least of your worries, so don't fret about it so much, because when you do, it really looks like you almost know what you're doing (in this particular topic, I'm sure you're very able in a lot of things that I or others are not, this isn't a diss,).
-
I wouldn't know how to do that...
Ahem...
You do know how to use a computer, and a text editor? It's not that complicated. Not sure what you're expecting others to do for you if editing a 5-line XML file is really that insurmountable. Have someone guide you through it, I've seen some nice folks even posting some hitool screenshots here, maybe they can even try the file for you to see if it's valid, even if not able to flash a real box.
-
Try creating a file which would be something like the attached - make sure you pick the right files for the box for both the fastboot and bootargs, and create the right path under the hitool directory.
-
HiSilicone cheap devices - but I am not aware of one exactly like that, with only 256MB...
So, we need an appropriate XML for 256MB eMMC...
I don't have any of those boxes, but this doesn't seem particularly difficult to do.
You probably need to modify the flash type to nand (maybe, not really sure) or similar - I also haven't ran or used HiTool.
The layout of the partitions can probably be derived from the bootargs in an image, e.g., from file
openatv-6.4-zgemmah9s-20201021_usb.zip, we extract and can see the following in bootargs.bin:
mtdparts=hinand:1M(boot),1M(bootargs),1M(baseparam),1M(pqparam),1M(logo),1M(deviceinfo),16M(kernel),234M(rootfs),-(others)
I'd imagine that, due to the way the image is structured, if you create a very simple xml file and restore bootloader on the first 2Mb of the flash with the fastboot.bin file (partition name = "boot", start="0", size="1M") and the bootargs.bin file (partition name="bootargs", start="1M", size="1M"), you'll probably be able to then flash a regular image via USB (again, this assumes restoring the bootloader via HiTool and serial port is successful).
-
Hi, is there a way / command that from shell allows you to immediately close an open plugin? In my case XCplugin, thank you.
Not that I'm aware of. You can of course restart the enigma2 process: killall -KILL enigma2 OR telinit 5; telinit 3 OR similar.
-
Display More
Hi,
I'm looking for a plugin to stream automatically from E2 box to VPS or PC.
Basically I have E2 box in 1 location with dynamic IP and want to watch channels in another location (fixed IP). No port forwarding option available in 1st location.
Is there that kind of plugin ? If not is there anyone who can make it for me for $$$ ?
Thanks in advance
Why no port forwarding option?
Have you looked into VPN solutions? E.g., zero tier?
Have you looked into port forwarding over SSH? E.g., location 1 has a keyed SSH session into location 2 and configures reverse port forwarding.
-
No worries; I've left the image up, but folks should now use the party.py script to create their own images if desired (or at least check the README there), with whatever number of slots they require, and making sure they understand the recovery options. https://github.com/oottppxx/en…tree/master/scripts/party
-
oottppxx how about the file hd51x8miS.img how and where to install it, please write in detail how to install
That was the first item in the README ;-)
I've updated it to make it a bit clearer, and provided a better hint. <- and just now highlighted the clue :-) Also added well deserved thanks to BazB!
-
Hello,
It should be pretty self explanatory, if you do some dev work on Enigma2 and have one of these, you might enjoy https://github.com/oottppxx/enigma2/tree/master/mutanthd51.
Hopefully it flashes alright, although I didn't try from the img file (I generated the image from the manually carved flash).
-
Display MoreDisplay More
How do you know the box can still ping the router when it's frozen? Do you see the traffic?
What seems to happen on these boxes, si that they run out of memory, and then you can't even exec() anything, so your script probably wouldn't be able to run anyway.
To try and avoid freezes due to running out of memory, I've an hourly crontab entry that calls the following:
sync && echo 3 > /proc/sys/vm/drop_caches
Hi, oottppxx and thanks for replying.
I'm quite sure the decoder can still interact with the LAN because I've set up a simple script which forces it to reboot in case it's not able to ping its own router.
The script has been inserted in my crontab list, of course.But if the box freezes due to out of memory, the script won't even run, so... :-]
