BigPart Repartition Upgrade and Resource Center

Search This thread
By:
Advanced…
realjumy

realjumy

Senior Member
Nov 18, 2007
631
332
Hello everyone.

You should know that time ago Motorola decided to stop updating our Xoom, but we showed (and we are still showing) them that our tablet is still alive and kicking.

Let me update this with the last news (a big win, indeed) from @bigrushdog:

IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, your cow starts to give bitter milk or if it unchains a thermonuclear war.

bigrushdog said:
BigPart Repartition Upgrade and Resource Center


Credits

Much love, credit, and respect go out to @Schischu and @rchtk! 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 @runandhide05, 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


CM10.1 BigPart Kernel by @matt4321
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 thi


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
Click to expand...
Click to collapse

Q&A

Q: OK to understand this right, now we have a new recovery and boot. Which ROM do we use? The same as before? And BigPart @dreamcwli MyWingray 4.3 is only for wingray?

A: Yes, we have new recovery and boot. For this recovery and boot you need to use the new BigPart roms. If you are not using BigPart roms, you will need to install old recovery and boot and format everything again. And yes, it seems like @dreamcwli MyWingray 4.3 is only for wingray at the moment, but brd published a version of the last EOS4 stable with the new kernel working for BigPart.

Q: 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)

A: You can use the GApps that you prefer. Now we have space enough, but scaled down versions might be slightly faster as it uses less resources (I guess).

Q: 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?

A: I think that that is something to implement in the kernel. I think that it is easy to do and our bakers eventually will implement it.

Q: Can cm10.2 be flashed instead of an eos4 rom after the repartition?

A: You need to replace BOOT.img in the CM zip with the BigPart compatible with your Xoom, and if the kernel is compatible with CM it will work.

Q: I'm on stingray_cdma.....unless i can flash a wingray rom and boot.img after the repart?

A: No idea, but it's safer to use roms build for your device. Take a look to the previous question.

Q: 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

A: brd published some EOS4 working with BigPart (see http://xdaforums.com/showpost.php?p=47005701&postcount=1 )

Q: 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 @dreamcwli 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?

A: Use only BigPart roms. You will need to change the boot.img from the rom if the rom is not compatible with BigParts, but if the rom is not compatible with the new kernel, it is useless... MyWingray is compatible with Everest but you will not have 3G, I guess... But I'm not sure.

Q: That's great. @bigrushdog @realjumy Is there a way to get the radios for everest and stingray on a separate zip?

A: The rom must be cooked with the radios...

Q: 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

A: No idea.

Q: 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?

A: Something something went wrong... Copy the data from the SD to your PC, format SD and put back data. Let's see if that works...

Q: 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.

A: Only roms with BigPart in their name can be used with the new layout.

Q: 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?

A: Not all the roms are compatibles with the boot.img method (kernel method). You will need to try to be sure. EOS4 and Dream's have proper versions. If you want to use, for example, CM you will need to:

option 1.- Build it yourself patching the kernel

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

option 3.- Ask to the CM maintainer to release BigPartition versions.


There is a lot of 4.2.2 projects running, some 4.3 and if we are successful, MAYBE we will be able to port 4.4 to our devices. One of the main problems (but not the only one) is the internal storage structure of the tablet. It seems that is not too hard to solve, as in other devices (mainly Samsung) is common to change it.

The aim of this project is to compare how the internal partitions are setted up in order to change them and have more room for system and apps. This will improve all the ROMS (4.1, 4.2.*, 4.4). @bigrushdog is doing a big effort to change it but we need more data from all models to compare and be sure that we don't break anything.

It will take up to 3 hours (depends on the model) but is something that can work while you are sleeping or not using the tablet. With the data provided by you, we can compare and choose the best changes.

IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.

IMPORTANT: It should be harmless for your PC, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your PC bricks, dies, gets cursed, loses the data, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.

What are you going to do:
You are going to do a 1:1 copy of your internal storage into your PC. Then, we will detect the partitions and where begins and ends each one. Nothing else. We will compare the different versions and in the future a tool will be released to make the changes.

What you will need:

  • Linux (maybe you can use a Live DVD / USB?). It should be a way to do this process under Windows. If you know how to do it, please, share the info.
  • 33GB of disk space in your computer, anywhere.
  • Android SDK working (that means that if you plug your tablet turned on and run
    Code: 
    ./adb devices
    in the folder "platform-tools" of your SDK will provide a serial number): http://developer.android.com/sdk/index.html
  • 3 hours (can be done while sleeping, not using the tablet, etc) if you have a 32GB Xoom.
  • Rooted Xoom.

Before you begin:

  • DO A NANDROID BACKUP!!!!!
  • READ EVERYTHING AND ASK IF YOU DON'T UNDERSTAND SOMETHING


Step by step:

  1. Full charge your tablet (or keep it connected to AC?) and turn it on WITHOUT SDCARD.
  2. If your Android SDK is not installed or working properly, fix it now: http://developer.android.com/sdk/index.html
  3. Install the dependencies. For Ubuntu / LinuxMint / Debian:
    Code: 
    apt-get install testdisk netcat pv extundelete testdisk
  4. Activate USB Debug on your device (in order to connect with adb). You can find it under Settings > Developer options.
    Note: On Android 4.2 and newer, Developer options is hidden by default. To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options.
    Click to expand...
    Click to collapse
  5. Plug your tablet (it must be on) and run
    Code: 
    ./adb devices
    in the folder "platform-tools" of your SDK. If you don't get as a result a serial number, STOP. Something is wrong with your SDK. Please, fix it to continue.
  6. Open a terminal on your computer, go to the Android SDK directory's subdirectory sdk/platform-tools (where adb is located).
  7. We will setup a forward port to be able to download the data to our PC:
    Code: 
    ./adb forward tcp:5555 tcp:5555
  8. Now we will connect to the tablet
    Code: 
    ./adb shell
  9. Maybe you need to grant permission to do it. Take a look to your tablet's screen.
  10. We become superuser:
    Code: 
    su
    Grant permanent permissions when asked. You can revoke the permissions later if you want.
  11. With this we will transfer the data to the port that we set previously:
    Code: 
    /system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
  12. DON'T CLOSE THAT TERMINAL. An now OPEN A NEW ONE IN THE PC.
  13. Go again to the folder "platform-tools" of your SDK and let's collect the data:
    Code: 
    ./adb forward tcp:5555 tcp:5555
    Code: 
    nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
    If you want to save the file in a different place/partition, change what is after ">". For example, if I want to save the file in my home folder, I will write /home/jumy/mmcblk0.raw. If you are not sure or don't know how to do it, don't change it.
  14. You will to wait up to 3 hours until it finish.
  15. When the transfer is finished, run this in the folder where the dump is located (if you changed nothing, it is located in the older "platform-tools" of your SDK):
    Code: 
    testdisk mmcblk0.raw
  16. First restore the GPT partition table. Select mmcblk0.raw in the TestDisk interface and choose Proceed.
  17. Choose EFI GPT.
  18. Then select Analyse.
  19. Choose Quick Search.
  20. The search will return a table that you should copy and paste in this thread.
  21. Now you can exit and remove the dumped file (mmcblk0.raw).

Please, when you provide the data, tell us which model, storage size, ROM name and version and indicate if it is the Hong Kong model.

Info collected from http://www.df.lth.se/~jokke/androidfilerecovery/ --> Visit it if you want some screenshots.
 
Last edited:
  • Like
Reactions: Kovaelin, Chris2714, israelnobrega and 79 others
realjumy

realjumy

Senior Member
Nov 18, 2007
631
332
Everest, 32GB, using EOS4 V170, NOT Hong Kong model.

Code: 
     Partition               Start        End    Size in sectors
>P MS Data                    47104      51199       4096
 P MS Data                    61440      65535       4096
 P MS Data                   122880     647159     524280
 P MS Data                   647168     993279     346112
 P MS Data                   993280   62319583   61326304
 
  • Like
Reactions: MReinke, parkentosh, m-khalaf and 2 others
LOGMD

LOGMD

Senior Member
Jun 22, 2010
495
275
London
Ill Help!

Testing in progress... =]

Device: XOOM 32GB Wingray MZ604
Android: 4.2.2
ROM: EOS4 Nightly 203

EDIT: i did my bloody SD card... did it again and now heres the internal 32GB

Code: 
Disk mmcblk0_1.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     647159     524280
 P MS Data                   647168     993279     346112
 P MS Data                   993280   62319583   61326304
 
Last edited:
  • Like
Reactions: Peterpaulmarie
realjumy

realjumy

Senior Member
Nov 18, 2007
631
332
djripster said:
I would really love to test Android 4.4 on my Xoom... The new platform seems to be much faster and my Xoom feels very slow and clumpy on Android 4.2 and even 4.1
Click to expand...
Click to collapse

4.4 will have the same problem that 4.2.* and 4.3 as it is a problem with the storage. That is the reason why we need so badly to change the partitions, and that is why we are asking for help to collect this data.
 
bigrushdog

bigrushdog

Inactive Recognized Developer
Apr 23, 2007
3,547
7,244
I derped my development laptop so I was down a few days. I think we have what we need for a repartition script. As some of you know kitkat source dropped. Under the hood, not much changed. At least from what I hear. So I'll slap together a theoretical repartition script. Any volunteers?
 
  • Like
Reactions: latinmaxima, m-khalaf, DriVAnce and 5 others
N

notbrodie

Senior Member
Sep 12, 2012
1,858
718
Portland
realjumy said:
That's great!!!!
Click to expand...
Click to collapse

Disk mmcblk0.raw - 1967 MB / 1875 MiB - CHS 240 255 63
Partition Start End Size in sectors
>P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 1860958 1862168 1211 [\^I]

Xoom WiFi 32GB EOS-203, Not Hong Kong.

also: 3 hours... lol. it took 18 minutes

---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------

bigrushdog said:
I derped my development laptop so I was down a few days. I think we have what we need for a repartition script. As some of you know kitkat source dropped. Under the hood, not much changed. At least from what I hear. So I'll slap together a theoretical repartition script. Any volunteers?
Click to expand...
Click to collapse

Count me in! i've got a nandroid on my external sdcard, though I'm not sure what good that'll do if the repartitioning fails...

---------- Post added at 08:18 PM ---------- Previous post was at 08:09 PM ----------

about to load 4.4 on my N4... let's see if this super-hyped new android is really that much different/better than 4.3!
 
  • Like
Reactions: realjumy
D

DaniLoveSky

Senior Member
Nov 2, 2006
111
15
Newcastle upon Tyne
Xiaomi Poco F2 Pro (Redmi K30 Pro)
Model: MZ604 (wifi-only)
Storage size: 32GB
ROM: EOS Stable release 3.0
NOT Hong Kong model
testdisk output:
Code: 
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

Took a bit more than 3 hours...

notbrodie, there may be something wrong in your experiment as the dump file is only around 2GB. Or maybe you just have non-standard partitioning, I am not sure...

PS: Small correction to the instructions (just to make it perfect):
- closing code tag seems to be lost in ./adb shell command
- A typo in "If you want to save the fine"
 
Last edited:
  • Like
Reactions: LOGMD and realjumy
realjumy

realjumy

Senior Member
Nov 18, 2007
631
332
DaniLoveSky said:
Model: MZ604 (wifi-only)
Storage size: 32GB
ROM: EOS Stable release 3.0
NOT Hong Kong model
testdisk output:
Code: 
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

Took a bit more than 3 hours...

notbrodie, there may be something wrong in your experiment as the dump file is only around 2GB. Or maybe you just have non-standard partitioning, I am not sure...

PS: Small correction to the instructions (just to make it perfect):
- closing code tag seems to be lost in ./adb shell command
- A typo in "If you want to save the fine"
Click to expand...
Click to collapse

Thanks mate. I will correct the post later from the PC.

Sent from my Nexus 4 using Tapatalk
 
bigrushdog

bigrushdog

Inactive Recognized Developer
Apr 23, 2007
3,547
7,244
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
 
Last edited:
  • Like
Reactions: realjumy
LOGMD

LOGMD

Senior Member
Jun 22, 2010
495
275
London
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
 
LOGMD

LOGMD

Senior Member
Jun 22, 2010
495
275
London
bigrushdog said:
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
Click to expand...
Click to collapse

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?
 
realjumy

realjumy

Senior Member
Nov 18, 2007
631
332
LOGMD said:
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?
Click to expand...
Click to collapse

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).

Sent from my Nexus 4 using Tapatalk
 
  • Like
Reactions: LOGMD
You must log in or register to reply here.

Similar threads

S
[ROM][4.4.4] OmniROM - Wingray - bigPart
Replies
1K
Views
554K
T
The_Nitro
solarnz
[Root] Universal Xoom Root - ANY XOOM ANY UPDATE
Replies
460
Views
495K
D
Diagon
bigrushdog
[KERNEL][AOSP]Tiamat Xoom 2.0.0 "Katana" [Update: 07/14]
Replies
3K
Views
636K
solarnz
solarnz
S
[ROM][4.4.4] CyanogenMod 11.0 - Wingray Stingray Everest - bigPart
Replies
974
Views
450K
hockeymikey
hockeymikey
S
[ROM][5.1.1] OmniROM - Wingray - bigPart - ALPHA
Replies
556
Views
362K
Alxoom33
Alxoom33

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 82
    realjumy
    realjumy
    Hello everyone.

    You should know that time ago Motorola decided to stop updating our Xoom, but we showed (and we are still showing) them that our tablet is still alive and kicking.

    Let me update this with the last news (a big win, indeed) from @bigrushdog:

    IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, your cow starts to give bitter milk or if it unchains a thermonuclear war.

    bigrushdog said:
    BigPart Repartition Upgrade and Resource Center


    Credits

    Much love, credit, and respect go out to @Schischu and @rchtk! 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 @runandhide05, 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


    CM10.1 BigPart Kernel by @matt4321
    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 thi


    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
    Click to expand...
    Click to collapse

    Q&A

    Q: OK to understand this right, now we have a new recovery and boot. Which ROM do we use? The same as before? And BigPart @dreamcwli MyWingray 4.3 is only for wingray?

    A: Yes, we have new recovery and boot. For this recovery and boot you need to use the new BigPart roms. If you are not using BigPart roms, you will need to install old recovery and boot and format everything again. And yes, it seems like @dreamcwli MyWingray 4.3 is only for wingray at the moment, but brd published a version of the last EOS4 stable with the new kernel working for BigPart.

    Q: 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)

    A: You can use the GApps that you prefer. Now we have space enough, but scaled down versions might be slightly faster as it uses less resources (I guess).

    Q: 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?

    A: I think that that is something to implement in the kernel. I think that it is easy to do and our bakers eventually will implement it.

    Q: Can cm10.2 be flashed instead of an eos4 rom after the repartition?

    A: You need to replace BOOT.img in the CM zip with the BigPart compatible with your Xoom, and if the kernel is compatible with CM it will work.

    Q: I'm on stingray_cdma.....unless i can flash a wingray rom and boot.img after the repart?

    A: No idea, but it's safer to use roms build for your device. Take a look to the previous question.

    Q: 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

    A: brd published some EOS4 working with BigPart (see http://xdaforums.com/showpost.php?p=47005701&postcount=1 )

    Q: 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 @dreamcwli 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?

    A: Use only BigPart roms. You will need to change the boot.img from the rom if the rom is not compatible with BigParts, but if the rom is not compatible with the new kernel, it is useless... MyWingray is compatible with Everest but you will not have 3G, I guess... But I'm not sure.

    Q: That's great. @bigrushdog @realjumy Is there a way to get the radios for everest and stingray on a separate zip?

    A: The rom must be cooked with the radios...

    Q: 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

    A: No idea.

    Q: 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?

    A: Something something went wrong... Copy the data from the SD to your PC, format SD and put back data. Let's see if that works...

    Q: 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.

    A: Only roms with BigPart in their name can be used with the new layout.

    Q: 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?

    A: Not all the roms are compatibles with the boot.img method (kernel method). You will need to try to be sure. EOS4 and Dream's have proper versions. If you want to use, for example, CM you will need to:

    option 1.- Build it yourself patching the kernel

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

    option 3.- Ask to the CM maintainer to release BigPartition versions.


    There is a lot of 4.2.2 projects running, some 4.3 and if we are successful, MAYBE we will be able to port 4.4 to our devices. One of the main problems (but not the only one) is the internal storage structure of the tablet. It seems that is not too hard to solve, as in other devices (mainly Samsung) is common to change it.

    The aim of this project is to compare how the internal partitions are setted up in order to change them and have more room for system and apps. This will improve all the ROMS (4.1, 4.2.*, 4.4). @bigrushdog is doing a big effort to change it but we need more data from all models to compare and be sure that we don't break anything.

    It will take up to 3 hours (depends on the model) but is something that can work while you are sleeping or not using the tablet. With the data provided by you, we can compare and choose the best changes.

    IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.

    IMPORTANT: It should be harmless for your PC, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your PC bricks, dies, gets cursed, loses the data, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.

    What are you going to do:
    You are going to do a 1:1 copy of your internal storage into your PC. Then, we will detect the partitions and where begins and ends each one. Nothing else. We will compare the different versions and in the future a tool will be released to make the changes.

    What you will need:

    • Linux (maybe you can use a Live DVD / USB?). It should be a way to do this process under Windows. If you know how to do it, please, share the info.
    • 33GB of disk space in your computer, anywhere.
    • Android SDK working (that means that if you plug your tablet turned on and run
      Code: 
      ./adb devices
      in the folder "platform-tools" of your SDK will provide a serial number): http://developer.android.com/sdk/index.html
    • 3 hours (can be done while sleeping, not using the tablet, etc) if you have a 32GB Xoom.
    • Rooted Xoom.

    Before you begin:

    • DO A NANDROID BACKUP!!!!!
    • READ EVERYTHING AND ASK IF YOU DON'T UNDERSTAND SOMETHING


    Step by step:

    1. Full charge your tablet (or keep it connected to AC?) and turn it on WITHOUT SDCARD.
    2. If your Android SDK is not installed or working properly, fix it now: http://developer.android.com/sdk/index.html
    3. Install the dependencies. For Ubuntu / LinuxMint / Debian:
      Code: 
      apt-get install testdisk netcat pv extundelete testdisk
    4. Activate USB Debug on your device (in order to connect with adb). You can find it under Settings > Developer options.
      Note: On Android 4.2 and newer, Developer options is hidden by default. To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options.
      Click to expand...
      Click to collapse
    5. Plug your tablet (it must be on) and run
      Code: 
      ./adb devices
      in the folder "platform-tools" of your SDK. If you don't get as a result a serial number, STOP. Something is wrong with your SDK. Please, fix it to continue.
    6. Open a terminal on your computer, go to the Android SDK directory's subdirectory sdk/platform-tools (where adb is located).
    7. We will setup a forward port to be able to download the data to our PC:
      Code: 
      ./adb forward tcp:5555 tcp:5555
    8. Now we will connect to the tablet
      Code: 
      ./adb shell
    9. Maybe you need to grant permission to do it. Take a look to your tablet's screen.
    10. We become superuser:
      Code: 
      su
      Grant permanent permissions when asked. You can revoke the permissions later if you want.
    11. With this we will transfer the data to the port that we set previously:
      Code: 
      /system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
    12. DON'T CLOSE THAT TERMINAL. An now OPEN A NEW ONE IN THE PC.
    13. Go again to the folder "platform-tools" of your SDK and let's collect the data:
      Code: 
      ./adb forward tcp:5555 tcp:5555
      Code: 
      nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
      If you want to save the file in a different place/partition, change what is after ">". For example, if I want to save the file in my home folder, I will write /home/jumy/mmcblk0.raw. If you are not sure or don't know how to do it, don't change it.
    14. You will to wait up to 3 hours until it finish.
    15. When the transfer is finished, run this in the folder where the dump is located (if you changed nothing, it is located in the older "platform-tools" of your SDK):
      Code: 
      testdisk mmcblk0.raw
    16. First restore the GPT partition table. Select mmcblk0.raw in the TestDisk interface and choose Proceed.
    17. Choose EFI GPT.
    18. Then select Analyse.
    19. Choose Quick Search.
    20. The search will return a table that you should copy and paste in this thread.
    21. Now you can exit and remove the dumped file (mmcblk0.raw).

    Please, when you provide the data, tell us which model, storage size, ROM name and version and indicate if it is the Hong Kong model.

    Info collected from http://www.df.lth.se/~jokke/androidfilerecovery/ --> Visit it if you want some screenshots.
    View
    27
    bigrushdog
    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.
    View
    24
    bigrushdog
    bigrushdog
    BigPart Repartition Upgrade and Resource Center


    Credits

    Much love, credit, and respect go out to @Schischu and @rchtk! 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 @runandhide05, 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
    View
    20
    S
    Schischu
    Recovery with bigPart
    http://duckbox.info/files/xoom/R.A.H._TWRPv2.6.3_bigPart.img.zip
    Android 4.1.2 with bigPart
    http://duckbox.info/files/xoom/wingray_bigPart.zip

    Flash R.A.H._TWRPv2.6.3_bigPart.img through fastboot.
    Flash wingray_bigPart.zip through recovery, dont reboot.
    Wipe Dalvik Cache Cache Data.
    Reboot System.

    After System startet, check adb shell -> df to confirm new partition layout.

    Please note: I only build this for wingray (NOT HK). This is a very very basic android, aosp without any modifications beside the kernel. (See patch above)

    And just to be clear again. YOU WILL LOSE EVERYTHING ON YOUR XOOM BY CHANGING THE PARTITON FORMAT. SO BACKUP BEFORE.

    And again. ONLY WINGRAY.

    Now the 4.3 and 4.4 images can come. ;)
    View
    18
    bigrushdog
    bigrushdog
    Just wanted to give an update on the status of affairs. 4.3 is done, finished, and cfx 4.3 will never run on Xoom. The reasons are complex. Just trust me on that. As I write, synergy is building our 4.4 master branch manifest. We ate taking a different approach to some things this time. There is no reason to believe I can't have a build soon after the project basics are proper. I do know this. Devices newer than xoom are having some graphics issues. Our kernel is a dinosaur. All that being the case, I'll be curious to see how things go. There will come a point where it will be time to retire the xoom. And that time is soon now. When or if I make thataassessment, I will return my loaner xoom to its owner and encourage people to upgrade. Just the scoop...
    View

New posts