yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] MrZ123:
So I loaded the new TWRP Recovery, booted into it. Then I wiped everything except SD. I tried to flash the BigPart recovery from the regular TWRP recovery but it kept failing, so I rebooted and flashed the BigPart recovery using Fastboot. However, now I cannot get back into recovery!

Because I wiped the device, I can't boot into android and adb reboot recovery. When I restart the device (power + volume up) I just get Starting RSD Mode 3, my charge status, etc and stays there w/ dualcore logo. If I restart the device again and then hold volume down it stays on the dual core logo and i can use fastboot commands.

Please advise on how I can either get into Recovery or flash a new rom!

Thanks
[Xoom Android Development] matt4321:
You need to flash a boot.img (kernel), that's why it's not booting at all, the kernel is the first port of call. doesn't matter if there is no /system.

Flash a boot.img in fastboot and then when you reboot you'll be able to use the volume keys to get into recovery and retry.
[Xoom Android Development] MrZ123:
Just tried flashing the stock boot.img, getting error "Flashed image is larger than partition size FAILED"

Help!
[Xoom Android Development] matt4321:
stock on which android version, make sure to try the one you were running before
[Xoom Android Development] MrZ123:
Got the boot.img here http://rootzwiki.com/topic/1586-stock-images/

for my Verizon Xoom. Says flashed image is larger than partition.
[Xoom Android Development] matt4321:
you're using "fastboot flash boot boot.img" yeah?
[Xoom Android Development] MrZ123:
Correct.

"C:\platform-tools>fastboot flash boot boot.img

sending 'boot' (119444 KB)...

OKAY [ 8.098s]

writing 'boot'...

(bootloader) Flashed image is larger than partition size

FAILED (remote: (00000002))

finished. total time: 9.099s

Not sure what to do now. Thanks for any help.
[Xoom Android Development] matt4321:
okay so the image you are trying to flash to the boot is 116mb, seen here: """"sending 'boot' (119444 KB)...""""

a boot.img is usually around 5/6mb or so. so you're flashing the wrong file. can you flash this boot.img (it's stock 4.1 boot.img): http://d-h.st/LsB
[Xoom Android Development] MrZ123:
Matt, that boot.img worked! However I still can't seem to get into recovery...
[Xoom Android Development] matt4321:
Flash the normal TWRP that is stickied in the development section then try

What happens now when you turn on the device? Do you know how to enter recovery using the volume keys?
[Xoom Android Development] MrZ123:
Same as I described before. Haven't tried with stock TWRP. Any other suggestions?
[Xoom Android Development] matt4321:
Try stock TWRP then when your device starts up after a few seconds hit the volume down button, it should say Android recovery and then hit the up button to accept it
[Xoom Android Development] MrZ123:
Hay Matt, unfortunately still not getting to recovery after TWRP.

"C:\platform-tools>fastboot flash recovery R.A.H._TWRPv2.6.3.img

sending 'recovery' (6087 KB)...

OKAY [ 0.642s]

writing 'recovery'...

OKAY [ 2.086s]

finished. total time: 2.735s"

Still can only get to either "Starting RSD Mode 3" screen w/ DualCore logo or if I hold Volume Down then I get just DualCore logo and can send fastboot commands.

Also, re-flashed the boot.img you sent and still not getting there...

***EDIT***

Use these steps to boot back up! http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/2788-how-return-stock-3g-4g-hr166.html

Seems the recovery is causing the problem, but why?

**EDIT 2**

Got TWRP 2.6.3 installed and got into recovery. When I go install, and select the R.A.H._TWRPv2.6.3_BigPart_selinux.zip from the SD card, I get

E: Unable to open zip file

Error flashing zip /sdcard/R.A.H._TWRPv2.6.3_BigPart_selinux.zip

Updating partition details

Failed

So how to i get the BigPart recovery flashed??

Thanks for any more help!
[Xoom Android Development] MrZ123:
Finally got BigPart TWRP to install, wiped, installed ROM and boot paritition, everything mounted in TWRP fine, however when I reboot to system I get stuck at Dual Core logo.

Any suggestions?
[Xoom Android Development] gcounts:
I had a super hard time as well. I was having the failed message as well. I flashed the twrp zip again and followed the op instructions to a t. and it worked finally. Don't give up. Keep trying and make sure your zip downloads are good. I had the omni rom and the gapps downloaded but they were bad. Redownloaded them them and all went perfect.
[Xoom Android Development] MrZ123:
I am trying that, having trouble getting the redownloaded files onto the SDcard as I don't have an external reader and cant copy from recovery...
[Xoom Android Development] gcounts:
Can't you put the sd card in your phone do the download and pop it back into the xoom? That's what I did.
[Xoom Android Development] MrZ123:
Got everything to work except the last and final step. Repartitioned, made sure it worked, formatted, however when I flashed Omni ROM or CM ROM, either way it went to the Dual Core screen and never loaded the ROM, just stuck at boot screen. Any suggestions?
[Xoom Android Development] gcounts:
No. If you have good zip downloads and you flashed the rom and gapps and it's stuck.....I would do the whole process over until it works. Sorry I can't help any more than that.
[Xoom Android Development] webeougher:
Go with the oldest version of these roms that you can find and then if that works, start updating.
[Xoom Android Development] cyaclone:
Now that I have TWRP 2.6.3.0 BigPart and the OmniROM BigPart, can I use the TWRP Manager with this version of TWRP?
[Xoom Android Development] drewski_1:
Doubtful as the BigPart version is not official.

There is a twrp BigPart 2.7.0.0 in the Dev Forum, if you want to upgrade
[Xoom Android Development] thenemis:
how about f2fs support?
[Xoom Android Development] drewski_1:
Not at the moment
[Xoom Android Development] Chelseablue:
Thanks for all the hard work you guys put in to keep the Xoom up to date. The whole process went buttery smooth and couldn't have taken more than ten minutes. You guys rock!
[Xoom Android Development] drewski_1:
RAH just updated his TWRP thread with a F2FS capable 2.7.1.0

http://xdaforums.com/showthread.php?t=1782235
[Xoom Android Development] Submarine854:
Quoted from OP.

As I understand this, I've got a "normal" touch recovery (TWRP 2.6.3.0 touch recovery) and one with BigPart (TWRP 2.6.3.0 BigPart).

When looking at the other steps. I only find hints to install the BigPart TWRP nothing about the "normal" one:

So when do I've to flash the first "TWRP 2.6.3.0 touch recovery"? :confused:
[Xoom Android Development] drewski_1:
non-BigPart TWRP 2.6.3.0 is Step 0. it needs to be installed before you start the BigPart process.

And you can use the newer 2.7.1.0 BigPart TWRP now. might as well use the newest.
[Xoom Android Development] tnfsmith:
Hi there I following these step as post #1 but Mount in Recovery show that only sdcard and Data checked Cache unchecked.

Is it done successful repartition or not? Can I replace boot image in the next step or must be done checked Cache and Data?

Thanks
[Xoom Android Development] tnfsmith:
Pls I need help here. Thanks:D :good:
[Xoom Android Development] tnfsmith:
Pls I need help

I post help for several day but still no question about my case. I want to make clearly to upload log file recorded my steps in with BigPart problem.

I am between with Bigpart but Cache cannot mount with wipe with error Failed appear and turn back #170 build 4.2.2 but hangout at Motorola logo.

Thanks your for reply and appreciate it much.
[Xoom Android Development] Jeremy537:
I just finished doing the upgrade to BigPart and I had the same issue. I used the latest recovery 2.7.1.0 with support for f2fs and it formatted cache as f2fs instead of ext4. I went into the wipe menu, advanced wipe , select cache, repair or change file system. If the current file system is f2fs, click change file system and select ext4. Once I did that I was able to use cache as normal.

That's what worked for me and now I have CM11 running nicely. Hope this helps!
[Xoom Android Development] fairyshacker:
finally managed to flash it
[Xoom Android Development] Beeko:
So I think I got the BigPart to work, I have the new CM installed with 27gb readable on the PC. But my only problem is that everything is in ext4. I know when you format the data partition it reformats to F2FS but my problem is that once data is in F2FS I can't mount it. Did I miss something or is this normal?
[Xoom Android Development] unonice:
I recommend using BigPart 2.6.3.0.. The one in the first Post of this thread.. That's what I'm using, and no issues with it.. Not upgrading to another version of BigPart or any other Recovery, unless it's needed.. I'm running CM11 4.4.4. Kitkat
[Xoom Android Development] lildanda:
unable to mount data

Hi, i have two Xooms, both are bigparted. I decided to un-Bigpart one but have been unable to check data.

Here is the process i used up to the point where i am stuck...

1. Boot into recovery

2. Flash non Bigpart recovery

Wipe- advanced- delvik, system, cache, data and internal storage

3. Reboot recovery ignoring no OS and SU

5. reboot

6. Ignore password screen ( did not get this)

7. Wipe - advance - wipe system and cache

8. Reboot (ignore no OS and SU)

9. Mount - check sd, cache, data, make sure system is unchecked, check it and uncheck again

That is where i get stuck, data will not check.

Please help

Thanks in advance
[Xoom Android Development] unonice:
[MENTION=4784067]lildanda[/MENTION].. I recommend repeat the process. Start from the beginning and BigPart 2.6.3.0 repartition process.. Link : http://xdaforums.com/showthread.php?t=2506997
[Xoom Android Development] lildanda:
bigpart

Thank you, it took a couple of goes but it worked.
[Xoom Android Development] beston94:
I followed this step by step and somehow I'm stuck at the motorola dual core screen......

I did all the steps then I flashed Eos 4 wingray latest nightly with the bootimage and then gapps...

Any help?

With regards,

Beston94
[Xoom Android Development] unonice:
Start over from the BigPart 2.6.3.0 repartition link I have provided.. Do Not use the "Bootimages".. And make sure you follow directions in order step by step.. Everything will work..
[Xoom Android Development] drewski_1:
By "Eos 4 wingray latest nightly" do you mean Build #205?

205 was borked. iirc, 203 was the last working EOS4 wingray build :)

But why not just go to EOS Revival (Kit Kat) This was build for BigPart so no additional BootImage flash needed.

http://xdaforums.com/showthread.php?t=2770722
[Xoom Android Development] Beeko:
So redid the steps with the 2.6.3 recovery in the OP and I still can mount /data when formatted to f2fs only mounts in ext4.
[Xoom Android Development] unonice:
[MENTION=2340657]Beeko[/MENTION]..at the moment there are not any F2FS support for Xoom kernels that support this file system.

I recommend repeat the process. Start from the beginning and BigPart 2.6.3.0 repartition process.. Link : http://xdaforums.com/showthread.php?t=2506997.. Follow instructions in order, exactly as they are in the link.. You will be successful.. Once you complete the process, go to Play Store and update SuperSU (chainfire)
[Xoom Android Development] lhanna:
No need for a separate BOOT.IMG when returning to stock partitions? Tks.
[Xoom Android Development] reppa:
Hi

sorry if my question seems stupid, can i can't update TWRP, when ever i enter recovery mode and try to update from sdcard, it says "can't mount /sdcard"

am on honeycomd, and i got enought of it;

any help would be really appreciated

thx in advance
[Xoom Android Development] :
bigpart query

I am about to get back a xoom I gave one of my kids. Last with eos 4 I think 170

do not remember if that build needed bigpart?

or if I upgrade to one of newer eos revival builds will I need to bigpart again?
[Xoom Android Development] Alxoom33:
Read, read, read! You have a lot of catching up to do. EOS 444 is awsome! Definitely with the effort[emoji41][emoji106]
[Xoom Android Development] jkd:
Please, i can't install new recovery or new rom ...

I used fastboot, rsd and recovery without issue, but they don't work. Still my old recovery or my old ROM Omni.

i need your help ...
[Xoom Android Development] stephaned:
issue with GAPPS

Managed to install BigPart and CM11 but I seem to have an issue installing GAPPS in the recovery... giving me an error "Error executing updater binary in zip".

Any idea where that could come from? (it feels like it comes from the recovery as the GAPPS zip file is fine)

Tks for your help.

PS: on a side note, I did not install the boot image file as per instruction as when I do, my tablet not longer boot to the system... not sure if the 2 are linked but thought I would mention.
[Xoom Android Development] da-pharoah:
Ihad to switch it up to use cwm bigpart. my xoom would not play well with twrp. try this: http://xdaforums.com/showthread.php?t=2686508

did you try different gapps??
[Xoom Android Development] jkd:
Thanks, i tried it but it don't work.

My recovery is still TWRP v2.6.3.0 :crying:

are there any other idea ?
[Xoom Android Development] da-pharoah:
And I say go back to fastboot and give that a whirl. But try redownloading the specific recovery you want and try that. If that dont work then try regular flashing in recovery, then if that dont work. Then grab the log file from /cache/recovery/last_log and post it here. That should help us underatand what your xoom is doing.
[Xoom Android Development] charos:
I know this sounds strange to most, but how to restore to stock partition??
[Xoom Android Development] chykal:
http://xdaforums.com/showthread.php?t=2669457

I hope this helps.
[Xoom Android Development] jkd:
i tried to flash TWRPv2.8.1.0-Wingray-BigPart.zip, my recovery still the same and my "/cache/recovery" is empty !!

I think i have lost my partition table, are there a way to build a new one ?
[Xoom Android Development] da-pharoah:
My quick thought is to fastboot everything all the way back to honeycomb. Then redo everything.. what makes you think you lost your partition table?
[Xoom Android Development] jkd:
I used fastboot for "MZ604_H.6.2-24_Retail_France" boot.img, recovery.img, system.img and userdata.img but my recovery and my ROM still the same:

- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition)

- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)

- kernel:2.6.39.4-ElementalX-Xoom-2.1+

Lost my partition table !?

i tried adb shell and this command:

root@wingray:/dev/block # fdisk -u -l /dev/block/mmcblk0

fdisk -u -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes

4 heads, 16 sectors/track, 973824 cylinders, total 62324736 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table

root@wingray:/dev/block #
[Xoom Android Development] da-pharoah:
Did you relock your bootloader by chance it sounds like either you relocked it or it some hoe got locked. Try the oem unlock again. Then try everything else
[Xoom Android Development] jkd:
I done it:

D:\LOGICIELS\SDK_tools>fastboot oem unlock

... INFO To continue, follow instructions on the d

evice's display...

OKAY [ 59.421s]

finished. total time: 59.421s

D:\LOGICIELS\SDK_tools>fastboot flash recovery recovery.img

sending 'recovery' (12288 KB)... OKAY [ 1.310s]

writing 'recovery'... OKAY [ 0.686s]

finished. total time: 1.997s

D:\LOGICIELS\SDK_tools>fastboot flash boot boot.img

sending 'boot' (8192 KB)... OKAY [ 1.295s]

writing 'boot'... OKAY [ 0.593s]

finished. total time: 1.888s

D:\LOGICIELS\SDK_tools>fastboot flash system system.img

sending 'system' (262144 KB)... OKAY [ 25.974s]

writing 'system'... OKAY [ 6.427s]

finished. total time: 32.417s

D:\LOGICIELS\SDK_tools>fastboot flash userdata userdata.img

sending 'userdata' (139245 KB)... OKAY [ 13.712s]

writing 'userdata'... OKAY [ 4.290s]

finished. total time: 18.002s

D:\LOGICIELS\SDK_tools>fastboot oem lock

... INFO To continue, follow instructions on the d

evice's display...

OKAY [ 31.824s]

finished. total time: 31.824s

D:\LOGICIELS\SDK_tools>

But no change !!
[Xoom Android Development] da-pharoah:
Why did you relock it? Thats for stock stuff. Keep it unlocked. That could be your problem. I have fastbooted back to honeycomb so many times but ive only ever ran the unlock code once. I have never locked it. Try keeping it unlocked. And redo the steps. Idk if that would make a difference, but its an extra step that doesnt let you change your recoveries I can tell you that much. Thats why you have to unlock it at first.
[Xoom Android Development] Beeko:
So after big parting a while ago, my xoom has now become super slow to the point I can't even use it. I've wiped the data and everything and its still super slow. Any thoughts on what I should do?
[Xoom Android Development] SgtTeabag:
Make sure your running the newest big part Twrp! Format everything except external SD. I do it at least 2-3 times then reboot recovery and start from a fresh build!

---------- Post added at 01:09 AM ---------- Previous post was at 01:07 AM ----------

I'm running the newest cm11 on my mz602 and its never been snappier or more stable!
[Xoom Android Development] TheKicKer69:
Well i loved my Xoom till like a month ago when like u said some games became extremely slow (i OCd it to 1400 for the last 2 years) but i think simply it is becoming really outdated. got me a quad core Lenovo and it is a flying tablet versus a crawling one.

one thing i can say about xoom is that they built back then everything super durable - high end cam, tons of RAM, etc...

maybe about time to change?

cheers,

Roger
[Xoom Android Development] Beeko:
What's the newest TWRP for wingray?
[Xoom Android Development] SgtTeabag:
The newest I think is 2.8.1.0 I'm pretty sure that's the version! Same as the others there's a normal version and one for big part! Make sure you install the big part version! Good luck! :)
[Xoom Android Development] Beeko:
Ok so I updated the recovery, reflashed my ROM and it's still super laggy. Have to press the power button like 5 times before it wakes. Any thoughts? How can I make sure the BigPart is installed correctly?
[Xoom Android Development] SgtTeabag:
Hmmm something is definitely wrong if its super laggy! If Big Part wasn't done right your big part ROM would've read errors and it wouldn't have flashed. What ROM are you using and is it the latest release?
[Xoom Android Development] Beeko:
Yea it is the CM11 build up here. I really don't think the BigPart was successful but it says it is, whats the steps to re-doing it or is it just the same as on the OP.
[Xoom Android Development] SgtTeabag:
Follow the guide again!
[Xoom Android Development] TheMan0790:
So, I am away from home for university and do not have an sd card on me. My XOOM is stock right now, but I am considering going back to KK. Is it possible for me to pull off big part through adb sideload? Sorry for the noob question and if this has already been asked.
[Xoom Android Development] attmakesmevomit:
Clarification

Hoping you all can help to clarify a couple of things for a guy who hasn't messed with his Xoom MZ601 (Everest) in a few years...

1) Step 2 of the Original Post states, "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." I don't see any steps in which I use the original (non-BigPart) TWRP 2.6.3.0... that is just the Recovery I need to be using as the starting point, correct? In other words, I'm remaining on the BigPart version of TWRP, not flashing back to the non-BigPart version after partitioning is complete... right?

2) If I'm understanding correctly, I don't need to flash the BigPart boot image package in Step 9 of the OP if I'm using a ROM that supports BigPart... is that correct? (I'm looking specifically at the Everest EOS 4 build by [MENTION=3900214]runandhide05[/MENTION] here)

Thanks in advance for the help, and all the work you folks do to keep this old tablet ticking...
[Xoom Android Development] realjumy:
That's right. Is enough with a BitPart working recovery and a BigPart compatible ROM. The instructions may look out-of date, but if you consider that the Xoom development is being lower and lower, makes sense to keep them like that, in order to help any other person in the future to figure up how to develop for this tablet. Also, any other other person developing for a different device can understand what was done in order to replicate this work.
[Xoom Android Development] bakuLaw:
i have MZ601 here,

i succesfully follow all steps but in the end,

there's no OS installed and i have all files deleted

how can i big part partition my unit if it doesnt have sd card/slot? {noob ?}

ty.
[Xoom Android Development] moeburn:
The TWRP link in OP's post is dead...
[Xoom Android Development] matt4321:
latest bigpart compatible TWRP is here: https://www.androidfilehost.com/?fid=23991606952607491

use that
[Xoom Android Development] lildanda:
Trouble with 2nd Xoom

Hi, I have two wingrays, one is mine which i manage to Bigpart some time ago , the other belongs to my son who has asked me to do his as well.

I have followed the procedure in the OP & everything seems to be going great until i have to reboot after installing the Bigpart bootl image and rom. The Xoom stops on the Motorola M logo. I have tried a few times yet still with the same end. Can anyone help on this, i cant believe im having trouble with this Xoom compared to my own Xoom.

Thank you
[Xoom Android Development] lildanda:
Sorted my problem of being stuck on the Motorola boot screen.I was flashing the bootloader 1st before the ROM,I swapped those around flashing the bootloader 2nd and it booted up
[Xoom Android Development] Alxoom33:
Good job, but time to consider retiring your Xooms.

A Pixel C is very nice.
[Xoom Android Development] Prack:
Sounds good, you buying me one?
[Xoom Android Development] Alxoom33:
I buy them for all my friends.[emoji6]
[Xoom Android Development] lildanda:
Can I be your friend, I could do with a new tablet lol
[Xoom Android Development] Alxoom33:
Some friend! Lol![emoji6]
[Xoom Android Development] lildanda:
Phew, someone with a sense of humour ?
[Xoom Android Development] Alxoom33:
Might be one of the only ones on XDA.
[Xoom Android Development] vronp:
Hi all,

I wonder if I could please get a bit of guidance.

I've got a wifi only XOOM. I've successfully unlocked the bootloader and I'm ready to take the next steps which I understand is to root the tablet and then perform the BIGPART partition.

I'm following the recommended guide as per this thread. I'd post the link I'm using but I'm not allowed to post links just yet.

Ok, so, here are a number of questions.

1) The instructions indicate that I should root with ClockworkMod Recovery. Is this really a requirement or may/should I root with TWRP? Does it matter?

2) If it's okay to use TWRP, can someone tell me where I can download the appropriate version? Thanks to matt4321, I have downloaded TWRPv2.8.6.0-Wingray-BigPart.zip which I apparently use later in the process. However, it appears I need a "non-bigpart" version of TWRP as well? If so, I am unable to find a matching version number of the "non-bigpart" TWRPv2.8.6.0. Regardless of what I use for root, it appears I need a matching set of TWRP zip files. Am I correct?

Thanks for any help I can get on this.

Dave
[Xoom Android Development] brewer75:
I used TWRP when I did the bigpart on my Xoom a few years ago. Here is the non bigpart TWRPv2.8.0.0 which is also available on the Matt4321 post... https://www.androidfilehost.com/?fid=95784891001604345. Just make sure you follow all the instruction steps carefully.
[Xoom Android Development] vronp:
Hi,

That file is actually v2.8.0.0, at least according to the file name.

Does the version number between BIGPART and non-BIGPART have to match?
[Xoom Android Development] brewer75:
They do not need to be the same version.
[Xoom Android Development] F-302:
Please, give a link to the Stingray-BigPart TWRP, but not to DevHost, because i can't download files from this... site.