Announcement

Collapse
No announcement yet.

Hacks already available here.

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hi, I have patched also imx179.ko for F60B, that is the version 128Kb long. I tried it on original F60B firmware, the one you had patched for me, and it looks it is doing something. I have also changed libcedarX to the one you have patched for better audio, but it does not work on my F60, audio is always 8K. At least it doesn't crash it either.
    Attached Files
    Last edited by plutonio; 10-25-2016, 08:32 AM.

    Comment


    • thegamut
      thegamut commented
      Editing a comment
      it needs libCedarX and libvideoresizer together. The latter was pretty much the same on both FWs and I'm still running it from the russian guys' release.

    • plutonio
      plutonio commented
      Editing a comment
      Unfortunately they don't work on my F60, installing both prevents booting :-(
      I tried to open them in IDA, and while I was able to find the code you have shown in libvideoresizer, in a different address than yours, unfortunately I was not able to find it on libCedarX

    • thegamut
      thegamut commented
      Editing a comment
      Did you try both original libs together? And also open both libcedarx side by side and you should see where they moved the variables to. I think when I patched mine one of the addresses was slightly further down. You also have the option of booting with the 2 I patched from the 360 camera. So that is at least 3 pairs to try.

    • petesimon
      petesimon commented
      Editing a comment
      plutonio hello. i'm trying to swap some of my .ko / .so files with modded files from here. does this file imx179-ko-128k.zip (18.3 KB) do some things more or better than the previous two imx179 ko files (on page 9 i think) ?
      Last edited by petesimon; 11-15-2016, 09:16 PM.

    • plutonio
      plutonio commented
      Editing a comment
      Hi petesimon, sorry I only now saw your comment. I hope you have found out, I saw that there are two different imx179.ko in the various firmwares (actually 3...) and I have patched both in the same way using the settings from thegamut posts. They are of different lenghts, 1 is 128Kb, and the other 313Kb. I swap the one corresponding to the firmware I'm patching.

  • So an update. My unit is still running, but only records in 720p with the firmware I loaded. This is still my same unit as posted previously. Mine indicates the model as being a F60R, for Remote control, and I am guessing a few other differences. Still, audio is now not recording.
    I have the same model coming from MFG this week, I would like to download a complete image from the device to upload here, and to try on my crappy device. Maybe someone here can benefit from it.

    Also, I was thinking of adding an external mic jack that turns the internal on and off when external is plugged in. This should help the quality of audio capture?

    Comment


    • petesimon
      petesimon commented
      Editing a comment
      DId you get F60R from ebay like this http://ebay.com/itm/291926249955 ? Because I saw these posts about a F60 (I have F60B model) but with a 2.4G radio remote control, I bought a generic one from ebay http://ebay.com/itm/182238229189 and hoping it has Allwinner and Android. If I can, I will provide the firmware backup here so you can try to use it.

    • goobnoob
      goobnoob commented
      Editing a comment
      Thank you petesimon! I have gotten a firmware back up from a duplicate device, and posted that back up firmware for others to play with or use.
      I believe that Ebay unit is similar, but the case is different. I got mine on through amazon.

    • petesimon
      petesimon commented
      Editing a comment
      goobnoob nice. and the remote control works again? I received that generic ebay camera with remote today. Nice price $42 USD.
      It's Crane SL609 Xiapc 20160913V1.0. Here is its backup.
      https://www.dropbox.com/s/ofdvy4oa9z...X-IMG.zip?dl=1
      ( or shorter link http://bit.ly/GenericF60Rcranesl609xiapc20160913IMGFEX )
      Last edited by petesimon; 11-16-2016, 03:20 PM.

    • nutsey
      nutsey commented
      Editing a comment
      petesimon Is the PCB color of this cam red?

    • petesimon
      petesimon commented
      Editing a comment
      nutsey - see https://www.goprawn.com/forum/allwin...=1057#post1057

    • goobnoob
      goobnoob commented
      Editing a comment
      Camera works perfect now with the image file I am uploading. I would love the sound to be better but really not sure how to go about fixing that via software..
      Remote, wireless, and sound are functional back to the factory spec of the unit. Thank you guys for all your help.

  • Depends on the mic you plug in and the electrical quality of the connector. The real help came from 44100 at the expense of 2 megabits off video bitrate.

    Comment


    • I have a RODE video mic that is made for DSLR recording. Has gold plated male stereo connector. It seems that internal only takes sound from mono, so I would combine mic channels and mount a female plug that goes to the inputs of the standard MIC.

      I have backed up firmware from a second unit, and restored that firmware to the unit I was having problems with.. So at least I have it saved. I wish there was a place to upload it to for you guys to mess with if you wanted.

      My video in low light really sucks, the sound really sucks, but everything is working, remotes, etc, just like it was new again. Though I did disconnect the speaker because it was driving me up a wall.

      How would I go about improving the sound and video quality of my build, I've been reading but due to some mental disability, having some difficulty getting through it.

      Thanks for your help.
      Here is the original firmware stats from Phoenix in case someone wants me to upload it somewhere.

      Comment


      • never seen tansuofaxian, that is a new one. A lot of the patches are broken out in the 360 camera thread. IDA disassembler can show you a more readable version of files and you can compare vs the patched ones. If the firmware has the same symbols usually everything except SDV can be pulled from another version.

        post to mediafire, filedropper, dropbox, etc. you can make an account using temporary emails.

        rode is huge. Most of the mics I come across for this purpose are mono XLR and then feed into a preamp or mixer if you want to break them down to normal mic input. works well on a C100 or DSLR but for a camera this tiny it might be better to just record into another device and match it to reference sound in post. the 44100 sound is acceptable off just the onboard but the 8k is good enough to match external recorded audio.

        Comment


        • goobnoob
          goobnoob commented
          Editing a comment
          I will figure a good way to post the firmware. Thank you. I've been far out of reverse engineering for a while. I appreciate all your info, suggestions and guidance. I agree it would be better to just sync up another source, I just thought it would be cool to plug a Mic into the thing as I often record nature. I wish there was a way to capture super high speed video by tweaking, but I think there is not enough processing speed to accomplish that task.
          Thank you, I will get a way to upload this one. Its great because it has a wireless remote. I think I will be taking that a part too and post the images.

        • goobnoob
          goobnoob commented
          Editing a comment
          Here is the link..

          http://www.filedropper.com/tansoufax...54818test-keys

        • petesimon
          petesimon commented
          Editing a comment
          goobnoob Im curious about your backup here so i want to get it. But filedropper has so many ads/popups/redirects Could you upload your backup to a file host with few or no ads (dropbox, yandex-disk, mediafire) please?

        • thegamut
          thegamut commented
          Editing a comment
          i had no problems while using ublock origin. as for over-cranking, not much to be done without reversing the sensor registers and what they do. getting close to 120f is hard enough and the quality is hardly there.

        • goobnoob
          goobnoob commented
          Editing a comment
          petesimon it is nearly impossible for me to upload files. Sorry about the ads, but it does work, and it is genuine. If you have a link to something open for me, I'd be glad to post, but I don't really want to create accounts.

        • petesimon
          petesimon commented
          Editing a comment
          goobnoob okay. good idea to make an online folder for people to upload files.
          *EDIT* Please upload backups to one or both of these online storage. I put my different backups and support files there too. Here are two drop folders.
          PM me https://www.goprawn.com/privatemessage/new/46 and I will write the password to you. Please don't share the password.

          UPLOAD FIRMWARE to my dropbox.com without an account
          link - https://www.dropbox.com/request/NUqzrXSnEOR72QUz3kLn
          - Notice: valid firmware files only. but spam junk files will be deleted
          - I will post your firmware to www.Goprawn.com forums and to my Facebook group.

          Let me know if it works or does not work. Cheers.
          Last edited by petesimon; 05-19-2017, 02:09 PM.

        • goobnoob
          goobnoob commented
          Editing a comment
          I have been away, but will upload those files petesimon. Thank you for the links, I'll catch up tomorrow.

      • Hello, everyone!

        I would like to ask your help in restoring the camera I have. I tried to update the firmware as per instructions their (seller's support) have given me, and now the camera is dead. Well, display in not showing anything, camera is not recognizable via USB (Win 10), no sounds coming of it. It powers up though and charges, but I would imagine these functions are not controlled by the OS.

        They didn't instruct me how to keep the old firmware, just gave me full_img.fex files. So I don't have any backup.

        The camera is WiMiUS Q1, on V3 chip. IDK what sensor is has...

        Could you please help me here with instructions?

        Cheers and thank you in advance!

        Comment


        • petesimon
          petesimon commented
          Editing a comment
          hello. if you haven't done so already, i recommend that you post this message and future general messages in this other thread "Allwinner V3 + Sony IMX179/s and Omnivision OV4689 action cameras".
          https://www.goprawn.com/forum/allwin...action-cameras

          If you have it, share here the full_img.fex and any other firmware files from the seller's support, or from a download or from you own backup.
          You may upload files to here https://www.dropbox.com/request/NUqzrXSnEOR72QUz3kLn
          - Notice: valid firmware files only. but spam junk files will be deleted
          - I will post your firmware to www.Goprawn.com forums and to my Facebook group.

          I'm not an expert about this procedure. there are probably other ways to reach the same result. but I would try these steps myself. It's all for Windows.
          download drivers. "F60_ADB_driver" and "F60B_recovery_driver" should work, but try others if you need to. PdaNet (drivers) sometimes works magic for various generic/chinese devices. when you will install them, disable "signature verification" blah blah whatever its called if you see this popup.
          https://www.dropbox.com/sh/aylp0e0u6...J0pUdC4ba?dl=0
          also try this Universal ADB driver
          http://adbdriver.com/downloads/

          extract PhoenixSuit. Remember this folder PhoenixSuit_V1.10. you may need drivers later from that folder. do _not_ run it yet.
          https://www.dropbox.com/s/ap8rbbuj4t...V1.10.rar?dl=0

          power on camera normally. do not touch or hold any buttons at this time. okay, connect usb cable to pc and camera. if there is no display or menu on the camera then let's hope for the best. if there is a display/menu then choose charging mode (down button twice, OK button once). as alternative, maybe disconnect/reconnect usb and choose pc camera mode (down button once, OK button once.)

          Option 1.
          follow this tutorial video

          and maybe view this tutorial video for more info


          Option 2.
          with camera power on normally and usb connected, open Device Manager, look for a new unknown device, and update/install ADB drivers.
          download - https://www.dropbox.com/s/bnbk25odwq...river.zip?dl=0 - if this driver does not work, then try others in the dropbox folder
          https://www.dropbox.com/sh/aylp0e0u6...J0pUdC4ba?dl=0
          for example this Allwinner driver may work better for you
          https://www.dropbox.com/s/00lsleegrj...river.zip?dl=0
          afterwards go into PhoenixSuit_V1.10 folder. and run PhoenixSuit.exe . in Windows10 you may need to run it in Compatibility Mode for Windows 8 or lower. and hopefully you should see something like this

          click - https://www.goprawn.com/filedata/fetch?photoid=1009
          text there is your camera's type and firmware date. match that info with firmware on page one post #8 in the other thread. however, be careful. you also must match the right sensor and LCD, or your camera will again show a white (or black) screen or just not work at all.

          Option 3.
          you could also use android-debug (adb.exe) in command prompt
          info - http://www.teamandroid.com/2016/06/1...ivers-windows/
          download and install adb executable - https://www.dropbox.com/s/gm5vrz0j9x...setup.exe?dl=0
          also install F60B ADB drivers - https://www.dropbox.com/s/bnbk25odwq...river.zip?dl=0
          you may try this other Allwinner driver - https://www.dropbox.com/s/00lsleegrj...river.zip?dl=0
          open command prompt (cmd.exe), go to your adb folder usually in C:\adb and run these commands:
          adb.exe shell cat /system/build.prop | more > build.prop.txt
          start build.prop.txt
          a lot of text will be there. look for "ro.build.display.id" and the text after that is your camera's type and firmware date. something like
          ro.build.display.id=crane_sl603tsfx-eng 4.2.2 lzm 20160514 ...
          now minimize that notepad window for 'build.prop.txt' and run these commands in command-prompt:
          adb shell cat /system/res/cfg/320x240.cfg | more > 320x240.cfg.txt
          start 320x240.cfg.txt
          again, a lot of text will be there. look for "[firmware_information]" and under this line you will see three more lines of text "product_type=", "software_version=" , and "updated=". Remember the text after the equals signs '='. This is your software version and camera type. Note: sometimes this text is not there.

          and match all the info with a firmware file on page 1 post #8 of other big Allwinner V3 ... thread.

          Option 4.
          get a copy of Phoenixsuit 1.10
          power OFF camera. Remove battery! remove SD card. disconnect usb cable! press and _hold_ UP button on side of camera. again, press and _hold_ UP button. but do _not_ press power/mode button. connect usb cable. A new unknown usb device "usb device(vid_1f3a_pid_efe8)"
          will show in Device Manager (devmgmt.msc) and if you see it then right click for "Update Driver Software" on that new unknown device and choose to browse for drivers in the PhoenixSuit_V1.10 folder (AW_Driver | ADB_Driver folders are there) or get these drivers https://www.dropbox.com/s/ittv0ulwwe...ivers.zip?dl=0
          also try drivers from "F60B_recovery_driver". and update/install the drivers. there are so many different android devices, I sometimes have to try to load different drivers to make it work. Maybe also disable "signature verification" blah blah whatever its called if you see this popup. go to page one post #8 in the other thread, download, build IMG for PhoenixSuit using 'makeimg' tool and flash every firmware using PhoenixSuit in the list there until your camera works either fully or partially. we can fix the "works partially" problem later.
          'makeimg' download - https://www.dropbox.com/s/tothsp7rgv...prawn.zip?dl=0
          also follow the video tutorial posted above...

          Option 5.
          otherwise, get a #00 (about 1mm to 2mm diameter) screwdriver and disassemble the camera completely and take photos of the circuit board and sensor front and back. post all the photos in the other thread. we'r looking for a V3 chip and either a OV4xxx or IMX179x sensor and some printing on the main board. hopefully someone can determine which type of camera you have.

          Option 6.
          ask others here for help. Buena suerte. Cheers
          Last edited by petesimon; 08-01-2017, 02:44 AM.

        • Euk
          Euk commented
          Editing a comment
          Thank you petesimon! Helped a lot!

      • Hi !
        Sorry for my english, i'm french ^^ but I will try to be clear.
        I bought a Excelvan Q6H that I updated with a Fuxin IMX179, ST7789v (shows 20161110V2.3) with Andoer logo firmware (the last one that seems to be compatible with my cam).
        But the quality image isn't really good...
        What I hope to do is : Increase the bitrate, desactivate the noise reduction, set the iso at 100. I think that's all that I can do to increase the image quality ?
        So I unfex the firmware, and extract the files with squashfs. I understood that I have to modify imx179.ko (correct me if I'm wrong), but with HxD it's very difficult to read the file.

        Wich software do you use to read the files ? And to edit the files ?

        Can you guide me in which lines I have to modify to increase the quality ?

        Thanks a lot

        Comment


        • First you need to unpack the 2-system.img by executing the squashfs tool in cygwin (at least if you are runnning windows 10).
          You can use IDA demo to decompile the .ko file, but I've not been able to edit anything in there. So you might use HxD to edit and IDA only as reference.
          Also I didn't find out where to make those changes. Unfortunately I've not enough time playing around with it.
          But you can also check this thread on dashcamtalk.com:
          https://dashcamtalk.com/forum/thread...amdroid.20507/

          There is a lot done by thegamut. But also in this thread on goprawn (page 2-3) there are a few information about increasing image quality, but I've not managed to apply them yet.
          Hopefully you got some skills and enough time to improve it!

          Comment


          • Thanks for your answer.
            That's exactly what I understood and what I did but I didn't find where I have to make changes...
            If thegamut can do a guide, it's will be perfect ! Because AllwinnerV3's cameras seems to have a good potential but the actual quality isn't exploit it at all...

            Comment


            • Originally posted by nutsey View Post
              What about creating a simple guide for Allwinner V3 FW modding?
              Yes please! But I don't think anyone is interested in changing the boot logo.
              I'm dreaming of a guide that goes something like this....
              -First backup your camera firmware.
              -Optionally download a new firmware from the list
              -Use ..... to extract ..... from ..... etc etc etc
              -Take .... that you extracted and convert it to ..... with ...... etc etc etc
              -Open that file with ..... that your can download here ...... Or alternatively use your favourite text editor. Dissamebly? etc etc etc
              -Search/locate appropriate values/mem locations and make modifications.
              -Here's a list of men locations/values that we know of so far and known valid values.... 0x123blah bitrate, nr reduction on/off etc etc
              -Save file. convert with..... repack with ---- etc etc etc etc...

              Appologies if this information exists buried deep within comments on posts on some other thread, but I can't for the life of me find them.

              Pretty please can you give us some precious infos so we can tinker aswel, without reinventing the wheel!
              Last edited by TequilaKez; 04-20-2017, 06:08 AM.

              Comment


              • Hello All,

                So please forgive some noob questions if they're totally off track.

                My cam is a IMX179 crane variety with 20170502v3.3 fw shipped, featuring horrible NR and over-sharpening. Discussion on this forum has mentioned (and members shared) modded imx179.ko files. Another poster mentioned there are 3 different varieties of these files in different FW's, most noticably differing in size (128k, vs 300+k, etc.). So to use the modded imx179.ko 's, is it just a matter of unfex a FW, replace the imx.ko with a modded one, refex, and flash?

                Similarly, discussion here touched on improving sound recording by modding libraries. What software and steps does this require?

                Thank you!
                Lex K
                Last edited by LexK; 07-27-2017, 08:04 PM.

                Comment


                • hi guys. I've read all three, but I don't understand. are you creating new module or modifying existing one? if yes, there is any rom to try?

                  Comment


                  • Hi people,
                    i know this is a years old thread, but i seriously need support.

                    I'm new here, and i apologize going straight to the point.
                    I had a Campark Xtreme II UHD 4K double lcd cam as a present, which has a terrible quality output in every format i try to use.
                    I'm a photographer and retoucher, recently entered the video editing world...and Campark's ISP output makes .mp4 nearly uneditable.
                    The problem is terribly high noise reduction, too high contrast and saturation and bad sharpening (all those things could be reasonably edited in postprocessing, if only the cam had a "pure" output).

                    Campark Xtreme II UHD 4k double screen has:
                    SoC:
                    Allwinner V3
                    Product:
                    fuxin4k30doublescreenimx179s-sdv
                    Manufacturer:
                    lzm
                    Short id:
                    fuxin
                    OEM id:
                    zhongxing_ir
                    Camera type:
                    fx2830
                    FW orig. date:
                    20170721
                    FW mod. date:
                    20170425
                    Camera name:
                    ACT76
                    Version:
                    C 20170725 V2 3
                    LCD model:
                    1 errors occurred. (2 lcd, rear and front)
                    LCD resolution:
                    320x240
                    LCD count:
                    2
                    Sensor model:
                    IMX 179s

                    I followed all the procedures to extract firmware, get full_img.fex, extracted script.bin from full img, but when i try to convert it to human readable format (fex) i get error from bin2fex (GPIO BANK error).
                    No success also with uberizer, which outputs me an empty fex file. I'm stuck here, and i feel like i'm so near...yet so far.
                    The only settings i'd like to correct are NR, sharpness and some bitrates, no fancy logos or other similar mod.
                    Can you please help me?

                    Comment


                    • nutsey
                      nutsey commented
                      Editing a comment
                      ISP settings are not in script.bin. You need to unpack system partition and edit the main binary - /bin/sdv (bitrate) and sensor driver - /vendor/modules/imx179s.ko (ISP settings + more).

                    • aw4ken
                      aw4ken commented
                      Editing a comment
                      Oh wow! Such a fast reply!!
                      So, i was searching in wrong files...i’ll check files you suggested as i get home and let you know!
                      I will also provide a firmware backup for this camera (20170725 seems not to be listed) since is one of amazon’s bestsellers and could be useful...
                      Thank you so much!

                    • aw4ken
                      aw4ken commented
                      Editing a comment
                      Ok well, i unpacked system partition.
                      I know ii may sound quite dumb, but can you explain me how to edit those files?
                      I probably need an editor because those file are only partially human readable...


                  • What about creating a simple guide for Allwinner V3 FW modding?
                    Last edited by nutsey; 11-06-2019, 03:50 PM.

                    Comment


                    • Originally posted by jhoney00 View Post
                      What about creating a simple guide for Allwinner V3 FW modding? https://9appsapk.vin https://vidmateapp.vin https://vlc.vin
                      Even I was thinking about the same haha
                      Last edited by smithclarkson01; 03-09-2020, 01:05 AM.

                      Comment


                      • petesimon
                        petesimon commented
                        Editing a comment
                        me too.
                    Working...
                    X