yashsingh1/xdaforums huggingface dataset:
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Looking at your reply, I'm confused.

Initially, I found a man posted on S.D. saying that he is able to get 1GB RAM based on modified nvflash package. The method is the same as the one in the OP's link. I personally did an experiment.

1. nvflash TeamDRH 350MPrep ---> G-Harmony ICS ---> 512MB detected

2. nvflash TeamDRH 350MPrep ---> Flashback 9 ---> 512MB detected

3. nvflash Malata original one ---> Flashback 9 ---> 1024MB detected

Since Flashback 9 is the same package but different situations resulted in different RAM size, it proves that nvflash package did play a role in the determination of RAM size.

Therefore, I followed that method to modified the nvflash package:

nvflash modified CM7 package (given in the linked post) ---> G-Harmony ICS ---> it won't boot, i.e. loops at Malata logo screen

I found that I have to delete the "odmdata=xxxxxx" string in the bat file of the CM7 nvflash package in order to get the zpad to boot. Therefore, I tried again. This time it boots but only 512MB RAM is recognized.

nvflash modified CM7 package ---> G-Harmony ICS ---> 512MB detected

I don't know why the user, providing this method, can boot without deleting the odmdata string in bat file or get 1GB RAM detected. Since fosser2 from TeamDRH and nobe here stated that in order to get 1GB RAM, kernel needs to be edited, I finally gave up.

After reading your reply, it seems that I might still get 1GB RAM without kernel editing. Can you please give me some instructions regarding it?
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
That odmdata parameter is what, I think, defines the amount of RAM on the tablet. So, you will need to include it when you do the nvflash. (There is some uncertainity here: Different nvflash binaries and different bootloaders seem to use different values in the .BCT file for the same purpose.)

The important thing to realize here is that you should only use the nvflash images meant for your tablet. If you use images meant for another device, like the gTablet, then you could have all sorts of problems. The .bct file, in particular, which is copied, along with the odmdata value, into the BCT partition (part2.img) of the device, is very tablet-specific. For instance, it holds the chip-specific values needed for the tablet firmware to correctly initialize the DDR-RAM and NAND chips. It also contains things like the amount of RAM installed on the tablet. It may also contain the amount of system RAM set aside as video RAM.

The other non-Android partitions images (for the PT, EBT & MBT partitions) are almost equally tablet-specific.

So, the first thing that you have to do is to download the nvflash image files meant for your Zpad model--there being other Zpad variants with/without 3G, which boot from the EMMC chip instead of NAND (Zpad T8), etc. After you've downloaded the correct image files, run nvflash and boot into the stock ROM and get me a dmesg output (see thread in post #1 for the commands to run).

But first, as a quick test, change the odmdata parameter in zpad-cm7rc4-2.3.3.rar's download.bat to read 0xbc0c0011. Then see if you can load G-Harmony ICS version 1.5. The newer versions of ICS and JB ROMs have a kernel which has a bug which causes that looping behaviour on some tablets.
[G Tablet Q&A, Help & Troubleshooting] digimon04:
I 've downloaded the Malata original nvflash pack for my Zpad T2 variant. The odmdata reads 0xbc0c0011 while the one in the CM7 nvflash pack reads 0xba0c0011. I will nvflash it again and give you the dmesg output ASAP.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Yeah, I noticed that discrepancy--which is why I asked for the modification.

Can you make 2 sets of outputs? One with odmdata set to 0xbc0c0011 and another with it as 0xba0c0011? Post 2 zip files, with each labelled to clearly mark the odmdata that was used for each set. I'd like to find out what difference the odmdata makes on the Zpad T2.
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Today, I've did several tests.

Firstly, I modified the CM7 package found at OP from odmdata 0xba0c0011 to 0xbc0c0011 and enlarged the system partition size. Then I installed G-Harmony ICS 1.5 after nvflash. I got same result as if odmdata is 0xba0c0011.

nvflash CM7 package (mod from 0xba0c0011 to 0xbc0c0011) ---> G-Harmony ICS ---> loops at Malata logo screen, i.e. stuck at logo screen, screen goes dim, and then reboot, stuck at logo screen. It loops forever.

I also started modifying the Malata nvflash package which is specifically for my Zpad variant. The odmdata inside the bat file reads 0xbc0c0011. The result is the same as above.

nvflash Malata original one (0xbc0c0011) ---> G-harmony ICS ---> loops at Malata logo screen......

The G-Harmony ICS I referred to as above is v1.5. Latest build makes the tablet stick at logo screen which is different from above situation. The screen will not go dim nor reboot.

It seems to me that the odmdata is affecting the RAM size. But with it being in the bat file, the ROM so installed subsequently will only loop at logo screen. I have attached the outputs from the commands in OP. I got them just after nvflashing the CM7 package with 0xba0c0011 odmdata. I cannot produce the output from Malata original ROM with 0xbc0c0011 odmdata as the ROM is not rooted and terminal emulator won't work. But I can tell you it has 1GB RAM detected.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
I like your initiative, but we need to be systematic about doing these tests. Let's use the original T2 nvflash images and get some logs before we move to ICS or JB.

This, for instance:

seems to be the same as this:

What are the exact steps that you're following to get ICS installed? Are you modifying the *.cfg files to enlarge the system partition? Are you either doing a "wipe data/factory reset" in CWM, or, better yet, repartitioning the internal SD card and then formatting cache before each ICS install attempt?

See below.

Thanks for the logs, but get another set with CM7 and odmdata=0xbc0c0011.

You can omit the "su -c" from the dmesg command line with the kernel in your stock ROM. Ie. none of the commands need root permissions to run on kernel versions 2.6.32.x. And, you can install Terminal Emulator from market.

If you can't install Terminal Emulator, then run the commands via adb. On a PC, run:

C:\> [B]adb shell dmesg > dmesg.txt[/B]
C:\> [B]adb shell cat /proc/meminfo > meminfo.txt[/B]
C:\> [B]adb shell free > free.txt[/B]

Things to do:

1. Since the TeamDRH package lets you install ICS with 512MB of RAM, add a --odmdata=0xbc0c0011 parameter to the batch file and try again.

2. Get 2 outputs for both odmdata values after stock nvflash.

3. Get output for --odmdata=0xbc0c0011 after nvflashing CM7. This is because the .bct files are the same in the Malata T2 nvflash images (that I have) and the CM7 package in OP, but, the bootloader.bin files are different. We need this for comparison against sets in #2.

4. Which Malata T2 rar file are you using?
[G Tablet Q&A, Help & Troubleshooting] digimon04:
I understand it may be confusing. Let me explain a little bit.

In response to your reply #6, I started nvflash the CM7 with 0xbc0c0011 to see if I can load the G-Harmony ICS. But the answer is negative.

After that, I nvflash my original Malata package with 0xbc0c0011. I tried to load G-Harmony then. The answer is also negative.

My procedure is the same as in OP, i.e. replace the new recovery.img from TeamDRH's, enlarge the system partition in cfg file, wipe data and dalvic twice, etc.

The second quote and third quote in #10 are actually the same. I just want to make it for easy reference.

Regarding the dmesg output from Malata original ROM, I installed Terminal emulator 1.0.52 yesterday but it won't work normally. The keyboard on screen has no keys on it. I can't type any command.

I'll produce the dmesg output from CM7 with 0xbc0c0011 today and do the rest of the request in #10.
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Here is the finding:

1. If I add the odmdata (either 0xbc0c0011 or 0xba0c0011) to the bat file in TeamDRH package, it will stick at 3 birds screen. I can't even load into recovery. "recovery key detected" as well as "loading into recovery kernel" is shown on the upper left hand corner but it stuck at that screen forever.

2. see attachment for the outputs from Malata nvflash with 0xbc0c0011 and 0xba0c0011. However, "cp /proc/meminfo /mnt/sdcard/meminfo.txt" and "free > /mnt/sdcard/free.txt" gave "not found" as output.

3. see attachment

4. The Malata T2 nvflash I use is T2_nvflash_mp_wifi_20110801
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Well, this was a long shot anyway. Looks like you need both the amount of memory and the correct memory map (see below) to boot a kernel. Changing the amt. of memory alone isn't sufficient.

There is another thing to check, though. Can you try 0xbc0c0011 again using this recovery CWM-5.5.0.4Beta15 instead?

There's no discernable difference in the kernel dmesg outputs between odmdata=0xbc0c0011 and odmdata=0xba0c0011 within each set, so stick with odmdata=0xbc0c0011 from now on. However, between CM7 and the Malata stock ROM there were differences. On the stock ROM we have this memory map:

Kernel command line: [B]mem=256M@0M nvmem=256M@256M mem=512M@512M vmalloc=384M[/B] video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1011 bspversion=0202100907 btmac=78d76d131a00 tegraboot=nand mtdparts=tegra_nand:16384K@7424K(misc),16384K@62208K(recovery),16384K@79104K(boot),225280K@96000K(system),201984K@321792K(cache),4096K@24320K(bootbmp),32768K@28928K(logodata)

On CM7 the memory map is different because both the boot.img and recovery.img contain a kernel command line file which overrides the bootloader supplied command line (which is constructed by the bootloader from the BCT, PT, MBT and other data):

Kernel command line: [B]mem=448M@0M nvmem=64M@448M mem=512M@512M vmalloc=192M[/B] video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 bspversion=0202100907 btmac=3bbe06131a00 tegraboot=nand mtdparts=tegra_nand:16384K@12032K(misc),16384K@62208K(recovery),16384K@79104K(boot),204800K@96000K(system),222464K@301312K(cache),4096K@7424K(bootbmp),32768K@28928K(logodata) androidboot.hardware=harmony

Unless you have very good reasons for doing it, it's generally not a good idea to override the bootloader's command line with a custom one. So, from now on don't use that CM7 nvflash package. Use only the stock ROM's nvflash files, but, copy the CWM-5.5.0.4Beta15 recovery image over both the stock recovery.img and boot.img. This way, you'll get a known good (well, mostly good) recovery however you boot.

Might have to change the output file paths for the stock ROM. What's the exact command you typed and the what's the precise error message you got? Did you use the adb method or the terminal?

Any reason why you didn't download the T2_nvflash_mp_wifi(no sim)_20110829.rar version?

Things to do:

1. Quick test: Try odmdata=0xbc0c0011 with the TeamDRH 350 MB nvflash files, but, with CWM-5.5.0.4Beta15 as part09.img and part10.img.

2. Use the stock nvflash package files from now on, but, replace both boot and recovery images with CWM-5.5.0.4Beta15. Change the size of the system partition as required. Post this modified .cfg file here.

3. Open the tablet up, take a high-res pic of the board (to get the exact board type) and post it.

4. Are you trying to install this G-Harmony 1.5 ROM?
[G Tablet Q&A, Help & Troubleshooting] digimon04:
I typed exactly as in the OP's linked post and got the following result:

$ cp /proc/meminfo /mnt/sdcard/meminfo.txt

cp: not found

$ free > /mnt/sdcard/free.txt

free: not found

I did this in terminal emulator.

The one you said is for T2 wifi only model. Mine is T2 wifi only with sim slot but without 3G modem. I downloaded the corresponding package from Malata website, i.e. T2_nvflash_mp_wifi_20110801

Here are the findings in response to #13:

1. I can't boot into recovery which is the same as point 1 in #12

2. I can boot into recovery and install G-Harmony ICS. But it loops at the logo screen which is the same situation as in #9. Please find the attachment for the modified cfg file. I only enlarge the system partition size. I renamed CWM-5.5.0.4Beta15 into boot.img and recovery.img.

3. Is it a must? I really don't want to open it apart again. It requires lots of effort. Also, each time I open it up I make some damages to the edge of the tablet. Even though I experienced SOD, I'd wait until battery drain to avoid opening it up.

4. Yes
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
The stock ROM has busybox, but there aren't symlinks for commands like cp and free, so you'll have to prefix busybox to the commands you run: busybox cp ...

Incidentally, the stock ROM also has su, but it doesn't have the correct permissions to function properly. (In fact, none of the files have the correct permissions/owners.)

OK, so you have the correct nvflash package. I had figured that there were at least 2 T2 models using Google's mangled Chinese translation of the text files inside the stock nvflash packages.

I wouldn't be asking if it wasn't needed:

The build.prop and other files in the T2_nvflash_mp_wifi_20110801 nvflash package say the board type is smba1004. But, the mbtdata.img says the devicetype is 1011 (see the 1st dmesg fragment in post #13). However, the mbtdata.img from CM7 specifies a devicetype of 1002 (2nd dmesg fragment). If I have to modify the kernel to fix the boot-loop issue, then I'll need an accurate board type. Along with the part nos. of the major chips on the board. If I had the tablet, I could open it up and run some commands to find all this out. But since I don't have the tablet, you'll have to be my field guy here and post pics.

The .cfg file looks OK, but try again with a reduced size (250 MB) for system. G-Harmony ICS 1.5 is not set up to use a directory on /data as /cache--which is what has to be done with a 350 MB system and a consequently much smaller cache partition (~72 MB):

1. Use the stock nvflash package files.

2. Reduce system partition size to 250 MB: size=259784704

3. Use CWM-5.5.0.4Beta15 as boot.img and recovery.img.

4. Boot into CWM, and

a) re-partition Internal SD card, then

b) format /cache

5. Transfer ROM to tablet and install it.
[G Tablet Q&A, Help & Troubleshooting] digimon04:
This time I typed prefix busybox at the beginning of the command and got the following result:

$ busybox cp /proc/meminfo /mnt/sdcard/meminfo.txt

cp: applet not found

$ busybox free > /mnt/sdcard/free.txt

free: applet not found

After installation of G-Harmony ICS and reboot, it looped at the logo screen which is the same situation as point 2 in #14.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Lovely. Another quirk in the stock ROM: Multiple, custom versions of busybox installed. Use busybox_e instead this time. When you're getting me the meminfo.txt and free.txt file get a dmesg also for correlation.

OK. Time to fix the kernel. Gimme a day or two. I'll send you a kernel which prints messages so we can see what's happening.

In the meantime, run the adb commands in post #10 while in CWM-5.5.0.4Beta15. Also the pics.
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Please find the attachment for the results.

I am experiencing problem setting up adb. I will upload the results as soon as I set up adb.

I start feeling that the kernel don't like the odmdata string. Every time when there is odmdata, the system won't boot. If you are going to edit the kernel for 1GB RAM, could you please make it non-device-specific so that all Zpad T2 variants can use it?

I am going to be on a short trip. I will complete the tests when I come back.

Thank you very much for your help.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
How were these outputs collected? Ie. For each set which nvflash package did you use? Did you nvflash some other images in between? Because now there are differences between the two stock ROM dmesg outputs for different odmdata values when previously there weren't. Did you do the initial run correctly?

As I said in post #4, the kernel should support 1 GB of RAM without any changes. What we have to find out (and fix) is why the kernel boot-loops on your tablet.

Time for another experiment: Follow the steps specified in post #15, but, this time remove the odmdata parameter from the batch file before doing the nvflash using the stock image files. All other installation steps remain exactly the same. Get the outputs as before.
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Just a quick update. I tried the newest 4.2.2 ROM from TeamDRH where it has been posted recently here. No loops at logo screen. The new kernel works flawlessly. I'm using it now on the trip. So far so good. The only problem remains at the 512MB RAM.

I collected the data with the original Malata package with 0xbc0c0011 first. Then I revised the odmdata to 0xba0c0011 and nvflash again. From there, I collected the data. Each time after nvflash, I had wipe data and cache before booting into system. Once booting into system, I installed terminal emulator and typed the cammand exactly as you said.

I highly appreciate your help. But could you tell me how are you going to get the 1GB RAM? If it doesn't require kernel modification, is it just to edit the file(s) inside nvflash package?
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
It's a newer kernel code base (version 3.1.10), so that boot-loop bug may not be present. The older 2.6.32.x kernels (in the stock ROM, in CM7 and CWM) also don't have it because they too boot fine.

1. Use the stock nvflash image files.

2. Replace the stock CWM with DRH CWM-6.0.2.8 and

3. Change the system partition size to 400 MB (size=419430400) in the stock android_fastboot_full_i_malata.cfg file.

4. Nvflash this modified stock, then boot into CWM-6.0.2.8.

5. Repartition internal SD card. Format /cache.

6. Transfer and install DRH JB 4.2.2 ROM.

This procedure is correct, but, the problem is that I'm seeing 2 different results (post #12 and post #18) from the same procedure and I don't now which sets of outputs to trust.

I know its easy to get confused when doing so many exploratory nvflashes, so if you didn't do the first set (post #12) correctly, its fine. Just tell me and I'll discard that set and use the outputs in post #18 as being correct.

Also, are you positive that you installed G-Harmony ICS v1.5 V6 Supercharged exactly as outlined towards the end of post #15? If there is any confusion, or you're unclear about any of the steps, tell me, and I can explain things in more detail.

Kernel mods are required, but, to fix the boot-loop issue, not to get it to recognize the 1GB of RAM. As explained before, the bootloader determines the amount of RAM on the tablet (from the .bct file(?) and the odmdata parameter) and passes this to the kernel. (Which is why we have to resolve this odmdata output mismatch.)
[G Tablet Q&A, Help & Troubleshooting] iampik:
Hi there!

I have clone of Malata Zpad T2 - 3Q TS1004t (distributed in Russia) :)

TS1004T has wifi,gps,3g and 1GB of RAM

I faced 512MB problem when i installed TeamDRH 5.2 Jelly Bean 4.1.1

But somewhere i downloaded working nvflash package with 1GB RAM support

When TeamDRH released 5.3v i installed it from recovery menu using update.zip. Everything was fine.

Now we have the same 512MB limit with TeamDRH Dirty Bean 4.2.2

I attached dmesg,free,meminfo outputs for 1GB DRH 4.1.1 and 512 MB DRH 4.2.2

I also attached NVFLASH zips.

It would be cool to enable all RAM =)

P.S

I tried that:

1. Use the stock nvflash image files. (i used NVFLASH_1GB_4.1.1.zip)

2. Replace the stock CWM with DRH CWM-6.0.2.8 and

3. Change the system partition size to 400 MB (size=419430400) in the stock android_fastboot_full_i_malata.cfg file.

4. Nvflash this modified stock, then boot into CWM-6.0.2.8.

5. Repartition internal SD card. Format /cache.

6. Transfer and install DRH JB 4.2.2 ROM.

Stuck at logo forever.
[G Tablet Q&A, Help & Troubleshooting] gmenik6:
good info never think of that
[G Tablet Q&A, Help & Troubleshooting] iampik:
Keep waitin' for rajeevvp answer =)
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Where did you get the image files in the NVFLASH_1GB_4.1.1.zip file? Is it for your specific tablet model or from another related tablet?

Not surprising--the nvflash NAND images in the 512MB zip file is for the gTablet which constrains the kernel to only using 512MB of RAM.

I've got all your files and I'll look at the logs and the image files in a few days, then send you a test kernel to try out.
[G Tablet Q&A, Help & Troubleshooting] iampik:
Hello.

I downloaded it from 3q ts1004t related forum.

so i think that ROM is based on the original ts1004t FW.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Which forum? Specific links help.
[G Tablet Q&A, Help & Troubleshooting] iampik:
it's Russian site - 4pda.ru
[G Tablet Q&A, Help & Troubleshooting] JohnnyInBriz:
How's the test kernel going rajevvp?
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Far too busy these days, so no time for any of this fun stuff. May have some free time this weekend...
[G Tablet Q&A, Help & Troubleshooting] iampik:
Keep waiting for rajeevvp :)
[G Tablet Q&A, Help & Troubleshooting] iampik:
Still waitin' :)
[G Tablet Q&A, Help & Troubleshooting] iampik:
:crying::crying::crying::crying:
[G Tablet Q&A, Help & Troubleshooting] mazharoddin:
I could able to install Adam JB on my Malata t2

I could able to install Adam JB on my Malata t2 3g/GPS i.e HCL ME AP10-A1 after modifying its .bct and bat file, you can find more details here wwwdotmazharuddindotcom/content/jelly-bean-rom-malata-t2-hcl-me-tablet-ap10-a1-3g-gps ...from couple of days am using it and its working fine without having much issues, but here and there some crashes observed on first boot ...you can give a try aswell.. hope it may work for you aswell ... :)
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Please take a look at this

http://xdaforums.com/showthread.php?t=2337848
[G Tablet Q&A, Help & Troubleshooting] mazharoddin:
Thanks for sharing the link, i am familiar with kernal compilation in general , however it requires lot of testing to make sure its not breaking any other working functionality ..moreover i could able to get 728MB RAM and my tablet is running smooth , any way I can give a try...but if you are looking for a working JB 3G ROM for Zpad T2 with around 700 MB RAM then you can follow my link for now. Thanks.
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Thank you very much for your help. If you can compile a kernel, I could post back to that chinese forum for a larger test group including me.

The method you mentioned is about the installation of 4.1. However, TeamDRH has already released the newest 4.2.2 for Gtablet. Maybe due to RAM issue, the tab just runs sluggishly. I hope the tab could run smoother with more RAM. Besides, this kernel (fosser2's github) is designed for Gtablet which might give you a working camera and USB OTG.
[G Tablet Q&A, Help & Troubleshooting] mazharoddin:
hi, please let me know from where i can download the kernel source for Malata T2 ( I have Malata T2) , but please note that I will try my best , but I can't guarantee that I will spend time on it definitely because of my other personal commitments/issues, moreover my tab with current ROM which I published working fine without any major issues, so become bit lazy to try ...
[G Tablet Q&A, Help & Troubleshooting] digimon04:
Mine is also Malata T2 but without 3G.

Do you mean the kernel source from Malata? I think they never release the source...... but why do you need it? It's rather old kernel, 2.6.32.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Sorry about that, but apart from being extremely busy these days, my desktop, which had been randomly and spontaneously rebooting for the past month, has now died. So, until I either fix it, or, buy a new dev box, any work involving serious programming is out. For everything else, though, I'll still be around (occasionally).
[G Tablet Q&A, Help & Troubleshooting] iampik:
keep waiting till the end. :)