PDA

View Full Version : Dumping ROM using ADB guide



domrad
03-14-2012, 04:52 PM
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 :ROLL.. 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/

Finless
03-14-2012, 05:04 PM
Great write up! Thank you so much for doing this. It will help a lot of people get ROMs in the future.

Thanks!

Oh and you just got your first sticky post here on FreakTab :)

Bob

domrad
03-14-2012, 05:13 PM
cool! tnx bob.

swlaraut
03-14-2012, 06:54 PM
Dang missed a sticky by this much. I just asked Bob how to go about this earlier. Thanks for the tutorial.

Sent from my NXM726HN using Tapatalk

hellfoot
03-15-2012, 08:44 AM
hey nice tutorial domrad..


been getting a hard time trying to get the dump files of the 7bg2c coz we have the same tablet...hehe

you're a life saver...

thanks!

Damo
03-15-2012, 08:48 AM
Wow that is one hell of a tutorial :thumbup:

Sent from my SK17i using Tapatalk

WillJames
03-15-2012, 12:27 PM
wow that is one hell of a tutorial :thumbup:

Sent from my sk17i using tapatalk

+1

nice!!!!

crazy12know
03-21-2012, 04:17 AM
I'm going to work right now but when I get home I'm going to run ADB and dump the ROMS. I been playing around with thing for about a week since I had no previous experience with Android devices and now I understand how crippled this device really is. I really hate that some of the Apps on this device can't be removed in its current state. I never really knew what the advantages of rooting the device would be. Most of you who play around with device for a while and read what other Android users can do will definitely find some inspiration to get it rooted.

Hats off to you guys for figuring out how to do this and hope this device is 95% similar to what you've been working on before so it doesn't take too much additional effort.

Where should I put the ROMS once I download them so they can be accessed?

domrad
03-21-2012, 01:24 PM
Where should I put the ROMS once I download them so they can be accessed?
you can message finless or any chef here with your dumped rom as attachment or use any free cloud storage, like dropbox for example, so you can just give them the link on the files.

Finless
03-21-2012, 01:36 PM
PM me and if you know how to FTP, I can give you the FreakTab public FTP for uploading ROMs.

Bob

Zarealius
03-27-2012, 10:08 PM
Tried using this to flash my PMID701c, I was unseccessful just incase any "stalkers" were wondering.

On a side note I may be purchaseing the 4.3inch version soon in hopes of progressing one with the other.

BTW HUGE PROPS ON EVERYTHING!

pokimon
03-28-2012, 07:41 AM
What you need :

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.

(http://androtab.info/rockchip/devel/rkutils/)

i did all properly and my system at mtd1

i wrote /data/rkdump /dev/block/mtdblock1 /sdcard/system.img
it gave me a error;

/data/rkdump: read: I/O error

have u got any idea why im gettin this error :S

thanks alot

Finless
03-28-2012, 04:32 PM
Guys, the RKdump utility only works for RK processors and architecture. So if your PMID is not a Rock Chip this proceedure will not work for you. In the Polaroid forum someone took a pmid apart and it is a All Winner Processor.

Bob

MrWeelson
06-01-2012, 12:21 PM
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

lohtse
06-03-2012, 11:00 AM
o a dump of my a7 G3 if someone knows what the usb id thing will be.....

Also where should I upload it for everyone??

Finless
06-03-2012, 11:08 AM
I believe all Arnova use this ID
0x0e79

So you need to put that in your adb_usb.ini file.
If your on Windows 7 this file goes in:
/users/your user name/.android/adb_usb.ini

If the file does not exist make it.

Bob

joshendy
06-03-2012, 04:06 PM
Hi everyone,

The steps above worked great for me, however when I entered the shell 'adb shell' I only had the '$' showing, as opposed to the '#' root access character. Without root access there was no way to continue. So I managed to find another topic where freaktab user N4RPS posted a series of commands to get superuser access on his Nextbook. Big thanks to him!

Here they are:

1. C:\ADB> adb shell
2. shell@android:/ $ mv /data/local/tmp /data/local/tmp.bak
3. shell@android:/ $ ln -s /data /data/local/tmp
4. shell@android:/ $ exit
5. C:\ADB> adb reboot
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. shell@android:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. shell@android:/ $ exit
10. C:\ADB> adb reboot
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. root@android:/ # chown root.shell /system/bin/su
16. root@android:/ # chmod 06755 /system/bin/su
17. root@android:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|root@android:/ # ln -s /system/bin/su /system/xbin/su
19. root@android:/ # exit
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
21. C:\ADB> adb shell
22. root@android:/ # rm /data/local.prop
23. root@android:/ # rm /data/local/tmp
24. root@android:/ # mv /data/local/tmp.bak /data/local/tmp
25. root@android:/ # exit

(Instead of 'C:\ADB' make sure to use your own adb.exe from your 'android-sdk/platform-tools' folder.)

This is a shorter version of what N4RPS posted but it was all I needed to do. After doing this and rebooting my device, I was able to enter 'adb shell', still get the '$' icon but then by typing 'su' (Superuser) I was given the '#' icon and I was able to then dump my ROM to my sd card!

Being a real noob to android this took me some 10 hours of playing around to figure out, but I'm always ready for a challenge. I really hope this saves others from having to hit their head against the wall repeatedly like I had too.

If you google 'android superuser' you will be able to find the 'su' file and the 'Superuser.apk' file that you need to complete the above steps.

Cheers,
Josh

c0nK3R
06-03-2012, 10:02 PM
Please HELP!!!

I have a Nextbook Premium 7 Capacitive. Version/Serial number YF 0911 Manufactured on Sept 2011 and Flashed Dec 2011.

This was bought from a hastings franchise so good chance it is a 0911 (Not a refurbished/ returned).

I plan on flashing theses two roms 0911 test (http://www.freaktab.com/showthread.php?637-Nextbook-0911-TEST-rom-by-Finless-Version-1-45&highlight=0911) and ics stock rom 0512 (http://www.freaktab.com/showthread.php?987-NextBook-7P1N-SE-Ice-Cream-Sandwich-STOCK-ROM) ,but before I do I want to make sure If they don't work I can get back to what I had.

Okay now for my problem. At Step 8 of the original guide it says to copy the rkdump file to the /data/ folder in which I have No root access and file system is read only. So no dice :(.

The same with the root bypass right above this message. I get stopped at Step 8. As well as the original (http://www.freaktab.com/showthread.php?601-Nextbook-Premium-7-SE-w-ICS&p=13041&viewfull=1#post13041)

I tried the terminal emulator (http://www.freaktab.com/showthread.php?601-Nextbook-Premium-7-SE-w-ICS&p=11105&viewfull=1#post11105.) way also. I can't even read the files

Also something very peculiar happened when I installed android sdk. Instead of installing at the regular place c:/Programs(x86)/.... it installed in C:\Users\<user name>\AppData\Local\Android\android-sdk\ It does seem to work. It recognizes my device. I can send commands to it such as reboot and install/uninstall packages etc...

(Also My serial number in ADB is listed as 123456789ABCDEFG lol don't know if that is important)


I'm tired of seeing access denied :BANG lol
So if anyone can help me Please do.

lohtse
06-04-2012, 02:47 AM
Guys, the RKdump utility only works for RK processors and architecture. So if your PMID is not a Rock Chip this proceedure will not work for you. In the Polaroid forum someone took a pmid apart and it is a All Winner Processor.

Bob

hmmmmm thats what the Arnova 7 G3 is..

was good to do a dump of the rom for the devs here... but guess I can't...

DAMN IT!!!!

Finless
06-04-2012, 06:58 AM
The 7 G3 is not a Rockchip processor? It's a AllWinner?

Bob

MrWeelson
06-04-2012, 07:31 AM
Yep, looks like the 7G3's are not Rockchip, Allwinner / Qualcomm according to Arctablet.

http://www.arctablet.com/blog/archos-tablet/arnova-g3-specifications-prices-and-availability-product-lineup/

lohtse
06-04-2012, 03:08 PM
Any ideas how to do a rom dump for you guys then?

snakekiller
06-05-2012, 11:05 AM
yes i have a allwinner yarvik tablet.
have you tried my method with adb. look at the yarvik topic please.
and let me now if it works for you too.

Verstuurd van mijn Galaxy Gio GT-S5660 met Tapatalk

d3kilo
07-09-2012, 05:17 AM
I have a question. I have followed step to install driver.

I have set the driver for my tablet

[Google.NTx86]

;Advan Vandroid T2i
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&REV_0222&MI_01

[Google.NTamd64]

;Advan Vandroid T2i
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&REV_0222&MI_01

After that i install it without problem and in the device manager it show :
Android Phone
- Android Composite ADB Interface

I install Android SDK tools & Android SDK platform-tools
so i have "platform-tools" folder, after that i copied the rkdump file to "platform-tools" folder

I run the cmd in "Run as administrator"
and go to "platform-tools" folder and run "adb devices"

The problem is why i can't see any device list?

It is tablet base RK29 chipset identically with Nextbook 7P S

[Solved]
I only need to put adb_usb.ini with 0x2207

MaxMagic
07-11-2012, 03:08 PM
Hello Everyone,

I moved over from the root section of the "next 7s resistive screen" were I was able to root the device just fine with Finless' rom. There are no problems with it, that I can see, but I have not been able to get the ADB driver to see the device. I have followed this thread and the instructions and even reloaded sdk several times. When I put the rkdump into the adb directory, go to dos in admin mode and run adb devices, all I get is "list of devices attached" and nothing else. It just goes back to the cmd prompt.

Max

soulhd
07-20-2012, 03:39 AM
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 :D

OK, I have this device:


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


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 (http://www.freaktab.com/showthread.php?401-Dumping-ROM-using-ADB-guide&p=5057&viewfull=1#post5057) but when I tried to dump I got this:


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..

Finless
07-20-2012, 07:16 AM
It's not update.img it's backup.img you want from your mtd list

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

Bob

soulhd
07-20-2012, 07:26 AM
It's not update.img it's backup.img you want from your mtd list

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

Bob

Thanks for the reply, Bob.

But it's still no go, I got this:

https://dl.dropbox.com/u/5646363/androids/rkdump.PNG


Should I upload factory's firmware update image?

It's on here (http://image-hosting.king.net.id/sftab/Skyworth_S7_Stock_ROM_Batch_2.zip), BTW.

Finless
07-20-2012, 07:31 AM
Odd..... try increasing the block# by 1 over what mtd says. I seem to recall this on some tablets due to fstab

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

See if you can dump any of the images by playing with the number vs the image name

Bob

soulhd
07-20-2012, 07:49 AM
Yes, it is. I followed changing the mtd numbers as you suggested and got the same error.

Does rkdump linked in the first post work for both RK28 and RK29? Because my device is RK29 with ICS.

vendorz
08-04-2012, 11:30 AM
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 :D

OK, I have this device:


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


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 (http://www.freaktab.com/showthread.php?401-Dumping-ROM-using-ADB-guide&p=5057&viewfull=1#post5057) but when I tried to dump I got this:


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.

cowboyv
08-07-2012, 12:36 PM
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?

snakekiller
08-07-2012, 01:00 PM
Have you selected usb debug in settings.
Thats needed for adb

Verstuurd van mijn Freaktab met Tapatalk

cowboyv
08-07-2012, 04:06 PM
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.

Finless
08-08-2012, 08:18 AM
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

cowboyv
08-08-2012, 10:45 AM
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.

mufi
08-09-2012, 02:57 AM
8. type

adb push rkdump /data/


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



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 $.



10. type

chmod 755 /data/rkdump

*this will make RKDump executable


Again, chmod 755 /sdcard/rkdump instead of chmod 755 /data/rkdump.



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.

hellfoot
08-30-2012, 10:27 AM
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!:o:o


hellfoot

isitmondayyet
09-28-2012, 06:22 PM
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

AjeTovski
10-14-2012, 07:55 PM
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 :ROLL.. 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.

Finless
10-14-2012, 11:48 PM
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

bryman777
11-15-2012, 04:47 PM
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..

bryman777
11-15-2012, 08:50 PM
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..

noobz
11-17-2012, 01:13 AM
I got error too

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:/ #



??

murigny64
11-20-2012, 02:24 AM
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

Finless
11-20-2012, 07:54 AM
What you want to dump is backup.img This is a full ROM image like update.img and will have the parameter file in it. If backup.img is empty then the maker did not flash it :(
Thus no parameter file. :(

My syggestion then would be to use one from another RK3066 ROM of the same SDK level.

Bob

murigny64
11-20-2012, 08:16 AM
What you want to dump is backup.img This is a full ROM image like update.img and will have the parameter file in it. If backup.img is empty then the maker did not flash it :(
Thus no parameter file. :(

My syggestion then would be to use one from another RK3066 ROM of the same SDK level.

Bob

Thanks finless.

I've made an update.img with this dump and a yarvik tab9-200 parameter file.

It's seem good:
- i've unpack and all is present
- unpack of boot.img : initramfs is complete

I can't test it, you know why :rolleyes:

Is there a beta tester in this place ?

EDIT: Yzipro successfully flashed with my build !!! data partition extended to 1Go.

tcpipipx
11-24-2012, 08:48 AM
I dumped my Nextbook 9P last night, so I hope this helps.

FIRMWARE_VER:1.0.1
MACHINE_MODEL:Next9P
MACHINE_ID:007
MANUFACTURER:RK29SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 2929
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
COMBINATION_KEY: 0,6,A,7,0
CMDLINE: console=ttyS1,115200n8n androidboot.console=ttyS1 init=/init initrd=0x62000000,0x800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00004000@0x00004000(kernel),0x00008000@0x00008000( boot),0x00008000@0x00010000(recovery),0x000F0000@0 x00018000(backup),0x0003a000@0x00108000(cache),0x0 0100000@0x00142000(userdata),0x00002000@0x00242000 (kpanic),0x000E6000@0x00244000(system),-@0x0032A000(user)

grymace
12-04-2012, 10:18 AM
Hey Gang,

I'm a relative newbie here (I rooted my old android phone, and that's it). I'm attempting to make a backup image of my MK808, before I install Finless' 1.5a ROM. I was given a link to this page, and told this is what I need to do.

I followed the instructions, but didn't have to manually install the drivers, because my Windows XP (SP3) found my MK808 and the installed SD card (RockUSBDriver was used). They are both in my "MY COMPUTER" as separate removable disks. I see the directory of my MK808 flash in one removable disk, and some file I copied to my SD card (because I couldn't tell which removable disk was which) in the other. There is nothing out of the ordinary in my Device Manager.

I copied the RKDump file into the platform-tools directory, but when I type adb devices - there is none listed.

Any ideas what I could be doing (or not doing) wrong??

Thanks in advance...

Finless
12-04-2012, 12:16 PM
RKdump will not work with RK3066 devices which the MK808 is. So forget that route. Only way to dump it is to use linux and RKflash.

But why do you need to dump it? A stock ROM is available.

Bob

grymace
12-04-2012, 01:33 PM
RKdump will not work with RK3066 devices which the MK808 is. So forget that route. Only way to dump it is to use linux and RKflash.

But why do you need to dump it? A stock ROM is available.

Bob

Hi Bob,

I just wanted a "factory restore" option, in the event that something goes wrong when installing your finless 1.5a ROM. A restore point, so to say. If I understand you correctly, there's one built in? Can you tell me how to access it, in case I need it?

katmaster210
12-22-2012, 12:27 PM
Hi everyone,

The steps above worked great for me, however when I entered the shell 'adb shell' I only had the '$' showing, as opposed to the '#' root access character. Without root access there was no way to continue. So I managed to find another topic where freaktab user N4RPS posted a series of commands to get superuser access on his Nextbook. Big thanks to him!

Here they are:

1. C:\ADB> adb shell
2. shell@android:/ $ mv /data/local/tmp /data/local/tmp.bak
3. shell@android:/ $ ln -s /data /data/local/tmp
4. shell@android:/ $ exit
5. C:\ADB> adb reboot
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. shell@android:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. shell@android:/ $ exit
10. C:\ADB> adb reboot
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. root@android:/ # chown root.shell /system/bin/su
16. root@android:/ # chmod 06755 /system/bin/su
17. root@android:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|root@android:/ # ln -s /system/bin/su /system/xbin/su
19. root@android:/ # exit
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
21. C:\ADB> adb shell
22. root@android:/ # rm /data/local.prop
23. root@android:/ # rm /data/local/tmp
24. root@android:/ # mv /data/local/tmp.bak /data/local/tmp
25. root@android:/ # exit

(Instead of 'C:\ADB' make sure to use your own adb.exe from your 'android-sdk/platform-tools' folder.)

This is a shorter version of what N4RPS posted but it was all I needed to do. After doing this and rebooting my device, I was able to enter 'adb shell', still get the '$' icon but then by typing 'su' (Superuser) I was given the '#' icon and I was able to then dump my ROM to my sd card!

Being a real noob to android this took me some 10 hours of playing around to figure out, but I'm always ready for a challenge. I really hope this saves others from having to hit their head against the wall repeatedly like I had too.

If you google 'android superuser' you will be able to find the 'su' file and the 'Superuser.apk' file that you need to complete the above steps.

Cheers,
Josh

honestly, i'm quite lost on this issue. i guess i'm just not understanding how the command prompt is supposed to react. this is the first time ive tried anything this complex before, and im about ready to give up. maybe someone could explain the command prompt a little better? like for instance; if the location of the dump folder matters, or will it automatically find it? (probably a stupid question) if it does matter; then where is the best place to put it?:confused:

crooked8s
01-26-2013, 05:24 PM
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 :ROLL.. 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 cant your drivers to work. the device shows up as V8 in the device manager, I have followed your steps to the T. although when I install moborobo the drivers get installed automatically. then when i go to cmd.exe and type "adb devices" it shows no devices in the list.

device manager shows driver provider as HTC CORPERATION.

help!:BANG


specs
http://www.freaktab.com/showthread.php?3588-CX-803-Need-to-learn-how-to-root-I-have-the-stock-boot-img-file

crooked8s
01-27-2013, 11:35 AM
Hi...

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

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


Thanks for the help!!! worked like a charm!




ok I am about to give up........ I did everything I could within my knowledge of trying to get this to work....

I got the drivers installed as per post 14 of this thread. but i still cant see my device in "adb devices".

I need help here guys.......

I am at your mercy.

or my device is at my mercy of being thrown against the wall !!!!

vik2009
02-04-2013, 06:53 AM
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..


You have two devices connected:
emulator-5554 device
20080411413fc082 device

You use instead:
> adb -s 20080411413fc082 push rkdump /data/
for copy rkdump to physical device "20080411413fc082".

Vik

camel
03-14-2013, 09:25 AM
https://dl.dropbox.com/u/5646363/androids/rkdump.PNG


hi i have got same problem with cx803 with fineless bob 1.7 making a full img backup.

tried all blocks, only block 1 was able to read., other blocks gave me unknow image

regards

Finless
03-14-2013, 11:36 AM
RKdump wont work on rk3066.

You have to use linux and DD or use the Linux RKflash tool found on XDA.


Bob

camel
03-14-2013, 12:06 PM
thnx bob for the info.

abdul_pt
04-20-2013, 05:59 AM
RKdump wont work on rk3066.

You have to use linux and DD or use the Linux RKflash tool found on XDA.


Bob

Hi all,
you can use romdump (http://android.podtwo.com/romdump/) in rk3066. It gives you 5 files boot.img,recovery.img,system.rar,system.info.rar and a checksum. I dumped my rk3066 yesterday using this, but haven´t flashed back to confirm if it´s ok.

Finless
04-21-2013, 11:02 AM
Hi all,
you can use romdump (http://android.podtwo.com/romdump/) in rk3066. It gives you 5 files boot.img,recovery.img,system.rar,system.info.rar and a checksum. I dumped my rk3066 yesterday using this, but haven´t flashed back to confirm if it´s ok.

This does not dump kernel.img so if you ROM does not have kernel in boot.img you wont be able to make a flashable rom.

Bob

abdul_pt
07-08-2013, 09:24 AM
I have made a small batch script that will save us some time, it makes a dump of boot,kernel,recovery and system using the dd comand.
Feel free to kang it.

Dump (http://www.mediafire.com/download/ewwru9dpm29uyje/Script.7z)

Finless
07-09-2013, 08:12 AM
Thanks! This should help some folks dump the ROM!

Bob

geofferyh
07-21-2013, 08:05 AM
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 :ROLL.. 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 am trying to understand how to apply this tutorial and am finding problems with parts of the instructions because there seems to be an implied burden of prior knowledge that some of us do not yet have. For example:

"What you need : a pc, usb cable and, ofc, your android device with sdcard" What is "ofc"? What is its purpose?

"2. Download and Install android SDK (dont forget JAVA JDK if you havent got it yet)". What is JAVA JDK and how is it applicable to the tutorial?

"3. now connect your device to your pc, you will see Windows will try to install appropriate driver...". "Connect" needs to be defined because how you connect may make a difference in whether the tablet will be recognized as being attached. For example; the PiPo UpU1 is connected for updates using the RKBatchTool by pressing Volume+ while inserting the USB cable into the tablet. Also, to enable USB storage on the PiPo UpU1 simply "Power" up the tablet and insert the USB cable into the tablet. Which method is valid for the tutorial? Or, is another method required?

These are all things that need to be defined.

Using both PiPo UpU1 and M8Pro3G tablets I have managed to get through the instructions to the point of Step #7. It states,

"7. type adb devices there should be 1 device on the list. otherwise review previous steps."

The result of this step #7 produces no result except for the following line of text, "List of devices attached". (See attachment of screen shot for further clarification)

If the author of this tutorial, or some other knowledgeable person, could please answer my questions, perhaps I and others could better utilize this tutorial.

geofferyh
07-21-2013, 08:48 AM
I have made a small batch script that will save us some time, it makes a dump of boot,kernel,recovery and system using the dd comand.
Feel free to kang it.

Dump (http://www.mediafire.com/download/ewwru9dpm29uyje/Script.7z)

Could you please include some instruction on how to utilize the script. Some of us are still a little behind on the use of such scripts.

Thank you for your understanding.

rrileypm
07-21-2013, 09:29 AM
Yes, it seems that Domrad's instructions need to be clarified a bit.

Freaktab is growing by leaps and bounds on a daily basis....and while we used to take for granted that everyone "just knows" what we are talking about...for the benefit of new members, who have never done this stuff before, we need a step by step process (including installing the correct Windows drivers)...that JUST WORKS!!!!!!!

Although I am a developer here, I have NEVER gotten this ROM Dumping process to work either.

I'm needing geofferyh to dump a tablet, so I can do a ROM for him. Can anyone help him through this process and hopefully help make this thread's instructions more seamless to first time ROM dumpers?

geofferyh
07-21-2013, 12:51 PM
Yes, it seems that Domrad's instructions need to be clarified a bit.

Freaktab is growing by leaps and bounds on a daily basis....and while we used to take for granted that everyone "just knows" what we are talking about...for the benefit of new members, who have never done this stuff before, we need a step by step process (including installing the correct Windows drivers)...that JUST WORKS!!!!!!!

Although I am a developer here, I have NEVER gotten this ROM Dumping process to work either.

I'm needing geofferyh to dump a tablet, so I can do a ROM for him. Can anyone help him through this process and hopefully help make this thread's instructions more seamless to first time ROM dumpers?

If someone can get me the basic information that I need, I can rewrite this tutorial (already done through step #6) so it makes sense and works for everyone. Do it here or PM to me, your choice.

Thanking you all in advance for your assistance.

abdul_pt
07-22-2013, 09:35 AM
What version of Windows are you running?
How does your device appears in device manager?

The usage off the script, download it to were ever you want, unpack it, click the runme.bat. It will tell that you need a 1GB( it's less) of free space on the SDcard, and make the Dump using DD comand. In the end it will tell you were is the Dump.

geofferyh
07-22-2013, 11:16 AM
What version of Windows are you running?
How does your device appears in device manager?

The usage off the script, download it to were ever you want, unpack it, click the runme.bat. It will tell that you need a 1GB( it's less) of free space on the SDcard, and make the Dump using DD comand. In the end it will tell you were is the Dump.

I am using Windows XP SP3 on Dell Optiplex GX780.

See attachments of Device Manager.

I would ask that if you wish to offer something here to help others (who may not be at your level of expertise), you need to be much more detail specific. Please, you should explain this statement, "It will tell that you need a 1GB( it's less) of free space on the SDcard, and make the Dump using DD comand."

My best guess is the following:

1) Connect the tablet to the Windows PC with USB cable.
2) Run the "dump.bat" file.
3) The internal "SDCard" will be checked to see if it has at least 1GB of free space available.
4) If free space is available, ADB will complete the ROM Dump.

Am I correct?

abdul_pt
07-22-2013, 11:46 AM
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

First try this to make sure you have a ADB connection. Check with the command adb devices.

If you are to use ADB you have to connect your device to the PC, and enable USB Debug.
Yes, it's Dump.bat, this a part of other script i have and changed the name. Sorry.
No, it will not check you SDcard, you have to do that.

I'm trying to explain the best i can, but if still isn't understandable, i will try harder.

geofferyh
07-22-2013, 12:48 PM
First try this to make sure you have a ADB connection. Check with the command adb devices.

If you are to use ADB you have to connect your device to the PC, and enable USB Debug.
Yes, it's Dump.bat, this a part of other script i have and changed the name. Sorry.
No, it will not check you SDcard, you have to do that.

I'm trying to explain the best i can, but if still isn't understandable, i will try harder.

With regard to "Checking the SDCard", do you mean that I should check that the remaining storage space on the internal SDCard (not external SDCard) is at least 1GB?

My PiPo UpU1 Hardware ID's:
USB\Vid_2207&Pid_0010&Rev_0222&MI_01
USB\Vid_2207&Pid_0010&MI_01

My android_winusb.inf [Google.NTx86] and [Google.NTamd64] setup:
;PiPo UpU1
%SingleAdbInterface% = USB_Install, USB\Vid_2207&Pid_0010
%CompositeAdbInterface% = USB_Install, USB\Vid_2207&Pid_0010&MI_01

My Windows XP "adb_usb.ini" file reads as follows:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.

Notice it states "DO NOT EDIT". Do you know the .ini file format for me to add my device ID, which is also 2207 (Hex = 0x2207), to what is currently in that file?

abdul_pt
07-22-2013, 01:22 PM
Yes, internal SDcard.

If you want make a backup of the file.
Edit the file with notepad++, add the 0x2207, below # 1 USB VENDOR ID PER LINE, or below anything that is there, and leave a blank line in the end. Save it, and try adb devices.

geofferyh
07-22-2013, 06:12 PM
Thank you abdul_pt for your clarifications to utilize your very clever "Dump" .bat file. I have utilized it on both my PiPo UpU1 and M8Pro3G tablets. It works flawlessly. Based on your assistance today I have been able to write a complete Tutorial (User Instruction), which I hope you will review and approve.

- First Draft -
Generic MDT Dump Instructions

NOTE: A Windows XP computer is being used for purposes of this tutorial.

NOTE: Download "Script.7z". [http://www.mediafire.com/download/ewwru9dpm29uyje/Script.7z] Extract it to your Windows Desktop. Rename the "Script" folder to "Generic MDT Dump".

1) Start the tablet, then goto Settings --> Storage. Check that the "Internal Storage" (Internal SDCard) has at least 1GB of free space available.

2) Connect the tablet to the Windows PC with a proper USB cable. We now assume the ADB Interface is running on the PC.

3) Locate the “adb_usb.ini” file because we may have to edit it to include our “adb device” ID. [Example: C:\Documents and Settings\Administrator\.android] Right Click and then "Open" the file using Windows Notepad.exe. The data without your tablet device number may look like the following:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.

4) Now we will need an adb device number. Right Click on My Computer, select Manage --> Device Manager --> Android xxxxx --> Android Composite ADB Interface. Right Click and select "Properties". Select the "Details" tab. You can now see the "Device Instance Id" [Example: USB\VID_2207&PID_0010&MI_01\9&2E9A2C21&0&0001]. Note the number after "USB\VID_" and before "&PID_0010&MI_01\9&2E9A2C21&0&0001. In this case, "2207". Converted to Hex it becomes "0x2207", our adb device number.

5) In the already opened .ini file, add the Hex value adb device number, in this example case “0x2207”, at the end of the existing information and include a “blank” line entry after the adb device number. For example:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207
|[Blank line]

6) “Save” and then “Close” the file.

7) Now your ready to run the "dump.bat" file (Double Click to start). Now, just follow the onscreen prompts.

8) When the dump is finished you will find a new folder in the "Generic MDT Dump" folder on the Windows Desktop. It will contain the newly created backup kernel.img, boot.img, recovery.img and system.img. Congratulations!

geofferyh
07-22-2013, 09:04 PM
If someone can get me the basic information that I need, I can rewrite this tutorial (already done through step #6) so it makes sense and works for everyone. Do it here or PM to me, your choice.

Thanking you all in advance for your assistance.

Well I guess nobody but me is interested. After working successfully with abdul_pt today we just might have a much more simple method to dump using ADB (See post #72 here). However, never wanting to let a challenge go to waste I press on. Below is my revised tutorial with a lot more "stuff" added to get something out, even though I don't think we are there yet.

What you need to get started:
A Windows XP PC (and logged in as an Administrator), USB cable, and your Android tablet with an external SDcard.

What you need to download:

Android SDK, download link - http://www.developer.android.com/sdk/installing.html
USB driver for your device - http://www.db.tt/2Cm2KUV6
RKDump file - http://www.db.tt/plRFmRh6

Instructions:

1. Enable USB debugging on the device.

2. Download and Install Android SDK Bundle.

3. Now connect your device to your pc, you may see Windows try to install an appropriate driver for your device; if it has already been installed properly you can proceed to “Step 4”. If not then you need to install the driver using the USB driver you downloaded above.

Here's how to do it...

3a. Extract the USB_driver.rar you downloaded above.

3b. Open the driver folder you just extracted and look for android_winusb.inf, right click it and click open with, and choose “Notepad”.

3c. Right Click on “My Computer” on the Windows Desktop, click on “Manage”, then click “Device Manager”.

3d. In the Device Manager, look for an improperly installed driver (Android xxxxx).

3e. Right Click on that driver (Android xxxxx) --> Click “Properties” --> Click on the “Details” tab --> and look in the drop-down list for the “Hardware ID’s.

3f. In the Values section, Right Click the shorter value and “Copy” it. For example:
PiPo UpU1 = USB\Vid_2207&Pid_0010&MI_01
PiPo M8Pro3G = USB\Vid_2207&Pid_0010&MI_01

3g. On the opened Notepad, edit the android_winusb.inf, review the entries, there's two entries, one in the [Google.NTx86] area and one in the [Google.NTamd64], for example:

;PiPo UpU1
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_143B
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_143B&MI_01

3h. Add your tablet name (;PiPo UpU1). On the %CompositeAdbInterface% entry, erase everything after the "=" sign and then press Ctrl+v (paste)... same thing for the %SingleAdbInterface% entry, but delete the last "&" sign and anything after it.

You need to do this in both the [Google.NTx86] and [Google.NTamd64] parts. Select to “SAVE” the file and then “Close” Notepad.

3i. In Device Manager, Right Click on the improperly installed driver and click update driver software, then choose browse my computer for driver software --> locate the folder with the USB driver, then just click next etc, etc..., until you have finished installing the driver.

Now for the ADB part:

4a. Now locate the “adb_usb.ini” file because we have to edit it to include our “adb device” ID. [Example: C:\Documents and Settings\Administrator\.android]. Remember the “Hardware ID’s” from Step #3f, [Example: USB\Vid_2207&Pid_0010&MI_01]. The data after “USB\Vid_” and before “&Pid_0010&MI_01” is your adb device number. In this case “2207”.

4b. Now Right Click on the “adb_usb.ini” file, then select “Open”. Now add the Hex value of the device number, in this example case “0x2207”, at the end of the existing information and include a “blank” entry after the adb device number. For example:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207
|

“Save” and then “Close” the file.

5. Copy the RKDump file you downloaded to the same folder as ADB.exe, usually it’s in folder “C:\Program Files\Android\adt-bundle-windows-x86-20130717\sdk\platform-tools”.

6. Click “Start” and then select “Run” from the menu selections. Enter “cmd” (or C: /System32/, then right click on “cmd.exe” and set to run as administrator).

7. At the command prompt enter the path to the platform-tools folder: "cd\program files\android\[other]\platform-tools" (without the quotes). [Example: [B]cd\program files\android\adt-bundle-windows-x86-20130717\sdk\platform-tools]

7. At the prompt enter: adb devices. There should be one device in the list [Example: PiPo UpU1 = 2207, PiPo M8Pro3G = 2207] otherwise review the previous steps.

8. Now enter: adb push rkdump /data/

9a. Now enter: adb shell
NOTE: If you see a "#" sign and a cursor next to it then we're good to go.. otherwise.. review all above steps as you have somehow gotten the previous steps wrong.

9b. Now enter: cat /proc/mtd (Optional for information only)

10. Now Enter: chmod 755 /data/rkdump
NOTE: This will make RKDump executable.

11a. Now enter: /data/rkdump /dev/block/mtdblock1 /sdcard/kernel.img
11b. Now enter: /data/rkdump /dev/block/mtdblock2 /sdcard/boot.img
11c. Now enter: /data/rkdump /dev/block/mtdblock3 /sdcard/recovery.img
11d. Now enter: /data/rkdump /dev/block/mtdblock4 /sdcard/system.img
11e. Now enter: /data/rkdump /dev/block/mtdblock5 /sdcard/update.img

NOTE: This will copy the update.img on your sdcard.

It gave me a kernel.img, boot.img and recovery.img only. Perhaps someone could evaluate the attached screen shot of the cmd window.

Standing-By for further input from some more knowledgable than myself.

rrileypm
07-22-2013, 09:40 PM
Great job...now those are my kind of instructions!!!!

How do you get the parameter file?

Sent from my M8 pro

abdul_pt
07-23-2013, 11:26 AM
To me they are understandable.:ROLL

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

It's backup.img not update.img. Block5 is cache not backup.img and system is in block8 not in 4.
Also the mtd partition may be empty and rkdump will post an error, and it's not 100% liable, sometimes it will give an error without any reason, at least in my experience with it. And the system comes in tar format, and for me, that is a time consuming feature when modding the system.
So i made that script. It can me improved.

Randy
I'm do not have your experience, but i think, the parameter's are all the same. If you sum all the space of the partition's, i think that will be the same of the space in @user.

geofferyh
07-23-2013, 01:51 PM
To me they are understandable.:ROLL

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

It's backup.img not update.img. Block5 is cache not backup.img and system is in block8 not in 4.
Also the mtd partition may be empty and rkdump will post an error, and it's not 100% liable, sometimes it will give an error without any reason, at least in my experience with it. And the system comes in tar format, and for me, that is a time consuming feature when modding the system.
So i made that script. It can me improved.

Randy
I'm do not have your experience, but i think, the parameter's are all the same. If you sum all the space of the partition's, i think that will be the same of the space in @user.

Randy
"How do you get the parameter file?" I can't yet answer that because I have not yet gained the knowledge. Perhaps abdul_pt has that answer.

Checkout the cmd screen shot #2 attachment. When you enter "cat /proc/mtd" the result is the listing you see, mtd0 thru mtd9.

Now have a look at what you get from the link at the bottom of the original tutorial [http://androtab.info/rockchip/devel/rkutils/]. See attachment "dumpstuff".

Recall the note at the end of the original tutorial, "NOTE: if you want to copy any other part of your device partition.. look in here http://androtab.info/rockchip/devel/rkutils/".

Notice that the screen shot listing of mtd0 to mtd9 files have different assigned mtd numbers than those found on the "dumpstuff" attachment coding when you follow the link in the note outlined above, which was used in the original tutorial. As abdul_pt has found, "backup.img" should be block#4, and not block#5. And, if you review "dumpstuff" attachment you will see "mtdblock5" is "update.img" with a following statement "update.img found (116115456 bytes) dumping...". Mtdblock5 should actually be "cache"???

I dumped mtd1 (kernel 7.15MB), mtd2 (boot 2.49MB), and mtd3 (recovery 1.48MB) to sdcard without any problem. However, see cmd window #2 attachment with regard to what happened to mtd4 (backup) and mtd8 (system).

Here is where I need to ask a question. Can we get all the image dump information we need from just the backup.img (update.img) or do we need the kernel, boot, recovery and system .img's too? And, if all we need is kernel, boot, recovery and system the script from abdul_pt is a much easier road to follow.

What next?

abdul_pt
07-23-2013, 02:17 PM
This is where is ask if you have read this topic?


RKdump will not work with RK3066 devices which the MK808 is. So forget that route. Only way to dump it is to use linux and RKflash.

But why do you need to dump it? A stock ROM is available.

Bob


RKdump wont work on rk3066.

You have to use linux and DD or use the Linux RKflash tool found on XDA.


Bob

You have this for rk30 devices


Hi all,
you can use romdump (http://android.podtwo.com/romdump/) in rk3066. It gives you 5 files boot.img,recovery.img,system.rar,system.info.rar and a checksum. I dumped my rk3066 yesterday using this, but haven´t flashed back to confirm if it´s ok.

That tut is out-dated, and it's manly for rk29 devices. I forget to write backup in the last post, so, in this new devices the most common thing is that backup partiton is empty, is just a blank space or with nothing useful there.

blackoutmassive
12-07-2013, 07:11 PM
I'm new to this forum and I'm sure someone has already covered this in some sense but inno way

I bought on of the Nextbook 7 SE from Walmart's sale ~$79; went on the manu's website and found no drivers at a quick glance. This guide is how to create your own Windows ADB driver for any Android device and in this case this peticular one.

1. Go into the Nextbook's settings>Developer Options>check "USB Debugging"

2. Install Android SDK and update USB Drivers

3. Plug in the device to a Windows computer, wait for the prompt to install the driver and perform the following (now this is where the "any" Android device comes into play: goto your device manager, right click the Android device>properties>choose the "Details" tab>change the drop down to "Hardware ID" and look at the shortest length entry (the bottom one (read below for this to make sense if your VIN and PID is not the same))>add the number after the PID with a "0x" in front of it in "adb_usb.ini" and the you will see what to do for the "android_winusb.inf" file. After you save both, point the Windows device installation to "android_winusb.inf" and you'll be all good.)

Alter the generic Google USB driver adding the NEXT7P12-8G hardware ID information to android_winusb.inf under the following headings:

For the model running 4.1, the following lines allow the driver to recognize the tablet:

[Google.NTx86]

;Nextbook
%SingleAdbInterface% = USB_Install, USB\Vid_18d1&Pid_4e22
%CompositeAdbInterface% = USB_Install, USB\Vid_18d1&Pid_4e22&MI_01

I no longer have the ID information for the 4.2 tablet.

If you have used ADB on your windows system, you will also need to alter the file "adb_usb.ini" to include the following line:

0x4e22

Just use the your file search window and it will pull the file up.

4. Verify that you have an interface; run "adb devices" you will see a UUID (random looking serial number)

5. If you have a UUID then you are able to root the device. Download Cydia Impactor http://www.cydiaimpactor.com/ , run the exe and just tap the "Start" button.

6. Now verify that you're root: go back to the adb shell and type: "adb devices" this will ensure that you're still connected to your device, if you see the UUID then goto step 7.

7. Type "adb shell" then "su", if you go from a $ to a # then you have successfully rooted your device!

8. Insert a SDCard of recommended size of 8GB and strip your default data out by doing the following (this is just a copy / paste):

C:\adb>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
0123456789ABCDEF device




C:\adb>adb shell
shell@android:/ $ su
su
127|root@android:/ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 01000000 00400000 "bootloader"
mtd1: 00800000 00400000 "logo"
mtd2: 00800000 00400000 "aml_logo"
mtd3: 00800000 00400000 "recovery"
mtd4: 00800000 00400000 "boot"
mtd5: 20000000 00400000 "system"
mtd6: 08000000 00400000 "cache"
mtd7: 20000000 00400000 "userdata"
mtd8: 1b4800000 00400000 "NFTL_Part"
root@android:/ # cd dev/mtd
cd dev/mtd
root@android:/dev/mtd # ls
ls
mtd0
mtd0ro
mtd1
mtd1ro
mtd2
mtd2ro
mtd3
mtd3ro
mtd4
mtd4ro
mtd5
mtd5ro
mtd6
mtd6ro
mtd7
mtd7ro
mtd8
mtd8ro
root@android:/dev/mtd # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 01000000 00400000 "bootloader"
mtd1: 00800000 00400000 "logo"
mtd2: 00800000 00400000 "aml_logo"
mtd3: 00800000 00400000 "recovery"
mtd4: 00800000 00400000 "boot"
mtd5: 20000000 00400000 "system"
mtd6: 08000000 00400000 "cache"
mtd7: 20000000 00400000 "userdata"
mtd8: 1b4800000 00400000 "NFTL_Part"
root@android:/dev/mtd # dd if=/dev/mtd/mtd0 of=/sdcard/external_sdcard/bootloader.img
dd if=/dev/mtd/mtd0 of=/sdcard/external_sdcard/bootloader.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.062 secs (8136380 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd1 of=/sdcard/external_sdcard/logo.img
dd if=/dev/mtd/mtd1 of=/sdcard/external_sdcard/logo.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.425 secs (5886742 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd2 of=/sdcard/external_sdcard/aml_logo.img
dd if=/dev/mtd/mtd2 of=/sdcard/external_sdcard/aml_logo.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.257 secs (6673514 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd3 of=/sdcard/external_sdcard/recovery.img
dd if=/dev/mtd/mtd3 of=/sdcard/external_sdcard/recovery.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.196 secs (7013886 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd4 of=/sdcard/external_sdcard/boot.img
dd if=/dev/mtd/mtd4 of=/sdcard/external_sdcard/boot.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.282 secs (6543375 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd5 of=/sdcard/external_sdcard/system.img
dd if=/dev/mtd/mtd5 of=/sdcard/external_sdcard/system.img
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 117.583 secs (4565888 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd6 of=/sdcard/external_sdcard/cache.img
dd if=/dev/mtd/mtd6 of=/sdcard/external_sdcard/cache.img
262144+0 records in
262144+0 records out
134217728 bytes transferred in 27.869 secs (4816022 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd7 of=/sdcard/external_sdcard/userdata.img
dd if=/dev/mtd/mtd7 of=/sdcard/external_sdcard/userdata.img
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 117.091 secs (4585074 bytes/sec)
root@android:/dev/mtd # /sdcard/external_sdcard/NFTL_Part.img: write error: File too large
8388608+0 records in
8388607+1 records out
4294967295 bytes transferred in 1042.615 secs (4119418 bytes/sec)

(yes the NFTL_Part seems is too large, if someone needs it I can work harder on pulling it)

9. I will post more if needed

Hope this helps

tattman65
12-07-2013, 10:19 PM
I'm new to this forum and I'm sure someone has already covered this in some sense but inno way

I bought on of the Nextbook 7 SE from Walmart's sale ~$79; went on the manu's website and found no drivers at a quick glance. This guide is how to create your own Windows ADB driver for any Android device and in this case this peticular one.

1. Go into the Nextbook's settings>Developer Options>check "USB Debugging"

2. Install Android SDK and update USB Drivers

3. Plug in the device to a Windows computer, wait for the prompt to install the driver and perform the following (now this is where the "any" Android device comes into play: goto your device manager, right click the Android device>properties>choose the "Details" tab>change the drop down to "Hardware ID" and look at the shortest length entry (the bottom one (read below for this to make sense if your VIN and PID is not the same))>add the number after the PID with a "0x" in front of it in "adb_usb.ini" and the you will see what to do for the "android_winusb.inf" file. After you save both, point the Windows device installation to "android_winusb.inf" and you'll be all good.)

Alter the generic Google USB driver adding the NEXT7P12-8G hardware ID information to android_winusb.inf under the following headings:

For the model running 4.1, the following lines allow the driver to recognize the tablet:

[Google.NTx86]

;Nextbook
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&REV_0222&MI_01

[Google.NTx86]

;Nextbook
%SingleAdbInterface% = USB_Install, USB\Vid_18d1&Pid_4e22
%CompositeAdbInterface% = USB_Install, USB\Vid_18d1&Pid_4e22&MI_01

I no longer have the ID information for the 4.2 tablet.

If you have used ADB on your windows system, you will also need to alter the file "adb_usb.ini" to include the following line:

0x4e22

Just use the your file search window and it will pull the file up.

4. Verify that you have an interface; run "adb devices" you will see a UUID (random looking serial number)

5. If you have a UUID then you are able to root the device. Download Cydia Impactor http://www.cydiaimpactor.com/ , run the exe and just tap the "Start" button.

6. Now verify that you're root: go back to the adb shell and type: "adb devices" this will ensure that you're still connected to your device, if you see the UUID then goto step 7.

7. Type "adb shell" the "su", if you go from a $ to a # then you have successfully rooted your device!

8. Insert a SDCard of recommended size of 8GB and strip your default data out by doing the following (this is just a copy / paste):

C:\adb>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
0123456789ABCDEF device




C:\adb>adb shell
shell@android:/ $ su
su
127|root@android:/ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 01000000 00400000 "bootloader"
mtd1: 00800000 00400000 "logo"
mtd2: 00800000 00400000 "aml_logo"
mtd3: 00800000 00400000 "recovery"
mtd4: 00800000 00400000 "boot"
mtd5: 20000000 00400000 "system"
mtd6: 08000000 00400000 "cache"
mtd7: 20000000 00400000 "userdata"
mtd8: 1b4800000 00400000 "NFTL_Part"
root@android:/ # cd dev/mtd
cd dev/mtd
root@android:/dev/mtd # ls
ls
mtd0
mtd0ro
mtd1
mtd1ro
mtd2
mtd2ro
mtd3
mtd3ro
mtd4
mtd4ro
mtd5
mtd5ro
mtd6
mtd6ro
mtd7
mtd7ro
mtd8
mtd8ro
root@android:/dev/mtd # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 01000000 00400000 "bootloader"
mtd1: 00800000 00400000 "logo"
mtd2: 00800000 00400000 "aml_logo"
mtd3: 00800000 00400000 "recovery"
mtd4: 00800000 00400000 "boot"
mtd5: 20000000 00400000 "system"
mtd6: 08000000 00400000 "cache"
mtd7: 20000000 00400000 "userdata"
mtd8: 1b4800000 00400000 "NFTL_Part"
root@android:/dev/mtd # dd if=/dev/mtd/mtd0 of=/sdcard/external_sdcard/bootloader.img
dd if=/dev/mtd/mtd0 of=/sdcard/external_sdcard/bootloader.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.062 secs (8136380 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd1 of=/sdcard/external_sdcard/logo.img
dd if=/dev/mtd/mtd1 of=/sdcard/external_sdcard/logo.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.425 secs (5886742 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd2 of=/sdcard/external_sdcard/aml_logo.img
dd if=/dev/mtd/mtd2 of=/sdcard/external_sdcard/aml_logo.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.257 secs (6673514 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd3 of=/sdcard/external_sdcard/recovery.img
dd if=/dev/mtd/mtd3 of=/sdcard/external_sdcard/recovery.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.196 secs (7013886 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd4 of=/sdcard/external_sdcard/boot.img
dd if=/dev/mtd/mtd4 of=/sdcard/external_sdcard/boot.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 1.282 secs (6543375 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd5 of=/sdcard/external_sdcard/system.img
dd if=/dev/mtd/mtd5 of=/sdcard/external_sdcard/system.img
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 117.583 secs (4565888 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd6 of=/sdcard/external_sdcard/cache.img
dd if=/dev/mtd/mtd6 of=/sdcard/external_sdcard/cache.img
262144+0 records in
262144+0 records out
134217728 bytes transferred in 27.869 secs (4816022 bytes/sec)
root@android:/dev/mtd # dd if=/dev/mtd/mtd7 of=/sdcard/external_sdcard/userdata.img
dd if=/dev/mtd/mtd7 of=/sdcard/external_sdcard/userdata.img
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 117.091 secs (4585074 bytes/sec)
root@android:/dev/mtd # /sdcard/external_sdcard/NFTL_Part.img: write error: File too large
8388608+0 records in
8388607+1 records out
4294967295 bytes transferred in 1042.615 secs (4119418 bytes/sec)

(yes the NFTL_Part seems is too large, if someone needs it I can work harder on pulling it)

9. I will post more if needed

Hope this helps



all i can say is wow dude nice ! thanks for the info :HBANG

blackoutmassive
12-08-2013, 03:33 AM
all i can say is wow dude nice ! thanks for the info :HBANG


No problem, just been scavangin the community long enough and figured I'd finally contribute :beerlight:

Polotab
01-07-2014, 09:55 AM
Will this work for the RK3188 devices?
I have The ASUS Memopad 10 (me102a, K00F) which has a rockchip and I am trying to figure out how to dump the Rom. I am at work right now and do not have my device handy to try this.

I attempted to use ROMDUMP as per this post over at XDA:

http://forum.xda-developers.com/show....php?t=2027311 (http://forum.xda-developers.com/showthread.php?t=2027311)

and

http://forum.xda-developers.com/show....php?t=1771347 (http://forum.xda-developers.com/showthread.php?t=1771347)

The only files I get are:
checksum.md5
config.gz
system.info.gz
System.tar

Under under Dev/block/mtd there are several files
ADF
APD
Backup
boot
cache
hidden
kernel
kpanic
misc
recovery
system
userdata

Would these be the .img files?

If I try cat /proc/mtd it does not list any partitions.

Taajan
04-09-2014, 09:50 AM
Needs to help and forgive me if I've missed this.

I'm new to the adb and trying to become an up and coming dev. I've created a Linux enviroment via Virtual Machine. Everytime I get my device to become seen by my pc, it disconnects when the linux vm boots up. Not sure why on this Any tips would be helpful.

PS: I have a Pipo M8 HD that I'm playing with as well. It has the RK3188. No matter what I do it will still not show up in adb

snakekiller
06-01-2014, 05:19 AM
It's not update.img it's backup.img you want from your mtd list

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

Bob

hey bob i bought a difrnce tab 7" for my youngest son. rk3026 dual core.
i setup adb on linux.
everything works good.
when i look to the mtdblocks i have this.

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"

when i take the backup its only 24mb big.
when i will take the system i got an error unknown img.
witch parts did you need it for making a custom rom for this tab.

Finless
06-01-2014, 11:28 AM
hey bob i bought a difrnce tab 7" for my youngest son. rk3026 dual core.
i setup adb on linux.
everything works good.
when i look to the mtdblocks i have this.



when i take the backup its only 24mb big.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"
when i will take the system i got an error unknown img.
witch parts did you need it for making a custom rom for this tab.

Please do a mount command from terminal and show me what it says.
My bet is system is cramfs

Also how are you doing the backup? My suggestion to make it easier is use DD.

You only need these to make a ROM but you do need the bootloader and parameter file from the stock ROM


mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"

mtd8: 1cc00000 00004000 "system"



Bob

snakekiller
06-01-2014, 11:37 AM
Can you tell me the command for the terminal.
I don't know it anymore.

And how about with dd ?
Wich command do you use than.

Verstuurd vanaf mijn E380 met Tapatalk

Finless
06-01-2014, 12:03 PM
From the terminal just type mount. However you may have to be rooted!

The DD commands are in my ROM hacks post telling you how to dump.

Also you might try using the 2.1 tool to dump ROM while in flash mode.

I know it's been a while since you did anything with RK but I don't have time to retype everything. It's all here. Sorry Snakey very busy so your going to have to study a little :)

Bob

snakekiller
06-02-2014, 06:14 AM
Ok bob i have these files .
But there is no stock rom for the parameter file .so what now

Verstuurd vanaf mijn E380 met Tapatalk

Finless
06-02-2014, 02:27 PM
Ok bob i have these files .
But there is no stock rom for the parameter file .so what now

Verstuurd vanaf mijn E380 met Tapatalk

With the RK tool 2.1 you can dump the parameter file.
Or you can dump it with the RK flash tool for Linux. 900supersport knows how to use that.

Bob

snakekiller
06-03-2014, 01:48 PM
Ok bob i have the parameter,system,recovery,boot,kernel,and misc files hahaha.
I looked in terminal su,mount and my system cache and userdata are ext4.
So have we all the parts for making a custom rom now?

Verstuurd vanaf mijn E380 met Tapatalk

Finless
06-03-2014, 03:49 PM
Ok bob i have the parameter,system,recovery,boot,kernel,and misc files hahaha.
I looked in terminal su,mount and my system cache and userdata are ext4.
So have we all the parts for making a custom rom now?

Verstuurd vanaf mijn E380 met Tapatalk

Yes you do!

Bob