Announcement

Collapse
No announcement yet.

Dumping ROM using ADB guide

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

  • #31
    Originally posted by soulhd View Post
    Hi everyone!

    I've been a while reading discussions in this forum after landing from Google some weeks ago looking for RK29 mod resource, but just registered myself today

    OK, I have this device:

    Code:
    shell@android:/ # cat /proc/cpuinfo
    cat /proc/cpuinfo
    Processor       : ARMv7 Processor rev 2 (v7l)
    BogoMIPS        : 407.77
    Features        : swp half thumb fastmult vfp edsp thumbee neon vfpv3
    CPU implementer : 0x41
    CPU architecture: 7
    CPU variant     : 0x3
    CPU part        : 0xc08
    CPU revision    : 2
    
    Hardware        : RK29board
    Revision        : 0000
    Serial          : 0000000000000000
    Code:
    shell@android:/ # cat /proc/mtd
    cat /proc/mtd
    dev:    size   erasesize  name
    mtd0: 00400000 00004000 "misc"
    mtd1: 00800000 00004000 "kernel"
    mtd2: 01000000 00004000 "boot"
    mtd3: 01000000 00004000 "recovery"
    mtd4: 1e000000 00004000 "backup"
    mtd5: 07400000 00004000 "cache"
    mtd6: 40000000 00004000 "userdata"
    mtd7: 00400000 00004000 "kpanic"
    mtd8: 1cc00000 00004000 "system"
    mtd9: 69200000 00004000 "user"
    I have followed the first post but when I tried to dump I got this:

    Code:
    shell@android:/ # /data/rkdump /dev/block/mtdblock5 /sdcard/update.img
    /data/rkdump /dev/block/mtdblock5 /sdcard/update.img
    unknown image (41 4e 44 52)
    What have I done wrong? I am sure my tablet has Rockchip processor.

    Please help..
    The cpuinfo on my Next7P-12 (YF031211****) reports identical cpuinfo. I am currently running Finless 1.2 root with GPlay and I am able to retrieve kernel.img and boot.img (which appears to be part of kernel.img).

    C:\Users\webwerkx>cd c:/adb
    c:\adb>adb devices
    List of devices attached
    NXM727HCF0123456 device

    c:\adb>adb shell
    root@android:/ # cat /proc/cpuinfo
    cat /proc/cpuinfo
    Processor : ARMv7 Processor rev 2 (v7l)
    BogoMIPS : 407.77
    Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
    CPU implementer : 0x41
    CPU architecture: 7
    CPU variant : 0x3
    CPU part : 0xc08
    CPU revision : 2
    Hardware : RK29board
    Revision : 0000
    Serial : 0000000000000000root@android:/ # cat /proc/mtd
    cat /proc/mtd
    dev: size erasesize name
    mtd0: 00400000 00004000 "misc"
    mtd1: 00800000 00004000 "kernel"
    mtd2: 01000000 00004000 "boot"
    mtd3: 01000000 00004000 "recovery"
    mtd4: 1e000000 00004000 "backup"
    mtd5: 07400000 00004000 "cache"
    mtd6: 20000000 00004000 "userdata"
    mtd7: 00400000 00004000 "kpanic"
    mtd8: 1cc00000 00004000 "system"
    mtd9: 89400000 00004000 "user"
    root@android:/ # /data/rkdump /dev/block/mtdblock0 /sdcard/misc.img
    /data/rkdump /dev/block/mtdblock0 /sdcard/misc.img
    unknown image (00 00 00 00)
    1|root@android:/ # /data/rkdump /dev/block/mtdblock1 /sdcard/kernel.img
    /data/rkdump /dev/block/mtdblock1 /sdcard/kernel.img
    kernel.img found (6963208 bytes)
    dumping...
    crc found (4 bytes, 0x750a6930)
    done
    root@android:/ # /data/rkdump /dev/block/mtdblock2 /sdcard/boot.img
    /data/rkdump /dev/block/mtdblock2 /sdcard/boot.img
    kernel.img found (985634 bytes)
    dumping...
    crc found (4 bytes, 0x3f98ad68)
    done
    root@android:/ # /data/rkdump /dev/block/mtdblock3 /sdcard/recovery.img
    /data/rkdump /dev/block/mtdblock3 /sdcard/recovery.img
    unknown image (41 4e 44 52)
    1|root@android:/ # /data/rkdump /dev/block/mtdblock4 /sdcard/backup.img
    /data/rkdump /dev/block/mtdblock4 /sdcard/backup.img
    unknown image (00 00 00 00)
    1|root@android:/ # /data/rkdump /dev/block/mtdblock5 /sdcard/cache.img
    /data/rkdump /dev/block/mtdblock5 /sdcard/cache.img
    unknown image (00 00 00 00)
    1|root@android:/ # /data/rkdump /dev/block/mtdblock6 /sdcard/userdata.img
    /data/rkdump /dev/block/mtdblock6 /sdcard/userdata.img
    unknown image (00 00 00 00)
    1|root@android:/ # /data/rkdump /dev/block/mtdblock7 /sdcard/kpanic.img
    /data/rkdump /dev/block/mtdblock7 /sdcard/kpanic.img
    unknown image (00 00 00 00)
    1|root@android:/ # /data/rkdump /dev/block/mtdblock8 /sdcard/system.img
    /data/rkdump /dev/block/mtdblock8 /sdcard/system.img
    unknown image (00 00 00 00)
    1|root@android:/ # /data/rkdump /dev/block/mtdblock9 /sdcard/user.img
    /data/rkdump /dev/block/mtdblock9 /sdcard/user.img
    unknown image (eb 58 90 4e)
    root@android:/ #

    In addition, I did try Finless' recommendation for cat /proc/mtd +1.

    Comment


    • #32
      Hi, sorry to bother, well... everyone. I'm trying to do a rom dump but my device isn't appearaing on adb; I tried unplugging, and uninstalling the drivers and plugging them back in and I get the same thing; Linux File-CD Gadget USB Device ready to use, and then, ADB doesn't recognize mt tablet, any ideas?

      Comment


      • #33
        Have you selected usb debug in settings.
        Thats needed for adb

        Verstuurd van mijn Freaktab met Tapatalk
        if you love my work please buy a coffee





        Comment


        • #34
          Yeas, usb debuging is selected. The strange thing is my computer recognizes the device as "RK2918 device", and when I go to device manager, it appears as "Linux File-CD Gadget USB Device". But ADB doesn't recognize the device.

          EDIT: I think I know what the problem may be; I have pdanet installed, which supposedly automatically recognizes any android device that is connected via USB teethering. I'll try and do a rom dump using ADB from another computer.
          Last edited by cowboyv; 08-07-2012, 05:35 PM. Reason: Edited entry

          Comment


          • #35
            What windows version are you on?

            If windows 7 you may have to add your device ID to the adb_usb.ini file.
            Using device manager get your device id.
            1) prop your ADB device whatever shows up in device manager.
            2) Select the details tab and using the pull down select "hardware IDs"
            it should show somehting like this:
            USB\VID_xxxx&PID_xxxx&REV_xxxx&MI_01
            So my Yuandao is
            USB\VID_2207&PID_0010&REV_0222&MI_01

            2207 is my device ID.

            Now go into c:/users/YOUR USE NAME/
            and you should see a .android folder. If not create it
            In .android create a file called adb_usb.ini if it is not there.
            Open that file in text editor and add that device ID in HEX format
            So I added 0x2207

            Reboot the PC and now ADB should have no problem finding your device.

            Bob
            "Przebacz im, bo nie wiedzą, co czynią"
            "Прости их, ибо не ведают, что творят"
            "Perdona loro perché non sanno quello che fanno"
            "Vergib ihnen, denn sie wissen nicht, was sie tun"
            "Vergeef hen want ze weten niet wat ze doen"
            "Pardonne-leur car ils ne savent pas ce qu'ils font"
            "Perdónalos porque no saben lo que hacen"
            "Oprosti im, jer ne znaju što čine"
            "Atyám, bocsásd meg nekik, mert nem tudják mit cselekszenek!"
            "Odpusť jim, neboť nevědí, co činí"
            "Πάτερ άφες αυτοίς, ού γάρ οίδασι τί ποιούσι"
            "Ojcze, przebacz im, bo nie wiedzą, co czynią"
            "Forgive them as they know not what they do"

            Comment


            • #36
              I tried running that. but when I open the adb usb file in .android it tells me "# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.# USE 'android update adb' TO GENERATE.
              # 1 USB VENDOR ID PER LINE."
              I opened adb to do the update, but so far nothing.

              Comment


              • #37
                Originally posted by domrad View Post
                8. type

                adb push rkdump /data/
                Here I had to type adb push rkdump /sdcard/ otherwise Permission was denied

                Originally posted by domrad View Post
                adb shell
                *if you see a "#" sign and a cursor next to it then we're good to go.. otherwise.. review all above steps as you might somehow got the previous steps wrong.
                After Typung adb shell, I had to type su to get # instead of $.

                Originally posted by domrad View Post
                10. type

                chmod 755 /data/rkdump

                *this will make RKDump executable
                Again, chmod 755 /sdcard/rkdump instead of chmod 755 /data/rkdump.

                Originally posted by domrad View Post
                11. type

                /data/rkdump /dev/block/mtdblock5 /sdcard/update.img

                *this will copy update.img on your sdcard which most dev needed to cook rom

                the end.
                Fisrt I typed cat /proc/mtd to see a list with the sections where in my case backup was in mtd4.
                Now I typed /sdcard/rkdump /dev/block/mtdblock4 /sdcard/backup.img
                to get backup.img which seems to be update.img onto my internal storage.

                Made with Arnova 8b G3 and Windows 7.

                EDIT:
                To Copy backup.img I had to pull the file via adb, I could not copy the file like copying images or music files. Am I right? Or is there an easier way, because not everybody would get the idea that adb has more commands than push and so on.
                Last edited by mufi; 08-09-2012, 03:24 AM.

                Comment


                • #38
                  Originally posted by MrWeelson View Post
                  Hi...

                  In case anyone else is easily confused like me when editing the 'INF' file :

                  You get your hardware ID, for my 10G2 it is : USB\VID_0E79&PID_1433&MI_01
                  Then find the following under the [Google.NTx86] and [Google.NTamd64]

                  ;Arnova 7b g2
                  %SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_143B
                  %CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_143B&MI_01

                  Change to
                  ;Arnova 10 g2
                  %SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1433
                  %CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1433&MI_01

                  then save.

                  May be just me but the original post confused me a little as it said to delete everything after the = sign and after the & under the first entry.
                  Easy to see what was meant once you've done it but it could confused a simple person like me!

                  Hope you don't mind me adding the slight clarification!

                  Cheers

                  i see now..that's where i got confused!! thanks man for the clarification..made a whole new finding!


                  hellfoot

                  Comment


                  • #39
                    abd doesn't see my Next7S tablet - Win7 shows it as a storage device

                    I have a Toshiba netbook running windows 7 ultimate (32 bit). I edited the group policies to prevent windows from putting in whatever driver it pleases.I edited android_winusb.inf to remove all other phone info and added the following:

                    [Google.NTx86]
                    ;NEXT7S
                    %SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01
                    %CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01

                    [Google.NTamd64]
                    ;NEXT7S
                    %SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01
                    %CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01

                    I added adb_usb.ini to the proper directory with 0x2207 as the contents of the file. I used USBDeview to change drivers.

                    With all of that done, in device manager, my tablet shows up as android phone >> android USB interface. In Devices and Printers, the icon shows up as a portable disk drive and right clicking on the icon shows that it is a storage device. However, there are no drive letters associated with it in USBDeview.

                    AND, when I enter adb devices at the command prompt, I get a blank line after list of devices.

                    I have been working on this for about two weeks, 2 to 6 hours a day, and am getting close to giving up. Any one have any ideas?

                    (Every Tom, Dick and Harry is named) Bob

                    If I have seen further it is by standing on the shoulders of giants. - Issac Newton

                    Comment


                    • #40
                      Thanks, this post was super helpful.

                      Originally posted by domrad View Post
                      What you need :
                      a pc, usb cable and, ofc, your android device with sdcard

                      What you need to download(if you havent got it yet):
                      Android SDK. here's the link on how to install it and download link.. http://developer.android.com/sdk/installing.html

                      USB driver of your device. http://db.tt/2Cm2KUV6

                      RKDump file. http://db.tt/plRFmRh6

                      Instructions:
                      1. enable USB debugging on the device
                      2. Download and Install android SDK (dont forget JAVA JDK if you havent got it yet)
                      3. now connect your device to your pc, you will see Windows will try to install appropriate driver for your device, if it installed properly then you're lucky, you can proceed to step 4, if not then we need to install the driver using USB driver you downloaded earlier, here's how..

                      3a. extract the usb_driver.rar you downloaded.

                      3b. open the folder you just extracted and look for android_winusb.inf, right click it and click open with, choose notepad.

                      3c. click start menu, and on the search bar, type device manager, then choose device manager on the search result.

                      3d. on device manager.. look for a not properly installed driver, on mine its arnova because i have arnova 7b g2 capacitive..

                      3e. right click on that driver --> click properties --> click on the details tab --> look for the hardware ids, it usually comes after device description on property section

                      3f. on the Value section, right click the shorter value and copy it. mine is like this... USB\VID_0E79&PID_143B&MI_01

                      3g. on the open notepad editing android_winusb.inf, look for this entries... there's 2 entries like this..
                      1 on [Google.NTx86] area and 1 on [Google.NTamd64].

                      ;Arnova 7b g2
                      %SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_143B
                      %CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_143B&MI_01

                      3h. change Anova 7b g2 to your device name or whatever you want, im sure it doesnt matter as its just a comment .. on %CompositeAdbInterface% entry, erase all value after "=" sign and then press ctrl+v(paste)... same on %SingleAdbInterface% entry but delete the "&" sign and any letters after it.
                      you need to do this on [Google.NTx86] and [Google.NTamd64] part. SAVE it and close notepad.

                      3i. on device manager, right click on not properly installed driver for your device and click update driver software, then choose browse my computer for driver software --> locate the folder usb_driver then just click next etc etc..until you finish installing the driver. ok so thats the hard part.. the rest is just easy..

                      now for the adb part..
                      4. copy RKdump file you downloaded on the same folder as ADB.exe, usually its in folder Program Files (x86)/android/android-sdk/platform-tools
                      5. click menu and on search bar, type cmd, right click cmd.exe and run as administrator.
                      6. on the cmd command prompt, type "cd\program files (x86)/android/android-sdk/platform-tools" without the quote.
                      7. type

                      adb devices

                      there should be 1 device on the list. otherwise review previous steps.

                      8. type

                      adb push rkdump /data/

                      if no error then proceed, otherwise, review step 4

                      9. type

                      adb shell
                      *if you see a "#" sign and a cursor next to it then we're good to go.. otherwise.. review all above steps as you might somehow got the previous steps wrong.

                      10. type

                      chmod 755 /data/rkdump

                      *this will make RKDump executable

                      11. type

                      /data/rkdump /dev/block/mtdblock5 /sdcard/update.img

                      *this will copy update.img on your sdcard which most dev needed to cook rom

                      the end.

                      note: if you want to copy any other part of your device partition.. look in here http://androtab.info/rockchip/devel/rkutils/
                      I could only dump the backup image in my case. Using the i97D which looks exactly like the Cube 9GT2, running the same RK2918 firmware.

                      Comment


                      • #41
                        Thats good though! backup.img is actually the full ROM! Well thats IF the manufactirer actually flashed backup.img. Many do but I have seen cases where it was not flashed.

                        So backup.img can be treated as a update.img and now can be taken apart.

                        Bob
                        "Przebacz im, bo nie wiedzą, co czynią"
                        "Прости их, ибо не ведают, что творят"
                        "Perdona loro perché non sanno quello che fanno"
                        "Vergib ihnen, denn sie wissen nicht, was sie tun"
                        "Vergeef hen want ze weten niet wat ze doen"
                        "Pardonne-leur car ils ne savent pas ce qu'ils font"
                        "Perdónalos porque no saben lo que hacen"
                        "Oprosti im, jer ne znaju što čine"
                        "Atyám, bocsásd meg nekik, mert nem tudják mit cselekszenek!"
                        "Odpusť jim, neboť nevědí, co činí"
                        "Πάτερ άφες αυτοίς, ού γάρ οίδασι τί ποιούσι"
                        "Ojcze, przebacz im, bo nie wiedzą, co czynią"
                        "Forgive them as they know not what they do"

                        Comment


                        • #42
                          Strange, ADB says I have two devices connected

                          Heres my Tab ..
                          Proscan 10.1
                          Boxchip A10,
                          Im not sure if this is because im on Windows 8 or not, but I followed your directions for the usb drivers. Heres what im getting in the command prompt.

                          Microsoft Windows [Version 6.2.9200]
                          (c) 2012 Microsoft Corporation. All rights reserved.
                          C:\WINDOWS\system32>cd\program files (x86)/android/android-sdk/platform-tools
                          C:\Program Files (x86)\android\android-sdk\platform-tools>adb devices
                          * daemon not running. starting it now on port 5037 *
                          * daemon started successfully *
                          List of devices attached
                          emulator-5554 device
                          20080411413fc082 device

                          C:\Program Files (x86)\android\android-sdk\platform-tools>adb push rkdump /data/
                          error: more than one device and emulator
                          C:\Program Files (x86)\android\android-sdk\platform-tools>

                          only other things I have attached to the usb are my wireless network adapter, wireless keyboard and mouse. Any Idea of what im doing Wrong? You Rock Finless !!!

                          Okay figured it out, It seems I had installed a program called Bluestacks that was running on the 5554 port..
                          Last edited by bryman777; 11-15-2012, 04:17 PM.

                          Comment


                          • #43
                            I was Able to abd dump the Proscan 1044

                            Thank you so much for the windows driver Info, It really Helped out a lot, I couldn't have done it with out it. I also used yarviks adb dump Info, worked really easy..

                            Comment


                            • #44
                              I got error too
                              Code:
                              root@android:/ # cat /proc/mtdcat /proc/mtd
                              dev:    size   erasesize  name
                              mtd0: 00400000 00004000 "misc"
                              mtd1: 00800000 00004000 "kernel"
                              mtd2: 01000000 00004000 "boot"
                              mtd3: 01000000 00004000 "recovery"
                              mtd4: 20800000 00004000 "backup"
                              mtd5: 08000000 00004000 "cache"
                              mtd6: 40000000 00004000 "userdata"
                              mtd7: 00400000 00004000 "kpanic"
                              mtd8: 1ec00000 00004000 "system"
                              mtd9: 14fc00000 00004000 "user"
                              oot@android:/ # cat /pro/cpuinfo
                              at /pro/cpuinfo
                              system/bin/sh: cat: /pro/cpuinfo: No such file or directory
                              |root@android:/ # cat /proc/cpuinfo
                              at /proc/cpuinfo
                              rocessor       : ARMv7 Processor rev 0 (v7l)
                              rocessor       : 0
                              ogoMIPS        : 503.83
                              
                              
                              eatures        : swp half thumb fastmult vfp edsp neon vfpv3
                              PU implementer : 0x41
                              PU architecture: 7
                              PU variant     : 0x3
                              PU part        : 0xc09
                              PU revision    : 0
                              
                              
                              ardware        : RK30board
                              evision        : 0000
                              erial          : 0000000000000000
                              root@android:/ # /data/rkdump /dev/block/mtdblock1 /mnt/sdcard/kernel.img
                              /data/rkdump /dev/block/mtdblock1 /mnt/sdcard/kernel.img
                              kernel.img found (6873132 bytes)
                              dumping...
                              crc found (4 bytes, 0xf60cb92c)
                              done
                              root@android:/ # /data/rkdump /dev/block/mtdblock2 /mnt/sdcard/boot.img
                              /data/rkdump /dev/block/mtdblock2 /mnt/sdcard/boot.img
                              kernel.img found (1029616 bytes)
                              dumping...
                              crc found (4 bytes, 0x0877278a)
                              done
                              root@android:/ # /data/rkdump /dev/block/mtdblock3 /mnt/sdcard/recovery.img
                              /data/rkdump /dev/block/mtdblock3 /mnt/sdcard/recovery.img
                              unknown image (41 4e 44 52)
                              1|root@android:/ #
                              ??

                              Comment


                              • #45
                                Hello. I have an Yzipro (rk3066 with 4.0.4), very similar to Yarvik TAB9-200.

                                There is no stock firmware for this tab, so, i want to recreate it with a dump.

                                I've the same issue with rkdump: unknown image.

                                So, i'm dumping with dd if=xxx of=xxx bs=4096 and it's seem working.

                                I have now boot.img, misc.img, kernel.img, system.img, recovery.img (backup.img is empty)

                                But i haven't "parameter" file: how can i recover it ?

                                thanks

                                Comment

                                Working...
                                X