yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] mcfisch:
I got root back on my Everest running MyWingray 4.3 with BigPart (I know about losing 3G with that setup, so no posts regarding that please).

Here are the 3 things I needed at the end:

- a new boot image (built that on an Ubuntu server I own by reusing the file init.superuser.rc out of the CM10.1 boot.img and integrating it in Bigrushdogs 4.3 boot image)

- a working supersu (latest official version Chainfire released is currently 1.69)

- busybox (took the CM version from Jazzruby here)

1. Repartition your Xoom by following the 1st post

2. Flash Dreamclwis MyWingray 4.3

3. Flash the attached BusyBox

4. Flash the attached SuperSu

5. Reboot to fastboot mode

6. Flash the boot image from the attached boot_BigPart_3.zip (fastboot flash boot boot_BigPart_3.img)

7. Reboot your system, start SuperSu - if everything worked there should appear no error message ;)

8. If SuperSu doesn't work, go to Play Store, update to latest version and update the binaries then (thx to Drewski_1)

It's a quick'n'dirty patch, I haven't validate the 3 steps again on a virgin install, gone a much more twisty way to get there. I'll wipe and test the procedure again when I have some time later. But there is nothing to harm your Xoom as long as you follow the guides.
[Xoom Android Development] shpitz461:
Did you try to unmount/remount the external card inside TWRP?
[Xoom Android Development] hawkstorm:
Hey Guys,

Are there any windows users who have successfully dumped their partition information? I tried using minimal Adb and fastboot with no luck. Is there a way to do it on the Android terminal emulator?
[Xoom Android Development] drewski_1:
You may need to change your USB mode. I unchecked MTP before adb connected.

Android terminal works too. 'df' command
[Xoom Android Development] ronvanv:
I got one. I will post a copy today.
[Xoom Android Development] illyfilly:
So I just did all the steps and installed MyWingray 4.3 but lost root in the process.

Is that normal? Do I have to root again?

---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------

So I just did all the steps and installed MyWingray 4.3 but lost root in the process.

Is that normal? Do I have to root again?
[Xoom Android Development] rajones19:
It's normal - for the immediate future. See Bigrushdog's post: http://xdaforums.com/showpost.php?p=47540937&postcount=211
[Xoom Android Development] illyfilly:
yeah after reading all the pages saw that, patiently waiting.
[Xoom Android Development] ronvanv:
ok. file finally uploaded: https://www.dropbox.com/s/uvvac4eqkg9col6/EOS-wingray-20130705-205[1].zip?n=47030769

:) I've been using EOS 203 for a long time now. Don't remember if there were any problems with 205.
[Xoom Android Development] grussinko:
I think 203 might have been the last stable version. There were a few later on that wouldn't boot past the Moto logo.
[Xoom Android Development] ronvanv:
I think you're right. I'm getting old or I've been drinking too much lately:D

---------- Post added at 10:55 PM ---------- Previous post was at 10:28 PM ----------

ok here is a link to EOS 203: https://www.dropbox.com/s/xr9jl0jd11jdhx4/EOS-wingray-20130617-203[1].zip
[Xoom Android Development] mcfisch:
root for 4.3

I've found some time to update my previous post with some more details about the procedure for regain root in 4.3 and added another piece of software (BusyBox) you'll need to apply that patch.
[Xoom Android Development] drewski_1:
are you getting any graphical glitches on 4.3? it was mostly in dialog boxes, iirc.
[Xoom Android Development] shpitz461:
Does this apply only to Everest?

---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------

In dialogs, and when I close an app and get back to homescreen. Also, when the tab is docked and the clock appears (daydream) instead of the whole screen going black parts of the homescreen will show (and slowly erased as the clock jumps from one place to another).
[Xoom Android Development] drewski_1:
it looks like the BusyBox flash is the addition needed to the process so it should be device agnostic. his custom Kernel may be Everest specific, but you could probably use the previously posted 4.3 kernel zip (easier too since you can flash it in Recovery vs. exiting to Fastboot to flash it)
[Xoom Android Development] mcfisch:
It applies to all 3 versions. The graphics glitches look weird, but usually don't really block from using.

I've added another note that I used Bigrushdogs 4.3 boot image, so it does NOT contain an Everest kernel, I only added the superuser loading procedure to the init script.
[Xoom Android Development] drewski_1:
I just gave this a try and root didn't stick (said no binary installed) :(

EDIT: I reordered the procedure to:

- Flash ROM

- Reboot to Fastboot & Flash mcfisch's modified Kernel the SU loading procedure

- Reboot to Recovery

- Flash Busybox

- Flash SuperSU

SuperSU wasn't installed when I rebooted. :mad:

Installed from PlayStore and it successfully updated the binaries (new version 1.75) :D
[Xoom Android Development] buffalo_guy:
Thanks!

Appreciate it. Thank you.

http://xdaforums.com/images/icons/icon7.gif
[Xoom Android Development] hawkstorm:
Finally! I got my partition dump thanks to [MENTION=4752026]drewski_1[/MENTION]. [MENTION=697814]realjumy[/MENTION], I think you should add the "df" command for the terminal emulator in the first post as an alternative for those who don't have linux. It literally took 20 seconds using that command.

This is my Partition Data. Not too sure if it's a normal umts_everest build or a HK build.

Model: MZ601 Umts_Everest

Memory: 32GB

ROM: 4.2.2 (AssefMod based on EOS170)

Filesystem	Size	Used	Free	Blksize

/dev	357.6 M	48K	357.6 M	4096

/storage	357.6 M	0K	357.6 M	4096

/storage/emulated	357.6 M	0K	357.6 M	4096

/mnt/secure	357.6 M	0K	357.6 M	4096

/mnt/asec	357.6 M	0K	357.6 M	4096

/mnt/asec/com.ianvink.reader.gpb-1 5M	4M	1M	4096

/mnt/asec/radiotime.plater-2	16M	14.8M	1.2M	4096

/mnt/asec/com.zolmo.twentmm-1 20M	16.8M	3.1M	4096

/mnt/asec/com.eamobile.nbajam_row_wf-1	14M	12.6M	1.4M 4096

/mnt/asec/com.eamobile.nfshp_row_wf-1	18M	16.8M	1.2M 4096

/mnt/asec/net.hubalek.android.apps.reborn.pro-1	11M	9.6M	1.4M	4096

/mnt/asec/deadspace_row-1	11M	9.4M	1.6M	4096

/mnt/touchtype.swiftkey.tablet.full-1	32M	22.4M	9.6M	4096

/mnt/ginlemon.flowerpro-1	4M	2.6M	1.4M	4096

/mnt/obb	357.6 M	0K	357.6M	4096

/system	252 M	230.8M	21.2M 4096

/pds	1.9M	108K	1.8M	2048

/cache	166.3M	4.2M	162.2M	4096

/data	28.4G	13.8G	14.6G 2048

/mnt/shell.emulated 28.4G	13.8G	14.6G 2048

/storage/emulated/0	28.4G	13.8G	14.6G	2048

/storage/emulated/0/Android/obb	28.4G	13.8G	14.6G	2048

/storage/emulated/legacy	28.4G	13.8G	14.6G	2048

/storage/emulated/legacy/Android/obb	28.4G	13.8G	14.6G	2048
[Xoom Android Development] drewski_1:
I may have led you astray. I thought you were just checking the partitions after applying the BigPart mod. It sounds like you're looking for the detailed partition structure to determine if the existing mod should work.

I don't think this output has the detail like the starting block of each partition.

Did you say have ADB on your computer? if so, you can boot into Recovery and then go to your Command Prompt and type

adb shell
dmesg

if you scroll up you will see a section like this

<6>[ 5.288277] mmc1: new high speed SDHC card at address e624
<6>[ 5.288882] mmcblk0: mmc1:e624 SU64G 59.4 GiB
<6>[ 5.310063] mmcblk0: p1
<6>[ 5.397569] mmc2: new high speed MMC card at address 0001
<6>[ 5.398168] mmcblk1: mmc2:0001 SEM32G 29.7 GiB
<4>[ 5.408773] Primary GPT is invalid, using alternate GPT.
<4>[ 5.408870] ebb 0x000000d800 - 0x000000f000 = 6144 (0x0000001800)
<4>[ 5.409024] pdsb 0x000000f000 - 0x0000010000 = 4096 (0x0000001000)
<4>[ 5.409178] misc 0x0000010000 - 0x0000011000 = 4096 (0x0000001000)
<4>[ 5.409266] logo.bin 0x0000011000 - 0x0000013000 = 8192 (0x0000002000)
<4>[ 5.409417] kpanic 0x0000013000 - 0x0000014000 = 4096 (0x0000001000)
<4>[ 5.409567] recovery 0x0000014000 - 0x000001a000 = 24576 (0x0000006000)
<4>[ 5.409655] boot 0x000001a000 - 0x000001e000 = 16384 (0x0000004000)
<4>[ 5.409801] Fixing up system part
<4>[ 5.409885] system 0x000001e000 - 0x000021e000 = 2097152 (0x0000200000)
<4>[ 5.410031] Fixing up cache part
<4>[ 5.410116] cache 0x000021e000 - 0x000031e000 = 1048576 (0x0000100000)
<4>[ 5.410262] Fixing up userdata part
<4>[ 5.410347] userdata 0x000031e000 - 0x0003b6ec00 = 59051008 (0x0003850c00)
<6>[ 5.410495] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10

I think this is the info they need.

i'm not sure if you can get this from the Terminal Emulator
[Xoom Android Development] buffalo_guy:
Got Root on mz604 with Big Partition Dreamcwli 4.3

Thanks!. This got me root access with Dream's 4.3 and Big Partition. Well done! :good:
[Xoom Android Development] hawkstorm:
Ah... I see. I'll try it now. Hopefully it'll take. Cause I've tried using the way outlined in the OP.

---------- Post added at 01:34 PM ---------- Previous post was at 12:58 PM ----------

@drewski_1 I'm using TWRP. How do I access adb from recovery?
[Xoom Android Development] notbrodie:
It just works. adb push/pull and shell work while in recovery
[Xoom Android Development] hawkstorm:
Managed to get it running on both the recovery and adb and also the android terminal emulator. But the information about the partition didn't seem to appear though there was alot of error and fail in mine.

In the android terminal emulator i just used the "su" command instead of /adb shell

---------- Post added at 11:29 PM ---------- Previous post was at 10:39 PM ----------

I hope this information is the correct ones. I found an app on the PlayStore called partition table and was able to extract some partition information from it. I'm attaching the 3 screen caps here. [MENTION=4752026]drewski_1[/MENTION] [MENTION=697814]realjumy[/MENTION] [MENTION=470268]bigrushdog[/MENTION] Does this information help when it comes to determining whether it's a HK version?

Model: MZ601 Umts_Everest

Memory: 32GB

ROM: 4.2.2 (AssefMod based on EOS170)

Kernel: Elemental-X
[Xoom Android Development] matt4321:
I've managed to get a CM10.1 kernel compiled with the patch! I've just tested and it works. I'm going to upload it now for those who want it

---------- Post added at 08:01 PM ---------- Previous post was at 07:42 PM ----------

Here we go!

http://d-h.st/IzQ

For CM10.1, follow instructions in the OP but when getting to the flashing of ROMs, flash CM10.1, then flash this :)

Big thanks to [MENTION=470268]bigrushdog[/MENTION] for helping me out.

[MENTION=697814]realjumy[/MENTION] feel free to add this to the OP so people will be able to find it easily when this post gets lost among the rest
[Xoom Android Development] shpitz461:
That is good stuff, thanks!!

How do you find the GUI experience with 4.2.2? for me on Stingray it was always very sluggish. 4.1 was great and so is 4.3, but 4.2 was always very sluggish.

Also, your zip doesn't include the libs BRD added to his boot images, so I need to just copy them over to your zip? or aren't they necessary?
[Xoom Android Development] matt4321:
I find 4.2 on CM really good, EOS is a little sluggish for me.

I decided they were EOS related files. I removed them and put my CM kernel in and it and flashed. It worked fine. You don't need them
[Xoom Android Development] rchtk:
Not sure why I got credit for the patch as the included patch is entirely the work of Schischu. And mine would need a one liner for strcmp.

Anyway..

Where's this alternate GPT?

I've been dd'ing for an hour and can't find this damn HEADER_SIGNATURE. Supposed to be at LBA-1.

Also why this kernel parameter gpt_sector. I don't see this used in the kernel. And dd'ing on this sector does't show me the signature still.
[Xoom Android Development] Alxoom33:
Has Run'nhide put encryption support in the modified TWRP? :cool:
[Xoom Android Development] uzi2:
It is an amended version of the latest R&H TWRP, so yes and no...
[Xoom Android Development] jasonbtx:
Not able to access sd card through twrp. Can't mount or wipe or format it. Can see card from inside rom. Can all activities be done through adb?
[Xoom Android Development] Alxoom33:
Man, Uzi you have to clarify that one. :what:
[Xoom Android Development] drewski_1:
The RAH version that was modified had encryption support already. Should have carried over to this BigPart version
[Xoom Android Development] shpitz461:
Tried flashing to regain root to no avail.

What worked for me was:

1. ROM (dream's 4.3) was already installed.

2. flashed mcfisch's boot_bigpart_3.img

3. flashed mcfisch's busybox

4. rebooted

5. went to store and installed SuperSU

6. opened SuperSU, it said binary needs updating, and if i would like to flash in recovery, i selected recovery

7. tablet rebooted into TWRP and flashed update.zip

8. rebooted automatically after flashing

9. SuperSU installed and working :)
[Xoom Android Development] pots22:
Normal size

How to return to original partition size ?
[Xoom Android Development] mermigas:
Try to change card. I had the same problem but with a new sdcard all OK
[Xoom Android Development] pots22:
REVERSE

I flash with RSDlight the original ROM Moto to returned to origin. all work perfect

I check the partition size the Tab returned to original size.

But when i flash TWRP and try to reboot on nothing the tab stay on Read fuse1

Finally i flash ClockworkMod Touch Recovery 6.0.2.7 (20130124)

This starting

I Flash my preferred ROM EOS 170

But stay bloqued on the logo EOS turn turn turn

If somebody can help me to return with all like origin

Big thank's for advance
[Xoom Android Development] pots22:
SORRY

I find the problem and now all it's ok

Original partition size

EOS 170
[Xoom Android Development] matt4321:
My CM kernel will work on stingray, wingray and everest with data. For anyone wanting to know, thanks to [MENTION=1643257]mermigas[/MENTION] for testing with his everest
[Xoom Android Development] realjumy:
Hi folks. This has been a busy week for me.

From this afternoon I will work in something to make everything easier, but give me some time. Also, what are the latest versions of EOS4 working for each device? I know that the last stable Everest was 170, but I don't know for the other models.

Keep tuned!

I will update the main post as well :P
[Xoom Android Development] jgardner:
203 was latest stable for Wingray. Thanks for everyones hard work!
[Xoom Android Development] Domunus:
For Stingray i'm using EOS4 197 with the BigPart and everything is working fine.
[Xoom Android Development] bacon612:
Easier to flash cm11? ;)
[Xoom Android Development] Alxoom33:
Is that 4.4 KK?
[Xoom Android Development] bacon612:
Haha. Ya
[Xoom Android Development] IcyAgitator:
Are you saying that you have flashed a cm11 on Xoom? With a modded bigpart kernel? Details please...........
[Xoom Android Development] bacon612:
No. I was joking with realjumy. I wish. Have cm11 working on my HTC rezound. It's quick
[Xoom Android Development] IcyAgitator:
I was gonna say.....share the wealth, lol
[Xoom Android Development] julyaann:
Great job realjumy & bigrushdog!!!:D

Some progress on 4.3????
[Xoom Android Development] rmkenney12:
You guys. Always the compliment right before you ask for more, More, MORE!

:p :laugh:

OK, I'm greedy too - I won't deny it. ;) I would love to see Android 8.3 on my Xoom.

By last week, if possible. What, it's not already on my Xoom?

Devs get hungry and thirsty - to misquote Smoky the Bear, "only YOU can help Android

development: by paying towards the Devs beer and pizza fund!".

I just wish you had a donate button, realjumy.
[Xoom Android Development] Asphyx:
Always put the carrot before the stick! LOL

Here is a request I would have for any Dev who plans on playing with creating a Xoom Rom for 4.3 or 4.4

Since we have no option for a stock rom for 4.3 or 4.4 available for our unit, Can the first release anyone attempts be a straight up stock AOSP with the new BigPart?

I think it might help us root out any STOCK OS issues before we go messing around trying to track down custom bugs?

Just a thought....
[Xoom Android Development] rmkenney12:
Or forgetting to feed that Dancing Bear before whacking it on the nose with a stick... (claw marks?).

Lord only knows what pitfalls an angry dev might have put into that ROM

you just flashed onto your Xoom. :laugh:
[Xoom Android Development] drewski_1:
Dream's 4.3 is a stock AOSP build (with an old Linux 2.6 Kernel)
[Xoom Android Development] Asphyx:
Yes but I'm a Stingray....

I'm sure a lot of folks who have models other that Wingray would like a plain vanilla stock aosp They could keep as a backup to fallback to.

---------- Post added at 11:54 PM ---------- Previous post was at 11:53 PM ----------

LOL not sure feeding really helps in that situation because a bear always has room for dessert! LOL
[Xoom Android Development] Alxoom33:
HELP!

Repartitioned and set up Dream' 4.3 Rom on my Wingray. Lost SUsu /root. Tried to reroot, everything flashed OK except for Mcfish's boot_bigpart_3.Ing.zip says flash railways in red letters! Tried reposing 1.75 SuSu update.zip and flashing. Still don't have working Susu and root. Advice would be appreciated.

PLEASE! :confused:
[Xoom Android Development] uzi2:
1.76 - check the thread

1.65 has also been proven to work with this Rom

I'm sticking with Dream's 4.2 at the moment, which I consider to be the best Rom ever produced to date for this device, so no need yet for a big partition.

Swyped from grouper
[Xoom Android Development] drewski_1:
It's not a flashable zip. His instructions are to flash with fastboot.
[Xoom Android Development] publicanimal:
I'm repartitioned and running dreamcwli's 4.3 with root. Looking forward to breaking off a piece of that Kit Kat!
[Xoom Android Development] uzi2:
Be careful what you wish for. You will lose flash player...

Swyped from grouper
[Xoom Android Development] Alxoom33:
How do you do that? I have always used one click root methods. I don't know how to flash with fastboot, although I know how to Trevor into fastboot... Help please!
[Xoom Android Development] publicanimal:
That's the least of my worries! Almost every site that I visit that used to rely on Flash video now has HTML5 video that is viewable in Chrome. I hate to say it but ultimately Steve Jobs was right about Flash.
[Xoom Android Development] uzi2:
Unfortunately here in the UK the BBC still rely heavily on flash

Swyped from grouper
[Xoom Android Development] shpitz461:
reboot into bootloader, extract boot_bigpart_3.img from within the zip, then do

fastboot flash boot boot_bigpart_3.img
[Xoom Android Development] Alxoom33:
I tried to use RSD light, but it could not read the files. I don't know how to use fastboot or terminal on computer. Is there a way of using terminal emulator or the terminal in TWRP?

Thanks!
[Xoom Android Development] IcyAgitator:
Rsd lite does not flash *.img files. It only uses *. sbf packages for your device.
[Xoom Android Development] drewski_1:
Not sure, but you could try modifying one of the flashable kernel Zips in the OP with the image file (rename to boot.img and replace what's in the Zip)
[Xoom Android Development] shpitz461:
Do this.

1. Boot into android, connect tab to PC

2. in a cmd window do

adb reboot bootloader

3. once you see the bootloader (fastboot) mode shown on the tab, issue the fastboot command

fastboot flash boot boot_bigpart_3.img

4. once the image is flashed successfully, you can issue the following to reboot:

fastboot reboot

Another way to enter bootloader is to do the following:

1. reboot tab

2. after M logo shows up, wait 3 seconds

3. press the down-volume

4. a 1-line menu will appear at the top-left of the screen

5. press vol-down to change menu, vol-up is like 'enter'

6. toggle menu until you get to bootloader then press vol-up

I'm not exactly sure about the wording, but you get the idea...
[Xoom Android Development] realjumy:
Thanks mate. Now it should be fixed.
[Xoom Android Development] LOGMD:
Makes sense to me, if its any help my 32GB wingray US is up in the 3rd post ;)
[Xoom Android Development] bigrushdog:
Ran into a problem. In recovery, "parted" can't read the block. I'm using twrp, but i'm gonna try cw and see if it gives me anything.

Nope. Parted isn't reading anything on cw recovery either
[Xoom Android Development] realjumy:
I will try to figure up later what to do... In thinking about flashing the partitions with the different size instead of using parted...
[Xoom Android Development] jophil2412:
Device: XOOM 32GB MZ604 (wifi only)

Android: 4.1.1

ROM: Codename-Android-3.6.6

Should NOT be the Hong Kong model

Took about 2,5 hours to complete :)

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] nhizzat:
Ready to help, just need instructions for Windows
[Xoom Android Development] rchtk:
Here is the info, would be glad to help further. Took about 3h15 to complete.

Device: XOOM 32GB MZ604 (wifi only)

Android: 4.0.4

ROM: Stock build l.7.1-42

NOT the Hong Kong model

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 643007 524224
P MS Data 643072 989183 346112
P MS Data 989184 62512095 61522912
[Xoom Android Development] realjumy:
I will try to provide a step by step tomorrow, but I need to figure up how to do it under Windows. Today was a busy day...
[Xoom Android Development] realjumy:
Curious... Look to the there is a partition with different ending points...

P MS Data 118784 643063 524280

P MS Data 118784 643007 524224
[Xoom Android Development] nininhocovre:
Model: MZ604 made in China (find nothing about Hong Kong)

ROM: EOS nightly 203

Android 4.2.2

32 GB

Disk mmcblk0.raw - 21 GB / 19 GiB - CHS 2569 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

Process stopped after 1,5 hours, but I don't know if dump is OK because it has 1 partition less then the others posted here.
[Xoom Android Development] drewski_1:
you're missing the data partition. for some reason it only dumped 21 GB
[Xoom Android Development] notbrodie:
does anyone here still have a copy of eos203 they can mirror?

Sent from my Xoom
[Xoom Android Development] burnmatoaka:
I can help you out with that when I get home from work in 9 or 10 hours. PM me if you don't get a copy before then.
[Xoom Android Development] notbrodie:
so i reloaded the factory honeycomb image, then ota'd to 4.1.2. the only changes to the factory image was flashing supersu 1.65 and installing busybox. here are the results:

Disk mmcblk0.raw - 31 GB / 29 GiB - CHS 3880 255 63

Partition Start End Size in sectors

P MS Data 47104 51199 4096

P MS Data 61440 65535 4096

P MS Data 122880 614399 491520

P MS Data 647168 993279 346112

P MS Data 993280 62319583 61326304
[Xoom Android Development] Geeba:
Happy to help.... but again I'm a windows man :( - I can put together a Ubuntu machine but I'm not really that good a driving it....

Just curious would the partition tool used for the HD2 be of any help? really easy to use...

http://xdaforums.com/showthread.php?t=1090783
[Xoom Android Development] realjumy:
I will take a look to that.

I'm still figuring up how to do the process under Windows...
[Xoom Android Development] realjumy:
Can you do it using fastboot?
[Xoom Android Development] bigrushdog:
Negative. Parted is a binary installed in recovery. I'm going to revisit the symlink solution. I'm really iffy here if we can't access the partition table.
[Xoom Android Development] realjumy:
Can we download the image of the Xoom, modify the partitions size and then flash it back to the device?
[Xoom Android Development] realjumy:
By the way, Windows users, any of you is expert enough to test if netcat (nc) from http://joncraton.org/blog/46/ and testdisk from http://www.cgsecurity.org/wiki/TestDisk_Download can be used to do this tutorial under Windows?