yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] trevd:
Hi Folks.

I'm slightly perplexed why the size of the system partition appears to be such a big problem, as you can the use mount loop@ command in init.rc to mount ext4 filesystem image from where ever you like ( /data/local ). They you go. Problem Solved!! ;)

... But no, lets do things properly ..

[MENTION=470268]bigrushdog[/MENTION] I think you were on the right path with "simple" repartitioning , obviously that version of parted is a load of crap and if it's the one distributed with "Every Recovery Ever" then it'll be way out of date aswel. It's actually statically link to glibc aswell ( although makes no odds ) , probably because it's such a bastard to compile lol. I did tease libparted out of it the parted sources for my own evil deeds. [ https://github.com/trevd/libparted-android ]

Anyways this thread caught my eye so I decided to dust off the xoom , dump the booloader ( ok , ran strings over it ) and tried some things out Here's wjhat I know so far. It is possible to resize the partitions while leaving the broken partition table still broken by using resize2fs from the e2fsprogs utilities. This is included in the aosp build although I did build myself a statically linked version to use in recovery. The notable things here is that I shrunk the data partition by 700MB these changes persisted across reboots and the installed OS ( CM-10.something ) still booted successfully, This suggests that resizing to system to fill the space would be fine as well.

Now I'm fairly certain that on a fully unlocked MZ604 UK version that you can use the gpt-utils ( gfdisk, sgfdisk ) to just go and repair the the broken partition table and boot with no ill effects. I still need to confirm this however as I've reached a kind comedic sticky situation.......

=============================

So I completely wiped the partition table on the internal mmc, that not a major concern as I have a factory cable and an sbf file [ PROTIP: Always have a root back from disastar ] , plus fastboot works but obviously won't flash because it has no partitions to goto, Recovery stil boots into TWRP as recovery and boot images are stored with the bootloader on the mtd nand device. Now here's the kicker what is concerning me., the battery went flat and I can't for the life of me find the mains adapter so I've been on this cliffhanger since yesterday lol..... So I'll take it to my mates phone shop later and plug it in. Then I'll let y'all know if I'm full of s**t or not.

References :

Fixing a Corrupt GPT Partition on the Eee Pad Transformer Prime - http://xdaforums.com/showthread.php?t=1675300

This thread contains the arm version gfdisk, sgfdisk - USE AT YOU OWN RISK!!! AS CHANGES ARE COMMITTED STRAIGHT AWAY.

which along with my casual approach to hacking on these infernal devices is why I ended up remove the mmc superblock in the first lol.

Just remember folks, It's not a real brick until you see the blue smoke :good:.
[Xoom Android Development] realjumy:
The HK partition tables are different. We need to know how it is structured to make advances. If you obtain the data, publish it. Thanks.
[Xoom Android Development] realjumy:
I need to say that I tried but I was not able to help. All credits goes to [MENTION=470268]bigrushdog[/MENTION], [MENTION=2371134]Schischu[/MENTION] and [MENTION=4533695]rchtk[/MENTION]!
[Xoom Android Development] realjumy:
Not all the roms are compatibles with the boot.img method (kernel method). You will need to try to be sure. EOS4 and Dream's have proper versions. If you want to use, for example, CM you will need to:

option 1.- Build it yourself patching the kernel

option 2.- Use CM and try to use a different kernel

option 3.- Ask to the CM maintainer to release BigPartition versions.
[Xoom Android Development] realjumy:
Thanks dude. I think that this will provide a new point of view. Definitely we need to find the safest and easier method to do the repartition.
[Xoom Android Development] realjumy:
Yes, you are changing partition sizes. You will erase all your internal data as well. You will need to flash "regular" recovery and erase all the data again if you want to recover the initial partition structure. If you are not confident with what are you doing, please don't do it until some definitive advance is done.
[Xoom Android Development] ifti_a:
doesnt seem that hard, ive done this a few times before so im confident.

fingers crossed,

thanks again
[Xoom Android Development] Asphyx:
Thanks RJ I had forgotten that different ROMS use different Kernels which is what confused me...

As for CM compatible Boot.Img since it is all on the GITHUB should be relatively easy to fork, patch and build a boot.img for CM at some point.

I don't run CM on my Xoom so I'm all good with what we have now and I'm more inclined to wait to see if BRD pulls a Kit Kat rabbit out of his hat as he is known for his ability at pulling off Xoom Magic! LOL

Thanks for the clarification though.

I just wanted to add how amazing this site and the developers who live here remains to be! We went from last week wondering if repartitioning was even possible to seemingly having one KNOWN fix and two possible ways of doing it! LOL

I been coming here since 2007 and this site (and the Devs here) still continues to amaze me!

Thanks to all!
[Xoom Android Development] jgardner:
[MENTION=744716]Asphyx[/MENTION] I believe BRD said they were going to wait for KitKat to hit the master branch before whipping up a 4.4 rom for us. As of this morning it hasn't hit the master branch yet. Hopefully soon!
[Xoom Android Development] Asphyx:
yeah I'm in no rush..I have my EOS which is currently my daily driver and can BigPart that till BRD does his magic....I suspect It's going to take much longer than just hitting the master branch to see Kit Kat on Xoom...Neon will delay and complicate the build I'm almost certain! (I just hope not to the point of killing it as an option entirely!)

That said If BRD gets it working I can see at least another year or two of life in this old Xoom until someone makes a tablet that blows me away and makes me want to spend again. LOL
[Xoom Android Development] pots22:
EOS4

Hello [MENTION=697814]realjumy[/MENTION]

You say BRD published some EOS4 with big part

It's just the boot.img big part zip ?

first make the manipulation on page one for change the size of the partition

After flash the normal EOS4 for me Everest 170 and after the specific big part boot.img everest ?
[Xoom Android Development] realjumy:
I think that everything is explained in the 1st post. Please, take a look and if you still have questions I will try to help you. ;)
[Xoom Android Development] Asphyx:
Yes it's just the Boot.img posted...

Here is what you need to do....(easiest method unless your fluent in editing zips)

On a computer...Extract the zip of your preferred EOS ROM into a folder....

Then extract the BigPart EOS boot zip ...

Copy the Boot.img file from the BigPart into the folder you extracted the Rom Zip into and replace the one that is there...

Zip up all the files and folders (make sure boot.img is in the root of the zip as well as the META-INF and system folders or it won't flash)

Copy to SD card

Follow instructions on page one to repartition then when done flash the new zip that has the new boot.img...

You should have whatever version of EOS you used with a 1GB partition.
[Xoom Android Development] drewski_1:
it's even easier and no need to mod the zip files :D

repartition according to instructions

flash EOS4 ROM

flash BigPart boot.img zip

flash Gapps, etc.
[Xoom Android Development] matt4321:
Awesome work all round to everyone who contributed to this! My Xoom is repartioned and running EOS4 now.

I've had my Xoom for gone 2 years and never thought I'd see this happen
[Xoom Android Development] shpitz461:
EOS4 is sluggish as hell on my Stingray, is that everyone's experience as well? dreamcwli's 4.3 is much more fluid, and the graphics glitches are not that bad...

if your EOS4 is not sluggish, can you share your tweaks (kernel, trickster, etc...)?
[Xoom Android Development] michie:
Timundru has a kitkat build running on his tf101 which is almost identical to the xoom. Its not released yet though as the rom suffers from many fc's. But it proves our NEON devices are still holding strong without the support from google.

His katkiss rom and kernel makes the tf101 fly, even faster and less lag than my galaxy nexus on 4.3! He is a very talented DEV (i even think he was part of team eos BRD?), maybe we can work together with him for our tegra 2 devices in general?
[Xoom Android Development] Asphyx:
Thanks Drewski....Had not considered that....But it makes a ton of sense!
[Xoom Android Development] hochoch:
congrats on making the "news"!

http://www.xda-developers.com/android/squeeze-bigger-roms-onto-the-motorola-xoom-with-bigpart/
[Xoom Android Development] sublimaze:
Nice :cool:
[Xoom Android Development] DriVAnce:
was wondering if this was working on Xoom European 3G umts?

was gonna flash EOS 4.0 umts (170) on the xoom, and then I saw this :-p dropped my jaw

Just need a few clarifications that it does work with EOS umts (be it 3.0 or 4.0) and that its doesn't require 2 much. I feel safe with using adb :-p + I have Shidapu next to me
[Xoom Android Development] realjumy:
It is working in the EU version ;)
[Xoom Android Development] ifti_a:
Priceless!
[Xoom Android Development] DriVAnce:
sadly i ended up with CM :'( since the build 170 wasnt gonna DL uncorrupted for me... a bit tired.. dont have the XOOM for maintaince for long before mother needs it... so she will have to live with the CM =) *Running CM on my S4*
[Xoom Android Development] ifti_a:
Just out of curiosity what was the system and cache size before repartitioning ?

---------- Post added at 10:40 PM ---------- Previous post was at 10:21 PM ----------

Also I don't know why but my eos 203 build was show after using it for a few months.... Now I have reflashed it, it's good again.... It's not the ROM but somthing else, maybe data issue....
[Xoom Android Development] HairyMerkin:
Maybe the Xoom needs to use TRIM? What kind of HDD does it have, flash or an SSD?
[Xoom Android Development] drewski_1:
around 250MB system, 160MB cache
[Xoom Android Development] logitechor:
I attempted to install a Custom Kernel. It did not take. Are there any Kernels that can be used with4.3.
[Xoom Android Development] aR_ChRiS:
[MENTION=225651]op[/MENTION] Thanks for making this work, finally a full solution to fit larger roms :D

I just want to ask whether there's a CWM image for this mod? No offence that TWRP is a good recovery, but I'm just too used to the CWM interface and don't really wanna change :/

---------- Post added at 10:57 AM ---------- Previous post was at 10:57 AM ----------

@OP Thanks for making this work, finally a full solution to fit larger roms :D

I just want to ask whether there's a CWM image for this mod? No offence that TWRP is a good recovery, but I'm just too used to the CWM interface and don't really wanna change :/
[Xoom Android Development] jgardner:
dreamcwli's kernel should support most 4.3 roms (in theory). Link's in OP (here for reference: http://d-h.st/9Hi)
[Xoom Android Development] Twerkeologist:
Are there any devs working on 4.4? Sorry if I sound impatient, im just curious.
[Xoom Android Development] pots22:
Thanks'

Tanks' it's more clear like this
[Xoom Android Development] alex_72gr:
Sorry where did this come from?
[Xoom Android Development] Asphyx:
Actually PotsDrewski's answer is even BETTER and less involved!

Follow his instructions!
[Xoom Android Development] ifti_a:
No way, I don't believe it !
[Xoom Android Development] drewski_1:
In the days of Honeycomb what more did you need? ?
[Xoom Android Development] dron39:
If i prefer CM 10.1, which files i need to flash?

Boot image from EOS4 isn't working with CM10.1, i think...

---------- Post added at 10:51 AM ---------- Previous post was at 10:50 AM ----------

If i prefer CM 10.1, which files i need to flash?

Boot image from EOS4 isn't working with CM10.1, i think...
[Xoom Android Development] mcarrion78:
Awesome work sir and thank you for keeping our beloved Xoom alive. I've been debating on getting a newer tab but you guys keep me from making a final decision. I will be getting setup to try this as soon as I have the free time. If there is anything I can do to help this project progress don't hesitate to hit me up. I will do my best to get whatever is needed. I can't wait to get sum Kit Kat sweetness on this baby.
[Xoom Android Development] logitechor:
Still using Dreams4.3. Have not fully installed all my apps. Working quite well.

I attempted something I quests we can't. I tried a Kernel to overclock. No luck. Did not boot. I suppose it changes the boot image.
[Xoom Android Development] realjumy:
As BDR said, still no OC. Please, be patient.
[Xoom Android Development] Bux1982:
Has anybody actually thought about contacting the User flar2 to ask if he could publish his ElementalX kernel with BigPart support.

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

I´m running his kernel for Roms that don´t include OC yet and it works like a charm.

Sweep2Wake is lots of fun too.

Maybe someone with some knowledge what needs to be done to his kernel could get in contact with him.
[Xoom Android Development] jgardner:
It's in the first post, just above the Q&A section:

MyWingray 4.3 BigPart wingray Boot Image

---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------

BRD had mentioned that they're waiting for 4.4 to hit the master branch then they'll get it pulled over. So far google hasn't merged it into master yet.
[Xoom Android Development] matt4321:
I'm trying to compile CM10.1 kernel with this patch but am getting;

matt@Bull-Pavilion:~/android/kernel$ patch -p1 < ../kernelPatch
patch: **** Only garbage was found in the patch input.

It's this file here I'm using as the patch: http://www.mediafire.com/?gwrhqymvebc9k79

I'm still relatively new to compiling and have never added patches before so I'm probably doing something stupid. But help would be appreciated by anyone as I'd love to get CM10.1 running with the bigger /system
[Xoom Android Development] jgardner:
It almost looks like the patch is missing the first line. Try adding this to the beginning of the patch file and try again:

@@ -652,6 +652,41 @@ int efi_partition(struct parsed_partitions *state)
[Xoom Android Development] matt4321:
thanks, tried adding it and got the same error.

I'm interested as to where you found that line of code. In the patch posted here: http://xdaforums.com/showpost.php?p=47421260&postcount=120

it isn't there
[Xoom Android Development] jgardner:
Got it from his GitHub: https://github.com/codefireXperimen...mmit/5025a00ba23c9a3a9958b81c648c40f7510a7cf1

Sorry I don't do too much patching, its only a few lines may be worth your while to just modify it yourself.
[Xoom Android Development] dron39:
If you patch CM 10.1 kernel please let us know. =)
[Xoom Android Development] matt4321:
I'm compiling the CM kernel as we speak, I've got to go out and see my girlfriend though now. So I'll test tonight/tomorrow and let you guys know
[Xoom Android Development] shpitz461:
Mate, you sure got your priorities reversed... :p
[Xoom Android Development] pots22:
big seize partition

I make this tuto with my MZ601

It's OK ?

Screen shot attached
[Xoom Android Development] realjumy:
Seems like is working fine ;)
[Xoom Android Development] pots22:
work very fine

The 170 work like a charme

I'm French so now i stop to play and start to watch on the tab with the new partition size France-Ukraine for the next soccer World Cup
[Xoom Android Development] matt4321:
Any help would be appreciated, I've not compiled a kernel before.

The modules seem to compile fine, but the guide I'm following says there should be a zImage in arch/arm/boot/ but there isn't one, and I'm stuck. haha
[Xoom Android Development] CBDSonline:
quick way to change partition sizes without reinstalling

i have been reading and following this tread since it started and enjoy playing with things i think i have found a quick way to to do this without loosing or having to reinstall things.

if there is a bigpart boot for your current setup then you are onto a winner. all it involves is a backup and restore with a couple of things changed. (i have done this 4 times so far and always works but i take no responsibility for others is it bricks etc.)

Copy the needed files to your sdcard. R.A.H._TWRPv2.6.3.0_BigPart_selinux.zip, and your BigPart boot image that goes with your installed rom and then !! IMPORTANT !! backup any data you want to keep (music. pictures etc from internal memory to your sdcard or computer-laptop because you will loose them forever when you format the new partitions)

Reboot into twrp recovery.

in twrp select backup. Select System and data partitions and swipe to create a nandroid backup (on external SD)

once complete return to main menu and FlashH._TWRPv2.6.3.0_BigPart_selinux.zip. Don't reboot just yet

Go back into wipe menu and wipe everything apart from SDcard (dalvik, system, cache, data, internal storage)

Go to reboot menu and reboot into recovery. Disregard the "No OS" warning bla bla

When you come back into recovery, it will think your data is encrypted but it's not press cancle and Go into wipe menu and "format data". Type "yes" when prompted. When done, go back into wipe menu. Select "Advanced Wipe". Check "system" and "cache" and wipe them.

Hit Home then go to reboot menu and reboot recovery. Once again, disregard "No OS" warning bla bla

When you come back into recovery, go into mount menu. You should see "cache" and "data" checked. "System" will be unchecked. Check it to confirm it mounts, then uncheck it. Congratulations! You are now repartitioned! (dont think you need this bit !! but try it if you want)

Go into Restore . It should show your microsd storage by default. If not, tap on the white bar and select the SDcard, using the navigation panel, Navigate to TWRP then backup and select your nandroid backup to restore

do not select the boot partition option, restore only system and data.

swipe to start the restore.

once complete return and flash bigpart boot that matches your nandroid

reboot and you should be back to where you were but with the new bigger system and cache partitions

I will go back to old partitions again and try following my tute just to make sure it works again.

Hope this migh help and make things a bit quicker for Xoom users
[Xoom Android Development] yosterwp:
I've only built kernels a couple times. So as a non-dev, here's what I have:

Were there any errors during the build process? If you aren't sure, reduce the number of threads used to compile, so the build stops exactly where an outstanding error occurs (as opposed to waiting for the other threads to finish-causing the error to be lost in the verbose messages of the build process). If there was anything, you'd then know.

Hope that helps
[Xoom Android Development] matt4321:
Everything is ok regarding compiling (i think)

it's when I try to make the modules I get this error right at the beginning

matt@Bull-Pavilion:~/android/kernel$ make modules
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CC [M] net/mac80211/main.o
net/mac80211/main.c: In function 'ieee80211_alloc_hw':
net/mac80211/main.c:588:4: error: 'WIPHY_FLAG_SUPPORTS_SEPARATE_DEFAULT_KEYS' undeclared (first use in this function)
net/mac80211/main.c:588:4: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [net/mac80211/main.o] Error 1
make[1]: *** [net/mac80211] Error 2
make: *** [net] Error 2

Anyone know what's up with that?
[Xoom Android Development] drewski_1:
you keep your system & apps, but you still lose your /data/media user files? which aren't included in the Nandroid.
[Xoom Android Development] CBDSonline:
Fair point drewski.. i never use the xoom for pictures or music etc so would never have noticed. what files i do have i keep on external sd as its 32gb as i am am prone to clean installing and playing every couple of weeks just for somthing new to do.
[Xoom Android Development] bigrushdog:
In most cases working with Android, you won't run "make modules" Here's a little something to help you out. Adapt for your personal environment

#!/bin/bash
# Kernel Builder 1.0 -Stingray

PRODUCT_CONFIG_FILE=bigrushdog_defconfig
#PRODUCT_CONFIG_FILE=stingray_defconfig
WORKING=/home/bigrushdog/cfx/kernel/moto/wingray
CONFIGFILE=$WORKING/arch/arm/configs/$PRODUCT_CONFIG_FILE
OUTPATH=/home/bigrushdog/Desktop/xoom_kernel_out/
MODULEOUT=$OUTPATH/system/lib/modules

rm -rf $OUTPATH
mkdir -p $MODULEOUT

cd $WORKING
make mrproper
git clean -f

export CCOMPILER="/home/bigrushdog/android-ndk-r9b/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/arm-linux-androideabi-"
export ARCH=arm

make ARCH=arm CROSS_COMPILE=$CCOMPILER defconfig $PRODUCT_CONFIG_FILE

echo "Kernel is now compiling, please go smoke a cigarette"
make -j16 ARCH=arm CFLAGS_MODULE=-fno-pic CROSS_COMPILE=$CCOMPILER

find $WORKING -name "*.ko" -exec cp {} $MODULEOUT \;
cp $WORKING/arch/arm/boot/zImage $OUTPATH

git clean -f
make mrproper
[Xoom Android Development] pots22:
BigPart

Now i have my MZ601 with BigPart and the EOS170 Everest

All work perfect

What's happened after this ?

A 4.4 kitkat ROM ?

A 4.4 kitkat ROM with specific boot.img?

And another question how to return with original partition size?

Flash with SDK tool the original ROM Motorola?

Because my contract 3G finish the 5 of next month and i'm think flash the original Motorola US MZ604 to upgrade in OTA to 4.1.2

Thanks' for advance
[Xoom Android Development] Albert52:
Xoom Everest nightly 170

Need a bit of help, can somebody give me a link to a proper Everest nightly 170. The one I DL from Goo won't install and I cannot find another link.

Thanks in advance.
[Xoom Android Development] pots22:
EOS 170

On my Box

https://www.dropbox.com/s/d0n074kvb6i4a8i/EOS-umts_everest-20130617-170.zip
[Xoom Android Development] mermigas:
I am following instructions from 1st post carefully but external sd card cannot be detected. What I am doing wrong?
[Xoom Android Development] matt4321:
Awesome, I'll give that a look over tonight and try get it to work. Thanks for the help
[Xoom Android Development] buffalo_guy:
sdcard issues

I could see the contents of my card on the pc and running my former os on the Xoom Twrp could not see it..I tried reformatting and that didn't work. After I wiped the sdcard through twrp and recopied the files from the pc it was finally recognized
[Xoom Android Development] mermigas:
Thanks but doesnt work for me
[Xoom Android Development] Albert52:
Thanks very much for your quick response
[Xoom Android Development] buffalo_guy:
Looking for EOS-wingray-20130705-205.zip

Hi:

For the past week I have not been able to download any EOS 4.0 from Goo.im. I keep getting an internal server error. Does anyone have this file available? Many thanks!