yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] sreezhere:
Flashing stock rom

DISCLAIMER:This process may damage your tab or void warranty.Do at your own risk.You are solely responsible for anything that happens following this method.

Ok! you have the update.img with you

1. Copy the AFPTool.exe in attachment into C: drive of windows.Copy update.img to same C: drive

2. Open a command terminal in windows as administrator.type

cd c:\

c:

3. type

AFPTool.exe -unpack update.img abc

You will see something like this:

Check file... OK

------- UNPACK ------

HWDEF 0x00000800 0x000003AC

package-file 0x00001000 0x0000022D

Rock28Boot(L).bin 0x00001800 0x0001B85C

parameter 0x0001D800 0x00000208

Image/misc_data.img 0x0001E000 0x0000C000

Image/misc.img 0x0002A000 0x0000C000

Image/kernel.img 0x00036000 0x00503A23

Image/boot.img 0x0053A000 0x00033004

Image/recovery.img 0x0056D800 0x00141004

Image/system.img 0x006AF000 0x02AF6000

SELF 0x00000000 0x031A6004

Skip SELF file.

update-script 0x031A5000 0x000000F7

recover-script 0x031A5800 0x0000003D

Unpack OK!

Now you will have a new folder inside your working folder called abc. It contains all files from the update.img. (loader,parameter,boot.img,system.img,recovery.img,kernel.img,misc.img etc)

4. Turn off your tab.Remove sdcard.Plug in charger(Even if you have enough charge) and connect to PC via usb cable of ur tab.

Press reset pin and Menu button together.Release reset pin and continue holding Menu till windows detects device.

5. Using device manager in windows,install correct driver for this device from Driver folder in attachment.If installed correctly,the driver shows as "Class for rockusb".

6. Run RK29 update.exe as administrator.It shows "Found RKandroid loader rock usb" if drivers installed correctly.

Erase IDB,tick all columns,select corresponding files in abc folder in it.Use your update.img itself in backup column and click Run

7.If ok,after some time tab boots up in stock rom.

image attached is just to give u an idea.excact values may be different..Cheers :p
[Upgrading, Modifying and Unlocking] sreezhere:
[/QUOTE]Will this app unroot itab without any xtra files like firmware or ROMs. You mean we'll just have to run this app to root and unroot? Which itab model do you have? I have 12T055. Customer Care says 12T055 & 65 are upgradable to Android 4.0 ICS.

And about the rooting. I am already getting root shell with # sign in Android Commander's adb. Is itab prerooted or something(like Micromax Funbook). I'm not sure if there's any fault wid Commander. I haven't tried any root commands yet.[/QUOTE]

Yes.rooting&unrooting is simply done by this Gingerbread app.mine is I2T65. the method i mentioned doesnt need ADB shell.the # sign is there in I2T65 also,but its not rooted.Try Root checker app from market.;).
[Upgrading, Modifying and Unlocking] HEXcube:
Itab root in adb

Could it be possible that there is root permission in adb shell, but not accessible from device (unless rooted)? I can use Android Commander to read & write save files of apps and games, which i believe can be done only using a rooted device.

Your iTAB is a newer model. One of the Customer Care agents said only 12T065 is upgradable to 4.0 ICS (but i'm not sure if they're right as some others says both 55 and 65 are upgradable).
[Upgrading, Modifying and Unlocking] sreezhere:
There is nothing like "not upgradable to ics".it only means there may not be an official ics release.official ics is nothing but a custom ics fully fine tuned for our device.;) so u can use custom ics roms even if official update doesnt come out(though 100% smooth function wont be there).as far as i tested,itab doesnt come prerooted.can u upload demsg.txt from your itab from 0.0 sec?
[Upgrading, Modifying and Unlocking] HEXcube:
ROOT permissions in adb

I used Root Checker on device and got 'Not Rooted' notice. But i'm gettin' Root Access Ok in Android Commander and # in adb.

And about official update. It would be much more optimised for a specific device than a custom one, right? So, i don't want to risk the stability of the current official Gingerbread s/m with a custom ICS.

I think it's better to try out ICS on an SD card. Do you know how to install android on mem card? I think it would be fun to have 2 OSs at the same time(without havin' to sacrifice the stability of official gingerbread).

---------- Post added 4th September 2012 at 12:05 AM ---------- Previous post was 3rd September 2012 at 11:15 PM ----------

Do we have to backup only the backup partition? What about boot,recovery and system partitions? Wouldn't it be better to do a system restore to get a clean ROM backup? Is this equivalent to a Nandroid?

And now about rootin'. Don't we have to install tools like Busybox,root shell, super user,etc to get full benefits of rooting and to manage a rooted device efficiently?

---------- Post added at 12:16 AM ---------- Previous post was at 12:05 AM ----------

I saw something like

dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096

on net and tried it on adb. It dumps boot.img on sdcard. So why use rkdump instead of this adb command?
[Upgrading, Modifying and Unlocking] sreezhere:
There are various methods for dumping rom.adb method and rkdump are examples.rkdump is quite simpler.if you are afraid of rooting ur device,u can use the adb method.Gingerbreak installs su,busybox and other essential root tools.Also u can dump each of ur system partition seperately as u did.but in itab,it is enough to dump backup partition as that has all the data(boot,loader,kernel,sys,recovery,misc)..so why waste ur time dumping each?
[Upgrading, Modifying and Unlocking] HEXcube:
ROM backup

I found out how am i getting Root access on adb(Oma told me the reason). It's bcoz in default.prop file has a value ro.secure=0. In most standard devices, ro.secure=1 and hence no root access through adb. However, some manufacturers don't care to set it to 1,as in the case of iTab. You could say that iTab comes pre-rooted with adb root though,still there'll be no root on device itself.But,i'm not worried as Gingerbreak uploaded by sreezhere is there for the rescue.:D

I assume if i restore the backup.img, i'll get the device like factory restore has been done on it. Or will i get the filesystem in the exact state at which backup was taken(like Nandroid)?

And one more thing: the dump of backup partition done using dd method was 512MB in size. Why is it so?
[Upgrading, Modifying and Unlocking] sreezhere:
Yes.backup partition can restore as factory device only.If u need backup similar to nandroid,u may have to backup system partition seperately and flash accordingly.There are CWM custom recovery available for gingerbread.U can try flashing it if u r keen on doing a nandroid backup(nobody has reported succesful testing yet)

http://xdaforums.com/showthread.php?p=29419029
[Upgrading, Modifying and Unlocking] HEXcube:
Different Rom backup size

Ok, i just want a factory reset. I'll restore the app data manually to get all my save game data. But , do you know why the size of backup.img obtained using adb and rkdump are different? I guess it is the difference in compression levels or formats.

---------- Post added at 03:23 PM ---------- Previous post was at 03:00 PM ----------

Do you know how to dual boot ICS on SD card for iTab or any other Rockchip Tablet?

Are there any projects,forums or anything focussing on rockchip dual boot, custom ROM, rootin and stuff like that?
[Upgrading, Modifying and Unlocking] HEXcube:
I noticed that there is no Wifi Tether and Hotspot option in Wireless and Network Settings. This feature is supposed to be there since 2.2 Froyo.

But i can indirectly access this feature through a shortcut. Does your new Custom ICS have this feature? I wanted to know whether this is a problem with all Rockchip devices or just iTab.
[Upgrading, Modifying and Unlocking] HEXcube:
Itab has no manufacturer info

My iTab in shows manufacturer name as unknown in Google play and PC Suites. If i modify build.prop's manufacturer field to INTEX, will it cause any problem?
[Upgrading, Modifying and Unlocking] HEXcube:
New iTAB with Android 4.0

INTEX has recently released a new iTAB with Android 4.0 :) . Hardware specs seem to be similar to previous 1GB RAM models(12T055 & 12T065). This could mean 2 things:

1. Official update soon.

2. We could get the official stock ICS ROM if it is leaked.
[Upgrading, Modifying and Unlocking] sreezhere:
OMA JELLYBEAN on Intex Itab

:cowboy:

OMA JELLYBEAN works smoothly on itab..so far no flaws detected..

http://xdaforums.com/showthread.php?t=1903745

use this fix attached for autorotation..all credits to oma
[Upgrading, Modifying and Unlocking] HEXcube:
Great news

I thought Jelly Bean won't run on iTAB. It's got 1GB RAM,but isn't the processor too slow for JB?

With improved GPU accelerated rendering, the UI should be better and smooth on ICS and JB.Gingerbread had no GPU acceleration for UI.

Did you run any games, apps or benchmarks on iTAB with ICS and JB. If not please do. I'll test with my Gingerbread iTAB and then we can compare the results.
[Upgrading, Modifying and Unlocking] Oma7144:
Just to give you an idea ;)

- Oma -
[Upgrading, Modifying and Unlocking] sreezhere:
benchmarks with oma jb

Hey OMA.I haven't used NoFrill CPU governer after flashing OMA Jb.only after running it the CPU gets over clocked??
[Upgrading, Modifying and Unlocking] Oma7144:
Ok, let me see what the kernel supports. Install CPU Tweaker and upload the result.

- Oma -
[Upgrading, Modifying and Unlocking] HEXcube:
Overclocked mod?

It's not fair to compare normal clocked stock ROMs with overclocked mods. Most of the performance increase may be due to overclocking and not due to effectiveness of the mod. Could you upload the benchmark results for Stock vs Mod(either both overclocked or both normal clocked)
[Upgrading, Modifying and Unlocking] HEXcube:
iTAB Stock GingerBread Benchmark

Here are the results of antutu benchmark performed on iTAB 12T055 with Stock Ginger Bread 2.3.1 OS(without overclocking)
[Upgrading, Modifying and Unlocking] HEXcube:
Root ICS

Did u root your tab after flashing ICS and JB? As GingerBreak is only for GingerBread(well, i suppose or is it so?), a new way must be found to root iTAB with ICS. If you have done so, please share your ideas.
[Upgrading, Modifying and Unlocking] Oma7144:
All my imgages are already rooted.

- Oma -
[Upgrading, Modifying and Unlocking] HEXcube:
Root Stock ICS

But, do you know how to root Stock ICS ROMs on Rockchip devices?
[Upgrading, Modifying and Unlocking] sreezhere:
ICS

http://www.flashmyandroid.com/forum/showthread.php?309-ROOT-TOOL-for-ICS-4-0-3

http://www.unlockroot.com/

these links gives method to root ICS 2918 tab..not idea if it works for itab...
[Upgrading, Modifying and Unlocking] HEXcube:
Cannot start recovery!

I pressed and held menu power button on boot. Then a screen with Android logo and exclamation mark appears. No matter how much i waited, the screen didn't change. I had factory reseted and erased internal SD memory before. Could this have wiped the recovery partition?

Edit: Here's the solution!

Hold the menu power buttons at boot to get into recovery. When you see the belly open Android logo and exclamation, press keys randomly especially volume down power key. Most of the time, it'll get into recovery menu. Thanks to sreezhere for his help(View Post).The recovery problem is still there in Android 4.0.4 Update for iTAB.

And about the factory reset, it only resets data partition(and SD card if you choose). Therefore, recovery and other partitions remain untouched.
[Upgrading, Modifying and Unlocking] Jalaj007:
Help plz....

There is software problem with my intex i-tab. I had installed "easy battery saver" application and then customized the saving profiles. Accidently i had set screen brightness too low which resulted in totally switching off of screen light. Now nothing is visible on screen and i cant switch the profile back. One thing i must tell u i have not rooted my i-tab.

Please tell me any method by which i can wipe all applications or just remove that application.
[Upgrading, Modifying and Unlocking] HEXcube:
No Brightness Problem Solution.

Don't panic i've done the same thing before.

Method 1:Just switch off the tab by holding power button down for about 15~20 seconds. Turn on again. After you turn on guess the position of lock and unlock it(as the screen is blank you wont see any thing). Tap at the position of status bar(the bar at bottom where you see notifications).Now,slide your finger around the relative position of brightness indicator. Hope it works.

Method 2: If you have a Windows PC-Use MoboRobo PC Suite for Android and connectivity drivers. I couldn't find drivers, so i installed MobileGo and after that MoboRobo could work. Ensure that usb-debugging is turned on in device. You don't need to root the tab as USB-root is enabled by default in iTab. Now connect the tab to PC(don't turn usb storage on). Go to screenshot option in MoboRobo and turn click fullscreen and viola! you can see your device's screen. Now adjust the brightness on device by looking at what is displayed on PC.

Hope that helps.
[Upgrading, Modifying and Unlocking] Jalaj007:
No Brightness Problem Solution.

HEXcube

Thank you very much.

:)
[Upgrading, Modifying and Unlocking] sreezhere:
stock recovery

this problem occurs to me also..at the android exclamation mark,try pressing vol down button repeatedly and try al button combinations ..some will get it into recovery.. i tried several times but never got the exact key combnation..most of the times as i get tired trying to get into recovery,sum button accidentally get into recovery..lol..seems funny but its true..
[Upgrading, Modifying and Unlocking] sreezhere:
stock recovery

i have tried getting into recovery of omas fw using menu+power button..works all the time smoothly..so recovery problem in stock GB is firmware related.and specific to OS.intex has knowingly or unknowingly made an error in kernel related to key combination to recovery i guess.and i have got into recovery of stock GB also,so its possible..depends on luck ..really..
[Upgrading, Modifying and Unlocking] sreezhere:
Obtaining dmesg

To obtain dmesg from 0.0 sec, connect tab to adb,reboot tab n then do dmesg..
[Upgrading, Modifying and Unlocking] HEXcube:
Updated to Official Android ICS

Yoohoo! I got my iTAB updated to Official Android 4.0.4 Ice Cream Sandwitch! Lot better and faster than the Stock GingerBread 2.3.1.

However, i've got some connectivity problems: adb no longer detects the device and so Android Commander ain't working anymore. However, MobileGo works fine(if not better) and MoboRobo is having trouble detecting the device. Anyway, i need the usb drivers for adb and flashing(or are they the same?). Do Android devices normally require different drivers for different Android versions?( in the sense that hardware remains the same). Please upload compatible drivers.
[Upgrading, Modifying and Unlocking] HEXcube:
iTAB rocks with official ICS update!

iTAB runs better,faster and super smooth on the new Official Android 4.0.4 ICS.I've attached dmesg from 0.0 sec (boot time) obtained from iTAB with the new Official firmware . You can use it to check if iTAB is compatible with your device and hence to see if you can use it's firmware.

Pros:

-> Everything appears faster but, soon I found out the main reason behind the speed: an Overclocked CPU @ 1.2GHz ! I didn't expect the manufacturer itself to do this.Normally,manufacturers doesn't set the cpu at it's highest clock rate.I had planned to overclock it, and luckily they made our work easy by already doing it! It's OK if there are no side effects( i've read that battery will be drained faster)

->RAM is shown as 1GB as opposed to 800MB on Stock ROM(where's the reserved video/graphics RAM? )

->4.0.4 is the most stable version of ICS to date.

->For the UI,there's no laggy,buggy and boring Rockchip Launcher either. We have fast and smooth Stock ICS Launcher.

->Portable HotSpot problem is fixed. Now it's possible to create real Wifi HotSpot(Access Point) without root!

-> Some games which didn't work earlier works now!:) Temple Run, Muffin Knight, Blood and Glory Legend, to name a few.

Cons:

->No usb adb root The new firmware isn't pre-rooted for adb like the previous one, though root shell is accessible by su command.

->Recovery Key Combination Problem is still there, though this can be solved. Refer to this and this.

->Stock Apps are pretty much the same. Well,i didn't expect much. Anyway,we have Play Store,right? It can be taken as a plus considering there isn't as much Bloatware as Stock version.

-> There isn't anything special done by INTEX or Rockchip, most of the improvements are due to Android 4.0.4 itself.

As per the benchmarks, it has the highest score ever, beating the Stock GingerBread and even iTAB with Oma JB. If ICS is this fast,JB'll be faster. I'll upload the update images as soon as i get any kind of root:adb,temp or perm. According to sreezhere,it may be possible to produce a faster ROM by combining Official kernel with Oma JB. Odyx Loox has a high score on Oma JB @1.1 GHz (See benchmark results). Here are the benchmark results of iTAB on Official Android 4.0.4 Ice Cream Sandwitch:
[Upgrading, Modifying and Unlocking] sreezhere:
Fantastic...!! :) the drivers for adb and flashing are different ..both drivers that worked with oma ics in itab have been uploaded by me in post under topic ' flashing itab' ..use device manager in windows to manually install it if windows automatically doesnt detect..connect tab to pc in flash mode for installing flash mode drivers..cheers
[Upgrading, Modifying and Unlocking] sreezhere:
ADB drivers

here is the adb drivers
[Upgrading, Modifying and Unlocking] sreezhere:
adb driver 32 bit

adb driver 32 bit
[Upgrading, Modifying and Unlocking] sreezhere:
ADB

adb interface
[Upgrading, Modifying and Unlocking] sreezhere:
link to adb toolkit

http://xdaforums.com/showthread.php?t=1800335

This may turn useful..it lists support for rockchip
[Upgrading, Modifying and Unlocking] HEXcube:
Working adb

The adb found inside MobileGo PC Suite v2.1's folder works fine for iTAB. I've attached this adb here.The adb in SferaDev's Rk29 Root Toolkit also works.Android Commander works but its shell doesn't work perfectly with these adbs. So, i used them from window's command prompt.SferaDev's adb is ver 1.0.29.MobileGo adb is 1.0.26 version but is bigger(~460kb).The windows adb binary from adb.rar uploaded by sreezhere and Android Commander v0.7.9.11 also have version number 1.0.29, but these don't work.I haven't yet tried the linux and mac binaries included in sreezhere's package. I noticed that iTAB is no longer usb adb pre-rooted. So, Android Commander won't be able to run in root mode. However, that's not much of a problem as su command is available in adb shell. su binary is present in /system/xbin.And busybox binary is also there in /system/bin. Pretty much everything needed to root the tab.

Thanks to sreezhere for notifying about adbtools. Never seen any non-rockchip targeted tool offer support for Rockchip before.
[Upgrading, Modifying and Unlocking] HEXcube:
How to manually Root iTab on Android 4.0.4 ICS

You'll need:

1.Superuser.apk and su binary by ChainsDD.(you may use Chainfire's SuperSU instead)

2. A working adb

3. A pc(win,linux or any OS which runs adb).

4. You may need drivers(sreezhere has uploaded win drivers)

Step 1: Enable usb debugging in tab and connect to pc. Install the necessary drivers if prompted.

Step 2: Push su and superuser.apk to any suitable location on tab, preferably /sdcard.

adb push su /sdcard
adb push Superuser.apk /sdcard

If for some reason /sdcard is unavailable, try copying to /data/local/tmp.

Step 3: Now elevate to root shell by typing:

su

Make sure you get #sign for the prompt instead of $. We need it for the steps below.

Step 4:Remount /system partition as writeable.

i.To do this first type

mount

and find out system's device name from the list. In case of iTAB(and many Stock ICS devices) this device name would be /dev/block/mtdblock?. ? varies for each device. I had /system as mtdblock8.

ii. Now type the following command

mount -o remount,rw -t ext3 /dev/block/mtdblock? /system

use the number you have for '?'.

Step 5: Use cat command with redirection to copy su and Superuser.apk from where you pushed it to /system/bin and /system/app respectively( don't try adb push here - it wont work bcoz the new firmware doesn't have adb root)

cat /sdcard/su > /system/bin/su
cat /sdcard/Superuser.apk > /system/app/Superuser.apk

As busybox is pre-installed in /system/bin, no need to copy them,unless you want to update the existing binary.

Step 6: If Step 4 was successful, chmod su to 06755(this should set the setuid and setgid bits for su)

chmod 06755 /system/bin/su

Step 7(Optional): If you need adb root or insecure adb as well, type

echo ro.secure=0 >/data/local.prop

or create a file local.prop with ro.secure=0 as it's content and copy it to /data

Step 8: Type adb reboot ,or disconnect the device and reboot. You should have rooted iTAB by now! :)

Reason:This works because iTab(and possibly any rk2918 device with Official Android 4.0 firmware) already has pre-installed su in /system/xbin (though not ChainDD's su).For those Terminal users, Busybox binary is also pre-installed in /system/bin. We just need to add the final piece to get root.This is of great use to developers and advanced users ,and allows to root the device from adb without using any risky exploits.I hope the ROM makers will maintain this feature in future updates, even if pre-root isn't there.

Note:This is a manual rooting method without using automatic Rooting Tools and hence not recommended for beginners. If you find this method difficult, you may try an easier method by SferaDev in [RK29][TOOL] Root RK29 Tab Toolkit thread.

Acknowledgements: Thanks to drjbliss,the researcher who discovered local.prop emulator exploit and many other exploits and vulnerabilities for showing cat copy method.I had previously used Busybox cp command. The cat method can be used directly from adb shell,thus eliminating busybox dependency.
[Upgrading, Modifying and Unlocking] HEXcube:
Enable adb root on Android 4.0.4 iTAB

adb root/insecure adb means root access for adb daemon,so that adb can work in root mode.Android Commander,QtADB or other adb GUI users may find this useful as this can enable root mode for there apps. For more information refer to this post: adb root

This method works by creating /data/local.prop file with

ro.secure=0

as it's content. You need not have rooted your iTAB prior to doing this(this may work for other devices ,but only if you can call su from adb shell).However,there's no problem if you have rooted too.

Step 1: This step isn't necessary.But,if you get any errors with the following step or local.prop doesn't get created in /data,try this. Start adb shell and elevate to superuser by typing

su

Step 2: If you get a # sign for the prompt and not $,proceed.(Else find some way to get # ;) ) Now, type the following command

echo ro.secure=0 >/data/local.prop

Step 3: Now exit the shell and reboot the device either manually or by adb reboot command.

When your device reboots open adb shell and see if you get # prompt by defaut(without doing su). Also the username would be root@root or root@shell. If yes, you have successfully attained adb root on device, enjoy :) .

Note: This method works for iTAB because firmware makers didn't set ro.secure=1 in build.prop or default.prop property files. According to the Recognised vulnerability researcher Dan Rosenburg( drjbliss ) many manufacturers set ro.secure=1 value explicitly.As a result,it's not possible to override this read only property using local.prop. So, this may not work for all Android devices. There's another property ro.kernel.qemu=1,which'll make the device think that it's an emulator and hence allow adb root. But,it may have side effects. So,it's recommended to use this property only temporarily for gaining root and reverse the changes immediately after.

Please note that this won't work on Android 4.1 Jelly Bean and above. Dan Rosenberg explains that Jelly Bean doesn't use property files to set the ownership of adb daemon.