Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Ematic 7" Pro series EGP007BL

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #46
    As an update, I can play with my Nexus 4 just fine in Lubuntu; but have nothing for the eMatic tablet.

    I can't figure out if there's a setting I have wrong other than "Android Debugging" is enabled. Wish I could get ADB to see this thing...

    -Eric

    Comment


      #47
      If you want i can Help you via TeamViewer.
      Just write me a Message to [email protected]

      For Team Viewer just Download this:


      Neomode

      Comment


        #48
        Works

        Got it working thanks to neomode!!!

        I had to put the device ID 0x2207 into the adb_usb.ini file located in c:\users\myname\.android\adb_usb.ini. I had done this previously, but windows decided it knew better and would name the file adb_usb.ini.

        After that was straightened out, I had to go back into the driver (last night after my dinner neomode) C:\Android SDK Tools\extras\Google\usb_driver\android_winusb.inf and add the device hardware ids again. (Like an idiot I forgot I screwed with it a few days ago and changed a bunch of values that apparently made the adb-usb.ini not work function.)

        ;ematic GP007BL
        %SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
        %CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01

        under [Google.NTx86] and [Google.NTamd64]

        I uninstalled the driver for the tablet and reinstalled again, and voila! It sees it now!

        Beyond this I have no idea what to do but whatever I can do to help, let me know.

        -Eric

        Comment


          #49
          Originally posted by rccardude04 View Post
          Got it working thanks to neomode!!!

          I had to put the device ID 0x2207 into the adb_usb.ini file located in c:\users\myname\.android\adb_usb.ini. I had done this previously, but windows decided it knew better and would name the file adb_usb.ini.

          After that was straightened out, I had to go back into the driver (last night after my dinner neomode) C:\Android SDK Tools\extras\Google\usb_driver\android_winusb.inf and add the device hardware ids again. (Like an idiot I forgot I screwed with it a few days ago and changed a bunch of values that apparently made the adb-usb.ini not work function.)

          ;ematic GP007BL
          %SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
          %CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01

          under [Google.NTx86] and [Google.NTamd64]

          I uninstalled the driver for the tablet and reinstalled again, and voila! It sees it now!

          Beyond this I have no idea what to do but whatever I can do to help, let me know.

          -Eric
          That´s good News.
          You are able to Dump the Rom ?
          If so please gave it to me or i can help you.

          Neomode

          Comment


            #50
            I thought the ROM was dumped already? Weren't we looking to dump the kernel now? Or are they the same thing?

            Sorry for my n00bness I'm still learning.

            You're more than welcome to help me again if you'd like.

            -Eric

            Comment


              #51
              I need a new Dump because the last Dump we make did not Work right.
              When you can make some with my help this would be great.

              Thank´s a Lot !!

              Neomode

              Comment


                #52
                I found the tutorial on dumping the rom; I was able to get rkdump on the tablet and have been trying the following:

                /data/rkdump /dev/block/mtdblock4 /sdcard/backup.img

                However, it gives me the following response:

                unknown images <00 00 00 00>
                root@android:/_

                I also typed cat /proc/mtd and was able to see the table
                dev: size erasesize name
                ....
                mtd1: 008000000 000040000 "kernel"
                ....
                ....
                mtd4: 17c000000 000040000 "backup"
                ....
                ....
                ....
                ....
                ....

                Changing the "mtdblockX" to make X 1, 4, 9, any number, i still get the "unknown image <xx xx xx xx>. Sometimes all zeroes sometimes not.

                Ideas?

                -Eric

                Comment


                  #53
                  Originally posted by rccardude04 View Post
                  I found the tutorial on dumping the rom; I was able to get rkdump on the tablet and have been trying the following:

                  /data/rkdump /dev/block/mtdblock4 /sdcard/backup.img

                  However, it gives me the following response:

                  unknown images <00 00 00 00>
                  root@android:/_

                  I also typed cat /proc/mtd and was able to see the table
                  dev: size erasesize name
                  ....
                  mtd1: 008000000 000040000 "kernel"
                  ....
                  ....
                  mtd4: 17c000000 000040000 "backup"
                  ....
                  ....
                  ....
                  ....
                  ....

                  Changing the "mtdblockX" to make X 1, 4, 9, any number, i still get the "unknown image <xx xx xx xx>. Sometimes all zeroes sometimes not.

                  Ideas?

                  -Eric
                  Yes for some reason rkdump is not Working on some Tablet´s.
                  Try it so.

                  But in a SD Card to your Tablet:

                  Then Type:

                  su
                  cat /proc/mtd
                  then you see the Listing
                  then make dd if=/proc/mtd/mtdblockxx of=/sdcard

                  make it with Kernel System Boot Recovery ...

                  After this connect Tablet to PC and Download the Dump, and please Upload it.

                  Thanks

                  Neomode

                  Comment


                    #54
                    I can do SU and get the # sign, cat /proc/mtd works as before.

                    However, when I type

                    dd if=/proc/mtd/mtdblock4 of=/sdcard

                    I get the following:
                    /proc/mtd/mtdblock4: cannot open for read: Not a directory

                    The same error happens with 1, 2, 3, 4, etc. None of the mtd1/mtd2/mtd3 works.

                    I'll keep playing with it but I may need a little guidance again

                    -Eric

                    Comment


                      #55
                      May i was wrong can you try it with this:

                      dd if=/dev/mtdblockxx of=/sdcard

                      Comment


                        #56
                        Hmm... Still get the "cannot open file for read. no such file or directory" error.

                        Is there a way to chase the folder names up to the root directory so i can find it manually? Or do we just have to keep guessing and checking?

                        Thanks for the patience. Eventually this thing will give it up...

                        I should ask does "mtdblockxx" = "mtdblock1" and "mtdblock2" or does it need to be 01/02/03...?

                        Also, is it mtdblockxx or just mtdxx?

                        -Eric
                        Attached Files

                        Comment


                          #57
                          AW: Ematic 7&quot; Pro series EGP007BL

                          it is /dev/block/mtdblock0 and tho on.
                          If you can't get Block 4 than there is no Backup Image. Then Dump the Rest.

                          Neomode

                          Send from my SG3

                          Comment


                            #58
                            I see!

                            It appears to have worked! I don't see a /dev file in the root directory of the tablet, so I am confused as to how you knew it was /dev/block/.... I need to do some research.

                            I have kernel, boot, recovery, system, backup all copied over to the root of the tablet. For some reason it didn't outfile to the sdcard even though i typed of=/sdcard/xxxx.img. Oh well.

                            I am currently putting them in my dropbox folder (if I have enough space left) which I can share with you when it's done uploading, or if there's somewhere else I need to upload them to let me know!

                            Thanks,

                            -Eric

                            Comment


                              #59
                              AW: Ematic 7&quot; Pro series EGP007BL

                              Thanks a Lot! When I got this Stuff we will have a Custom ROM in one Day.
                              Because the Rom itself is finished

                              That's right it is in the Internal Memory because SDCARD is internal Rom.

                              Neomode

                              Send from my SG3

                              Comment

                              Working...
                              X