Android Tablets Forum banner
1 - 20 of 34 Posts

·
Premium Member
Joined
·
2,596 Posts
Discussion Starter · #1 ·
This is the official firmware for the Irobot/Iweb , this is for rockchip based devices ;D
 

·
Premium Member
Joined
·
2,596 Posts
Discussion Starter · #3 ·
took a crap load of begging but hey you guys are worth it :'(
 

·
Premium Member
Joined
·
2,596 Posts
Discussion Starter · #6 ·
please read the how to I uploaded , it is in the same folder
 

·
Premium Member
Joined
·
2,596 Posts
Discussion Starter · #9 ·
sorry mac users, I am a linux user myself . I run windows in virtualboxany mac xperts please help
 

·
Registered
Joined
·
954 Posts
Now you can have the tool in English except for the one button which says ?? (Meaning Clear).Feel free to include this file in your distributions. 1. Download the firmware pack and extract it2. copy this following text into English.ini from this post into MD01-MydroidDevTool_v1.0-2010-0504RkAndroidToolLanguage
Code:
[Setting]Language=English[String]IDD102_TITLE=RKAndroidToolIDD129_1001=LoaderIDD129_1005=Offset:IDD129_1006=ParameterIDD129_1008=Offset:IDD129_1011=MiscIDD129_1013=Offset:IDD129_1016=KernelIDD129_1018=Offset:IDD129_1021=BootIDD129_1023=Offset:IDD129_1026=RecoveryIDD129_1028=Offset:IDD129_1031=SystemIDD129_1033=Offset:IDD129_1036=BackupIDD129_1038=Offset:IDD129_1041=ExecuteIDD130_1042=LoaderIDD130_1043=Offset:IDD130_1047=ParameterIDD130_1048=Offset:IDD130_1052=KernelIDD130_1053=Offset:IDD130_1057=ExecuteIDD131_1058=LoaderIDD131_1059=Offset:IDD131_1063=ParameterIDD131_1064=Offset:IDD131_1068=KernelIDD131_1069=Offset:IDD131_1073=ExecuteIDD131_1074=RootFSIDD131_1076=Offset:IDD131_1079=Please verify that files are accurate!IDS_1=RKAndroid rock usb devices not foundIDS_2=Found one RKAndroid Loader Rock Usb deviceIDS_3=Found one RKAndroid MaskRom Rock Usb deviceIDS_4=Found one RKAndroid Mass Storage Usb deviceIDS_5=Found multiple RKAndroid Rock Usb devicesIDS_6=Recorded IDB offset recorded in ID_BLOCK differs from actual detected value. Is the correct offset being used for this operation? IDS_7=Recorded system reserved blocks in ID_BLOCK error, attempt to correct? IDS_8=System volume size has increased. Low level format is required. All data will be lost! Proceed? IDS_9=Data volume size has increased. Low level format is required. All data will be lost! Proceed? IDS_10=Bad blocks exist in zones after reserved blocks, need to perform wipe. Data will be lost. Proceed? IDS_11=File not foundIDS_12=Cannot retrieve file sizeIDS_13=Setup was not performed. Cannot executeIDS_14=Starting to download files to FlashIDS_15=Writing data to Flash, data size is (%d)K, written (%d)KIDS_16=Starting to verify written dataIDS_17=Verifying written data,data size is (%d)K, verified(%d)KIDS_18=MaskRom device upgrade requres you to select LoaderIDS_19=Cannot find any upgradable devicesIDS_20=Multiple upgradable devices foundIDS_21=MaskRom device canoot perform Ram upgradeIDS_22=MSC device cannot be upradedIDS_23=Retreving Loader header messages failedIDS_24=Loader unpacking failedIDS_25=Starting to download BootIDS_26=Download Boot failedIDS_27=Download Boot successIDS_28=Starting device testIDS_29=Device test successIDS_30=Device test failIDS_31=Starting to write to ID_BLOCKIDS_32=Writing ID_BLOCK failureIDS_33=Writing ID_BLOCK successIDS_34=Restarting device IDS_35=Device restart failedIDS_36=Device restart successIDS_37=Execute failureIDS_38=Execute successIDS_39=Now testing devices, total number of blocks(%d), first block(%d)IDS_40=Starting to download filesIDS_41=File download failureIDS_42=Fila download success, time elapsed was(%dMS)IDS_43=Staring to wipe system driveIDS_44=System drive wipe failedIDS_45=System drive wipe completeIDS_46=Starting to download files to RAMIDS_47=File download to RAM failureIDS_48=File download to RAM success, time elapsed was (%dMS)IDS_49=Timeout waiting for Loader Rock usb deviceIDS_50=Execute GO command failed
3. Open MD01-MydroidDevTool_v1.0-2010-0504RkAndroidToolsetting.ini and replace "Chinese" with "English"
 

·
Registered
Joined
·
93 Posts
[quote author=xaueious link=topic=341.msg3336#msg3336 date=1275202411]Now you can have the tool in English except for the one button which says ?? (Meaning Clear).Feel free to include this file in your distributions. 1. Download the firmware pack and extract it2. copy this following text into English.ini from this post into MD01-MydroidDevTool_v1.0-2010-0504RkAndroidToolLanguage
Code:
[Setting]Language=English[String]IDD102_TITLE=RKAndroidToolIDD129_1001=LoaderIDD129_1005=Offset:IDD129_1006=ParameterIDD129_1008=Offset:IDD129_1011=MiscIDD129_1013=Offset:IDD129_1016=KernelIDD129_1018=Offset:IDD129_1021=BootIDD129_1023=Offset:IDD129_1026=RecoveryIDD129_1028=Offset:IDD129_1031=SystemIDD129_1033=Offset:IDD129_1036=BackupIDD129_1038=Offset:IDD129_1041=ExecuteIDD130_1042=LoaderIDD130_1043=Offset:IDD130_1047=ParameterIDD130_1048=Offset:IDD130_1052=KernelIDD130_1053=Offset:IDD130_1057=ExecuteIDD131_1058=LoaderIDD131_1059=Offset:IDD131_1063=ParameterIDD131_1064=Offset:IDD131_1068=KernelIDD131_1069=Offset:IDD131_1073=ExecuteIDD131_1074=RootFSIDD131_1076=Offset:IDD131_1079=Please verify that files are accurate!IDS_1=RKAndroid rock usb devices not foundIDS_2=Found one RKAndroid Loader Rock Usb deviceIDS_3=Found one RKAndroid MaskRom Rock Usb deviceIDS_4=Found one RKAndroid Mass Storage Usb deviceIDS_5=Found multiple RKAndroid Rock Usb devicesIDS_6=Recorded IDB offset recorded in ID_BLOCK differs from actual detected value. Is the correct offset being used for this operation? IDS_7=Recorded system reserved blocks in ID_BLOCK error, attempt to correct? IDS_8=System volume size has increased. Low level format is required. All data will be lost! Proceed? IDS_9=Data volume size has increased. Low level format is required. All data will be lost! Proceed? IDS_10=Bad blocks exist in zones after reserved blocks, need to perform wipe. Data will be lost. Proceed? IDS_11=File not foundIDS_12=Cannot retrieve file sizeIDS_13=Setup was not performed. Cannot executeIDS_14=Starting to download files to FlashIDS_15=Writing data to Flash, data size is (%d)K, written (%d)KIDS_16=Starting to verify written dataIDS_17=Verifying written data,data size is (%d)K, verified(%d)KIDS_18=MaskRom device upgrade requres you to select LoaderIDS_19=Cannot find any upgradable devicesIDS_20=Multiple upgradable devices foundIDS_21=MaskRom device canoot perform Ram upgradeIDS_22=MSC device cannot be upradedIDS_23=Retreving Loader header messages failedIDS_24=Loader unpacking failedIDS_25=Starting to download BootIDS_26=Download Boot failedIDS_27=Download Boot successIDS_28=Starting device testIDS_29=Device test successIDS_30=Device test failIDS_31=Starting to write to ID_BLOCKIDS_32=Writing ID_BLOCK failureIDS_33=Writing ID_BLOCK successIDS_34=Restarting device IDS_35=Device restart failedIDS_36=Device restart successIDS_37=Execute failureIDS_38=Execute successIDS_39=Now testing devices, total number of blocks(%d), first block(%d)IDS_40=Starting to download filesIDS_41=File download failureIDS_42=Fila download success, time elapsed was(%dMS)IDS_43=Staring to wipe system driveIDS_44=System drive wipe failedIDS_45=System drive wipe completeIDS_46=Starting to download files to RAMIDS_47=File download to RAM failureIDS_48=File download to RAM success, time elapsed was (%dMS)IDS_49=Timeout waiting for Loader Rock usb deviceIDS_50=Execute GO command failed
3. Open MD01-MydroidDevTool_v1.0-2010-0504RkAndroidToolsetting.ini and replace "Chinese" with "English" [/quote]what are the improvements made in this update?
 

·
Registered
Joined
·
18 Posts
I received my apad two days ago and this product is just incredible! I jsut want to understand what version I have and be sure if the new firmware is for me!I received the version WITHOUT CAM (pity) with white back-shell... IS IT THE ORPHAN M003 ?WHAT CAN I DO TO BE SURE IF THIS NEW FRIMWARE IS SUITABLE TO MY DEVICE? Thank you so much!
 

·
Registered
Joined
·
41 Posts
@ale.f76Go into 'Settings', scroll down to 'About MID' it's the last option on my device (some say 'About device', while others say 'About my phone') and under Firmware it will say 1.5. Unless someone has come up with a hack already, all these devices are on Cupcake (Android 1.5).
 

·
Registered
Joined
·
18 Posts
[quote author=Mikeami link=topic=341.msg3616#msg3616 date=1275310141]@ale.f76Go into 'Settings', scroll down to 'About MID' it's the last option on my device (some say 'About device', while others say 'About my phone') and under Firmware it will say 1.5. Unless someone has come up with a hack already, all these devices are on Cupcake (Android 1.5).[/quote]Thank you. But actally, what i meant was if MY HARDWARE IS COMPATIBLE WITH THE NEW FIRMWARE.Anyway I checked out the info as per your post and got the follwing data:Model: "SDKDEMO" (what does this mean???)Firmware version: 1.5 (vonfirmed)Kernel version: 2.6.25 rockchip version 1.2.7 (ruiguan)Does al this helps me to be sure I am not burning out this unit???
 

·
Registered
Joined
·
18 Posts
[quote author=ale.f76 link=topic=341.msg3705#msg3705 date=1275340749][quote author=Mikeami link=topic=341.msg3616#msg3616 date=1275310141]@ale.f76Go into 'Settings', scroll down to 'About MID' it's the last option on my device (some say 'About device', while others say 'About my phone') and under Firmware it will say 1.5. Unless someone has come up with a hack already, all these devices are on Cupcake (Android 1.5).[/quote]Thank you. But actally, what i meant was if MY HARDWARE IS COMPATIBLE WITH THE NEW FIRMWARE.Anyway I checked out the info as per your post and got the follwing data:Model: "SDKDEMO" (what does this mean???)Firmware version: 1.5 (vonfirmed)Kernel version: 2.6.25 rockchip version 1.2.7 (ruiguan)Does al this helps me to be sure I am not burning out this unit??? [/quote]NOOOOOOOOOOOOOOOOOOO!!!!I TRIED TO UPDATE THE FIRMWARE BUT... WHEN IT STARTED AGAIN...FORMATTING THEN THE UNIT SWITCHED OFF ....AND COULD NOT START IT AGAINSO I TRIED TO UPDATE AGAIN BUT NO SUCCESS... THE RKANDROID TOOL SAYS "ERROR"PLEASE HELP!! WHAT CAN I DO?
 

·
Registered
Joined
·
160 Posts
First, stop panicking.Second, did you do the second update like this:* Turn off aPad, but be sure that the switch is ON.* Hold menu button before plugging in aPad into USB (the left one of the rocker switches)* Keep holding benu button* Start update procedureIt will probably work then.The aPad does a crazy thing for updates: If you connect the powered off unit to usb while holding the menu button, it will report as a different USB device than when you just connect it the usual way. This seems to be kind of a service mode which allow flashing the system regardless of any contents, so it should always work. I hope this is right, as it would make the system pretty much unbrickable and would make experiments much safer.
 
1 - 20 of 34 Posts
Top