1, added auto start recording after writing problem happened;
2, set the default VIDEO QUALITY to FINE which make the bit rate lower
to make sure the lower speed card works on 0806
3, solve the image flip problem after 180degree rotate under 1080P HDR

will add GPS signal counter in next version

download link:
http://www.mini0806.com/firmware/0806firmware-161115.zip

 


Comments

01/09/2017 5:35am

Thanks for supporting this project! You are the best!

Reply

Thanks for this post. This will help me update my GPS. I'm glad that you improve this product and I hope that you will have another product or programs that you will share with us in the future. all your products really help us to improve our gadgets and even their systems. I hope you will come up some new ideas in the future, I will wait until you post something new.

Reply
Laurentiu
02/18/2017 10:35am

Mini 0806, GPS was burned because of the heat, summer has passed. It worked only two months. It has been eight months since I have no GPS !. The seller is always busy and silent. But I have problems with the two cards, new Samsung 128GB. Chamber warns me, audible each time that storage space is insufficient ... but there is enough storage space.
I'm disappointed.

Reply
Michel
06/07/2017 2:22pm

I keep having memory card errors on a regular basis (twice a week) with this FW version. Example is: "errId=0xfffffff12017-06-07" in carderr.txt file.

Reply
Pete Burns
01/10/2017 1:58am

I can't wait until I try this new FW, I really hope it will finally get rid of that stopped recording and noisy I/O storage error message even with brand new Samsung Evo memory card - thank you very much for improving this product! BTW - is there any chance of skilled users to help you improving this FW? I am sure there are many IT and electronics guys over here, who could significantly help with eliminating all existing flaws and problems...

Reply
Rob
05/17/2017 1:17am

This firmware update still didn’t solve the noisy I/O storage error message. Each time I have to pull the plug out. It's driving me crazy.
Now I have figured out that you musn’t use slot A. Only use slot B!
It seems that solves this annoying problem with me!

Reply
Mikalai
01/11/2017 2:46pm

I have noticed that I/O error issue likely caused by weak battery. Capacity is insufficient to provide power until recorder completely shut down. This interruption causes last file corruption (sometimes even entire SD-card damage). As a result eventually this corrupted file cannot be deleted at next delete-wright cycle causing the I/O error.
It would really better if recorder shutdown starts immediately the external power is removed saving battery charge. Anyways if during accident power disappears it is clear what happened and it is really important to get the last file properly closed and saved rather than corrupted and unreadable.

Reply
Mikalai
02/04/2017 11:25am

Replaced battery. Installed external 3.6V Ni-Cd battery from cordless phone about a month ago. Also removed bezel plates surrounding slots which on my opinion may improve cooling. No I/O errors so far. However, it is winter time outside.

Reply
Mikalai
02/13/2017 5:57pm

OK Finally got IO error again on 160507 firmware after 30 minutes of operation. Long fa-fa sound until I turned recorder off. Turned on. Recorder shuted down by itself and no reboot. Rebooted manually and noticed there is no card detected. Cam was set to slot "b". Switched cam from slot "B" to "auto" - recorder started to operate normally. It is clearly software glitch which prevented SD card detection.

Mikalai
03/07/2017 9:42am

Had to replace NICd battery to larger capacity NiMh of about 960 mAmpH as it died. Still got IO error on 64GB card. Replace card to smaller capacity of 32GB. No IO error. Smaller card is using FAT but larger card is using exFAT. Suspect buggy implementation of larger card format. Firmware 160507 runs on smaller card just fine as long as battery is OK.

Mikalai
03/28/2017 1:50pm

Recorder stopped recording today in a middle of the trip (approximately after 20 minutes). FAT32, 32 GB card and firmware I stated before. Just few beeps and that's it. No reported I/O warning, just stop to operate. Rebooted recorder in a middle of a highway, it continued to operate normally. What is it? Additional bug? Or new appearance of old issue? I kept troubleshooting and repair this device for 2 years!!! I payed 170 bucks! Price of this device is 30 dollars. The rest is a technical support budget. What kind of expertise this technical support possess if this device have that multiple design flaws? If I know that this gadget is a piece of BS, I would buy recorder with GPS from Garmin at that time! Stay away from this crap!

Pete Burns
01/11/2017 11:27pm

Well, to my big disappointment - there is no difference at all, the problem stays the same - dashcam stops recording and doesn't start again, the only difference is no warning sound - it looks like they just managed to turn it off, the rest is unchanged - PLEASE FIX IT for real! My dashcam is hardwired and running all the time, so the reason for invalid files is completely different. And by the way, they are not locked or write protected, so they can be deleted without any problems. This entire writing problem is caused by wrong approach to the filesystem, writing is not reliable and not under control, it needs to be improved completely in order to work flawlessly. Investigation needs to be done first to find out, what exactly is the cause for any writing problems - H2TESTW is accessing the memory cards at much faster speeds and yet there is no memory error at all, not a single time, so the writing problem is definitely on the dashcam side. Sometimes there are no invalid files, which proves that the hardware is OK, otherwise there would be always some - so it must be definitely a firmware fault and skilled programmer has to be able to make it work 100%. Please try bit more, I am sure you can do it!

Reply
Pavlo
01/23/2017 5:33pm

Now I am testing my camera with new firmware. It also has Memory I/O error. First time it happened 3-4 months ago when internal battery died( 1 year old camera). Replaced battery but error still pops up once a day. What I did: replaced battery, changed camera settings from High to Low, use new Ultra High speed SD card (UI3), changed slots A to B, B to A, changed firmware, reprogrammed with DirectUSB, changed thermal compound on chip radiator. NO LUCK! Memory I/O error still here :(((( I believe it is board degradation.

Reply
Mikalai
02/04/2017 11:13am

You may have hardware failure which is not unusual. Software will not fix hardware.

Daimian Williams
01/12/2017 4:27am

Now going to test...

Reply
01/17/2017 5:11am

I downloaded this software.i am so impressive after the using that one.thanks for launching this software.

Reply
Pavlo
01/25/2017 2:23pm

48 hours of testing on highest video quality settings no "Memory I/O error". No corrupted files. Keep my fingers crossed.

Reply
Pete Burns
01/25/2017 11:13pm

What kind of info is this? What are the video settings? Memory cards details? Is the camera recording on both cards correctly? Have you looked at the file thumbnails to make sure none of them is invalid?

Reply
Pavlo
01/26/2017 6:17am

I am testing new Nov 2016 firmware. Video settings: 2304x1295, Super Fine. Memory card SanDisk 32 Gb, Class 10. Loop recording( 1 min file). Tested 48 hours in slot B, now 12+ hours in slot A. Now using just one card. No damaged files on card. No Memory I/O errors. No "blue light" issue.

Testing with Class 10 because before I had every 2-3 hours errors on that card.

Thomas Matthews
01/26/2017 12:11am

After 1 year, the DASHCAM is malfunctioning....CANNOT DO SETTINGS ???? tried.... LCD LIGHT SWITCHES OFF ...can't see what's going on... cannot UPDATE FIRMWARE of Nov 2016 ....it is on the MICRODISK but it is not FUNCITIONING...Please assist asap. Thanks Tom:-) 7.10pm/26.1.2017

Reply
Pete Burns
01/26/2017 7:25am

Is it just LCD backlight not working? Or the LCD is dead completely? You need to have at least some microelectronics skills to try to fix something like that...

Reply
Pete Burns
01/26/2017 7:03am

Pavlo, that is not very correct test - how many hours will it record to that 32GB memory card until it's full at that resolution? Few hours? Have you checked all the files every time the card got full? Or you just waited 48 hours and then checked those files? It would be much much better to try two 64GB cards at least, in both slots, to test bigger size cards, try 5min files (there are too many 1min) if there is any difference or not. In my case the video quality doesn't matter, so it is not about card speed obviously. The dashcam creates problems where there are not any and should not be any.

Reply
Pavlo
01/26/2017 9:01am

Ok. It is not complete test. Agree. Actualy I always use only one card in slot A, and I have back up card in my car just in case. Unfortunately, I don't have 64 Gb card. Only two 32Gb one class 10 and another UI3 High speed.
It is loop recording(1 min) it means card is always full. I check all files and all of them works. No damaged files like before.
I can try 5 min files for you but my opinion is better to have 5 files by 1 min then one 5 min file. In case file damaged u loose only one min of recording. :)

Reply
Pete Burns
01/26/2017 11:30pm

That's true, of course it depends on the intended use of the dashcam - primarily it is meant to record your driving, but in my case I use it more as video surveillance - and this Mini0806 with its dual big memory card capability is ideal for this application, so it can work as both dashcam and video surveillance camera - that's why solving this writing problem and creating of invalid files needs to be solved, because this camera is unique comparing to others regarding its storage space and it should stay unique, but not because of its firmware problems...

Pavlo
01/26/2017 9:25am

When I used lowest video quality settings I had less errors. For example 1280x720 Normal. High speed card less errors too. Believe me I tested! First year I used my old Class 10 card without any problems but later internal battery died and since that time something happened. Looks like hardware degradation. Even with new Li-on I had errors. Now with new firmware it works MUCH better!

Reply
Pavlo
01/27/2017 11:58am

Testing 4 days. So far, so good.

Reply
Pete Burns
01/27/2017 2:22pm

Yesterday I put empty formatted memory cards into dashcam, it started recording on card A - I came to have a look this morning, and recording stopped again, red light on - it stopped after few minutes of recording on card B - which was empty! So obviously there are more different issues, where the dashcam stops recording and doesn't start again, because now there were no files at all, so there was nothing to be deleted or empty space problem. I started recording again and it is still working, after many hours, that's completely strange. It looks like the dashcam lives its own life :-D Simply there are still many routines not behaving correctly and need to be amended - apparently some of them were corrected already, but it's still not enough. Especially switching over to another card and starting of recording after stopping for whichever reason. But the dashcam shouldn't stop recording in the first place, so they should focus on solving causes, not consequences.

Reply
Pavlo
01/28/2017 10:56am

Yesterday I had very similar problem. Turns my car on and camera starts too automatically but turns of immediately. No recordered files. Turned on manually and it starts recording. Strange!!!

Did you get message "Memory I/O error"? My camera( with old firmware) after that message ( red, green, blue lights all on) stops recording and 2-3 min later turns off itself.

Pete Burns
01/28/2017 12:19pm

Issue confirmed - I checked it this morning and recording stopped again - at the same position from beginning - 0:03:50 - I think exactly as yesterday, but this time in slot A - so it is different slot, different memory card, and yet - the same problem. The weirdest thing is, that it didn't do this before, god knows, how the main program is running and how they call different sub-routines, how they handle all the temporary data - because right after flashing firmware it changed memory cards correctly, it always starts later, so there has to be bug in the FW regarding this, it is definitely not a HW failure or memory card issue. These time there was no "storage I/O error" message as before, but what matters most - the dashcam stopped without any real reason at the same position at both slots and didn't recover from it, didn't start recording again as it is supposed to. So as far as I know, there are 3 main bugs still to be fixed:
1. non logical recording stop after changing to other memory card
2. creating invalid files with correct file size without any real reason
3. inability to start recording again after it stopped for whatever reason
But as we can see, they amended many different bugs and made this camera better, so I hope they will manage to fix these last important ones and this dashcam will become a truly unique one...

Reply
Mikalai
02/04/2017 11:19am

Hardware may have intermittent failures. Something may affect addressing.

Reply
Pete Burns
02/04/2017 12:06pm

This is clearly not such case - this is not intermittent, but quasi-random and yet regular, real HW failure would be affected by temperature changes, air humidity, vibrations etc - this is completely different story, the behaviour is roughly the same and it's getting worse with time - again, regardless of the video quality and according writing speed, used memory cards and their format type.

Woody
01/31/2017 8:14am

Tried this firmware update, it restarts the camera after an I/O error but goes straight into another I/O error routine.

Reply
Pavlo
02/01/2017 8:06am

What kind of I/O error?

Reply
Pavlo
02/01/2017 8:05am

Updated second camera. 2 days works fine.

Reply
Roman
02/03/2017 6:28am

Installed new firmware - still have 3 beeps , and then 3 beeps again once a while, but this time at least camera resumes recording.
This is improvement.
Tried to play with video settings "fine", "super fine" , normal .. still getting the same 3 beeps.
The card I have is SanDisk MicroSDXC Ultra 128GB SDSDQUAN-128G , should be OK based on specs (type 10 , XC1).
Tryed to reformat it several times - no luck either.

Reply
Pete Burns
02/03/2017 7:14am

Do you get any invalid files or not? I tested all resolutions, all quality settings and there is no difference, many invalid files as on lowest, so on highest setting, with different 64GB class 10 memory cards. Clearly the problem is not in memory card speed or format, the same for FAT32 and exFAT.

Reply
Pavlo
02/11/2017 6:38am

3 beeps and what kind of message? It is really strange that my 2 cameras starts working after update and no beeps signals, no errors.

Reply
Pete Burns
02/11/2017 2:03pm

I tested all options again, because someone mentioned the oldest firmware is the most stable one, although it doesn't allow to automatically switch between memory cards - and I can confirm, that it is not true, it also creates invalid files without any real reason, on the brand new memory card designed for dashcams - the only thing they "solved" is starting of recording again instead of switching off. But the most important thing here is - it is necessary to solve THE CAUSE, not the consequence! And because they are trying to solve it, but until now unsuccessfully, it means the problem is really there, I am not convinced at all, that "some" of these Mini0806 work OK - I am sure they are just not tested for long enough time for the errors to appear, because hardware-wise they are all the same. With a special software I managed to play even those invalid files and they are of correct size - it appears that the header is invalid, that's what causes them to be unplayable and invalid - but after skipping the header, the rest of the video and sound is OK, so this is the point they need to focus on - to find the reason, why there is invalid header written, causing the files to be invalid. Please focus on fixing the cause instead of consequence!

Reply
Pavlo
02/12/2017 6:49am

I did many things with my camera before update with latest firmware. Cleaned slot A,B contacts, reinstalled chip radiator with new thermal compound, used PC to remove old firmware and installed new... Who knows it could help+new firmware solve camera problem?

Reply
Pete Burns
02/12/2017 11:39am

Well - obviously new FW didn't solve the problem, when it's still there ;-) If one dashcam creates invalid files more often than others, there has to be some conflict (either HW or SW), which is on the very edge of all the related circumstances - the same for different memory cards (if one is better than others) - the problem is in the dashcam itself, not somewhere else, it has to accept any modern memory card, any resolution, any bitrate, and yet write correctly and create valid files, which are playable. If they release new FW with corrected writing routines, I will confirm immediately, whether it has been solved or not...

Pavlo
02/12/2017 4:15pm

Actually I updated 2 cameras. My friend has identical MINI0806. We bought them from Amazon 1.5 years ago. Both cameras came with stock OEM firmware and both of them after 1 year had battery issue. Since that time we start receiving memory I/O (3 beeps) error. I thought it is hardware degradation. But after update with latest firmware both cameras works like new. No any errors at all! No beep signals, no damaged files. Strange. I believe new firmware can solve one reason of 3 beep error but camera still has more reasons produce same error.

Miro
02/12/2017 10:43am

About "low card speed" error - in this version it's worse. With previous version after the error the camera stop responding to anything than turning on and of the screen after few minutes the camera was turning off and I could started it again. Now after the beeping - the camera again stops recording, it does not respounce to anything than power button for turning on and off the screen, but now it does not turn off. And I can't start it again if I don't cut the power - from the cable or turning off the whole car. Now instead of turning off, the camera beeps again with the warning from time to time but that's all. Some times the error happens after just 30 seconds from the starting of the car. Some times I don't have a working camera for more than the half of the time I'm driving. I use only one SD card - 128gb SanDisk. I've changed the slots from A to B and back again without any positive effect. Now I'm going to try with another sd card, but I use this card from the beginning and with older versions it was OK.

Reply
Woody
02/15/2017 6:44am

I have 2 of these, after the latest firmware update 1 of them is now working perfectly the other still crashes with an I/O error

Reply
Pete Burns
02/15/2017 12:06pm

This example definitely confirms my theory, that it is firmware fault, but related to some most likely hardware conflict on its edge - it could be interrupt request, some critical timing etc - causing exactly this type of error and results - certain hardware combination may work fine, while other fails - and this is again confirmed by many people, having problems with SanDisk, while other memory cards work fine. And I repeat again - the firmware must be adjusted to the point, where this critical problem will be eliminated and basically all hardware combinations have to work OK, including using any modern class 10 memory card, regardless of its capacity or manufacturer.

Reply
Pavlo
02/15/2017 6:20pm

Absolutely NO! For example camera 2 works in critical conditions video chip overheated. In this case you will get I/O error also. This camera has at least 4 well known hardware issues. 1. Poor GPS mount contacts due to "gold" coatings . 2. Internal battery. 3.Chips overheating due to poor contact between chip and radiator. 4. Out of focus. I can assume 2 more 1. SD card slot contacts oxidation. 2. not all MINI0806 have same hardware. Manufacturer can use "compatible" chips, transistors with similar(not identical) parameters.

Pete Burns
02/16/2017 7:23am

Absolutely YES! ;-) If it was caused due to chip overheating, if would behave completely differently, it would get worse with rising temperature - but it doesn't make any difference, whether it's cold or warm, it causes the same problems as after switching on, so after many hours of operation - at least in my case there is no relation to temperature at all - I tested it at 5 degrees in the car, I tested it in my office at 25 degrees - no difference at all. What I noticed in my case - there is no relation to either temperature, or memory card type, or video quality or bitrate. Nothing of that makes any influence on the dashcam failures, it has to be something else - and it's either firmware problem, or very specific hardware problem, but that is not very likely since they use original and working components. I wish we find out one day what the real cause is...

Reply
Pavlo
02/16/2017 11:05am

I'm working with two identical cameras and both of them have identical problems. We bought new cameras with original firmware appx 12 months no any issues. Used Sun Disk Class10 cards and highest resolution settings. Finally we got battery problem it can not hold charge. Ordered new battery and unplugged old one. SINCE that time camera starts making 3 beeps signal and shows Memory I/O error. So, problem appears only when battery died. Second camera had exactly same story - battery stops holding charge and 3 beeps with memory error on display. I expected new battery can solve this problem. I was wrong 3 beeps still here. Bought new high speed SD card and it improve situation a little bit. Before I had error every day but with new card one error in 2-3 days. Finally new firmware realised. Now both cameras works as it should with SanDisc Class 10 card. New card moved to my cell phone :)

Reply
Pete Burns
02/16/2017 1:46pm

You are luckier than others :-) But weak battery can't cause any hardware damage - and when rewriting firmware helped in your case, it is again evidence and confirmation of my theory - god knows what the firmware did during the battery failure, maybe there was some invalid writing of some registers or important information to a some kind of flash memory on the chip or something similar, and since then the dashcam kept failing, even after changing the battery. That's why updating your firmware helped to solve the problem, because it rewrote all the important information and allowed the dashcam to work properly again. But it didn't help in my case at all, which means the specific problem has to be found yet.

Pavlo
02/16/2017 4:24pm

Of course, weak battery can't damage hardware. My first idea was damaged firmware. I did update no luck. I used my PC to clean and reprogram camera- no luck again. If it is not hardware issue why camera continue shows Memory I/O error? I noticed that 8+ month old cameras produce this kind of errors. Newer new! It might be hardware degradation. For example, capacitor lose capacity and it can change I/O chip timing( or signal level). Why not? Firmware should consider similar situations. Basically, chip can accept I/O signal level 1 and up but real level some times drop to 0.9 and in this case we receive Memory I/O error.

gsxr
02/17/2017 12:12am

my camera doesn't even work anymore. right when I turn it on I get the frgmt error

Reply
Delta Bravo
02/20/2017 5:16pm

Here is what helped to relieve the symptoms in my case - low level card formatting.

Plug it into computer (I have windows 7) and format it but make sure to check off the "Quick format" option. So there is NO check mark there. Used FAT32.

It might take a while to format, but after that the card which I had a problem with worked like a charm for at least a week.

Reply
lolwut
02/21/2017 12:36am

so have you gotten the error again?

Reply
Delta Bravo
02/21/2017 9:26am

Yes I have. But not at the rate I was getting it before - once a week or so.

I am now thinking to try using a journaling FS like NTFS. Have anyone tried that? Hopefully camera will be able to write on it. Too bad I cannot plug in EXT3.. :(

Pete Burns
02/21/2017 10:29am

I noticed that FAT32 filesystem works better than exFAT, but that might just have been a coincidence, plus it also depends on chosen sector size, but what the most important thing is - the camera itself uses exFAT filesystem and it MUST operate correctly under that one, there is no way of demanding some other filesystems or special software or hardware - it needs to be made reliable as many other dashcams are - for example my ex-mini0801 has never had any problems whatsoever, regardless of any settings or used memory cards - and this has to be done on this mini0806 as well, no excuses.

Pavlo
02/22/2017 8:14am

My camera can accept FAT32 only. If I format as a exFAT it shows message "Not optimum format. Reformat Yes/No"

William R
02/22/2017 11:53am

So this is what i found, if you read my commits in the last firmware upgrade you'll see i was completely fed up and pissed. both my cameras would not work, stay on record, were beeping, and dying, and not auto card switching very frustrating. So i see this new firmware, grab one of the cameras, still cant find the other one because i had to hide it from the wife so she would quit bitching cause i wasted $300 on these things, and it let me down load this new firmware which it took. My only issue then was it wont hold a charge and would die immediately. So i did some research order a new battery, stock one was 3.7v at 200mh, got one that was 3.7 at 500mh so it might last longer when unplugged. it was a pain the ass to pull camera apart, i lost the spring and little steelie, found steelie, and to rigged up a spring, having to soldering these tiny ass wires from the battery to the small board also was a pain. Got it all back together, and she has worked. no three beeps, no locked screen, and it actually switches from card to card. its been running for a week. knock on wood i hope i fixed it. Now if i could remember where i hid that other damn camera.

Reply
kimono
02/25/2017 10:27pm

hey william, you made my morning! i'm still laughing... regards to your wife and wish you to find the lost cam :)

Reply
Leo
02/26/2017 10:57am

Are You able to put a battery change video on YOUTUBE.
If so leave the contact on this site,please.
Thanks.

lol
05/02/2017 10:40pm

since you posted this in february, does the camera work fine now?

Reply
Pavlo
03/03/2017 11:25am

Over 1 month. No errors at all.

Reply
Dave
03/09/2017 2:19am

Does this update make the full SD card issue disappear? I see all over the last release that the IO error is basically down to it not being able to overwrite the data thats on the card (basically loop doesnt work).

Reply
Alessandro
03/15/2017 12:28am

My experience:
Samsung 64gb class 10 U1; frequent I / O errors, blocked, three beeps, impossible to use.
Mixza 16gb U1;
Random I / O errors, three beeb, etc ... giving the impression hardware failure.
Toshiba 64gb U3;
no problem, perfect operation.
setting time 5 minute, max resolution, superfine.
fingers crossed ...

Reply
Alessandro
03/28/2017 11:22pm

Update
Test two weeks: stop recording, random, happened four times on different days, red LED on (not flashing) no sound errors, no corrupt files, just stop rec. reset switch 20 seconds, and then normal operation.

Reply
Alessandro
03/28/2017 11:23pm

Update
test two weeks: stop recording, random, happened four times on different days, red LED on (not flashing) no sound errors, no corrupt files, just stop rec. reset switch 20 seconds, and then normal operation.

Reply
random happens
05/12/2017 5:28am

Just my finding. Check if your window (GPS) mount is ok.
I have two cameras one front one back. I was having a lot of IO errors and card corruption issues in the front one, i thought it was the camera. So i switched the cameras, but i was still having issues in the front one even after exchange, so i started to investigate. Firstly replaced the power adapter. Still issues. Then i monitored the voltage on the mount it was ok. So then i set the camera to not let the display to turn off, and i found out when i hit a bigger bump or hole, the display flickered. I tried to wiggle the camera but there was no flickering. So i bought a new mount and from that on camera is working ok. Probably the contacts in the mount has deteriorated somehow.

Reply
05/12/2017 12:12pm

1) is it not possible to increase the size of the text on the screen? For warnings. Then we'd know what was going on.

2) It eats SD cards. Please specify if it is able to take xc and or hc.

Reply
Bill
05/14/2017 3:45am

Finally, after more than 18 months I have a working dashcam (at least for 2 weeks anyway!).

It was constantly shouting at me. I changed cards several times, then realised I had a bad battery one. Changed the battery (very warped plastic even though this is the UK) and it still persisted, though recordings seem to be fine.

With this firmware there has been no problems at all so far. Using a Toshiba 64Gb U3 formatted as FAT 32.

Best of luck everybody.

Reply
MARTIN WHITE
06/23/2017 2:01am

Is changing the battery easy?

Reply
Matt
06/19/2017 4:04pm

Since upgrading to this firmware I've had constant errors and the damn thing won't stop beeping at me. It's been unplugged and just sitting there, when are we getting a new update? And...can I downgrade the firmware back to a stable version?

Reply



Leave a Reply