Develop Bugs

[Dev] *obsolete* Xperia S Boot Manager v0.1 (devs only for now)

Hello Guys,
Here is my last toy, it's a dual boot system for the xperia S:
It lets you start two different kernels with their associated cpio with a third kernel that handles the boot menu and embeds cwm. It works with any kernel, this is not kexec based. As a demo in the video, I have stock firmware on regular partitions on one and cm9 on the other one with loopbacks on internal storage. I'll experiment later on with partitioning to see if we could have two sets of native partitions to make it more comfortable.
As it it's, it's quite rough, but if anyone has interest in it I will release it as it is and try to improve usability.
This is for devs and advanced users only, you would have to fiddle a lot to get the second build to run, you need an arm toolchain to embed both kernels and you have to modify its cpio.
I'm working on tools to flash kernels directly on device, but they're not ready yet. And ideally, CWM would need to be extended to support two environments. Don't expect quick progress, I don't have much free time to work on this.
Here are some details on how it works:
I trimmed down a stock kernel to remove some fat and add a driver to set a specific memory location.
I embed a small assembly loader with this kernel and its cpio plus the other 2.
The tiny kernel is loaded first, it displays the menu and eventually starts cwm. The menu will set the memory location with the kernel choice, then reboot.
At next reboot, the assembly loader will detect the kernel choice and start the appropriate kernel.
So, in fact, you're booting two times, first the small loader, then the real boot.
It adds some boot time, but it's not dramatic. The advantage is that it's easy to build the loader, it's a simple init. Second advantage, the second kernel is running on a "fresh" start, no left-over in memory, no kexec patch to apply, it works with any kernel. Last, cwm can be embedded with the tiny kernel, so it's finally independent from the build kernel.
First a disclaimer: I'm not responsible if you fry your phone using this, it's very experimental and I'm not 100% sure running a build on loopback won't reduce internal flash lifetime. I don't expect problem, but proceed with caution!
* Updates *
2012-09-07: Trimmed kernel uploaded to gitorious here , branch bootloader_kernel, boot menu (FBMenu, thanks to openAOS for initial release!) source added here.
2012-09-06, more details here :
1) on-device kernel flasher attached (kf_v0.1.zip). It let you flash kernel 1 or kernel 2 directly from device (adb from recovery for instance). You must have previously flashed dual.elf in fastboot!
And again, all of this is highly experimental! Be careful.
syntax:
kf [1|2] kernel_zimage_file cpio_file
Source code at: https://gitorious.org/sony-tools/dual_loader_kf
2) Loader source code uploaded to: https://gitorious.org/sony-tools/sony-tools, in dual directory.
2012-09-04:
If you have a 6.1.A.2.45 stock firmware, you can try the setup displayed in the video:
Download package here (mirror) and extract it on your PC.
Copy the 3 ext4 files at the root of the phone internal storage.
Reboot in fastboot mode
Flash dual.elf in fastboot mode with "fastboot flash boot dual.elf".
Reboot with "fastboot reboot"
You should now have the boot menu at each phone start. If you want to get rid of it, just reflash your original firmware kernel.
Note:
- I'm not sure cwm is working completely properly, I barely tested it.
- it may work with another stock firmware version, but the embedded stock kernel is 6.1.A.2.45 one, I'm not sure how it behaves on other builds.
Don't hesitate to give feedback here!
LeTama

wow, this is very very nice, now we can have the best of stock and cm9, thanks for all your hard work, im sure this is going to go far in the xperia s development community

Thats Realschule great when You allow i will try to implement twrp 2 at an later Version just as an Experiment
Sent from my LT26i using xda premium

This is awesome
Great job
Take as much as u want , this is so promicing

ok so my two cents : -
1. we should NOT flash kernel every time we need to boot into other OS (too much flashing = bad blocks)
2. thus I suggest we need to maintain the same kernel tree for both stock and cm/aosp/aokp kernel. the zImage will be same, but ramdisk will be different ....
3. how will that help ? we will keep a minimalistic ramdisk (containing only bootmanager) on the original kernel.elf. the stock and aosp ramdisk can reside as stock_ramdisk.gz and aosp_ramdisk.gz either inside the ramdisk (if it has space) or inside /system/dual_boot/ and the required ramdisk will be inflated/deflated on the fly as per usage requires something like
Code:
rm -f -r /sys
rm -f -r tmp
rm -f -r etc
tar -xf ./stock_ramdisk.gz
for referrence see how CWM runs using chargemon script on locked bootloader
4. we will need our own custom CWM/whatever-recovery-we-want-to-use that shall allow us to flash system1 and system2, data1 and data2, like that....
5. for optimum results i want to suggest to use current system partition as system1 and current data partition as system2, both data partition can be kept as loop devices on the internal sdcard. that will be best for space as well as speed. using any other combination we will have to sacrifice either on speed or on space.
now these are my opinions, and I'll sit down an speak with OP after my exams are over on 17th Sept. I am very much interested on this idea, because it's a win-win situation. People get to use custom firmware alongside stock and devs get more users for their ROMs because there is no risk of non-working hardware as we always have stock on the other partition

Thanks for your reply championswimmer.
I wasn't clear enough in my message I guess, so to clarify: I'm not flashing kernel each time I boot, the three kernels are flashed once and everything happens in memory. I'm using the whole 20 MB space to fit the three kernels, and my assembly loader jumps in memory to the desired kernel.
Your idea of having a single kernel for all is nice, but afaik, cm differs in kernel from stock, this is not a problem of ramdisk only.
Regarding partition scheme, well, I have no opinion yet, I'd prefer avoid loopbacks if I can repartition, but I'm not sure bootloader will let me do it. If repartition is possible, cwmod handling should be easy and only a matter of launching it while swapping on two recovery.fstab.

Noob question , so it's a kernel that hot boot another ?

Forzaferrarileo said:
Noob question , so it's a kernel that hot boot another ?
Click to expand...
Click to collapse
Not really, the first kernel+cpio is here mostly to handle the boot menu. After selection is made, the phone reboots and a small assembly loader starts the final kernel.

I added my current setup if anyone want to test it, see bottom of first post.

letama said:
Thanks for your reply championswimmer.
I wasn't clear enough in my message I guess, so to clarify: I'm not flashing kernel each time I boot, the three kernels are flashed once and everything happens in memory. I'm using the whole 20 MB space to fit the three kernels, and my assembly loader jumps in memory to the desired kernel.
Your idea of having a single kernel for all is nice, but afaik, cm differs in kernel from stock, this is not a problem of ramdisk only.
Regarding partition scheme, well, I have no opinion yet, I'd prefer avoid loopbacks if I can repartition, but I'm not sure bootloader will let me do it. If repartition is possible, cwmod handling should be easy and only a matter of launching it while swapping on two recovery.fstab.
Click to expand...
Click to collapse
Got it
Makes more sense
Great job
About repartition... We do have a lot of space in system to partiton into system1 and system2 say....
But splitting data is not good idea
Some people keep.big.games on data which need lot of space
Lets see what happens
Will check your current scheme tomorrow
Really like your memory base shifting concept... Pretty neat
Instead of 3 we can still make do with 2 kernels and 3 ramdisk.
We can keep the first kernel for both stock rom as well as the for.bootmanager
Sent from my LT26i using xda app-developers app

Regarding repartition, my idea was to take space from internal storage, no from data and/or system. We'll see... I hope I won't fry my brand new toy
Regarding having two kernels, well, yes, it's possible, but it would mean that one of them is modified to support the driver I use. It would defeats the benefit of running any untouched kernels as it is now. My modified kernel is only 2MB, it's not such a big toll on the whole 20 MB.

You could get in touch with FXP, doomlord, and binary... They are brains of xperia.
together you can make it more stable, improve it and make it amAzing
Glad to hear this news, i would never sell my phone (AOSP, sony stock rom, cyanogenmod 10)
Sent from my LT26i

All works fine , but a little question , can you share source to allow everyone to integrate the kernel that anyone want ( until dualboot compatible recovery will finished)
P.S. +1 for stylish purple led color

WooooooooW amazing :laugh:
waiting for noobs version

What a great job!
wowwwww!!!!!! just brilliant!!!!!!!!!!!!!
it looks like the magldr for hd2, which enables a multi-boot!~:good::good::good::good:

Forzaferrarileo said:
All works fine , but a little question , can you share source to allow everyone to integrate the kernel that anyone want ( until dualboot compatible recovery will finished)
P.S. +1 for stylish purple led color
Click to expand...
Click to collapse
Sure, will do. I need to cleanup the mess a bit before, but it will come soon.
The purple led is from cm9 recovery, can't take credit for that

Nice work. Maybe we should use LVM for partitions? It doesn't seem like the bootloader will let us write a new partition table.

Awesome work dude !! +1 for the effort :victory:
You guys make our phone more and more lovely !!
Keep up the great work !!
I hadn't but now unlocking my bootloader for this !!
As I am on stock .45 i will try experimenting this and give you the feedback :fingers-crossed:

isn't it a bad idea to keep the data partition the same for both say cm and stock, i had conflicts with cm without wiping data?
Sent with my Sony Xperia S using a little bit of KA magic.

K900 said:
Nice work. Maybe we should use LVM for partitions? It doesn't seem like the bootloader will let us write a new partition table.
Click to expand...
Click to collapse
Well, I just tested repartitionning, it's possible:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 31162368 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 512 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 5120 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 1048576 mmcblk0p12
179 13 256000 mmcblk0p13
179 14 2097152 mmcblk0p14
179 15 25272312 mmcblk0p15
179 16 512024 mmcblk0p16
179 17 256024 mmcblk0p17
179 18 1023928 mmcblk0p18
Now, is it reasonable to release how, that's another debate I'm not sure yet... There is definitely a risk of permanent brick with this.

XOOM2/Xyboard BOOTSTRAP 11-16-12

This is a custom recovery, based off the Bootstrap recovery method originally from Koush
ALPHA!!!!
A Big thanks goes to the guys who have help test this, nchantmnt, taquion12, HussX, without them this would not have been possible (because I myself don’t own a xoom2/xyboard)
And a big shout out to the gentleman that brought this charge mode type of hijack to my attention luxxx123.
Also thanks to tenfar for his contribution to the Android communities
This project is being retired, i will give you all what i have so far but know that is it NOT 100% and will never be
This is a custom one off bootstrap, it works the way it does, remember im NOT going to be able to continue development of it, and im sorry if you dont like what i have so far, you are welcome to not use it.
HOW TO USE:
install apk,
open app
press install recovery
Allow SU permission
if everything goes as planed you will see a "success" toast
now press power off,
PRESS and HOLD all three keys to enter the Boot Options, using volume down navigate to BPTools, then volume up to select
You will boot into TWRP.
you can flash zips, and a backup, and all the other normal things, however DO NOT ATTEMPT TO RESTORE A BACKUP you wipe your /system and be left with nothing there.
this is HIGHLY recommended to not be used a primary solution.
Thank you all for your help over the month, and i will as always answer what ever questions you guys have.
com.runandhide05.xoom2recovery.Bootstrap.apk - 2.91 MB
source for device
https://github.com/runandhide05/moto_pasteur
wip source for bootstrap
https://github.com/runandhide05/xoom2_bootstrap-wip-
**Here is some helpful threads to fastboot your device back to stock
One Click restore
http://forum.xda-developers.com/showthread.php?t=1900755
http://forum.xda-developers.com/showthread.php?t=1923429

on my mz609 8.2: wipe cache work, wipe dalvik cache work, wipe battery stats work.
wipe data/factory reset not tested, first i want to make a backup : D
flash zip don't work, backup don' t work, (i sent e-mail with last_log)
this work without one xoom2 is already a great result. do not stop :good:

Very cool - once I get the ICS update and root, this is the first thing I am going to do.
Thanks!

wipe dalvik & cache works
backup and restore doesnt work and flashing zip doesnt work.
also factory reset doesn't work.
seems to be a mounting issue. unable to mount /sdcard and /cache.
will send you log via email.
do you need the partition table? don't know if there is a difference between xoom2 and xyboard e.g. between the models' tables
edit: log basicly consists of not being able to find/mount /cache /sdcard /userdata
edit 2: ok, sent you my logfile, seems like recovery can mount /cache on boot but not remount it after wiping it.
cheers

nchantmnt said:
wipe dalvik & cache works
backup and restore doesnt work and flashing zip doesnt work.
also factory reset doesn't work.
seems to be a mounting issue. unable to mount /sdcard and /cache.
will send you log via email.
do you need the partition table? don't know if there is a difference between xoom2 and xyboard e.g. between the models' tables
edit: log basicly consists of not being able to find/mount /cache /sdcard /userdata
edit 2: ok, sent you my logfile, seems like recovery can mount /cache on boot but not remount it after wiping it.
cheers
Click to expand...
Click to collapse
please try this one and report back
xoom2recovery_v0.0.3.apk - 2.29 MB
also need this one tested, and please report back which verision you are testing, refer to v0.0.X on the apk name
i think 0.0.4 should have a lot of things fixed.
but please feel free to test both,
xoom2recovery_v0.0.4.apk - 2.29 MB

Nice work there! Can you PM me telling how you did it? You're amazing, will try later if my mom let me test with her Xoom2
Sent from my 3g JB Xoom - By the 1st Xoom RC

ok guys im am seeing a problem. i need info. and some imgs.
need xoom2 (aka pasteur) , xyboard (aka fleming) and a xoom ME if anyone has one.
i need the following from them
please send me the model number mz609 and the details like "its the verizion droid xyboard" or the xoom media edition. the only img i have is of the pasteur which is the Xoom2 and i think its causing some issues, but i am not sure because im not getting enough detail on what deice you have and what the errors are, i cant remember what tablet each of you have some friendly reminders when you email or post would be great.
thanks
. that said i need the boot img and the reocvery img.
do this
in terminal
su
cat /proc/partitions
find the recovery and boot img block and then do this
dd if=/dev/block/mmcblk1p11 of=/sdcard/boot.img
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
subsituting the mmcblk1pXX for the correct block.
then send them to me please.

I have an MZ607 Xoom2 ME. I would be willing to help-I am rooted and on the ICS OTA, but this project is a bit over my head. I don't have fast boot files, for instance.
However, if I can be of assistance let me know - I'd love to see a custom recovery for this device!
Sent from my XOOM 2 ME using Tapatalk 2

jeffcavicchi said:
I have an MZ607 Xoom2 ME. I would be willing to help-I am rooted and on the ICS OTA, but this project is a bit over my head. I don't have fast boot files, for instance.
However, if I can be of assistance let me know - I'd love to see a custom recovery for this device!
Sent from my XOOM 2 ME using Tapatalk 2
Click to expand...
Click to collapse
You can. Do as stated right above your post and shoot me those imgs
Sent from my Galaxy Nexus using Tapatalk 2

Okay - got them. How do I send them to you?
Sent from my XOOM 2 ME using Tapatalk 2

jeffcavicchi said:
Okay - got them. How do I send them to you?
Sent from my XOOM 2 ME using Tapatalk 2
Click to expand...
Click to collapse
email or upload to a site and link,
my email is my name at gmail dot com
Someone try this for me please, its a twrp built apk ( im a LOT more familiar with twrp than cwm when it comes to building recoverys)
i have no ieda if it will even boot, ive never seen of a twrp bootstrap but hell... who knows right?
x2recovery_twrp_v0.0.1.apk - 2.36 MB

Sent them via email. Please let me know when you get them.
Sent from my XOOM 2 ME using Tapatalk 2

runandhide05 said:
ok guys im am seeing a problem. i need info. and some imgs.
need xoom2 (aka pasteur) , xyboard (aka fleming) and a xoom ME if anyone has one.
i need the following from them
please send me the model number mz609 and the details like "its the verizion droid xyboard" or the xoom media edition. the only img i have is of the pasteur which is the Xoom2 and i think its causing some issues, but i am not sure because im not getting enough detail on what deice you have and what the errors are, i cant remember what tablet each of you have some friendly reminders when you email or post would be great.
thanks
. that said i need the boot img and the reocvery img.
do this
in terminal
su
cat /proc/partitions
find the recovery and boot img block and then do this
dd if=/dev/block/mmcblk1p11 of=/sdcard/boot.img
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
subsituting the mmcblk1pXX for the correct block.
then send them to me please.
Click to expand...
Click to collapse
I don't mean to step on your toes, but shouldn't the command be cat proc/partitions?

jeffcavicchi said:
Sent them via email. Please let me know when you get them.
Sent from my XOOM 2 ME using Tapatalk 2
Click to expand...
Click to collapse
Nothing as of yet
Sent from my Galaxy Nexus using Tapatalk 2

mikeymike75 said:
I don't mean to step on your toes, but shouldn't the command be cat proc/partitions?
Click to expand...
Click to collapse
Both render the same result
Sent from my Galaxy Nexus using Tapatalk 2

Let me know if you don't get them. I assume your email is your username at Gmail dot com.
Sent from my XOOM 2 ME using Tapatalk 2

jeffcavicchi said:
Let me know if you don't get them. I assume your email is your username at Gmail dot com.
Sent from my XOOM 2 ME using Tapatalk 2
Click to expand...
Click to collapse
got it thanks, your tag here says xoom2, however your email tag said xyboard 8.2... which is it?

okey im still waiting to hear word back from the x2recovery_twrp_v0.0.1.apk, and now i have x2recovery_twrp_v0.0.2.apk for a possible fix for mount points
x2recovery_twrp_v0.0.2.apk - 2.36 MB
and also a cwm one for possible mount points
xoom2recovery_v0.0.5.apk - 2.29 MB
please let me know whats up with them.
thanks

**

Sure will try this evening. As you know i own the xoom 2 aka "pasteur". It's the mz616 from o2 germany, should be all the same tablets (in spite of the amount of internal storage) here in germany.
In case you need this:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
# cat /proc/partitions
major minor #blocks name alias
179 0 15552512 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 128 mmcblk1p4
179 5 4096 mmcblk1p5 pds
179 6 512 mmcblk1p6
179 7 1024 mmcblk1p7
179 8 2048 mmcblk1p8
179 9 512 mmcblk1p9
179 10 512 mmcblk1p10
179 11 8192 mmcblk1p11 boot
179 12 9216 mmcblk1p12 recovery
179 13 217088 mmcblk1p13 cdrom
179 14 512 mmcblk1p14 misc
179 15 512 mmcblk1p15 cid
179 16 4096 mmcblk1p16 kpanic
179 17 614400 mmcblk1p17 system
179 18 980992 mmcblk1p18 cache
179 19 716800 mmcblk1p19 preinstall
179 20 12959744 mmcblk1p20 userdata
179 64 1024 mmcblk1boot1
179 32 1024 mmcblk1boot0
#
Cheers
Gesendet von meinem XOOM 2 mit Tapatalk 2
---------- Post added at 09:20 AM ---------- Previous post was at 08:43 AM ----------
I'm still holding my promise. As soon as the recovery gets usable i willl donate
Gesendet von meinem XOOM 2 mit Tapatalk 2

[DEV] Dual Booting Project [Android - Ubuntu Phone OS] (HELP NEEDED)

Dual Booting Project
Android OS - Ubuntu Phone OS
As the title says, I think we can make posible dual booting Android and Ubuntu.
1st post Experimental Methods, Useful Infromation and Help Needed
2nd post News
3rd post How to install Ubuntu Phone OS​
Experimental Methods
1-. This method was originally posted by beidl
The method that beidl suggested us is to make this steps:
"Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff"
"Flash CM back to the device"
"Copy specific files back to /system"
"By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up."
NOTE: Nobody try it, be the first!​
*Using these methods you could brick your GNex, the poster of each method and me aren't responsible of any damage on your GNex!*
Useful Information
Here is partition table:
ytwytw said:
[...]
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
[...]
Click to expand...
Click to collapse
&
lrwxrwxrwx root root 2012-07-01 01:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-01 01:03 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-07-01 01:03 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-01 01:03 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-01 01:03 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-07-01 01:03 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-01 01:03 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-01 01:03 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-01 01:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-07-01 01:03 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-01 01:03 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-01 01:03 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-07-01 01:03 xloader -> /dev/block/mmcblk0p1
Click to expand...
Click to collapse
Info about GRUB on ARM v7​
Help Needed
I think we can modify partition table making more partitions and modifiying Ubuntu Phone OS kernel to boot in asigned partitions but I need help:
How much partition we have to add? (System, data..)
I think we have to edit bootloader + kernel, How to do it?
It will be posible?
I don't know a lot about partition tables and editing bootloader & kernel but, I think I will be able to help.
PD: If moderator or developers in this section think that it will be better to post this thread in general or in development, don't worry moving it.

News
News
22/02/2013:Thanks to beidl, I think we have the posibility to boot CM 10.1 and Ubuntu Phone OS. Take a look at the 10th post:
beidl said:
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
Click to expand...
Click to collapse
23/02/2013: I'm working on a modified version, now fisrtly I will delet all videos & images that came as a sample. EDIT: I have edited it, to download it, go to the 3rd post!

Files & How to install Ubuntu Phone OS
How to install Ubuntu Phone OS
NOTE: This files doesn't include the option to make a dual boot yet
-I'm not responable of any damage could have your GNex after flashing Ubuntu Phone OS this way-
Steps:
Download files quantal-preinstalled-armel+maguro.zip (4,6 MB) and quantal-preinstalled-phablet-armhf.zip (481 MB), and copy them to your GNex.
NOTE: You can use a modified file without all sample photos, videos and messages modified by me. Donwload it here: edited-quantal-preinstalled-phablet-armhf-v1.zip
Make a Nandroid Backup (to be able to restore Android later)
Make a Factory Reset
Flash them in CWM or TWRP (1-.quantal-preinstalled-armel+maguro.zip and 2-.quantal-preinstalled-phablet-armhf.zip)
Reboot (In a few seconds Ubuntu will boot up)
If you want to restore Android, make a backup of Ubuntu first if you want to install Ubuntu again
*This guide was originally posted by eng.stk*
NOTE: Second file (quantal-preinstalled-phablet-armhf.zip) will take few minutes to flash so don't panic and relax until it's flashed but, if you use the file that it has been modified by me, it will be faster. This method doesn't wipe your internal storage (/sdcard)
This way you could have both system only restoring backups of both OS. It's a good to have both system while dual boot it's being developed.

Don't you need like a bootloader to dual-boot?

jimmyco2008 said:
Don't you need like a bootloader to dual-boot?
Click to expand...
Click to collapse
Read the op again. *i think we need to edit the bootloader.
Sent from my Galaxy Nexus using Tapatalk 2

jimmyco2008 said:
Don't you need like a bootloader to dual-boot?
Click to expand...
Click to collapse
Yes, I need help to edit GNexs' bootloader to be able to boot both OS
Regards,
Urko
Enviado desde mi Galaxy Nexus usando Tapatalk 2

It's a very bad idea to screw around with the bootloader and partition table.
kexec would be the way to go, but it requires kernel patches for both the Android ROM and the Ubuntu ROM.
Also, since Ubuntu Touch is just chrooted inside CM, I guess it would be possible to make some CM specific tricks,
like creating a file on the filesystem, check for it on bootup, if it exists, boot into the chrooted Ubuntu environment.
I still have to take a look at the source though, basically finding out at which stage the ways of Android and Ubuntu seperate.

beidl said:
It's a very bad idea to screw around with the bootloader and partition table.
kexec would be the way to go, but it requires kernel patches for both the Android ROM and the Ubuntu ROM.
Also, since Ubuntu Touch is just chrooted inside CM, I guess it would be possible to make some CM specific tricks,
like creating a file on the filesystem, check for it on bootup, if it exists, boot into the chrooted Ubuntu environment.
I still have to take a look at the source though, basically finding out at which stage the ways of Android and Ubuntu seperate.
Click to expand...
Click to collapse
Do you think we will be able to run Ubuntu and CM? My idea was to modify partition table to add more partition and then, if you wanna run Android OS, flash its kernel to boot it in Android OS or flash Ubuntu Phone OS kernel (edited to boot specific partions) to boot Ubuntu Phone OS. Do you really think that it's a bad idea? I think it is the best option (and it's the only I know). Could you give me more details of that "Specific tricks" to do with CM?
BTW, I NEED MORE HELP!

Not a dev, but thought I'd try and give some helpful advise. I have an HP TouchPad that dual boots webOS and Android. Maybe looking at how that works will help you. Just a thought.

urko95 said:
Do you think we will be able to run Ubuntu and CM? My idea was to modify partition table to add more partition and then, if you wanna run Android OS, flash its kernel to boot it in Android OS or flash Ubuntu Phone OS kernel (edited to boot specific partions) to boot Ubuntu Phone OS. Do you really think that it's a bad idea? I think it is the best option (and it's the only I know). Could you give me more details of that "Specific tricks" to do with CM?
BTW, I NEED MORE HELP!
Click to expand...
Click to collapse
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.

beidl said:
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
Click to expand...
Click to collapse
I will give it a try later!
Thanks for your help!

couldn't modifying the bootloader be considered distributing a derivative work under the dmca?

In my opinion to have a dual booting you will need:
- A ramdisk that will prepare the partitions according to the choice of which OS
- A kernel that supports two versions of OS
- Two separate SD with the respective folders drivers etc. ... (This Is not possible on GNEX)
For the rest I do not know ubuntu for phone, it would take some expert.

anarkia1976 said:
In my opinion to have a dual booting you will need:
- A ramdisk that will prepare the partitions according to the choice of which OS
- A kernel that supports two versions of OS
- Two separate SD with the respective folders drivers etc. ... (This Is not possible on GNEX)
For the rest I do not know ubuntu for phone, it would take some expert.
Click to expand...
Click to collapse
Anarkia, What do you think about beidl's method?
NOTE: Thread organized and updated

A edited phablet file, I have deleted all sample photos, videos and messages. To download it, go to the 3rd post!

Excuse me,
can i flash these flies with CWM recovery?
urko95 said:
How to install Ubuntu Phone OS
NOTE: This files doesn't include the option to make a dual boot yet
-I'm not responable of any damage could have your GNex after flashing Ubuntu Phone OS this way-
Steps:
Download files quantal-preinstalled-armel+maguro.zip (4,6 MB) and quantal-preinstalled-phablet-armhf.zip (481 MB), and copy them to your GNex.
NOTE: You can use a modified file without all sample photos, videos and messages modified by me. Donwload it here: edited-quantal-preinstalled-phablet-armhf-v1.zip
Make a Nandroid Backup (to be able to restore Android later)
Make a Factory Reset
Flash them (1-.quantal-preinstalled-armel+maguro.zip and 2-.quantal-preinstalled-phablet-armhf.zip)
Reboot (In a few seconds Ubuntu will boot up)
If you want to restore Android, make a backup of Ubuntu first if you want to install Ubuntu again
*This guide was originally posted by eng.stk*
NOTE: Second file (quantal-preinstalled-phablet-armhf.zip) will take few minutes to flash so don't panic and relax until it's flashed but, if you use the file that it has been modified by me, it will be faster. This method doesn't wipe your internal storage (/sdcard)
This way you could have both system only restoring backups of both OS. It's a good to have both system while dual boot it's being developed.
Click to expand...
Click to collapse

LucaZPF said:
Excuse me,
can i flash these flies with CWM recovery?
Click to expand...
Click to collapse
Yes, you can, with TWRP or CWM, you choose.

Reporting semi-success
So i diffed the system directories of CM 10.1 and Ubuntu Touch and found the new files.
/system/bin/modelid_cfg.sh
/system/bin/ubuntuappmanager
/system/bin/ubuntu_chroot
/system/bin/uchroot
/system/usr/idc/autopilot-finger.idc
/system/quantal-ubuntu_stamp
Click to expand...
Click to collapse
I pushed those files to my working CM 10.1 installation on the GNex.
Since I did not wipe my GNex when I went back from Ubuntu Touch to CM 10.1, the folder structure
of Ubuntu stayed at /data/ubuntu/.
Then, I rebooted into the bootloader and flashed the boot.img of Ubuntu Touch to the GNex.
After rebooting, the device was stuck at the Google boot logo but the kernel did actually boot, so I was able to adb shell into the device.
dmesg returned:
Code:
<6>[ 15.739807] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4783, /home/ubuntu/jenkins/workspace/phablet-image/kernel/samsung/tuna/drivers/gpu/pvr/bridged_pvr_bridge.c]
That means Canonical still uses the kernel from before a week, this kernel doesn't play nicely with the new proprietary GPU driver.
I'll try pushing the old GPU blobs now...

beidl said:
Reporting semi-success
So i diffed the system directories of CM 10.1 and Ubuntu Touch and found the new files.
I pushed those files to my working CM 10.1 installation on the GNex.
Since I did not wipe my GNex when I went back from Ubuntu Touch to CM 10.1, the folder structure
of Ubuntu stayed at /data/ubuntu/.
Then, I rebooted into the bootloader and flashed the boot.img of Ubuntu Touch to the GNex.
After rebooting, the device was stuck at the Google boot logo but the kernel did actually boot, so I was able to adb shell into the device.
dmesg returned:
Code:
<6>[ 15.739807] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4783, /home/ubuntu/jenkins/workspace/phablet-image/kernel/samsung/tuna/drivers/gpu/pvr/bridged_pvr_bridge.c]
That means Canonical still uses the kernel from before a week, this kernel doesn't play nicely with the new proprietary GPU driver.
I'll try pushing the old GPU blobs now...
Click to expand...
Click to collapse
Waiting to your results, great job beidl!

Sv: [DEV] Dual Booting Project [Android - Ubuntu Phone OS] (HELP NEEDED)
First zip to flash is linked wrong it links to the IMG
Ubuntu phone os is nice but laggy buggy power eating just tried it. Maybe we should focus on it running good before dual boot
Did anyone try using it ? Gsm and all that did not work on my gnex. Did you guys have luck?
Sent from my Galaxy Nexus using xda premium

BigPart Repartition Upgrade and Resource Center

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://forum.xda-developers.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:
Full charge your tablet (or keep it connected to AC?) and turn it on WITHOUT SDCARD.
If your Android SDK is not installed or working properly, fix it now: http://developer.android.com/sdk/index.html
Install the dependencies. For Ubuntu / LinuxMint / Debian:
Code:
apt-get install testdisk netcat pv extundelete testdisk
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
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.
Open a terminal on your computer, go to the Android SDK directory's subdirectory sdk/platform-tools (where adb is located).
We will setup a forward port to be able to download the data to our PC:
Code:
./adb forward tcp:5555 tcp:5555
Now we will connect to the tablet
Code:
./adb shell
Maybe you need to grant permission to do it. Take a look to your tablet's screen.
We become superuser:
Code:
su
Grant permanent permissions when asked. You can revoke the permissions later if you want.
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
DON'T CLOSE THAT TERMINAL. An now OPEN A NEW ONE IN THE PC.
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.
You will to wait up to 3 hours until it finish.
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
First restore the GPT partition table. Select mmcblk0.raw in the TestDisk interface and choose Proceed.
Choose EFI GPT.
Then select Analyse.
Choose Quick Search.
The search will return a table that you should copy and paste in this thread.
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.

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

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

4.4
No problem for test

Would love to test
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

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.

I'm running it now!
Sent from my Xoom

notbrodie said:
I'm running it now!
Sent from my Xoom
Click to expand...
Click to collapse
That's great!!!!

i got no Linux box. will see if i can do some research over the weekend on Windoze tools.

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?

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!

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"

Thank you guys!
Sent from my Nexus 4 using Tapatalk

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

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://forum.xda-developers.com/showthread.php?t=1388996

You guys... are brilliant... I'm in. My Xoom is just collecting dust since Eos shutdown.

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 XOOM and S2

I have a mz605 umt_everest model, at monday in my lab I will do this and post here.

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://forum.xda-developers.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?

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

[Q] a little help here

I have a sm-t210r tab and ever since I've updated it to 4.4.2 it gives me so many bugs after I've install a new ROM for example nolekat and i know for a fact that it's not the ROM because I've install the same ROM on my little sister's tab and she has no bugs her tab is not updated. So my question is if there is any way to remove the new bootloader or to downgrade?

Please anyone? Its driving me crazy to see my little sister's tab running so nice and mine keeps unfortunately stopping apps at random and even random reboots it sucks.

kgalv419 said:
Please anyone? Its driving me crazy to see my little sister's tab running so nice and mine keeps unfortunately stopping apps at random and even random reboots it sucks.
Click to expand...
Click to collapse
You need to update your recovery to its latest version. I recomend philz touch!

That's what I'm using bro

i have installed philz touch, so how do we downgrade bootloader?

That's all i want to know too? I know someone can figure it out

from my post in note 10 forum
kgalv419 said:
I have a sm-t210r tab and ever since I've updated it to 4.4.2 it gives me so many bugs after I've install a new ROM for example nolekat and i know for a fact that it's not the ROM because I've install the same ROM on my little sister's tab and she has no bugs her tab is not updated. So my question is if there is any way to remove the new bootloader or to downgrade?
Click to expand...
Click to collapse
stewart30 said:
i have installed philz touch, so how do we downgrade bootloader?
Click to expand...
Click to collapse
this has worked on gt-p5210, gt-n8013 so it stands to reason it should work on the t210
keep in mind these instructions are in the specifics for the gt-n8013, adjust accordingly.
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb in recovery mode
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
edit-or pack it for recovery flashable
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
Click to expand...
Click to collapse
m
kgalv419; you can pull the original from your sister's tab if it's t210r , just don't screw it up.

Thanks a lot bro will get to work on it now and let u know how it went thanks again

i have one last question bro, i successfully got the fix.img from my sister's tab and turn it into a flash-able zip. Should i use odin to flash the official 4.1.2 then flash the zip via recovery? or flash the zip first then use odin?

kgalv419 said:
i have one last question bro, i successfully got the fix.img from my sister's tab and turn it into a flash-able zip. Should i use odin to flash the official 4.1.2 then flash the zip via recovery? or flash the zip first then use odin?
Click to expand...
Click to collapse
for my note 10 and for the tab 3 10
flash the fix first - provided you're absolutely certain you got it right.
then flash the rom though, i don't think you should any of the above for a tab
that doesn't really need a rescue. Just triple check every step before you perform it
and be deliberate and not impulsive. Good luck.
m

Thanks a lot moon

What exactly does the fix.img do moon?

kgalv419 said:
What exactly does the fix.img do moon?
Click to expand...
Click to collapse
k,
hey,
sorry to take so long in getting back to you,
please re-read my post in this thread about the procedure carefully, just to get your head in the game.
now, the reason for this approach to restoring original bootloader is because if you try to write the bootloader
via the dd command directly in normal operation and recovery the tab kicks back and reboots and in that
scenario you stand a VERY good chance of hard-brick, dead, done.
pulling/dumping from /dev/mmcblk0 for X=amount in MB has the same effect as a cloning procedure and seems to work
well, i have done this on my gt-n8013 and coached another user through the process for the gt-p5210 using the data i pulled
from my own tab and packeged for recovery flash. I am saying you should consider not doing this for a tab that isn't
soft-bricked to a degree that would make this exercise necessary. You may just need to use a different rom instead.
m
keep in mind you will need to re-flash a rom afterward. NOT and odin firmware but an appropriate xda recovery flashable
rom for your device.