yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] dizzy33:
Hello, I need to go back to my CM10.1 Rom, so I would like to revert the BIGPART procedure. I followed the BIGPART procedure but using the TWRP which is not bigpart, all went fine, then I flashed back my CWM Recovery, and now from this recovery I cannot install anything, it says "Couldn't open directory" ... I need to restore my CWM backup ...:crying: I tried formating evertyhing, wiping everything with CWM but still the same.

So what would be the clean process to go back to the original partitions ?
[Xoom Android Development] jasonbtx:
Success

Was able to use adb sideload after wiping tablet to push BigPart and then to push Omni. Finally
[Xoom Android Development] realjumy:
Schischu's Omni 4.4.2 on Xoom?

Sorry for the delay... I'm isolated in the middle of nowhere, in the countryside... No decent internet... But I'm working in something. No 4.4 and no kernel (yet), but something really useful... ;) Keep tuned!
[Xoom Android Development] logitechor:
I am intrigued. Good luck.
[Xoom Android Development] RoryPG:
Realjumy, you must be really isolated. Schischu released a version of Omni ROM 4.4.2 KitKat for Xoom Wingray last week, Dec 22. Now developing for Everest. ElementalX 2.1 kernel, PA-Gapps, no need for boot image, depends on a Bigpart repartition. Multiple releases and already a solid daily driver. http://xdaforums.com/showthread.php?t=2580256

Xoom is alive!!!
[Xoom Android Development] realjumy:
Thanks mate. Definitely, I'm really isolated. I'm looking forward to going to my home and having internet again... Instead of this limited slownet... xD
[Xoom Android Development] hawkstorm:
[MENTION=697814]realjumy[/MENTION], [MENTION=2371134]Schischu[/MENTION] is experimenting with a everest build and requires some testers. Which is amazing news!
[Xoom Android Development] jkd:
hello,

i have applied bigpart but i can't install [ROM][4.4.2] OmniROM - Wingray - bigPart ???

help ...
[Xoom Android Development] hawkstorm:
Go back to the Wingray OmniRom thread and start from step 1. Also, you don't have to flash the boot.img as mentioned in the OP cause it's in the Wingray zip
[Xoom Android Development] Adler12:
1 what have you done?

2 where it stops?

3 you need four things: TWRP @ BigPart, Omni-Rom for your device, Gapps & SuperSu

- TWRP@Bigpart over the TWRP

- Wipe Cache

- Reboot > Recovery

- Wipe everything (without SD)

- Format Data

- Reboot > Recovery

- Flash OMNI > Wipe Cache & Dalvik

- Reboot > Recovery

- flash gapps > Wipe Cache & Dalvik

- Flash SuperSu > Wipe Cache & Dalvik

- Reboot in to System

-
[Xoom Android Development] rcoliveirajr:
I did this process and installed this ROM: http://xdaforums.com/showthread.php?p=49060796, but the device stays in "Dual Core Technology" with Motorola Logo, I can boot normally into TWRP Recovery what should I do?? It's not a bootloop, it just keeps in the M Logo... Thanks..
[Xoom Android Development] jkd:
Thanks,

now all is ok.
[Xoom Android Development] billygoat32:
I've got the same issue, I followed both threads to the T - not sure what to do I can't get past the Dual Core log no matter what button combo I push - no recovery, no regular boot, no fast boot... any help would be appreciated.

UPDATE: Got into recovery by Power + tapping volume down then when it said -- android recovery hit volume up.. trying to reflash rom now. Following the directions by Adler12 worked - the OP should be updated to state that you do not need to flash the boot images, instead of saying "follow this thread" which tells you to flash the boot images.
[Xoom Android Development] atom_jack:
Does the BigPart version of TWRP display anything at the top of the screen differently than the runandhide05 version? I started following the instructions in the OP, to the letter, and am ready to flash Omni, however I noticed that TWRP displays "v2.6.3.0(RunAndHide05 Edition)" at the top of the screen. I just wanna make sure the recovery flash I did worked as I don't wanna brick it :)
[Xoom Android Development] drewski_1:
It probably should, but doesn't display anything about BigPart
[Xoom Android Development] tekrhino:
Worked like a charm!

Worked like a charm..

Had a "Android.phone.com" force close issue upon initial boot and setup screen but a Reboot seems to have fixed it.

I'm running CM11 for Stingray and in the process of restoring apps and Widgets.

Big Thanks to all the Devs that helped breath New Life into an Old Friend.

tek!

:cool:
[Xoom Android Development] armido:
Where are your instructions for restoring to stock partition?

Thanks
[Xoom Android Development] methogod:
What if my device is completely stock, do I need root to do this?

Never messed with rooting my Xoom because it was always a pain, and never though Kit Kat Stable would be available.

Now that it is, i can not find a straight answer - "DO I NEED TO BE ROOTED" to install BIG PART...

YES OR NO?

and how do we install it from recovery, without having ROOT ACCESS to install a customer recovery?

what is the steps (exactly) to installing BIG PART - which i assume ROOTS and installs the special custom recovery while re-partitioning the Xoom?

does it have to be renamed, "UPDATE.ZIP" and placed in a certain location and not on the SD CARD or when you say SD "do you mean the internal SD1" before BIG PART is ran??? Anyone see that its a little confusing... or is everyone rooted? and not had this issue?

Any one care to make a step by step FROM STOCK ROM 4.1.2 --- to BIG PART (what needs to be done)...

I am sure its in this thread but a few extra details about what you need to have before installing BIG PART would be helpful. Every place you go to ROOT your WINGREY has been taken down or is dated....

Which i think is why i never messed with it in the first place...

LOVE THAT KK is available and stable....Love XDA much love for developers who can keep these devices alive for so much longer.

please excuse my lack of knowledge with this device...

thanks...
[Xoom Android Development] peterkling:
Seems as my Xoom is bricked, because there is no chance to access /cache anymore.

Is there a "hard way" of repartition everything via fastboot?

Storyline:

(rooted, TeamEOS-ROM) Xoom stuck at "M"

still could access via fastboot so I flashed the new version of TWRP and followed instructions...

It always said

E:unable to mount '/cache'

Mounting of "/data" and "/cache" not possible/visible in TWRP

Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 366992 48 366944 0% /dev
/dev/block/mmcblk1p8 1032084 17652 1014432 2% /system
[Xoom Android Development] Adler12:
1. Open yor Bootloader

- Install ADB on PC (http://xdaforums.com/showthread.php?p=42407269)

- Install Motorola USB Driver (http://goo.gl/9VwNnb)

- Go on Telefon Info

- Push some times on "Over the Phone" to get Devoloper settings

- Go on Devoloper Settings an aktivate "USB-Debugging"

- Connect the phone to the PC via USB

- Open a Commandline

- Add "adb shell" Enter

- Add "adb reboot bootloader" Enter

- Your XOOM will reboot into the bootloader showing "Starting Fastboot Support Protocol".

- Add "fastboot oem unlock" Enter

- Add "fastboot reboot"

2. Install the TWRP Recovery

- Add "adb reboot bootloader" Enter

- Add "fastboot flash recovery recovery-xxxxxTWRPxxxxx.img

- Add "fastbbot reboot recovery"

3. Install the new BigPart

- Put the TWRP@BigPart on the SD Card

- Put the OmniRom on the SD Card

- Put the SuperSu on the SD Card

- Put the desired Gapps on the SD Card

The Rest:

you need four things: TWRP @ BigPart, Omni-Rom for your device, Gapps & SuperSu

- TWRP@Bigpart over the TWRP

- Wipe Cache

- Reboot > Recovery

- Wipe everything (without SD)

- Format Data

- Reboot > Recovery

- Flash OMNI > Wipe Cache & Dalvik

- Reboot > Recovery

- flash gapps > Wipe Cache & Dalvik

- Flash SuperSu > Wipe Cache & Dalvik

- Reboot in to System

- Have Fun
[Xoom Android Development] notbrodie:
it might do nothing, but try going into fastboot and erasing, then formatting cache

fastboot erase cache

fastboot format cache

then reflash bigpart recovery, then wipe EVERYTHING except sdcard

Sent from my Nexus 5
[Xoom Android Development] mikebeatrice:
It couldn't hurt to flash the normal recovery and do the formatting that's listed in the first couple steps of the big part procedure. Sounds like you just skipped ahead to the steps after the modified recovery is installed.
[Xoom Android Development] yel@ch:
Partition information

Hi.

I have the same problem: I've followed exactly the instructions, retried the normal recovery etc.

fastboot erase cache
erasing 'cache'...
OKAY [ 0.872s]
finished. total time: 0.879s

fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.510s

After several other tries I ended up that the userdata-partition is also not available anymore...

fastboot -w
erasing 'userdata'...
OKAY [ 18.017s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.514s]
erasing 'cache'...
OKAY [ 0.834s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.518s]
finished. total time: 19.902s

What are the recommendations for manually repartitionning (data,swap & system?). Would this be OK:

~10240MB ext4

~512MB swap

rest fat32

Thanks
[Xoom Android Development] peterkling:
Did not work :(

I didn't leave out any step.

Tried to flash back to Stock from: H.6.1-38-5_TMO_Germany.zip - surprisingly the recovery is still TRWP although:

fastboot flash system "...\MZ601_H.6.1-38-5_TMO_Germany\system.img"
sending 'system' (262144 KB)...
OKAY [ 14.531s]
writing 'system'...
OKAY [ 6.438s]
finished. total time: 20.969s

fastboot flash boot "...\MZ601_H.6.1-38-5_TMO_Germany\boot.img"
sending 'boot' (8192 KB)...
OKAY [ 0.688s]
writing 'boot'...
OKAY [ 0.594s]
finished. total time: 1.281s

fastboot flash recovery "...\MZ601_H.6.1-38-5_TMO_Germany\recovery.img"
sending 'recovery' (12288 KB)...
OKAY [ 0.922s]
writing 'recovery'...
OKAY [ 0.688s]
finished. total time: 1.609s

fastboot flash userdata "...\MZ601_H.6.1-38-5_TMO_Germany\userdata.img"
sending 'userdata' (139245 KB)...
OKAY [ 7.750s]
writing 'userdata'...
OKAY [ 4.328s]
finished. total time: 12.078s

fastboot erase cache
erasing 'cache'...
OKAY [ 0.516s]
finished. total time: 0.516s

Still stuck at "M"-logo

Flashing the regular TRWP and wiping like described from Step 1 - 10 (except step 3) to doesn't repartition the Xoom, does it? How do you revert to stock/factory image and partitions?
[Xoom Android Development] yel@ch:
Partition-Problems solved!

I was able to solve it myself: Before this procedure I was on the default TWRP2.6.3 and updated the BigPart-TWRP... That seems to have caused the problems! I've downloaded the 'Non-BigPart' TWRP 'R.A.H._TWRPv2.6.3.zip' and the partitions were able to be mounted and then the procedure from the first post worked perfectly

Device is in recovery and connected to PC and sdcard is mounted in TWRP (check!):

Pc-commandprompt>adb push R.A.H._TWRPv2.6.3.zip /sdcard

>adb reboot-recovery

in

recovery on the phone

you should be able to mount everything but cache (check) --> install the copied non-bigpart-RAH-zip from the sdcard

Reboot into recovery

Follow excactly the instructions 3-8 from the first post (incl. Big-part-recovery-Install & don't care the 'cannot mount cache' errors at the beginning).

Afterwards I've installed those: OmniRom 4.4.2, pa_gapps-modular-full-4.4.2-20131230-signed.zip & UPDATE-SuperSU-v1.86.zip

Works perfectly!
[Xoom Android Development] Fatboy1904:
How were you able to install the NonBigPart TWRP over the BigPart one ? When I try to do this, it crashes constantly.
[Xoom Android Development] superbay:
Once you use bigpart, you need to use bigpart based roms and recovery. Otherwise you have to revert the repartition to use others
[Xoom Android Development] elkedra:
Thanks realjumy and all those who have put in the work to keep our xooms up to date. I installed big part and an omni Rom. Found the omni Rom a bit buggy so installed Everest big part boot image and EOS v167 (in my opinion the best one) and all is working fine. Will wait a bit before trying another 4.4.x Rom.
[Xoom Android Development] dccrens:
Thanks go out to Realjumy and all the developers that have contributed to keeping the first and best Pad alive. I have been running EOS Stingray forever. I finally decided to take the plunge on going Bigpart. I followed the directions and they worked perfectly. I am running CM11 now and it rocks. Your hard work is much appreciated.
[Xoom Android Development] ifti_a:
Is there a latest ROM from the developers of the EOS 4 ?
[Xoom Android Development] audioblivious:
There's a cm11 for stingray?
[Xoom Android Development] hawkstorm:
Yes. Check Android development forum. Everest, stingray and wingray are in a single thread
[Xoom Android Development] audioblivious:
For xoom stingray got a link? Thanks
[Xoom Android Development] chykal:
http://xdaforums.com/showthread.php?t=2596566
[Xoom Android Development] audioblivious:
Can't dirty install over 4.2.2 cm can you or have to use trwp big partition for it
[Xoom Android Development] chykal:
Yes you need to do the BigPart mod and also use the instructions to flash CM 11 BigPart. You will have to wipe your internal memory. No dirty flash from non BigPart.
[Xoom Android Development] audioblivious:
Ok so have to make big part I'm using cwm any way to do this using it
[Xoom Android Development] rlmesq:
Is there a way to change the splash screen logo after installing BigPart & CM 11? I used the Team EOS splash screen app to replace the double-m with a Jellybean logo.

Now the EOS app says it only works on Xoom and closes.

I've tried the methods listed in this post, too, with no success.

http://xdaforums.com/showthread.php?p=49152172
[Xoom Android Development] notbrodie:
no. twrp is required

Sent from my Nexus 5
[Xoom Android Development] Alxoom33:
The last Eos 4 is 205 for wingray and I believe 184 for stingray, both are 4.2.2 builds.

EOS no longer develops a Xoom rom. BRD was involved in Big Part and rom devoted, but l don't know to what extent.

The most up to date Xoom Big Part ROMs are Omni and unofficial CM 11. Both were developed and are maintined by [MENTION=2371134]Schischu[/MENTION] and both run KitKat 4.4.2 and both have OTA updating available.

You can install clean and then restore data from your Nandroid.

It is hit or miss whether the data will be compatible with a later rom such as 4.3 or 4.4. Good luck.
[Xoom Android Development] audioblivious:
Ok how do I do this using cwm installing big partition so I can use this stingray rom also what gapps. To use
[Xoom Android Development] notbrodie:
you cannot use CWM. as has been said numerous times, TWRP is a requirement. you can use CWM to flash the bigpart TWRP zip. that's it. after that, just forget that CWM even exists

Sent from my Xoom
[Xoom Android Development] Alxoom33:
That's absolutely correct. Read the instructions in the OP very carefully. Otherwise you will end up with a glass top, Xoom coffee tray.:p
[Xoom Android Development] stingbandel:
Hi,

I have applied the BigPart TWRP but it asks for a password when it starts.

Do you guys have the same problem like me? Asking for a password?

thanks
[Xoom Android Development] drewski_1:
that's the part of Step 6 where it says the tablet thinks it's encrypted.

ignore it and hit cancel and follow the rest of the steps (format data, wipes, reboot, etc)
[Xoom Android Development] stingbandel:
Ok tq for the explanation. Now I need to configure how to get twrp to detect my sdcard. i have tried sandisk, transcend and samsung card. None of them works even though I already make it fat32.

I manage to get sandisk to mount but when I reboot, it gets stuck at the reovery main page..
[Xoom Android Development] hawkstorm:
http://xdaforums.com/showthread.php?t=2596566
[Xoom Android Development] gab_ITA:
guys, i need to remove bigPart to flash a rom. i set up it to usa a kitkat rom, but for a few problems i need my old jb rom. i flashed it with bigPart, but now my device is stucked on the initial Moto logo. what can i do ? do i have to restore old recovery ?
[Xoom Android Development] superbay:
What is your jb rom?
[Xoom Android Development] gab_ITA:
cm10
[Xoom Android Development] realjumy:
If your old ROM is not BP, restore the Simple Partition. It's like BP but using normal recovery. Remember to wipe and so.
[Xoom Android Development] gab_ITA:
thanks, now it work, but i can't restore the previous backup of the rom
[Xoom Android Development] realjumy:
The backup was done in BP or SP?

If it was done in SP, just remember that there is a Recovery version that had a big bug: the backups were done wrong and they were no able to restore it. Maybe that's the problem.
[Xoom Android Development] rlmesq:
Can't he just use the BigPart boot image?

When I went back to a 4.2 ROM so I could use the Team EOS splash screen app, I just flashed the old ROM, then flashed the BigPart boot image (from the first post in this thread) over it.

I could've edited the ROM zip file and replaced the boot image inside it, but I was too lazy.

I used the splash screen tool, removed all non-essential files with TiBu, and made a backup of that 4.2 installation (boot, data & system) in case I ever need it again.

I then restored my Kit Kat backup and all was back to normal.
[Xoom Android Development] realjumy:
Let me say... That was risky. The partitions are changed. What if you write some data in the wrong place?
[Xoom Android Development] notbrodie:
I'm confused. how was that risky? isn't the whole reason we do bigpart?

all the bigpart boot images are 4.1.2-4.4.2 compatible

Sent from my Nexus 5
[Xoom Android Development] realjumy:
The bootloader says where each partition begins and ends... Wrong bootloader and ROM will write data in the wrong places... Just imagine the consequences.
[Xoom Android Development] Schischu:
Well even if that happens, nothing serious will happen. The worst case is that your system cache and userdata partition are corrupt.

But that is automatically cleaned up the next time you wipe them to flash a new image.

So fear not, nothing bad can happen to you will using bigPart TWRP.
[Xoom Android Development] notbrodie:
Also, twrp doesn't touch the bootloader. BigPart installation completely bypasses the bootloader restrictions

Sent from my Nexus 5
[Xoom Android Development] iamezio:
Is it possible to flash stock image to undo the BigPart modification and go to the stock partition layout ?
[Xoom Android Development] kuskro:
Yes, it is possible. Follow again the OP instructions but this time flashing back the original TWRP 2.6.3.0 touch recovery to recover the stock partition layout, instead of using TWRP 2.6.3.0 BigPart.
[Xoom Android Development] GedeWK:
How to back to stock partition please? I want to back to stock and stuck on black screen after the dual core logo.

EDIT: Reflash and it worked as usual
[Xoom Android Development] bigrushdog:
I don't think dumping NAND to computer is even necessary at this point. Since parted is available in recovery and we have all the information from test disk. I fear the partition table is inside the bootloader partition. If that's the case, it's not good. Even though we are unlocked, the device still likely does a signature check on the bootloader. That means we can't modify it. You can't just modify partition sizes without letting the system where to look for the partitions. That's what a partition table is for.
[Xoom Android Development] realjumy:
I'm wondering if we can use this: http://javigon.com/2012/08/27/the-bootloader-understanding-modifying-building-and-installing/
[Xoom Android Development] realjumy:
It must be a way to doing it. Many devices have managed the way to bypass the signature check...

--- EDIT:

For example: http://xdaforums.com/showthread.php?t=1619913

Another example: http://xdaforums.com/showthread.php?p=25753055

An other one: http://xdaforums.com/showthread.php?t=1018260

And something else: http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html
[Xoom Android Development] halomademeapc:
The /system partition on my first Android, a Galaxy Player 5, was too small to handle some stuff but the developers got around it. It took me a little bit of digging to find it, but perhaps this could be of some use. http://xdaforums.com/showpost.php?p=39647276&postcount=23
[Xoom Android Development] realjumy:
Those are symlinks, and that's Brd is trying to do without success. Let's see what happens...
[Xoom Android Development] lepa71:
Just to add some thoughts. When I had my HP Touchpad, we had to expand system partition twice.
[Xoom Android Development] Domunus:
Model: MZ600 Stingray VZW 32GB

ROM: Android 4.3 for Xoom (Experimental)

Kernel: ElementalX-Xoom-v1.3

Disk mmcblk0.raw - 32 GB / 29 GiB - CHS 3892 255 63
Partition Start End Size in sectors
P MS Data 43008 47103 4096
P MS Data 57344 61439 4096
P MS Data 118784 643071 524288
P MS Data 643072 989183 346112
P MS Data 989184 62512095 61522912
[Xoom Android Development] caveman102:
Will do it when i get back home tonight

SENT FROM HTC ONE POWER HOUSE
[Xoom Android Development] pots22:
kitkat

A stupid question

Somebody here work for google entreprise?
[Xoom Android Development] realjumy:
People working for Google are not going to use Xoom, that's for sure...
[Xoom Android Development] ahmed007:
true that they are too busy playing around with new toys lucky bastards lol :D
[Xoom Android Development] kikuto:
MZ605 - Brazil model

Sorry about my late, but I finished the steps :D

Model: MZ605 umts_everest

Storage size: 32GB

ROM: EOS 4 nightly 170

Kernel: Elemental X 1.3

NOT Hong Kong model

testdisk output:

Time lapsed: 3:19:36
Disk mmcblk0.raw - 32 GB / 29 GiB - CHS 3892 255 63
Partition Start End Size in sectors
>P MS Data 43008 47103 4096
P MS Data 57344 61439 4096
P MS Data 118784 643063 524280
P MS Data 643072 989183 346112
P MS Data 989184 62512095 61522912
[Xoom Android Development] realjumy:
OK folks. I think that we already have enough partition data. That means that now we must get focus on the modification of the partition table. As [MENTION=470268]bigrushdog[/MENTION] said, it is maybe in the bootloader partition. So our next step is see if we can disassemble it and avoid the signature check... I'm afraid that that's is going to be hard, but I will try to do any approach this weekend.

I will let you know what I find, but definitely I will need some help from some expert...
[Xoom Android Development] no*boundaries:
Happy to help if your after MZ601 umts-Everest Australia

If you need a guinea pig happy to help
[Xoom Android Development] HairyMerkin:
I remember from when I had my nexus one that when we upgraded to ICS that we needed to use another HBOOT with larger system partitions. Maybe contact Texasice (he is a major dev still)
[Xoom Android Development] badaas:
http://xdaforums.com/showthread.php?t=1270589

blackrose dev tool..
[Xoom Android Development] seajamiet:
Dunno if its similar to what your trying to achieve but if it helps when I had a xperia x10 they crashed the bootloader and then ran their own over the top to load custom kernels and avoid signature checks. After this they figured how to unlock the bootloader which was what they were trying to do but the Xoom is already unlocked and now I'm waffling on. I'll stop here.