yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] rchtk:
From the kernel log

<4>[ 5.019486] ebb 0x0001900000 - 0x0001c00000 = 3145728 (0x0000300000)
<4>[ 5.019575] pdsb 0x0001c00000 - 0x0001e00000 = 2097152 (0x0000200000)
<4>[ 5.019728] misc 0x0001e00000 - 0x0002000000 = 2097152 (0x0000200000)
<4>[ 5.019877] logo.bin 0x0002000000 - 0x0002400000 = 4194304 (0x0000400000)
<4>[ 5.019963] kpanic 0x0002400000 - 0x0002600000 = 2097152 (0x0000200000)
<4>[ 5.020118] recovery 0x0002600000 - 0x0003200000 = 12582912 (0x0000c00000)
<4>[ 5.020267] boot 0x0003200000 - 0x0003a00000 = 8388608 (0x0000800000)
<4>[ 5.020355] system 0x0003a00000 - 0x0013a00000 = 268435456 (0x0010000000)
<4>[ 5.020504] cache 0x0013a00000 - 0x001e300000 = 177209344 (0x000a900000)
<4>[ 5.020658] userdata 0x001e300000 - 0x0773b80000 = 1434976256 (0x0755880000)

In the adress order:

System, then cache then userdata. So increasing system and change start of cache and userdata of this amount increased

Now the code:

+#define MB1024 0x200000

size are in block size(512 bytes). 0x200000*512 is indeed 1Megabyte

System:

size = MB1024;

So we increased the system by new system size (MB1024)-old system size

Cache:

Move cache forward to amount of increase

start += MB1024 - SYSTEM_SIZE;

size = MB512;

UserData

Same thing

+start += (MB1024 - SYSTEM_SIZE) + (MB512 - CACHE_SIZE);

+size -= (MB1024 - SYSTEM_SIZE) + (MB512 - CACHE_SIZE);

That's actually quite well written code :)

I'd also appreciate if people document a bit what they do (thanks Schischu for the clear code) , so that everyone shares the fun!! :D won't have time to rebuild whole android myself but might play with kernel related aspects.

edit:mehhh too long to type
[Xoom Android Development] realjumy:
Maybe recovery was not installed properly. You need to be at bootloader. Try this:

adb reboot bootloader

Then, after loading, type in your PC:

fastboot devices

You should see the serial number of your device if everything is ok. Then you can install recovery:

fastboot flash recovery R.A.H._TWRPv2.6.3_bigPart.img
fastboot reboot
[Xoom Android Development] hawkstorm:
Hey [MENTION=470268]bigrushdog[/MENTION], [MENTION=697814]realjumy[/MENTION]

Will the standardization of the repartitioning allow a common build over the variants? So you guys can develop general build and keep the radios separate? Or will it have to be a separate build for each variant?
[Xoom Android Development] matt4321:
I'm familiar with fastboot and adb, I already did what you said twice and tried again didn't seem to work.... Really weird
[Xoom Android Development] Schischu:
Can you paste somewhere the kernellog?
[Xoom Android Development] realjumy:
There is a small typo in the commands for flashing boot.img. It should be like this:

fastboot flash boot boot.img
[Xoom Android Development] realjumy:
Using Everest. I am not able to use SU, it freezes...

I mean, after installing the kernel, Xoom gets blocked after optimizing apps and then my shell freezes when trying to use su.
[Xoom Android Development] Asphyx:
I agree...1Gb sets a good standard size and if you found later that you needed to increase it more at least you know you can at that point.

I also suggest anyone planning on building for the new Partition scheme should note in their rom releases that this large partition scheme is required such as adding a word like REPARTED or 1GB into the title.

i.e. Team EOS5 Reparted or EOS5-1GB (as well as the usual Wingray/Stingray notations)

Special thanks to Schischu for solving this! I see another two years worth of usefulness for this unit now!
[Xoom Android Development] matt4321:
Is that last_ksmg?

I checked that and nothing is there! Just tried again and it didn't work. Am I not meant to format internal storage? Just cache, dalvik cache and data? as instructed
[Xoom Android Development] bigrushdog:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 358.7M 48.0K 358.6M 0% /dev
/dev/block/mmcblk0p8 1007.9M 17.2M 990.7M 2% /system
/dev/block/mmcblk0p9 503.9M 8.4M 495.6M 2% /cache

Looks good to me! Only issue I'm having is the recovery thinks my /data partition is encrypted. Could the big partition recovery cook double check init.stingray.rc. I believe there is something in there causing the wonk. Other than that, looks golden!

flashed recovery in fastboot. In recovery, formatted /system and /cache, and boom!

EDIT: did a ./fastboot erase userdata then went back into recovery and formatted /data All partitions are now the proper size. This is proper.
[Xoom Android Development] shpitz461:
Kinda funny that KitKat is supposed to work on old machines yet we need a 1GB system partition... :)
[Xoom Android Development] realjumy:
Ok, this is from an Everest Non Hong Kong:

<6>[ 4.923927] mmc2: new high speed MMC card at address 0001
<6>[ 4.924535] mmcblk1: mmc2:0001 SEM32G 29.7 GiB
<4>[ 4.929476] gpt_header 0x0003b6efff - 0x0003b6f05b = 92 (0x000000005c)
<4>[ 4.931362] gpt_entries 0x0003b6efdf - 0x0003b6f4df = 1280 (0x0000000500)
<4>[ 4.931524] Primary GPT is invalid, using alternate GPT.
<4>[ 4.931602] GUID Partition Table is valid! Yea!
<4>[ 4.931680] GUID Partition Table entries: 10
<4>[ 4.931831] ebb 0x000000d800 - 0x000000f000 = 6144 (0x0000001800)
<4>[ 4.931983] pdsb 0x000000f000 - 0x0000010000 = 4096 (0x0000001000)
<4>[ 4.932071] misc 0x0000010000 - 0x0000011000 = 4096 (0x0000001000)
<4>[ 4.932221] logo.bin 0x0000011000 - 0x0000013000 = 8192 (0x0000002000)
<4>[ 4.932373] kpanic 0x0000013000 - 0x0000014000 = 4096 (0x0000001000)
<4>[ 4.932460] recovery 0x0000014000 - 0x000001a000 = 24576 (0x0000006000)
<4>[ 4.932609] boot 0x000001a000 - 0x000001e000 = 16384 (0x0000004000)
<4>[ 4.932759] system 0x000001e000 - 0x000009e000 = 524288 (0x0000080000)
<4>[ 4.932845] cache 0x000009e000 - 0x00000f2800 = 346112 (0x0000054800)
<4>[ 4.932994] userdata 0x00000f2800 - 0x0003b6ec00 = 61326336 (0x0003a7c400)
<6>[ 4.933139] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10

I had to flash EOS 3 in order to flash later the "big" kernel, if somebody else want to give a try and compare.
[Xoom Android Development] realjumy:
And 1GB of RAM...
[Xoom Android Development] Schischu:
Thank you, and here the patch which should support also Everest.

if (!is_pte_valid(&ptes[i], last_lba(state->bdev)))
continue;
+
+#define MB169 0x054800
+#define MB256 0x080000
+#define MB512 0x100000
+#define MB768 0x180000
+#define MB1024 0x200000
+
+#define WINGRAY_SYSTEM_START 0x1D000
+#define WINGRAY_CACHE_START 0x9D000
+#define WINGRAY_USERDATA_START 0xF1800
+
+#define EVEREST_SYSTEM_START 0x1E000
+#define EVEREST_CACHE_START 0x9E000
+#define EVEREST_USERDATA_START 0xF2800
+
+#define SYSTEM_SIZE MB256
+#define CACHE_SIZE MB169
+
+	if (start == WINGRAY_SYSTEM_START || start == EVEREST_SYSTEM_START)
+	{
+	printk("Fixing up system part\n");
+	size = MB1024;
+	}
+	else if (start == WINGRAY_CACHE_START || start == EVEREST_CACHE_START)
+	{
+	printk("Fixing up cache part\n");
+	start += MB1024 - SYSTEM_SIZE;
+	size = MB512;
+	}
+	else if (start == WINGRAY_USERDATA_START || start == EVEREST_USERDATA_START)
+	{
+	printk("Fixing up userdata part\n");
+	start += (MB1024 - SYSTEM_SIZE) + (MB512 - CACHE_SIZE);
+	size -= (MB1024 - SYSTEM_SIZE) + (MB512 - CACHE_SIZE);
+	}

put_partition(state, i+1, start * ssz, size * ssz);

And here a new recovery for wingray and everest, maybe even stingray. We will see after we get our first kernellog from such a device:

http:/duckbox.info/files/xoom/R.A.H._TWRPv2.6.3_bigPart_wingray_everest.img.zip

Btw you can also create a kernel log by just flashing recovery.img. Flash it using fastboot, reboot to recovery and then just connect with adb shell while in recovery.

> dmesg

So you could check if it works before ever flashing an system image or wiping a partition.

[MENTION=4393511]matt4321[/MENTION]:

su and then dmesg. Or cat /proc/kmsg

Edit: And here is the patch for the partition debug output

info->volname[label_count] = c;
label_count++;
}
+
+	printk(" %12s 0x%010llx - 0x%010llx = %10lu (0x%010llx)\n",
+	info->volname, start, (start + size), size, size);

state->parts[i + 1].has_info = true;
}
[Xoom Android Development] realjumy:
Thanks mate. I must install your ROM after installing this recovery, right?

****

OK, at the moment we have the Wingray and Everest data. We need volunteers for the other models. It is easy to do:

[DO IT AT YOUR OWN RISK]

1.- Do a nandroid backup

2.- Install an EOS 3 rom (find it here: http://goo.im/devs/teameos/roms/eos3 ). Remember wipe cache and Dalvik cache.

3.- Reboot, unplug and plug usb and do a

adb shell

, check "allow always" in Xoom when prompted.

4.- Extract boot.img from http://duckbox.info/files/xoom/wingray_bigPart.zip

5.-

adb reboot bootloader

6.-

fastboot boot flash boot.img

7.-

fastboot reboot

8.-

adb wait-for-device

9.-

adb shell

10.-

su

11.-

dmesg

12.- Copy and paste here the chunk of info from "GUID Partition Table is valid! Yea!"

13.- Restore your nandroid backup. Then you should have your tablet as it was before doing all this.
[Xoom Android Development] Schischu:
Not really, I only build for wingray, no idea if it will work on everest.

But nevertheless, if you want to try, open the wingray_bigPart.zip and replace the boot.img (kernel) with the following:

http://xdaforums.com/duckbox.info/files/xoom/boot_wingray_everest.img.zip
[Xoom Android Development] grussinko:
Just a question - I have the original Verizon 3G Xoom, which was never sent in for the 4G upgrade. Is that technically still stingray? If so, I can try and have a shot at getting the partition data off my tablet when I get a chance later tonight.

Also to be clear, I have been running wingray ROMs for quite a while as I never activated the tablet for data through Verizon - this wouldn't have any impact on the partitions, right?
[Xoom Android Development] realjumy:
No idea for the 1st, but for the 2nd you can try to show the partitions as explained...
[Xoom Android Development] grussinko:
Understood, I was just trying to get a grasp on whether my unit is one that would be useful for getting partition data from. I won't have a chance until later this evening but I'll try and give it a shot.
[Xoom Android Development] realjumy:
Recovery ask for a password when loaded, but after pressing "Cancel" I can go to the menu. Solved as [MENTION=470268]bigrushdog[/MENTION] explained in http://xdaforums.com/showpost.php?p=47420123&postcount=116

The ROM seems like it don't finish booting, but I can access to the adb shell:

1|shell@android:/ # df

Filesystem Size Used Free Blksize
/dev 358M 32K 358M 4096
/mnt/asec 358M 0K 358M 4096
/mnt/obb 358M 0K 358M 4096
/system 1007M 177M 830M 4096
/pds 1M 108K 1M 2048

I obtain an error if I try to do an df -h

[MENTION=470268]bigrushdog[/MENTION], if you can publish an EOS 4 as it was previously to abandon it but with the new partition table, it could be great :)
[Xoom Android Development] drewski_1:
I'm just hanging at the Motorola Dual Core screen after flashing the BigPart ROM, wiping, and rebooting.

there was an error when I wiped cache, dalvik, & data saying it couldn't mount cache.

edit: also, like BRD, TWRP asked for a password like it thought things were encrypted
[Xoom Android Development] realjumy:
Give more details, please.
[Xoom Android Development] drewski_1:
I tried BRD's fastboot erase userdata and format data in recovery

this time flashing the ROM & wiping occurred with no errors (i.e. was able to mount Cache), but there doesn't appear to be a System partition?

EDIT System wasn't mounted in TWRP so partitions are OK. :o

this is the relevant (I think) output from dmesg
[Xoom Android Development] alex_72gr:
Thanks for the guide for people that do not have advance knowledge.

I want to help also, I have an everest.

All these can be done on windows cmd, right?
[Xoom Android Development] drewski_1:
my bad. system wasn't mounted :cyclops:
[Xoom Android Development] realjumy:
Yes. That's the reason why I did it without ./ or similar.

In any case, I obtained the data for Everest, so if you do it, it will be only to be sure. So if you prefer to don't risk to lost your data or something, you can simply wait until a proper ROM is released. At the moment the partitions seems to be right but the ROM for Everest is not working...
[Xoom Android Development] bigrushdog:
Haha I forgot I'm working on Stingray. But we don't have stingray offsets yet! I'll get us offsets tonight. Just a reminder, if you aren't comfortable playing around here, DONT! Once all the pieces are together, we can spoon feed it.
[Xoom Android Development] aFancyTickler:
if you need anything tested for stingray im willing to try
[Xoom Android Development] drewski_1:
i'm Wingray and even after the re-install the ROM is hanging at the Dual Core screen.
[Xoom Android Development] shpitz461:
The 3G version is known as MZ600 and nicknamed Stingray_cdma.

The 4G version is known as MZ602 and nicknamed Stingray.

You can see a full list here...

And they are incompatible, do not try a Stingray ROM on it...

You should be able to follow the instructions above and post a partition table...
[Xoom Android Development] realjumy:
After wiping cache in recovery I booted successfully the ROM and I can provide new partition data:

1|shell@android:/ # df
Filesystem Size Used Free Blksize
/dev 358M 32K 358M 4096
/mnt/asec 358M 0K 358M 4096
/mnt/obb 358M 0K 358M 4096
/system 1007M 177M 830M 4096
/pds 1M 108K 1M 2048
/cache 503M 8M 495M 4096
/data 27G 233M 27G 4096
/storage/sdcard0 27G 233M 27G 4096
/storage/sdcard1 29G 21G 8G 32768

Note: Still don't know why df -h gives me the error "-h: No such file or directory"
[Xoom Android Development] grussinko:
Thanks. Unfortunately goo.im is down at the moment so looks like it'll have to wait a bit before I can get the partition data. Unless someone has a mirror of the EOS 3 Wingray ROM handy. Trying the torrent but it's not moving very quickly.

Edit: right after posting the torrent suddenly started flying along.
[Xoom Android Development] grussinko:
Here's the partition data from my stingray_cdma (3G only Verizon Xoom)

<4>[ 5.029180] GUID Partition Table is valid! Yea!
<4>[ 5.029323] GUID Partition Table entries: 10
<4>[ 5.029412] ebb 0x000000c800 - 0x000000e000 = 6144 (0x0000001800)
<4>[ 5.029561] pdsb 0x000000e000 - 0x000000f000 = 4096 (0x0000001000)
<4>[ 5.029647] misc 0x000000f000 - 0x0000010000 = 4096 (0x0000001000)
<4>[ 5.029798] logo.bin 0x0000010000 - 0x0000012000 = 8192 (0x0000002000)
<4>[ 5.029951] kpanic 0x0000012000 - 0x0000013000 = 4096 (0x0000001000)
<4>[ 5.030036] recovery 0x0000013000 - 0x0000019000 = 24576 (0x0000006000)
<4>[ 5.030187] boot 0x0000019000 - 0x000001d000 = 16384 (0x0000004000)
<4>[ 5.030331] Fixing up system part
<4>[ 5.030416] system 0x000001d000 - 0x000021d000 = 2097152 (0x0000200000)
<4>[ 5.030559] Fixing up cache part
<4>[ 5.030642] cache 0x000021d000 - 0x000031d000 = 1048576 (0x0000100000)
<4>[ 5.030784] Fixing up userdata part
<4>[ 5.030868] userdata 0x000031d000 - 0x0003b9dc00 = 59247616 (0x0003880c00)
<6>[ 5.031013] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
[Xoom Android Development] bigrushdog:
I deleted info here. It was incorrect. Correct info for stingray coming soon

EDIT: Ok my initial information was correct, and it's the same as stingray_cdma

I'll post an updated patch, then upon review, i'll get something up on github.
[Xoom Android Development] LaserChicken:
Xoom 4G LTE Stingray--Stock, rooted 4.1.2

Hey guys, I keep trying to get this dump, but it keeps hanging:

23.1GiB 2:39:34 [2.47MiB/s]

I've tried twice, the first time it just stopped at 500mb, second time, 23Gib, as seen above. (by stopped, I mean the screen hasn't changed from 23.1Gb for the last two hours)

Is there a way to restart the dump on the 23Gb file and pick up where it left off, or do I have to start over again? Is it no longer needed now that someone posted a stingray dump?
[Xoom Android Development] rchtk:
Cause you're probably not hitting the same df executable. I've had these strange things happen: difference between open a terminal (/system/bin/df) and sshing to the xoom with sshdroid (/bin/df), or busybox installed differently (busybox on android is not that intuitive I think) or doing it through adb shell. Some binaries have a lot of options removed to decrease their size. As you can see, -h (human readable) is already included in your binary without you providing the option.

---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------

you could use dd option 'skip' to skip x blocks at input (where the other stopped). record to another file and then append the file. you might have to modify ibs too if your file is not a block (512 bytes) multiple.

sounds complicated maybe :D
[Xoom Android Development] bigrushdog:
EDIT: More derp removed lol
[Xoom Android Development] IcyAgitator:
so the stingray 3g and 4g will use the same patch, correct? hopefully we get to see some 4.4 chocolate soon :)
[Xoom Android Development] bigrushdog:
The kernel patch will be good for all variants. Basically what is foresee is this: New recovery with repartitioned kernel. In recovery, format system, cache, and userdata. When you format, that will resize the actual partitions to match the kernel. Now everything is wiped. Either flash a rom with a boot image from the new kernel patch from microsd or adb push to data/media.

Also, we will be unable to flash images or erase from fastboot. Since the gpt table is untouched, it will restore the partitions to stock size. Overall, it's looking real clean and smooth. Once all the dust settles, we can look at ripping the gpt table and writing a fresh layout for each device.

Dude, now that we got some room, I think this could be interesting. Here at CodeFireX, we're still waiting for the AOSP to reconcile the master branch with the release branch, since we only build from master. In the meantime, I think we can get some 4.3 going ;D

Please Please! Somebody cook me a recovery with the patch i posted! I'd WUB U 4Ever ;D
[Xoom Android Development] Schischu:
[MENTION=470268]bigrushdog[/MENTION]:

I think your patch is not needed/wrong as grussinko already posted the a kernel log for stingray which shows that it already works with the existing patch.

If you look at his log you will see that "Fixing up" is printed for all 3 partitions. So the offset and size values in his log are already with the new partition layout.

So we are only missing the HK models.
[Xoom Android Development] bigrushdog:
EDIT: Derp removed

EDIT: Or are those the new offsets after the recalculation is made? Geez i must be getting tired
[Xoom Android Development] uzi2:
It could also be simplified with the removal of the symlinks, so that full advantage is taken of the larger system partition.

Swyped from grouper
[Xoom Android Development] bigrushdog:
Ya, I need sleep. I took a fresh look. The patch is proper. "fixing up" only prints if one of the defined offsets is passed. Ok we're good. I'll remove the wonk i posted lol.
[Xoom Android Development] tekrhino:
This is fantastic.

Patiently waits!
[Xoom Android Development] matt4321:
It came out with this

<6>[ 4.921339] mmc2: new high speed MMC card at address 0001
<6>[ 4.921953] mmcblk1: mmc2:0001 SEM32G 29.7 GiB
<4>[ 4.928575] gpt_header 0x0003b6efff - 0x0003b6f05b = 92 (0x000000005c)
<4>[ 4.930453] gpt_entries 0x0003b6efdf - 0x0003b6f4df = 1280 (0x0000000500)
<4>[ 4.930550] Primary GPT is invalid, using alternate GPT.
<4>[ 4.930692] GUID Partition Table is valid! Yea!
<4>[ 4.930770] GUID Partition Table entries: 10
<4>[ 4.930922] ebb 0x000000d800 - 0x000000f000 = 6144 (0x0000001800)
<4>[ 4.931011] pdsb 0x000000f000 - 0x0000010000 = 4096 (0x0000001000)
<4>[ 4.931160] misc 0x0000010000 - 0x0000011000 = 4096 (0x0000001000)
<4>[ 4.931310] logo.bin 0x0000011000 - 0x0000013000 = 8192 (0x0000002000)
<4>[ 4.931396] kpanic 0x0000013000 - 0x0000014000 = 4096 (0x0000001000)
<4>[ 4.931545] recovery 0x0000014000 - 0x000001a000 = 24576 (0x0000006000)
<4>[ 4.931693] boot 0x000001a000 - 0x000001e000 = 16384 (0x0000004000)
<4>[ 4.931844] system 0x000001e000 - 0x000009e000 = 524288 (0x0000080000)
<4>[ 4.931930] cache 0x000009e000 - 0x00000f2800 = 346112 (0x0000054800)
<4>[ 4.932083] userdata 0x00000f2800 - 0x0003b6ec00 = 61326336 (0x0003a7c400)
<6>[ 4.932229] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
<4>[ 5.197234] wifi_set_carddetect = 1
<4>[ 5.197508]
<4>[ 5.197511] Dongle Host Driver, version 5.90.195.61
<4>[ 5.197515] Compiled in drivers/net/wireless/bcmdhd on Nov 11 2013 at 18:27:48

Checking over the various patches that have been posted, I think I've determined that my partition board is the same as that of an everest model. could someone confirm?

I 100% have a wingray, I have no sim slot for my device and when I bought it back in the day it was advertised as WiFi only, I even remember on stock honeycomb it said MZ604 which is wingray, so iI'm slightly confused.

I then flashed the recovery that is compatible with everest but TWRP came up asking for a password. I tried the instructions by BRD (formatting userdata via fastboot etc) and that didn't work either.
[Xoom Android Development] realjumy:
If your model is one of the already dumped, don't worry, we have enough data of them.

However, there is some models (like the Hong Kong variations) that are still missing and that we are interested in obtain their partition structure...
[Xoom Android Development] realjumy:
Press cancel and you can go into recovery. Once you format the other partitions and the cache (doing wipe), the password never comes back. That is because the partitions are corrupted and the recovery thinks that are encrypted. I think that at some point an update.zip will be released to do it automatically.
[Xoom Android Development] matt4321:
Yeah I tried doing that first time round (just tried again). It fails, comes up with failed! I was assuming it was because it was encrypted it wouldn't format but now I'm doubting everything I know haha
[Xoom Android Development] bigrushdog:
The recovery was built on a straight 4.1.2 tree. Twrp needs some crypto flags straight aosp doesn't have. I'll cook a fresh one later.
[Xoom Android Development] IcyAgitator:
When you get everything ready for final testing (recovery, script, rom) I can test (stringray_cdma).
[Xoom Android Development] drewski_1:
There appears to be some variants.

I also have a Wingray and noticed that my system partition starts at 0x000001E000 like yours & the Everest dump where the repartition code has it at 0x000001D000

I wonder if this is why the Wingray ROM is not booting for me? I'd need to make the edit suggested for Everest?
[Xoom Android Development] hawkstorm:
[MENTION=697814]realjumy[/MENTION],

how do i know if i have the hk variant?
[Xoom Android Development] matt4321:
Interesting? Is yours from the UK? Like mine.

The wingray rom booted for me but the partitions were unchanged
[Xoom Android Development] drewski_1:
not sure original origin. it was a Refurb from Woot! :)
[Xoom Android Development] realjumy:
To be honest, no idea. I know that they have a different partition table, as time ago there was a lot of problems of users of Xoom having less storage data than spected when using custom ROMs...
[Xoom Android Development] sibax:
So I tried this by flashing the later recovery for everest etc and came up with the same issue BRD had. However i could not get past it using the same technique having tried many times. I thought to try the other recovery image that was just for wingray and all appeared well however it was late at night and I had no time to check partition size. Today being lazy I used the partition table app and it appears I have not been successful in reparting my device.

From what I am reading does this mean I have the "HK variant" if so I am confused as I bought mine from the US via eBay......

I will wait patiently for news on how to tackle this encryption/password problem.

A sincere well done on all the work done so far it was very enlightening to tackle this task at home on my PC. I am no developer/coder and it took me some research through this thread and others before I could grasp the full process and reach conclusions as to why it didn't work.

Thanks so much for helping us all continue to extract further value from our Xoom.