yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] brewer75:
Have you tried this BigPart?...https://xdaforums.com/motorola-xoom/development/recovery-twrp-2-8-0-0-t2880998.
[Xoom Android Development] xoom...:
Bigpart TWRP link no longer works

Where can I get the TWRP BigPart image? The Dev-Host link does not seem to work.
[Xoom Android Development] F-302:
Thank you! :good:
[Xoom Android Development] Mecroob:
Can't flash TWRP bigpart (edit:solved)

Hey guys, I have problems flashing the TWRP bigpart. Flashing the standard TWRP (2.6.3) was working perfectly via the bootloader. But when I open the recovery and want to install the bigpart upgrade (R_A_H_TWRPv2_6_3_BigPart_selinux) there is an error. I also tried flashing the bigpart.zip via adb sideload but then I can open the recovery but I can't mount anything. I also tried diffrent versions of the bigpart TWRP like 2.7.0.0 or 2.8.6.0 and also tried flashing the bigpart.img via the bootloader, but either it fails or I can't mount anything. Do you have any suggestions or know what I am doing wrong?

I have a Motorola Wingray MZ604 and want to flash the OMNI 4.4.4 ROM.

Edit:

I managed to solve the problem. I do not know why the update to the BigPart wasn't working but in the end the problem, that I could not mount anything, was solved by formating data and wiping cache and system in the recovery, as explained in step 6.) of the guide. Sorry for that, I was confused because it was not exactly working as in the step by step tutorial. Hope this still helps someone who encounters the same problem I did.
[Xoom Android Development] godrick15:
Can this work with a Samsung 64gb sd card? I really don't want to purchase a 32gb card
[Xoom Android Development] just_magikkal:
For the love of safety, why on earth did the person who posted the links have to use that site? I couldn't get a real file from it; all I got was a freaking suspicious exe that I ran in a sandbox and got nothing from.

Anyone have all the stuff for stingray that they can put on google drive or something a lot less sketchy? I certainly couldn't get it....
[Xoom Android Development] Kazz5:
So is there a way to bring a Xoom into 2017 with an image that continues to support Google Play??
[Xoom Android Development] fmfrijoles:
Anyone have a reliable link for a big part boot.img for CM 10.1 for stingray??

I have everything else Big Part except for the big part boot.img required for CM 10.1

I have not seen any CM 11 reliable download links so would appreciate those too.

I just brought my MZ602 back from the grave and have gotten it back to stock IMM76L (JZ054M firmware I have found makes it bootloop).
[Xoom Android Development] da-pharoah:
This is a dumb question, but are you meaning a kernel that has the boot.img or the cwm big part recovery img?
[Xoom Android Development] jenkins.robl@gmail.com:
I have a mz604 and this will be my first time rooting and unlocking the bootloader. Does anyone have any suggestions or files that will help
[Xoom Android Development] jkd:
I have corrupted partition, is it possible to boot on sd card?
[Xoom Android Development] drdd:
Is there a chance to get the bigpart files for the mz601 (3G) = everest version?

thx in advance
[Xoom Android Development] machina77:
restore xoom with original firmware via fastboot

https://xdaforums.com/showthread.php?t=1049485
[Xoom Android Development] Diagon:
Could someone clarify which of these two versions of BigPart R.A.H._TWRPv2.6.3.zip is the right one?

R.A.H._TWRPv2.6.3_BigPart_selinux.zip is in the OP here:

[SHARE][WINGRAY][CM11][EOS] Missing Downloads Here

It is at this link and has MD5: f7b03dec4fd2341be646f75d758e81b2

In the OP of this Bigpart titled thread it's just called R.A.H._TWRPv2.6.3.zip:

[RECOVERY] TWRP 2.7.1.0 touch recovery [2014-7-4] BigPart F2FS support

It is at this link and has MD5: 6ce071bd701372394d6516df15e7e199

Since the OP of this thread, we now have newer BigPart TWRP's. Will either of these work?

BigPart version of 2.8.6.0: [RECOVERY][TWRP 2.8.6.0-BigPart/TWRP 2.8.0.0-Non-BigPart]

BigPart version of 3.0.1: My list of compiled Roms for Motorola Xoom (In this link.)

Edit: I was able to make this work by using the files linked from here:

[SHARE][WINGRAY][CM11][EOS] Missing Downloads Here

R.A.H._TWRPv2.6.3.zip - this is Run And Hide's non-BigPart recovery.

R.A.H._TWRPv2.6.3_BigPart_selinux.zip - this is his BigPart recovery.

Using these two I was able to get the BigPart procedure to work. I'll now go back and put in one of the more recent recoveries.
[Xoom Android Development] voxhel:
Hi,

I have a mz601 (everest) already rooted with tiamat 4.1.

Can someone please advise if I have option to go with big part? And what roms can I use to upgrade?

Thks!

V
[Xoom Android Development] DMcCunney:
Coming in late to this thread...

I was just given a Xoom LTE originally intended to be used with Verizon cellular service.

It came to me with Android 4.4.4 and CM11 installed. It boots and runs fine, but Play Store and Drive are borked. As expected, Play store wanted to download and install an upgrade to Google Play Servicfes, and I did. That cure was wore than the disease, and I had a machine where Play Services died and restrted every 5 seconds or so. I rolled back to original factory verion to preserve my sanity.

This thread seems to indicate the new firmware offered has patched ersions of Gapps that address the issue I have. If so, wonderful. My question is whether I have to wipe the machine and reinstaoll from scatch, or whether just installing the Gapps package would fix my problem.

If I have to wipe and redo from scratch, I can, but would just as soon not.

_______

Dennis
[Xoom Android Development] Schischu:
What I found out so far is that based on our kernel cmdline "tegraboot=sdmmc gpt gpt_sector=0x03b9dfff" we have a GPT partition layout with an really interesting offset.

Also notable in this regard is

6>[ 5.024997] mmc2: new high speed MMC card at address 0001
<6>[ 5.025705] mmcblk1: mmc2:0001 MMC32G 29.8 GiB
<4>[ 5.030257] Primary GPT is invalid, using alternate GPT.
<6>[ 5.030448] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10

which is correct cause alternate means that he found something at the above mentioned gpt_sector.

So next steps: Search for 54 52 41 50 20 49 46 45 to identify the GPT in our dump.

If unsuccessful add more debug to fs/partitions/efi.c.

Edit: With Blocksize 512 this means at address: 0x773BFFE00 which is pretty much at the and of our storage.

Then we can decide if we should directly change the GPT layout our if we should build an own kernel which ignores the read GPT and instead uses our own layout.

The first one will crash flashing older images. The second one is in my opinion the safer choice, of course we would have to change recovery for that too...

So good hunting guys ;)
[Xoom Android Development] pots22:
4.4 KITKAT

Good news, i read today Cyanogenmod 11 (Based 4.4 KITKAT) ported to 70 Devices (all devices supported JB)

So no Cyanogenmod 10.2 for XOOM, but not impossible they ported directly the Cyanogenmod 11 to the XOOM.

I check the last nightly 10.1 JB 4.2.2 is updated yesterday so developers from Cyanogenmod continue to work on XOOM :laugh:
[Xoom Android Development] notbrodie:
don't want to burst your bubble, but according to cm's Gerrit, the last commits for wingray/stingray were from July 4/11, respectively.

Sent from my Xoom
[Xoom Android Development] grussinko:
I'm a little confused, what are the nightlies that are coming up approx once a week through CM updater if there haven't been any changes since July?

Edit: Sorry for going OT, didn't realize which thread this was in since I just jumped to first new post.
[Xoom Android Development] notbrodie:
likely just translations, or android-wide bug fixes. cm is done with xoom. the only fixes xoom will get are MAJOR security flaws or huge bux fixes. However, due to the maturity of 4.2.2 (and the size of the beta pool), there will likely not be any more xoom-specific work done
[Xoom Android Development] Schischu:
I added some debug info to the kernel:

<4>[ 5.017495] gpt_header 0x0773bffe00 - 0x0773c0b600 = 47104 (0x000000b800)
<4>[ 5.019011] gpt_entries 0x0773bfbe00 - 0x0773c9be00 = 655360 (0x00000a0000)
<4>[ 5.019108] Primary GPT is invalid, using alternate GPT.
<4>[ 5.019251] GUID Partition Table is valid! Yea!
<4>[ 5.019332] GUID Partition Table entries: 10
<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)
<6>[ 5.020741] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
[Xoom Android Development] realjumy:
Let me know if I can help you with something...
[Xoom Android Development] Schischu:
Ok it works.

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 507M 437M 70M 4096
/pds 1M 108K 1M 2048
/data 28G 214M 28G 4096

You will need to build a new kernel and add follwing to

fs/partitions/efi.c

in function int efi_partition(struct parsed_partitions *state)

if (!is_pte_valid(&ptes[i], last_lba(state->bdev)))
continue;
+
+#define MB256 0x080000
+#define MB512 0x100000
+
+	if (start == 0x1D000)
+	{
+	printk("Fixing up system part\n");
+	size = MB512;
+	}
+	else if (start == 0x9D000)
+	{
+	printk("Fixing up cache part\n");
+	start += MB256;
+	}
+	else if (start == 0xF1800)
+	{
+	printk("Fixing up userdata part\n");
+	start += MB256;
+	size -= MB256;
+	}
+
put_partition(state, i+1, start * ssz, size * ssz);

/* If this is a RAID volume, tell md */

After that system part will be 512mb big.

You get the above mentioned df output by running make_ext4fs on the system cache and userdata partition while booting the new kernel.

Note after that you system wont work anymore cause, well your not supposed to do something like this.

Basically it should work to just do make_ext4fs on cache and userdata and resize2fs -p on the system partition. But have not tried that.

The correct way would be to replace also the kernel of the recover.img so that new images are installed correctly

Unfortunately, it seems that all recovery.img need cyanogenmod to be build and I only to aosp thats annoying.

Maybe some of the recover.img builders can build us a new recovery with this patch?
[Xoom Android Development] Asphyx:
Just because you see a new build doesn't really mean anything has changed from the previous build other than maybe some stuff not related to the hardware but part of CM software.

This sounds very promising!
[Xoom Android Development] hawkstorm:
Wow! This is really great news! Go developers!
[Xoom Android Development] rchtk:
Nice patch Schischu :)

So we just moved 256MB from userdata to system partition. Great!

Sorry for the ignorance but why shouldn't it work anymore if as you did, the kernel is patched and the physical layout is what you redefined?

Unless physical layout is assumed somewhere else in the system, which seems a bit dirty to me.

You did this test in the emulator right? How can we do this fdisk and mkfs ops on the device itself? In the recovery? Again, sorry for the ignorance :)

I'll be ok to test the new layout before something more portable for all users is done.

edit: no, fdisk is not involved here (cause partition table can't be modified right?). resize2fs for increasing system and mkfs for the 2 other moved partitions.
[Xoom Android Development] Schischu:
All my tests where done directly on the target.

Why it doesn't work anymore if you do a make_ext4fs on the system partition to increase the size?

Well, what I did was basically reformating the /system partition to a bigger size without any regard to the partition content.

So lots of files in this partition will afterwards be corrupt, and some file from a part of the former /cache partition are now listed in this new bigger /system partition. So lots of corrupt files. Thats why df says that over 400mb are used on the /system partition even if it was in reallity only 160mb.

The solution for this problem is very very easy, we just have to create a recovery.img which also has this kernel patch applied. Then recovery will create the partitions and filesystems correctly.
[Xoom Android Development] realjumy:
That's sounds absolutely brilliant. But, before doing that, do you thing that is possible to have 1GB instead of 512MB? If we are doing it, let's do it great. :)

Thanks a lot mate.
[Xoom Android Development] Schischu:
Yeah you are right, after looking at the nexus5 values we should probably also increase the cache partitionsize.

Number Start End Size File system Name Flags
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
[Xoom Android Development] hawkstorm:
The progress in the thread is getting me excited! XD I wish I could contribute more to the discussion. But all the info so far seems extremely promising.
[Xoom Android Development] LOGMD:
Building 4.4

i managed to get 4.4 to build all the way to packaging system.img where this thread comes in

join the google+ Xoom community too

i will post details of the error here later...

I beleive that the system has run out of space (like stated in the OP) so it wont build

it failed to allocate 4096 blocks on system.img

the /system folder still compiled it just wasnt packaged

i have packed system myself and attempted to flash my rom (failed i will work on this)

i also dont know if the kernel has compiled properly (anyone have any more info how to compile seperately)

i am rebuilding 4.4 with LOTS of apps missing to save space on /system to at least get it to build

any experienced developers with any knowledge please help!

my google+ is HERE

thanks for all the help on this thread so far! good to see people still using this insane device!

P.S. i check this thread regularly so anything posted here is useful =]
[Xoom Android Development] realjumy:
[MENTION=470268]bigrushdog[/MENTION] is a pro coder and we was releasing EOS roms for a long time. Maybe he can help you.
[Xoom Android Development] Schischu:
As requested:

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 1019M 949M 70M 4096
/pds 1M 108K 1M 2048
/cache 503M 8M 495M 4096
/data 27G 214M 27G 4096

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 SYSTEM_START 0x1D000
+#define CACHE_START 0x9D000
+#define USERDATA_START 0xF1800
+
+#define SYSTEM_SIZE MB256
+#define CACHE_SIZE MB169
+
+	if (start == SYSTEM_START)
+	{
+	printk("Fixing up system part\n");
+	size = MB1024;
+	}
+	else if (start == CACHE_START)
+	{
+	printk("Fixing up cache part\n");
+	start += MB1024 - SYSTEM_SIZE;
+	size = MB512;
+	}
+	else if (start == 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);
[Xoom Android Development] notbrodie:
I feel like you guys are so close. Just want to say thanks for all your efforts.

Sent from my Nexus 5
[Xoom Android Development] Schischu:
And done.

Flashed new recovery.img.

Flashed new update.zip

And have a running android on xoom with following partition table:

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 213M 27G 4096
/storage/sdcard0 27G 213M 27G 4096
/storage/sdcard1 3G 1G 2G 4096

Currently uploading a recovery.img and a test image for you guys.
[Xoom Android Development] julyaann:
And done.

Flashed new recovery.img.

Flashed new update.zip

And have a running android on xoom with following partition table:

Code:

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 213M 27G 4096

/storage/sdcard0 27G 213M 27G 4096

/storage/sdcard1 3G 1G 2G 4096

Currently uploading a recovery.img and a test image for you guys.

You are the best!!!
[Xoom Android Development] Schischu:
Recovery with bigPart

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

Android 4.1.2 with bigPart

http://duckbox.info/files/xoom/wingray_bigPart.zip

Flash R.A.H._TWRPv2.6.3_bigPart.img through fastboot.

Flash wingray_bigPart.zip through recovery, dont reboot.

Wipe Dalvik Cache Cache Data.

Reboot System.

After System startet, check adb shell -> df to confirm new partition layout.

Please note: I only build this for wingray (NOT HK). This is a very very basic android, aosp without any modifications beside the kernel. (See patch above)

And just to be clear again. YOU WILL LOSE EVERYTHING ON YOUR XOOM BY CHANGING THE PARTITON FORMAT. SO BACKUP BEFORE.

And again. ONLY WINGRAY.

Now the 4.3 and 4.4 images can come. ;)
[Xoom Android Development] tonemand:
I'm both speechless and excited! Thanks for all the effort so far to accomplish this!
[Xoom Android Development] alex_72gr:
Congratulations, please do not forget everest
[Xoom Android Development] notbrodie:
can't wait to get home and do this! i'm crossing my fingers that [MENTION=470268]bigrushdog[/MENTION] already has a build cooked in preparation!
[Xoom Android Development] julyaann:
+1:D
[Xoom Android Development] dccrens:
WOW! Will my Stingray get a new lease on life....
[Xoom Android Development] realjumy:
If you give me fast instructions of how to do it, I can try to do an Everest version. I have not idea about compiling kernel (but I can learn really fast).

Thanks dude.
[Xoom Android Development] rchtk:
That was fast Schischu! :)

I've mirrored the 2 files on a second hoster

R.A.H._TWRPv2.6.3_bigPart.img.zip

wingray_bigPart.zip

Can't test atm as it looks like my debug usb link doesn't work :( usbfs: USBDEVFS_CONTROL failed cmd fastboot

edit:

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 214M 27G 4096
/storage/sdcard0 27G 214M 27G 4096
/storage/sdcard1 1G 945M 959M 4096

Looks good!
[Xoom Android Development] IcyAgitator:
OK so after we flash these.....then what? Is there a ROM we can currently flash afterwards?
[Xoom Android Development] aFancyTickler:
cant wait for a stingray version and kitkat build ! finally i can dust off this mighty device lol
[Xoom Android Development] hawkstorm:
This is really exciting. Can't wait for a umts-everest version. How do I tell if I have a HK version of the MZ601?
[Xoom Android Development] Sparty73:
I have a Stingray Xoom, but I don't use Verizon LTE at all. I'm assuming I

should not

flash the Wingray only patch.

However, do we know that Stingray and Everest have different partition sizes than Wingray? Couldn't we, theoretically, flash the Wingray recovery on Stingray and Everest if they're partitioned the same by default?
[Xoom Android Development] aFancyTickler:
i was thinking the same thing. i dont use the LTE on my xoom. its prcatically a wifi xoom
[Xoom Android Development] IcyAgitator:
I have a mz600 (vzw 3g). I never activated the 3G. I have always just used wingray Roms and recoveries. Wondering if I should try this........
[Xoom Android Development] rchtk:
http://xdaforums.com/wiki/Motorola_Xoom

Warning: Stingray are Wingray roms are NOT the same, flashing a rom meant for a different model will result in a brick!
[Xoom Android Development] IcyAgitator:
Actually, you can run a Wingray (mz604) rom on a Stingray (mz600) without getting a brick or disastrous results. Those two models i listed are exactly the same except for the 3G feature. I and many others have been doing this since the wingray sbf was released. I flashed the wingray sbf, wingray custom recoveries, etc and profit! There are many articles on this here on xda, google it. I do not use the vzw 3g so I lost nothing as a result.

I will not hijack/offtopic this post proving it......I just had a simple question as to what the difference was in the partition tables.....
[Xoom Android Development] hawkstorm:
Does the NonNEON configuration for the tegra2 processor complicate things for 4.3/4.4?
[Xoom Android Development] realjumy:
[MENTION=2371134]Schischu[/MENTION] Do you calculate the offsets multiplying by 1024 and then calculating the equivalent in Hex?
[Xoom Android Development] Sparty73:
I know they're not the same, but that statement is frankly just not true. I have a Stingray Xoom, but have run multiple Wingray ROMs, including the one I'm running now.

It

can

result in a brick, but to say that it

will

just is not correct.
[Xoom Android Development] bigrushdog:
Update the system partition size in your boardconfig.

Well, awesome work! I got a few minor non-neon issues to work out and I should have some builds. I'll work on the kernel tonight. Personally, I think we need a consensus going forward regarding partition size. I'm good with the 1GB system, and whatever cache size was posted above. That way all the cooks are on the same page and not soft bricking devices.

This is gonna be fun!
[Xoom Android Development] realjumy:
[MENTION=2371134]Schischu[/MENTION] I'm still trying to figure up how did you obtained that data. Can you tell us how you did it? Thanks.
[Xoom Android Development] realjumy:
I agree with you with the partition size. A standard size will make everything easier...
[Xoom Android Development] matt4321:
Those who have completed the repartition. I hate to be the noob of the group. What am I doing wrong as mine hasn't repartitioned, I've done it twice and not sure what is up.

'fastboot flash recovery R.A.H._TWRPv2.6.3_bigPart.img'

'fastboot reboot'

power down on boot and into reocvery

flashed the wingray_bigPart.zip in recovery

wiped data, cache and dalvik cache

reboot

df via adb shell brings up the same partition sizes as I have always had.

Any help would be appreciated. Not sure what I'm doing wrong
[Xoom Android Development] rchtk:
I have no idea, just mentionned this from the wiki so that nobody does somethign silly.

This comment should be sent to the wiki maintainers.
[Xoom Android Development] Schischu:
I've added some debug output to the kernel to obtain this information. The values are multiple of the blocksize. So you will have to multiply them with 512 to get the offset in bytes.

If you flash my image and execute dmesg you will see this output.

I can upload a patch for that later today.

For our stingray, everest and HK friends. They could extract the boot.img from the wingray_bigPart.zip and do a

./fastboot flash kernel boot.img.

/fastboot reboot

./adb wait-for-device; ./adb shell

su

dmesg

and print this info, then we would definitely know the partition layout of all devices.

Afterwards just reflash your normal kernel. No flashing of the recovery_bigPart.img is needed for that test.

So if you have some time on you hands, ...