yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] realjumy:
Thank you guys!
[Xoom Android Development] realjumy:
Thanks mate. I will correct the post later from the PC.
[Xoom Android Development] bigrushdog:
I'm dumping stingray right now. From what i can see, it already looks like the offsets are different for different models. That's very good to know. So calculations will need to be made for each version. After talking with @Roach2010 he says there may be partition table info that needs updating somewhere in the NAND dump. However, it doesn't appear that is the case for all devices. Once i get this dump we can play some more.

EDIT: found some interesting information http://xdaforums.com/showthread.php?t=1388996
[Xoom Android Development] TrustAugustus:
You guys... are brilliant... I'm in. My Xoom is just collecting dust since Eos shutdown.
[Xoom Android Development] LOGMD:
also guys im getting my nexus 5 by the end of the week, let me know if you want any information extracted from that ;)! will be rooting that m*****f***er soon as! which leaves me with 2 dev devices :D XOOM and S2
[Xoom Android Development] kikuto:
I have a mz605 umt_everest model, at monday in my lab I will do this and post here.
[Xoom Android Development] LOGMD:
Nice find, so by doing this research and analysis it will be possible to create a universal partition structure (in terms of the XOOM versions). am i right in thinking this?
[Xoom Android Development] realjumy:
No... Whit this we will be able to:

1.- Check if every Xoom version have the same or different partition structure (done, each model has a different structure).

2.- See how every model need to be restructured (pending, that will be next step).

3.- Provide a script to make it easy to do (we need to do the 2nd step first).
[Xoom Android Development] sibax:
OK sorry:o

Can you tell me what the windows commands might be to print the dmesg or process/kmsg?

If so I can try again tonight if you still need the info.
[Xoom Android Development] bigrushdog:
Running dreams 4.3 on stingray. I'll upload a modded boot image and recovery later today. Got a refreshed 4.3/4.4 kernel going with backtrack modules, selinux, and all the goodies
[Xoom Android Development] realjumy:
I tried to compile your kernel this morning with no luck (but it's my fault, I'm still trying to learn how to manage the kernel). Just remember to release a version for Everest... No matter if it's a 4.2.2 :P
[Xoom Android Development] bigrushdog:
The jb-devel-mr2-release branch is updated for 4.3 bigpart. I'm gonna drop images for all the eos builds and dreams build. I'll also push the old eos branch as well. Next step is getting a cohesive package together.
[Xoom Android Development] realjumy:
That's sound great ;)
[Xoom Android Development] dccrens:
BRD,

Go Stingray! You are truly amazing... Another $50 donation coming your way.

Confirmation number: 06G44168YR8159913.
[Xoom Android Development] shpitz461:
What a joke, can only give 8 thank-you's a day... lol
[Xoom Android Development] bigrushdog:
BigPart Repartition Upgrade and Resource Center

Credits

Much love, credit, and respect go out to [MENTION=2371134]Schischu[/MENTION] and [MENTION=4533695]rchtk[/MENTION]! Your insight on the kernel patch paved the way! The Motorola Xoom cheats death once again!

Repartition Guide

1) Your data will be totally wiped! If you have Nandroids, TitaniumBackups, or anything of any value on your internal storage, copy them to your microsd or computer! They will be gone forever! Your microsd card is the only safe haven on your Xoom during this process.

2) Put all needed resources on your microsd card! You will need the original TWRP 2.6.3.0 touch recovery from [MENTION=3900214]runandhide05[/MENTION], TWRP 2.6.3.0 BigPart version, your desired rom, and the BigPart boot image that goes with your desired rom. The BigPart boot images can be found in the next section.

3) Reboot into recovery. Flash TWRP BigPart. Don't reboot just yet.

4) Go back into wipe menu and wipe everything but /sdcard.

5) Go to reboot menu and reboot into recovery. Disregard the "No OS" warning and don't install SuperSU when asked.

6) When you come back into recovery, it will think your data is encrypted but it's not. 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.

7) Hit Home then go to reboot menu and reboot recovery. Once again, disregard "No OS" warning and don't install SuperSU when asked

8) 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!

9) Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". Flash your rom, BigPart boot image package, and any other resources as you normally would.

10) Reboot into system. You are done!

Later.... How to restore to stock partitions.

TWRP 2.6.3.0 R.A.H BigPart Edition Recovery

TWRP 2.6.3.0 BigPart

BigPart Eos 4 boot images with the usual modules

WARNING: You must have already executed the repartition before using these boot images. If not, follow the guide above! These will soft brick your device otherwise!

Eos 4 BigPart Wingray Boot Image

Eos 4 BigPart Stingray / Stingray_CDMA Boot Image

Eos 4 BigPart Everest Boot Image

BigPart @dreamcwli MyWingray 4.3 (or in theory any 4.3) boot image with the usual modules

Note: This is a new kernel rebased on @dreamcwli 's tree. No overclock or gpu overclock yet, but soon ;D

WARNING: You must have already executed the repartition before using these boot images. If not, follow the guide above! These will soft brick your device otherwise!

MyWingray 4.3 BigPart wingray Boot Image
[Xoom Android Development] realjumy:
That's great!!! That you very much, mate.

This is my EOS 4:

u0_a34@android:/ $ df -h
Filesystem Size Used Free Blksize
-h: No such file or directory
1|u0_a34@android:/ $ su
root@android:/ # df -h
Filesystem Size Used Free Blksize
-h: No such file or directory
1|root@android:/ # df
Filesystem Size Used Free Blksize
/dev 357.6M 48K 357.6M 4096
/storage 357.6M 0K 357.6M 4096
/storage/emulated 357.6M 0K 357.6M 4096
/storage/sdcard1 29.7G 21.6G 8.1G 32768
/mnt/secure 357.6M 0K 357.6M 4096
/mnt/asec 357.6M 0K 357.6M 4096
/mnt/asec/com.mobisystems.editor.office_registered-1 49M 47.5M 1.5M 4096
/mnt/asec/com.ds.goolors-1 28M 25.6M 2.4M 4096
/mnt/obb 357.6M 0K 357.6M 4096
/system 1007.9M 256.3M 751.6M 4096
/pds 1.9M 108K 1.8M 2048
/cache 503.9M 8.4M 495.6M 4096
/data 27.7G 809.9M 26.9G 4096
/mnt/shell/emulated 27.7G 809.9M 26.9G 4096
/storage/emulated/0 27.7G 809.9M 26.9G 4096
/storage/emulated/0/Android/obb 27.7G 809.9M 26.9G 4096
/storage/emulated/legacy 27.7G 809.9M 26.9G 4096
/storage/emulated/legacy/Android/obb 27.7G 809.9M 26.9G 4096
root@android:/ #

Replace boot.IMG in your EOS 4 ROM only with provided by brd and it should work.
[Xoom Android Development] bigrushdog:
[MENTION=697814]realjumy[/MENTION] I updated my post some http://xdaforums.com/showpost.php?p=47513726&postcount=188

If you like, you could copy and paste into the OP or link to it or whatever. It should probably be near the front. Also, you may wanna consider changing the thread title just a bit to reflect the direction this thread has gone. This is more about repartitioning than porting builds.

Also, to the folks who donated to me, I can't thank you guys enough! You guys really go over the top! At the same time, we really need to show @Schischu and @rchtk some love as well. Without their insight into getting the kernel logic right, I fear we wouldn't even be having this conversation right now.

I'm working with [MENTION=440141]synergy[/MENTION] getting the toolchains, flags, and bionic right for Xoom. As we all know, Xoom is particularly challenging. But once we get it, we're off to the races! We build the aosp master branch, which is still on 4.3.2.1.000. So it's likely we'll get that build first. Then, I don't foresee any major challenges going to 4.4. At least not as many challenges as getting 4.3 going.

Stingray and Everest do concern me. I'm most curious to see how the radio libraries and telephony apk's play with the 4.3 framework. CDMA has been a nightmare on 4.3! And Everest telephony resources are just ancient. We'll see...
[Xoom Android Development] realjumy:
Yes, I will update the 1st post as soon as I arrive home. I'm sorry to be as poor as the rats right now, but eventually I will donate as well... :P
[Xoom Android Development] realjumy:
Sorry for the double post, my phone is derping... :P
[Xoom Android Development] alex_72gr:
OK to understand this right, now we have a new recovery and boot.

Which ROM do we use? The same as before?

And BigPart [MENTION=2383306]dreamcwli[/MENTION] MyWingray 4.3 is only for wingray?
[Xoom Android Development] Asphyx:
Quick Question for BRD regarding Team EOS roms after Re-Partitioning...

Does this new space mean we can start using full blown GApps Instead of the scaled down versions we had been previously?

(I understand there may be NEON ramifications causing a NO Answer here)
[Xoom Android Development] armido:
Ext2, 3 or 4 formatting for user space?

Seems like a good time to ask and reveal my limited understanding of why user space is formatted vfat. I'm a linux fan who dislikes being limited to 4096 Mb when creating a linux.img. A yes or no answer will suffice. As long as the devs are pushing the limits, can the user space (sdcard) be formatted ext2, 3 or 4?

Thanks! Really happy to see progress here!
[Xoom Android Development] uzi2:
Even with the larger system partition, there is still no point in using full blown GApps. The BaNkS core Gapps are more than adequate as anything else can be downloaded from Google Play.
[Xoom Android Development] IcyAgitator:
Can cm10.2 be flashed instead of an eos4 rom after the repartition?

Sent from my dlx
[Xoom Android Development] Asphyx:
Except flashing them as opposed to GPlaying them puts them in the System Partition not user space doesn't it?

I know it's fine to flash a scaled down version but it was only done that way because it didn't fit inside system before...A Problem that would appear to have gone away now.

NEON concerns not withstanding....
[Xoom Android Development] drewski_1:
you could try with Dream's AOSP 4.3 big-part kernel

---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------

Dream's 4.3 new partitions

1|root@wingray:/ # df
df
Filesystem Size Used Free Blksize
/dev 358.4M 48.0K 358.3M 4096
/storage 358.4M 0.0K 358.4M 4096
/mnt/secure 358.4M 0.0K 358.4M 4096
/mnt/asec 358.4M 0.0K 358.4M 4096
/mnt/obb 358.4M 0.0K 358.4M 4096
/mnt/fuse 358.4M 0.0K 358.4M 4096
/system 1007.9M 268.2M 739.7M 4096
/pds 1.9M 108.0K 1.8M 2048
/cache 503.9M 8.4M 495.5M 4096
/data 27.7G 483.9M 27.2G 4096
/mnt/shell/emulated 27.7G 483.9M 27.2G 4096
/storage/sdcard1 59.5G 18.4G 41.1G 32768
/mnt/asec/com.speedsoftware.rootexplorer-1 4.0M 2.4M 1.6M 4096
/mnt/asec/com.keramidas.TitaniumBackupPro-1 2.0M 100.0K 1.9M 4096
root@wingray:/ #
[Xoom Android Development] IcyAgitator:
I'm on stingray_cdma.....unless i can flash a wingray rom and boot.img after the repart?

Edit.....eos4 stringray build 197 refused to flash. So i flashed a eos4 wingray build 203 rom with appropriate boot.img. The device is reporting the new partitions correctly. I will try to find a working eos4 stingray build and flash it. but as long as this is working correctly i see no immediate need to. :)

C:\sdk\platform-tools>adb shell
root@android:/ # df
df
Filesystem Size Used Free Blksize
/dev 357.6M 48K 357.6M 4096
/storage 357.6M 0K 357.6M 4096
/mnt/secure 357.6M 0K 357.6M 4096
/mnt/asec 357.6M 0K 357.6M 4096
/mnt/obb 357.6M 0K 357.6M 4096
/system 1007.9M 222.2M 785.7M 4096
/pds 1.9M 106K 1.8M 2048
/cache 503.9M 8.9M 495.1M 4096
/data 27.8G 225.8M 27.6G 4096
/mnt/shell/emulated 27.8G 225.8M 27.6G 4096
/storage/sdcard1 14.8G 3.9G 10.9G 4096
root@android:/ #
[Xoom Android Development] aFancyTickler:
im on stingray and i tried using cm10.1 as my rom and it didnt get to the bootanimation so i tried eos 3 and it works well. couldnt get eos 4 to download from goo.im
[Xoom Android Development] b8892778:
Great work on my MZ601 with wingray 4.3...

edit.EOS4 could't flash bigpart...
[Xoom Android Development] alex_72gr:
Because no one bothered to answer me, I am asking again to understand this right, now we have a new recovery and boot.

Which ROM do we use? The same as before? Do we have to change the boot IMG in the ROM with the big part one?

And BigPart [MENTION=2383306]dreamcwli[/MENTION] MyWingray 4.3 is only for wingray or it can be used with everest as well? And what is its difference with the other big part in the kernel?
[Xoom Android Development] MashBill:
I went this route too, but lost root. How did you get root back? I am having trouble with SuperSU also....
[Xoom Android Development] b8892778:
I'am still trying to flash 4.3 again

---------- Post added at 06:43 AM ---------- Previous post was at 06:36 AM ----------

My Xoom is MZ601 3G+WiFi

But I change it to MZ604 by flashing wingray

Now...

The new method can't work on EOS4-wingray-203

but can work on dreamcwli 4.3....my system have 771.43 MB free

well...waiting someone make Android 4.4....

dreamcwli 4.3 have some bug on graphing
[Xoom Android Development] drewski_1:
flash the same old ROM + new Big Part Boot.img

the kernel hack (as I understand it) deals with the new partition structure.

not sure on the MyWingray 4.3, but had trouble getting Root back (SuperSU zip that worked previously didn't take) so reverted to EOS4

---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------

I tried many options. Chainfire, Chainsdd, CWM. none worked.

now back to EOS4 and patiently waiting for new ROMs :)
[Xoom Android Development] rajones19:
Same here. Successfully loaded dreamcwli's 4.3 build, but no root. Tried flashing the most recent SuperSU, without success. Looked through dreamcwli's original thread, but nothing suggested there was successful. Decided to try EOS, so did a factory reset, and flashed the EOS4 ROM I've been running for months, along with appropriate GAPPS, and the new EOS boot image. Boot image failed to flash, and of course the Xoom hung on boot. Tried to reflash 4.3, but that also failed to flash. I started back at the beginning of the re-partitioning procedure, I'm back on dreamcwli's 4.3 without root. Sure seems zippy compared to 4.2.2 - but that may change when I get all my apps back on there. Great work - THANK YOU!
[Xoom Android Development] b8892778:
Try this http://d-h.st/hk1

I found it at dreamcwli's 4.3 post 1 page
[Xoom Android Development] drewski_1:
didn't work for me. said SU binaries weren't installed.
[Xoom Android Development] rajones19:
Same here - it was the first thing I tried. Still had the zip on my SDCard.
[Xoom Android Development] bigrushdog:
SuperSU fails on dreams 4.3 because that build doesn't have BUSYBOX! I caught that when working out the guide. I'll get us busybox.
[Xoom Android Development] bigrushdog:
I see some interesting questions and commentary. I'm tired tonight so I'll address these matters tomorrow. Dreams 4.3 works on all variants. Just stingray and everest won't have radio.
[Xoom Android Development] hawkstorm:
That's great. [MENTION=470268]bigrushdog[/MENTION] [MENTION=697814]realjumy[/MENTION] Is there a way to get the radios for everest and stingray on a separate zip?
[Xoom Android Development] logitechor:
I have Dreams 4.3 installed. I assume that if it boots and it does it did it correctly. All good so far.
[Xoom Android Development] logitechor:
I meant to add that the Xoom has never run better for me. I installed Google Launcher in addition. Works great. I guess I will start to install apps I want back on it. I want to thank the developers. Great work.
[Xoom Android Development] seajamiet:
Definitely need a ROM cooker now to help us out to get a nice full non-partition restricted android 4.3 or even 4.4 ROM ready to serve. That's my opinion anyway. Does this partition change yield any more benefits apart from higher android versions?
[Xoom Android Development] :
I wanna ask you because i have my xoom forma two years, and laste time i format it and give me error with dev block mmblck or something else and i think that i could have my internal storage corrupt..

If i install your 4.3 image modded, and then the repartition, Will it works fine?? Thanks and sorry me
[Xoom Android Development] bigrushdog:
From a user point of view, not really. It just opened the door to future Android versions and allows for the advancement of development.

We've ran the new partitions for a few days now and haven't seen anything peculiar. 4.3 has some minor graphics issues but generally it's fully functional. I hope to have a monster 4.3 build booting soon.
[Xoom Android Development] P00r:
You will not fix bad block by repartitioning but if you are lucky they will end up in an unused place although with flash I am not sure there's such thing, not sure either how the bad block mapping are handled on the Xoom fs

Thanks to all the people who risked their tablet to get us this new partition size' this open up new possibilities

I have lost root as well and the restore su I tried didn't work, patiently waiting for newer images as I am sure that dream and others will make this tablet working good again :)

---------- Post added at 10:23 AM ---------- Previous post was at 10:17 AM ----------

Same here, Dream built where the best I had for a while, I noticed no funny graphics effect since this new install I used to have some problem, maybe that was related to size
[Xoom Android Development] sublimaze:
Agreed. I can't believe how many times I thought my Xoom was on the verge of death, only to be revived by clever devs. My refurbished Xoom was the best $200 I have ever spent on a gadget. I will definitely flash this once the root issues are cleared up.
[Xoom Android Development] rajones19:
Imagine how those of us feel who spent $800 for it at 7:30 a.m. on launch day ....
[Xoom Android Development] IcyAgitator:
I got mine for free on launch day with promo ;)
[Xoom Android Development] buffalo_guy:
Xoom not see external Sdcard

Followed the instructions for the re-partitioning. Everything worked except the Xoom cannot see the external sd card in recovery. I have re-formated it as fat32 and tried another card. When I view the files in the PC they are there. Any ideas? Thanks,

Steve
[Xoom Android Development] buffalo_guy:
Solved

Once I wiped the external sdcard in TWRP and recopied files on the pc to the sdcard I qas able to mount and recognize files on the sdcard in recovery.
[Xoom Android Development] marmo:
Repartition smooth as silk.

Thanks everyone for the steps to follow on the first post.

I repartitioned my Wingray without troubles and now it's running back EOS 203 till 4.3 will solve the root issues.

Thank you again, you guys are awesome!
[Xoom Android Development] buffalo_guy:
Re-partition Successfull!

Once I got around the issue of not being able to read the external sdcard everything went very well. Started loading up my usual apps with no problems. I am running 4.3 with no apparent problems at this point. A contribution is coming you way. Well done!

Steve
[Xoom Android Development] notbrodie:
Just want to chime in:

The re-partitioning worked for me! installed eos 203 and the big part kernel and am restoring my titanium backup right now

additionally, now that it has been re-parted, lagfix fstrim now works on the /data partition! sweet!
[Xoom Android Development] Justin.G11:
Here's my biggest question:

How can we identify which ROMs are for the new partition layout? Just assume everything 4.3 and later? It would be nice if we added [BigPart] to the thread title to make them more easily identifiable.
[Xoom Android Development] realjumy:
Only roms with BigPart in their name can be used with the new layout.
[Xoom Android Development] Justin.G11:
Search in the forum for "BigPart" comes up with exactly one thread hit: this one.

None of the ROMs have "bigpart" in their name in the title. That's my problem.
[Xoom Android Development] jgardner:
If you look, this was just finalized yesterday. It will still take some time to cook everything together. In the first post it has the boot images that you can use with the eos4 and my_wingray roms right now. Any others you'll just have to wait for them to be cooked for the big partition.
[Xoom Android Development] hawkstorm:
[MENTION=697814]realjumy[/MENTION] [MENTION=470268]bigrushdog[/MENTION] THANKS SO MUCH FOR THIS! It's amazing that we can get a breath of new life on the XOOM. Now my only worry is that the everest I have is a HK variant considering Malaysia doesn't really get our own variants. I'll try to pull the partition table to verify. What would be the main differences for a HK variant?
[Xoom Android Development] Asphyx:
Did I misread the First page or Misinterpret it?

I was under the impression that we could use old roms provided we replaced the boot.img in the zip with the NEW BIGPART boot.img for our unit?

(Only after repartitioning has been completed)

Is that wrong and we need to wait for a particular build?
[Xoom Android Development] notbrodie:
you can use any rom, but the kernel must be bigpart compatible. I'm going to assume that the eos kernel isn't compatible with cm.

currently, i'm running the latest eos4 build with the eos big part kernel

Sent from my Nexus 5
[Xoom Android Development] Justin.G11:
Fair enough ... and I seem to be off and running Big-Part and all.

I just went back to mywingray as it's been very reliable to me and all seems to be well.
[Xoom Android Development] Asphyx:
Thanks notbrodie....

I see the distinction your making there now!

We can use any EOS4 on Stingray because he posted a Stingray boot Image for EOS4 but other Roms will need a corresponding bigpart boot image to go with it....

Much clearer Thanks!
[Xoom Android Development] shpitz461:
I can't seem to get 4.3 to root, both UPDATE-SuperSU-v1.51-Xoom.zip and UPDATE-SuperSU-v1.69.zip refuse to work.

Got dreamcwli's 4.3 flashed on bigpart.

EOS4 197 Stingray flashed great prior to me trying 4.3, and supersu_v1.69 worked fine...

Any ideas?
[Xoom Android Development] scottgti:
Any ideas?
[Xoom Android Development] drewski_1:
This is (currently) a hack using existing ROMs so will depend on BigPart kernel compatibility.

Right now it's confirmed with just EOS4, EOS3 & MyWingray (4.3) for which BRD has provided modified kernels

You can try other ROMs and flash a BigPart kernel to see if it works. Ideally a somewhat universal kernel (modded Elemental?) would work for many existing ROMs.
[Xoom Android Development] mikewanda1971:
How do we know if we did it correctly. Is there something to look for to identify if we did it right
[Xoom Android Development] sibax:
There is a free app called partition table on play store that will display all info on your partition sizes.
[Xoom Android Development] realjumy:
Or write

df

and check the sizes.
[Xoom Android Development] ifti_a:
I might give this a try can I follow first page instructions and flash eos build 203 right back ?

By doing the first page instructions I'm just changing partition sizes for future builds correct ?