Code:
HOWTO for anyone interested: Updated on 2011 12-13
Update: resolved 'major:minor pair unavailable'
Update: Works for 32GB HP Touchpad and 16GB HP Touchpad
Credits to:
webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
for the 32GB HP Touchpad filesystem creation example
[FIRST]
1) THIS PROCESS WILL COMPLETELY WIPE YOUR TOUCHPAD! WEBOS, CM7,
& ANYTHING ELSE YOU'VE INSTALLED!!
2) This process also assumes you can get functional terminal to your HP
Touchpad already via novaterm, novacom open TTY://, or with putty.
3) This process also assumes you know how to install CM7 already.
YOU WILL ALSO NEED:
webOS Doctor version 3.0.0
webOS Doctor version 3.0.4
from All HP WebOS Doctor Versions:
webos-internals.org/wiki/Webos_Doctor_Versions
[NOW START]
1) Put your HP Touchpad in webOS Recovery Mode:
a. Power off the HP Touchpad or reset it with [Power Button] + [Home]
b. Hold [Up Volume] + [Power Button] until you see a usb symbol on screen.
2) Start up taskmanager in Windows:
a. [CTRL]+[ALT]+[DEL] and select task manager
3) Run webOS Doctor and let it run to 8% then use taskmanager to end task
on webOS doctor.
4) Open up windows command prompt and type in: novacom open TTY://
5) Run the following commands [CASE SENSITIVE] type it exactly as shown
and make sure to get the numbers after --minor correct:
[Note: Don't bother customizing webOS partitions because in this process
webOS doctor will re-size them back to the following anyways.]
a. lvm.static vgscan --ignorelockingfailure
b. lvm.static vgchange -ay --ignorelockingfailure
c. lvm.static vgremove store
d. lvm.static vgscan --ignorelockingfailure
e. lvm.static vgchange -ay --ignorelockingfailure
f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
g. lvm.static vgscan --ignorelockingfailure
h. lvm.static vgchange -ay --ignorelockingfailure
i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store
NOTE: THE FOLLOWING --minor JUMPS to 7 from 5 above
o. lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store
NOTE: THE FOLLOWING MAKES CM7 PARTITIONS, I specified a 5GB cm-data
partition, you can do more or less. 1 Physical Extent (PE) is 8MB.
The number after -l is the number of Physical Extents for
the partition.
p. lvm.static lvcreate -l 96 -M y --major 254 --minor 8 -n cm-system store
q. lvm.static lvcreate -l 32 -M y --major 254 --minor 9 -n cm-cache store
r. lvm.static lvcreate -l 640 -M y --major 254 --minor 10 -n cm-data store
NOTE: The following creates the media partition used as SDCARD and sets
it to --minor 6, make sure you set it to --minor 6, the SDCARD is
specified as dm-6 in CM7. This will save you from having to edit
/etc/vold.fstab in CM7.
s. lvm.static vgscan --ignorelockingfailure
t. lvm.static vgchange -ay --ignorelockingfailure
u. lvm.static vgdisplay
i. this command displays information on the Volume Group: store
at the bottom you should see:
Free PE/Size X / XX
where X is the number of Physical Extents free and XX is the size free.
ii. write down the number of X (Physical Extents free) to use in the
next command
v. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
w. lvm.static vgscan --ignorelockingfailure
x. lvm.static vgchange -ay --ignorelockingfailure
y. mkdosfs -f 1 -s 64 -F 32 /dev/store/media
z. mkfs.ext4 /dev/store/cm-system or mkfs.ext3 /dev/store/cm-system
za. mkfs.ext4 /dev/store/cm-cache or mkfs.ext3 /dev/store/cm-cache
zb. mkfs.ext4 /dev/store/cm-data or mkfs.ext3 /dev/store/cm-data
zc. run webOS Doctor 3.0.0 and let it complete and let it reboot to
the language selection screen
zd. reset the HP Touchpad with [POWER BUTTON] + [HOME] and put it into
webOS Doctor recovery mode with [POWER BUTTON] + [VOLUME UP].
ze. run webOS Doctor 3.0.4 and let it complete and let it reboot and
complete webOS install and go into webOS.
If you did everything right, you now have an HP Touchpad tablet with a fresh
webOS 3.0.4 and pre-created CM7 partitions. Now, just follow the standard
CM7 install procedure after you boot into webOS 3.0.4 to install CM7.
ACMEInstaller will use the cm-system, cm-cache, and cm-data file system
you've already created. :-) Enjoy.
webOS Doctor 3.0.0 is required. If you do not run this first, other webOS
Doctor version will fail. webOS Doctor 3.0.0 resizes and formats partitions
as needed, the other versions seem to no longer have this and fail when
the webOS partitions aren't perfect in format/size.
Thanks for the detailed response from my post on Xron Dev Thread.
Based on the following site...
http://www.webosbuzz.com/hp-touchpad/2499-cm7-alpha2-1-here.html
saying the following
"One thing to know is that the space in the /boot partition is extremely limited at the moment, and cannot be easily re-sized, as it will freak out WebOS Doctor and may create other issues. Unless and until the /boot partition can be extended, this size limitation will affect the number of OSes that can be squeezed onto the TouchPad at one time."
How does this affect/react with your 5GB cm-data size?
There is a typo in line V.
It reads:
Code:
. lvm.static lvcreate -l X -M y --major 254 --minor 6 -m media store
but should read:
Code:
. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
Just a head's up for those who get stuck at that point with error messages.
herrdude said:
There is a typo in line V.
It reads:
Code:
. lvm.static lvcreate -l X -M y --major 254 --minor 6 -m media store
but should read:
Code:
. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
Just a head's up for those who get stuck at that point with error messages.
Click to expand...
Click to collapse
You need to replace X with the number of Physical Extents obtained from the previous few lines of instructions. X is a variable.
qwerty007 said:
You need to replace X with the number of Physical Extents obtained from the previous few lines of instructions. X is a variable.
Click to expand...
Click to collapse
it would seem he is referring to last "-m". in his its "-n" before media store.
havikx said:
it would seem he is referring to last "-m". in his its "-n" before media store.
Click to expand...
Click to collapse
lol. yeah i realized that after i posted, then it said you're new so you have to wait 5, min so i couldn't make a fix to my post. lol. then i had to go to work. anyhow, noted and fixed. thanks guys.
flashypants said:
Thanks for the detailed response from my post on Xron Dev Thread.
Based on the following site...
http://www.webosbuzz.com/hp-touchpad/2499-cm7-alpha2-1-here.html
saying the following
"One thing to know is that the space in the /boot partition is extremely limited at the moment, and cannot be easily re-sized, as it will freak out WebOS Doctor and may create other issues. Unless and until the /boot partition can be extended, this size limitation will affect the number of OSes that can be squeezed onto the TouchPad at one time."
How does this affect/react with your 5GB cm-data size?
Click to expand...
Click to collapse
i think /boot is a webOS partition and not a CM partition. i haven't tried it, but increasing the size of the partitions shouldn't kill webOS. The problem is that when you use 3.0.0 doctor, it resizes partitions back to their original size. resizing CM partitions is safe, CWM restore, etc... isn't partition size specific. resizing the media partition that's the SDCARD, common between webOS and CM, doesn't do anything either. but all the other webOS partitions seem to be picky about size when webOS Doctoring. but i'm pretty sure you could upsize a partition after you webOS doctor and it'd be just fine and webOS wouldn't throw a fit or anything. i think the main developers just won't do it because it'll cause a headache since a lot of people trying to install CM/android with webOS don't really know what we're doing until we've done it. lmao.
the only reason I even bothered with resizing CM partitions in the first place is because of the SDCARD issue that occurs when you've moved too many apps onto your SDCARD. it starts remounting at random. then it doesn't mount at all once you reached the high limit which a lot of folks have said 30/50 not sure which is it. But i ran into this issue, and i was like WTH. You have a 32GB SDCARD why can't you just have a 5-8GB /cm-data partition so you can just simply not need to move any apps to SD and avoid the whole friggen problem. it's not like there's actually "internal" storage. it's all just partitions on the same physical SD anyways. so I started playing with file system. and came up with this. 8GB seemed to be too much for the /cm-data for me cause i still had way too much space free after I installed all my apps and games. 5GB seems to be the perfect number for me. Allows for all apps to be installed and still have space for temp web storage/cache on the /cm-data partition.
qwerty007 said:
i think /boot is a webOS partition and not a CM partition. i haven't tried it, but increasing the size of the partitions shouldn't kill webOS. The problem is that when you use 3.0.0 doctor, it resizes partitions back to their original size. resizing CM partitions is safe, CWM restore, etc... isn't partition size specific. resizing the media partition that's the SDCARD, common between webOS and CM, doesn't do anything either. but all the other webOS partitions seem to be picky about size when webOS Doctoring. but i'm pretty sure you could upsize a partition after you webOS doctor and it'd be just fine and webOS wouldn't throw a fit or anything. i think the main developers just won't do it because it'll cause a headache since a lot of people trying to install CM/android with webOS don't really know what we're doing until we've done it. lmao.
the only reason I even bothered with resizing CM partitions in the first place is because of the SDCARD issue that occurs when you've moved too many apps onto your SDCARD. it starts remounting at random. then it doesn't mount at all once you reached the high limit which a lot of folks have said 30/50 not sure which is it. But i ran into this issue, and i was like WTH. You have a 32GB SDCARD why can't you just have a 5-8GB /cm-data partition so you can just simply not need to move any apps to SD and avoid the whole friggen problem. it's not like there's actually "internal" storage. it's all just partitions on the same physical SD anyways. so I started playing with file system. and came up with this. 8GB seemed to be too much for the /cm-data for me cause i still had way too much space free after I installed all my apps and games. 5GB seems to be the perfect number for me. Allows for all apps to be installed and still have space for temp web storage/cache on the /cm-data partition.
Click to expand...
Click to collapse
Cheers for even more fine detail! I might venture into this if the new ROMs get any bigger. currently I'm just deleting unnecessary apps and have enough free space.
Sent from my Desire HD using XDA App
Hey,
I followed all the steps and everything went fine. I have my 5Gb for internal memory but I've just noticed that under Android the external Sdcard has about 21-22Gb. It's Ok but when I plug it,my computer only show me about 13-14Gb
Has anyone encountered same problem ?
Thanks
Thanx for this will give it a go when I'm a bit more sober ....
Sent from my Touchpad using xda premium
Since we are talking about adjusting the partitions can anyone tell me how to completely wipe the touchpad and get a fresh start (after installing, cm7 and ubuntu/archlinux chroots that seem to have taken some space from my media partition).
after a full erase and webos doctor i still see my old partitions from novaterm.
I'm not sure what this does lol
My 16GB Touchpad shows 1.5 internal storage and 10.5 external.
How come? Is it impossible to get near the 16?
I get that WebOS uses some but I'm sure eventually we will be able to uninstall which I will probably do.
Does this process increase available storage?
Sent from my GT-i9100 using xda premium
Varemenos said:
Since we are talking about adjusting the partitions can anyone tell me how to completely wipe the touchpad and get a fresh start (after installing, cm7 and ubuntu/archlinux chroots that seem to have taken some space from my media partition).
after a full erase and webos doctor i still see my old partitions from novaterm.
Click to expand...
Click to collapse
I know your post was from a week ago: but just so you know - this process will do that - completely wipe it.
If you leave out the steps for creating the cm partitions - you will end up with a virgin TP.
sudoo said:
Hey,
I followed all the steps and everything went fine. I have my 5Gb for internal memory but I've just noticed that under Android the external Sdcard has about 21-22Gb. It's Ok but when I plug it,my computer only show me about 13-14Gb
Has anyone encountered same problem ?
Thanks
Click to expand...
Click to collapse
Thanks OP.
I followed all the steps and everything went fine. My computer shows 21-22Gb correctly.
Will an ACMEunintaller process bring back the partitions to WebOS default?
Else what will be the solution to bring back to normal(scratch)?
Please advice for a 16GB touchpad.
Thanks
Hey,
does this work for 64 GB Touchpad, too?
Or are there any differences in the system/partition structure?
Best,
z3no
Edit: ok works
Any solution if i want to remove webOS completely?
Thanks for the great work..
What is the default partition format(ext3 or ext4) which created by ACMEInstaller of CM7 and CM9? If we format the partition to ext4, will the ACMEInstaller change it to something else? Thanks.
qwerty007 said:
Code:
HOWTO for anyone interested: Updated on 2011 12-13
Update: resolved 'major:minor pair unavailable'
Update: Works for 32GB HP Touchpad and 16GB HP Touchpad
Credits to:
webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
for the 32GB HP Touchpad filesystem creation example
[FIRST]
1) THIS PROCESS WILL COMPLETELY WIPE YOUR TOUCHPAD! WEBOS, CM7,
& ANYTHING ELSE YOU'VE INSTALLED!!
2) This process also assumes you can get functional terminal to your HP
Touchpad already via novaterm, novacom open TTY://, or with putty.
3) This process also assumes you know how to install CM7 already.
YOU WILL ALSO NEED:
webOS Doctor version 3.0.0
webOS Doctor version 3.0.4
from All HP WebOS Doctor Versions:
webos-internals.org/wiki/Webos_Doctor_Versions
[NOW START]
1) Put your HP Touchpad in webOS Recovery Mode:
a. Power off the HP Touchpad or reset it with [Power Button] + [Home]
b. Hold [Up Volume] + [Power Button] until you see a usb symbol on screen.
2) Start up taskmanager in Windows:
a. [CTRL]+[ALT]+[DEL] and select task manager
3) Run webOS Doctor and let it run to 8% then use taskmanager to end task
on webOS doctor.
4) Open up windows command prompt and type in: novacom open TTY://
5) Run the following commands [CASE SENSITIVE] type it exactly as shown
and make sure to get the numbers after --minor correct:
[Note: Don't bother customizing webOS partitions because in this process
webOS doctor will re-size them back to the following anyways.]
a. lvm.static vgscan --ignorelockingfailure
b. lvm.static vgchange -ay --ignorelockingfailure
c. lvm.static vgremove store
d. lvm.static vgscan --ignorelockingfailure
e. lvm.static vgchange -ay --ignorelockingfailure
f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
g. lvm.static vgscan --ignorelockingfailure
h. lvm.static vgchange -ay --ignorelockingfailure
i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store
NOTE: THE FOLLOWING --minor JUMPS to 7 from 5 above
o. lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store
NOTE: THE FOLLOWING MAKES CM7 PARTITIONS, I specified a 5GB cm-data
partition, you can do more or less. 1 Physical Extent (PE) is 8MB.
The number after -l is the number of Physical Extents for
the partition.
p. lvm.static lvcreate -l 96 -M y --major 254 --minor 8 -n cm-system store
q. lvm.static lvcreate -l 32 -M y --major 254 --minor 9 -n cm-cache store
r. lvm.static lvcreate -l 640 -M y --major 254 --minor 10 -n cm-data store
NOTE: The following creates the media partition used as SDCARD and sets
it to --minor 6, make sure you set it to --minor 6, the SDCARD is
specified as dm-6 in CM7. This will save you from having to edit
/etc/vold.fstab in CM7.
s. lvm.static vgscan --ignorelockingfailure
t. lvm.static vgchange -ay --ignorelockingfailure
u. lvm.static vgdisplay
i. this command displays information on the Volume Group: store
at the bottom you should see:
Free PE/Size X / XX
where X is the number of Physical Extents free and XX is the size free.
ii. write down the number of X (Physical Extents free) to use in the
next command
v. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
w. lvm.static vgscan --ignorelockingfailure
x. lvm.static vgchange -ay --ignorelockingfailure
y. mkdosfs -f 1 -s 64 -F 32 /dev/store/media
z. mkfs.ext4 /dev/store/cm-system or mkfs.ext3 /dev/store/cm-system
za. mkfs.ext4 /dev/store/cm-cache or mkfs.ext3 /dev/store/cm-cache
zb. mkfs.ext4 /dev/store/cm-data or mkfs.ext3 /dev/store/cm-data
zc. run webOS Doctor 3.0.0 and let it complete and let it reboot to
the language selection screen
zd. reset the HP Touchpad with [POWER BUTTON] + [HOME] and put it into
webOS Doctor recovery mode with [POWER BUTTON] + [VOLUME UP].
ze. run webOS Doctor 3.0.4 and let it complete and let it reboot and
complete webOS install and go into webOS.
If you did everything right, you now have an HP Touchpad tablet with a fresh
webOS 3.0.4 and pre-created CM7 partitions. Now, just follow the standard
CM7 install procedure after you boot into webOS 3.0.4 to install CM7.
ACMEInstaller will use the cm-system, cm-cache, and cm-data file system
you've already created. :) Enjoy.
webOS Doctor 3.0.0 is required. If you do not run this first, other webOS
Doctor version will fail. webOS Doctor 3.0.0 resizes and formats partitions
as needed, the other versions seem to no longer have this and fail when
the webOS partitions aren't perfect in format/size.
Click to expand...
Click to collapse
Hi
ACMEUninstaller doesn't work
I tried the command of first post but I've error like this
Invalid argument media : i think it's for "media store"
Else I've this
[email protected]:/# lvm.static vgscan --ignorelockingfailure
lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument
Volume group "store" inconsistent
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument
WARNING: Inconsistent metadata found for VG store - updating to use version 15
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument
Automatic metadata correction failed
What did you think ?
Related
Hi everyone,
I need to Format a SD Card (programatically ), and I havn't got the foggiest on where to start, I mean, do I need to build the whole structure on the card myself, or is there some API level I can go to to do the job.
Can anyone help me out here?
I just completed that from my linux box
I did this from my linux box to get set up for linux on the HTC apache and was listing all the gory details.
Code:
fdisk /dev/sdb //after verifiing itis correct device
p //print out partition table
d //delete existing partition if not 32M fat 16
n //new partition
p //primary
1 //number
<cr> //Accept default of first cylinder
+32M //make it 32M in size
t 6 //change it to fat16 type
n //create another partition
p //chose primary, even though it is callet ext3
2 //number it 2
<cr> //accept default
<cr> //to use rest of stick
t //set it's type
2 //select second partition
83 //type is linux (ext2 or ext3)
w // write table or you get to do it again
Unplug it and count to 5, plug it back in and cd /dev and "ls -al |grep sd"
it will probably be in a differnt location.
mkdosfs /dev/sdc1 //format the FAT16 partition In gentoo, this was in dosfstools'
mkfs.ext3 /dev/sdc2 //format the linux partition
//create a pair of mount points and mount them
cd /mnt
mkdir MiniSDDos
mkdir MiniSDLinux
mount /dev/sdc1 /mnt/MiniSDDos
mount /dev/sdc2 /mnt/MiniSDLinux
transfer rd,zimiage,default.txt and gnuharet-200603042123.exe to dos partition
ATTENTION!
This guide is outdated and I can no longer support it as I no longer own an HP Touchpad.
Disclaimer:
This WILL void your warranty.
I am not responsible for mistakes, typos, bricked devices, or any problems you may encounter. You have been warned.
You will most likely brick your device if you aren't very familiar with Linux file systems and advanced UNIX CLI.
Follow steps PRECISELY.
Back up your files, you WILL lose everything you have on your Touchpad.
Please, be very careful.
I no longer own an HP Touchpad, so please help each other with issues.
What Works
WiFi
Bluetooth
USB Host (via OTG and Y-Cable Solution)
It's pretty much stable and very useable
What Doesn't Work/Some Bugs
Camera
Microphone
Audio
Unity is laggy (I suggest Gnome Classic or LXDE)
Mouse pointer disappears sometimes
Prerequisites:
PC (preferably running a Linux operating system)
The ability to follow directions precisely
For WebOS (Part 1):
WebOS Doctor 3.0.0
WebOS Doctor 3.0.5
Novaterm and Novacom (available here)
For Ubuntu (Part 2):
4GBPartition.sh
4GBUbuntuInstallSystem.sh
Modifications.tar.gz
ts_srv_init.tar.gz
TouchPadBuntuRootfs.tgz
For Android (Part 3):
ACMEInstaller2
ClockworkMod
CM9 Alpha 2
GAPPS ICS
Part 1 (WebOS)
FYI: How to enter Developer Mode In the "Just type..." text field at the home screen, type "webos20090606". In the results, there will be an icon labeled "Developer Mode". Select this, do not enter a password, and turn on Developer Mode.
A. Turn on Touchpad and connect to PC via USB
B. Open WebOS Doctor 3.0.0 and allow to run to 8%
C. Kill WebOS Doctor
D. Open Novaterm (Linux/OSX, simply type "novaterm" into a terminal window. Windows, navigate to C:\Program Files\Palm, Inc\Terminal\novaterm [it's a Windows Batch File], now press CTRL+SHIFT+C and hit enter to connect to the device [Windows only])
E. You should now be in a bash shell. Enter the following commands (one by one) to manually recreate the device partition scheme:
Code:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
This command will display information about the Volume Group: store. At the bottom you will see "Free PE/SIZE X / XX" (where "X" is your own value). Please take note of the "Free PE" value.
Code:
lvm.static vgdisplay
Replace the "X" in the first command with the value you took note of in the previous command.
Code:
lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 -F 32 /dev/store/media
F. Run WebOS Doctor 3.0.0, allow it to complete and reboot into the language selection screen.
G. Power down the Touchpad by holding the Home and Power buttons simultaneously.
H. Boot into WebOS Recovery Mode by holding down the Volume Up and Power buttons simultaneously until a USB logo appears on the screen.
I. Run WebOS Doctor 3.0.5
J. Set up WebOS as you normally would
Part 2 (Ubuntu)
A. Mount USB Drive mode
B. Copy files from the prerequisite section of this guide into the root folder of the device.
C. Unmount/eject device
D. Enable Developer Mode (webos20090606 in "Just type...")
E. Open Novaterm again
F. Enter the following commands (one at a time):
This will create a 4GB partition for Ubuntu. Your device will reboot afterward, make sure it ends up back into WebOS with Developer Mode enabled again.
Code:
cd /media/internal
cp 4GBPartition.sh /tmp
cd /tmp
sh 4GBPartition.sh
This will install Ubuntu and the Moboot Bootloader. After install has completed, your device will reboot into Moboot, select "Ubuntu" to boot into Ubuntu and finish setup.
Code:
cd /media/internal
cp 4GBUbuntuInstallSystem.sh /tmp
cd /tmp
sh 4GBUbuntuInstallSystem.sh
Once you reach the Ubuntu log in screen, click on the universal access icon in the top right-hand corner and select On-Board keyboard. Type in the password "ubuntu". Once booted into Unity, click the dash home and browse through installed applications (opening On-Board and Terminal). Type the following into the terminal to enable Bluetooth and Wifi (sudo password is "ubuntu"):
Code:
sudo depmod -a
sudo gedit /etc/modules
Now a Gedit text editor window has opened. Add "ath6kl" to the bottom, save, and close. Go back to the terminal and type the following:
Code:
sudo update-rc.d bcattach_srv defaults
sudo reboot
Part 3 (Android)
A. Boot into WebOS
B. Connect via USB and enable USB Drive mode
C. Create a folder called "cminstall" in the root of the device
D. Copy all files from the Android prerequisite section into "cminstall"
E. Unmount/eject device
F. Enable developer mode (webos20090606 in "Just type...")
G. Open Novaterm
H. If in Windows, please copy the "ACMEInstaller2" file to "C:\Program Files\Palm, Inc\Terminal"
I. If in Windows, open a terminal and type the following commands in one line at a time:
Code:
cd 'C:\Program Files\Palm, Inc\Terminal'
novacom boot mem:// < ACMEInstaller2
J. If you are in Linux, simply change directories to where you have "ACMEInstaller2".
Code:
cd /directory/containing/ACMEUninstaller2/
novacom boot mem:// < ACMEInstaller2
K. Android will now install and the device will now reboot again.
L. Boot into ClockworkMod and flash GAPPS.
Sources
http://forum.xda-developers.com/showthread.php?t=1305891
http://code.google.com/p/hp-touchpad-ubuntu/wiki/Installation
http://wiki.rootzwiki.com/HP_Touchpad
http://forum.xda-developers.com/showthread.php?t=1304475
http://rootzwiki.com/topic/18843-releasealpha2-cyanogenmod-9-touchpad/
awesome
Been looking for this
Sent from my Touchpad using XDA Premium HD app
Nice. This is a nice rainy day project to check off the list. Well done.
Sent from my HTCEVO3D using Tapatalk
Leoisright said:
Nice. This is a nice rainy day project to check off the list. Well done.
Sent from my HTCEVO3D using Tapatalk
Click to expand...
Click to collapse
Thanks mate!
Sent from my Galaxy Nexus using Tapatalk 2
"TouchPadBuntuRootfs.tgz" link is broken
mirrors:
http://dl.dropbox.com/u/11867712/TouchPadBuntuRootfs.tgz
http://dl.dropbox.com/u/4357827/TouchPadBuntu/TouchPadBuntuRootfs.tgz
http://dl.dropbox.com/u/20796504/TouchPadBuntuRootfs.tgz
http://touchpadbuntu-touchpadbunutu.dotcloud.com/files/TouchPadBuntuRootfs.tgz
(found on http://wiki.hp-touchpad-ubuntu.googlecode.com/git/Installation.wiki )
edit Stuck on Part 2:
just after "cd /media/internal
cp 4GBPartition.sh /tmp
cd /tmp
sh 4GBPartition.sh"
Moboot works, but if I chose ubuntu it reboots after 15-20 sec (probably expected ?)
So I boot in WebOS in order to launch "sh 4GBUbuntuInstallSystem.sh" but I have "Cannot write: No space left on device"
Any hints please ? =)
Xmalek said:
"TouchPadBuntuRootfs.tgz" link is broken
mirrors:
http://dl.dropbox.com/u/11867712/TouchPadBuntuRootfs.tgz
http://dl.dropbox.com/u/4357827/TouchPadBuntu/TouchPadBuntuRootfs.tgz
http://dl.dropbox.com/u/20796504/TouchPadBuntuRootfs.tgz
http://touchpadbuntu-touchpadbunutu.dotcloud.com/files/TouchPadBuntuRootfs.tgz
(found on http://wiki.hp-touchpad-ubuntu.googlecode.com/git/Installation.wiki )
edit Stuck on Part 2:
just after "cd /media/internal
cp 4GBPartition.sh /tmp
cd /tmp
sh 4GBPartition.sh"
Moboot works, but if I chose ubuntu it reboots after 15-20 sec (probably expected ?)
So I boot in WebOS in order to launch "sh 4GBUbuntuInstallSystem.sh" but I have "Cannot write: No space left on device"
Any hints please ? =)
Click to expand...
Click to collapse
Thanks for the links. I'll place them in the OP when I get a chance.
Sorry to hear about your troubles, and even more sorry to say that you're going to have to go through Part 1 again :/. Even the slightest typo in a UNIX CLI can cause major issues. I'm on a 16GB TP and these are the steps I used to get a triple boot working perfectly. I can't imagine your EMMC is too small for 3 boot images.
Sent from my Galaxy Nexus using Tapatalk 2
I wanted to follow up these great instructions by adding that there is a way to do this if you are already dual booting Webos and Android.
I followed the instructions here http://code.google.com/p/hp-touchpad-ubuntu/wiki/Installation and had no trouble with a preexisting install of Android CM9 and Moboot. Smooth and easy as pie. I also was able to easily uninstall using the provided uninstall script.
Just wanted to let people know that if you are already dual booting you can add Ubuntu with no worry of breaking a preexisting dual boot or having to Doctor anything.
VitaZora said:
I wanted to follow up these great instructions by adding that there is a way to do this if you are already dual booting Webos and Android.
I followed the instructions here http://code.google.com/p/hp-touchpad-ubuntu/wiki/Installation and had no trouble with a preexisting install of Android CM9 and Moboot. Smooth and easy as pie. I also was able to easily uninstall using the provided uninstall script.
Just wanted to let people know that if you are already dual booting you can add Ubuntu with no worry of breaking a preexisting dual boot or having to Doctor anything.
Click to expand...
Click to collapse
I tried this a while back but it always bricked my device :/. And this is coming from an advanced Linux user.
Sent from my Galaxy Nexus using Tapatalk 2
ok so ubuntu doesn't work as the root password...
edit: nevermind
bbm21 said:
ok so ubuntu doesn't work as the root password...
Click to expand...
Click to collapse
Ubuntu disables root by default. You can enable it by typing "sudo passwd".
Sent from my Galaxy Nexus using Tapatalk 2
I'm wanting to do this but I am not up to date on the status of the Ubuntu port. What is actually not working at this point? Do I have to have a usb mouse and keyboard to set up ubuntu or can i use the touch screen? Can you play videos and such correctly in ubuntu?
You don't need them but they are preferred. Audio, mic, camera, and compositing are a few major bugs.
Sent from my aokp_tenderloin using Tapatalk 2
Please pardon my ignorance... is the Arch Linux implementation more complete? You didnt mention if the Ubuntu port required external keyboard / mouse or actually had touchscreen support.
babcocca said:
Please pardon my ignorance... is the Arch Linux implementation more complete? You didnt mention if the Ubuntu port required external keyboard / mouse or actually had touchscreen support.
Click to expand...
Click to collapse
Touch does work, or at least it did for me, but laggy. After the initial wireless fix I was also able to connect to wifi and bluetooth devices. I connected and used a bluetooth keyboard. Did not test a BT mouse but it probably works as well. I was also able to connect to wifi after the fix, but after another reboot, I could not connect to wifi again. My Touchpad saw my wireless but could not connect.
It's amazing that Ubuntu works as well as it does at this point, but for me, it's not useful enough to keep without a consistent wifi connection.
Which version of ubuntu is this?
jamesissocool said:
Which version of ubuntu is this?
Click to expand...
Click to collapse
11.10
Sent from my Galaxy Nexus using Tapatalk 2
Pardon me for sounding ignorant/stupid, but how do I open WebOS Doctor? It's a .jar file and I'm unsure what to do with it.
Mafuzzer said:
Pardon me for sounding ignorant/stupid, but how do I open WebOS Doctor? It's a .jar file and I'm unsure what to do with it.
Click to expand...
Click to collapse
Right click and open with Java.
Sent from my Galaxy Nexus using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tracked down the author of this. He likes coffee.
Sent from my Galaxy Nexus using Tapatalk 2
Gahh Its Lee said:
I tracked down the author of this. He likes coffee.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That guy has an epic beard and rocks AOKP. Obviously he's amazing.
Sent from my Galaxy Nexus using Tapatalk 2
Android Batch File to Partition SD Card
This batch command file invokes the /sbin/parted and /sbin/tune2fs tools hosted by ClockWorkMod (CWM) Recovery 5.0.2.0 to control partitioning of your SD card for a variety of purposes, some of which are listed below.
It is a good idea to review the command line options and parameters of the parted and tune2fs tools: On your phone (for example, via computer-enabled ADB or terminal emulator), get root and enter:
# /sbin/parted --help
# /sbin/tune2fs --help
I decided to make this a separate thread for a number of reasons:
Streamline the process of making room for second ROM in a dual boot configuration (see http://forum.xda-developers.com/showthread.php?t=1651356 ). These commands can theoretically be rolled into a flashable zip to almost fully automate a dual-boot install of fixed ROMs, e.g. CM9 and CM7.
My Dual Boot threads have “sensory overload” written all over them
The amount of material presented here is probably enough to warrant a separate thread
This is an Android-friendly alternative to GParted/MiniTool. For example there is no need to pull SD card, partition and reinsert. Of course, GParted has the pleasant GUI and gives you a chance to review your changes before committing, whereas the Android “parted” tool is highly utilitarian.
Batch commands are quickly and easily modified to create/remove/adjust partitions. The general consensus is that for large files, ext3 R/W speeds are faster than those of FAT32. And ext3[4] is more stable and can handle files exceeding the maximum 4GB allowed by FAT32.
Batch commands are easily modified to perform customizations other than dual boot
Some users may wish to host their entire system on SD card: ROM, music, pictures, movies etc.
Some users may wish to return their SD cards to a traditional single-boot state by running a subset of these batch commands
That said, I strongly advise that you NOT run these commands UNLESS you are comfortable with ALL of the following:
1. /sdcard (FAT32) and ALL subdirectories copied to /emmc/sdcard-backup. Ask yourself: Do I have enough space left on my 10GB emmc partition to host a full backup of /sdcard? AND, will there be enough room on the /sdcard filesystem to restore this backup AFTER downsizing my SD card's FAT32 partition?
2. Any existing ext* partitions of SD card are blown away, for example those generated by a previous dual boot zip install. In other words, you lose /system, /cache and /data from an existing sdcard-based ROM.
3. You MAY lose all data on your (backed-up) FAT32 partition depending on what boundaries were used for resizing.
Note that I do not include a command to push /emmc/sdcard-backup back onto SD card. That is because:
There may not be enough room on /sdcard after a FAT32 downsize, and
There may be a data conflict when flashing a different dual boot configuration as opposed to an updated one. But at least there is a full backup of /sdcard FAT32 --- assuming emmc has enough room to host it.
Presently there is no logic to detect the storage limits of the /emmc and /sdcard filesystems. I will leave that to you.
SO... if for ANY reason you are NOT comfortable with the potential changes outlined above, I recommend that you please STOP HERE and consider researching this topic further until you are comfortable.
For those willing and able to give this a try, I strongly recommend first performing an ADB-assisted run (i.e. with a computer hosting Android SDK Platform Tools) using an SD card with at least 4GB open (to be safe) AND with enough room on emmc to host a FULL backup of your entire /sdcard filesystem (/sdcard and all its subdirectories).
Fully charge your battery! CWM draws a lot of current, even if nothing else is running.
Boot phone to CWM
Connect phone to computer
Launch ADB shell to access phone
# adb shell (can do this on any ADB-enabled machine)
Get root (enter “su” at phone shell command prompt) and copy/paste/enter each and every command (those not prefixed by "echo") in your computer's command window:
Code:
#! /bin/sh
echo "Android batch script to create ext partitions for SD card-based ROM"
echo
echo "First unmount all filesystems of primary (emmc) ROM"
umount /system > /dev/null 2>&1
umount /cache > /dev/null 2>&1
umount /data > /dev/null 2>&1
echo
echo "Mount external (sdcard) and internal (emmc) memory"
mount /sdcard > /dev/null 2>&1
mount /dev/block/mmcblk0p18 /emmc > /dev/null 2>&1
echo
echo "Create sdcard-backup directory on emmc with current date and time"
echo "Recommend delete any unnecessary backups of sdcard at this point"
bkdir="sdcard-backup-`date +%d-%b-%Y-%H%M%S`"
mkdir /emmc/$bkdir > /dev/null 2>&1
echo
echo Backup directory: /emmc/$bkdir
echo
echo "Press ENTER to continue..." ; read
echo
echo "Backing up contents of sdcard FAT32 to emmc"
cp -a /sdcard/* /emmc/$bkdir/
echo
echo Done...
ls -ld /emmc/$bkdir
echo
echo "Unmount internal and external memory"
umount /emmc > /dev/null 2>&1
umount /sdcard > /dev/null 2>&1
echo
echo "Show existing partition map of SD card"
parted /dev/block/mmcblk1 print
echo
echo "Press ENTER to continue..." ; read
echo
echo "Delete any existing ext* partitions and show results"
parted /dev/block/mmcblk1 rm 4 > /dev/null 2>&1
parted /dev/block/mmcblk1 rm 3 > /dev/null 2>&1
parted /dev/block/mmcblk1 rm 2 > /dev/null 2>&1
parted /dev/block/mmcblk1 print
echo
echo "Press ENTER to continue..." ; read
echo
echo "Resize START/STOP values MUST be expressed in MB"
echo "Downsize FAT32 and generate new ext2 partitions"
echo "Resize START/STOP values MUST be expressed in MB!"
echo "This example shows TYPICAL repartitioning of 16GB card..."
parted /dev/block/mmcblk1 resize 1 4.194 10700
parted /dev/block/mmcblk1 mkpartfs primary ext2 10.7GB 11.1GB
parted /dev/block/mmcblk1 mkpartfs primary ext2 11.1GB 11.8GB
parted /dev/block/mmcblk1 mkpartfs primary ext2 11.8GB 13.9GB
echo
echo "Upgrade from ext2 to ext3"
tune2fs -j /dev/block/mmcblk1p2
tune2fs -j /dev/block/mmcblk1p3
tune2fs -j /dev/block/mmcblk1p4
echo
echo "Review changes"
parted /dev/block/mmcblk1 print
echo
echo "Press ENTER to continue..." ; read
echo
echo "Final review. Mount SD card ROM filesystems"
mount /dev/block/mmcblk1p2 /system > /dev/null 2>&1
mount /dev/block/mmcblk1p3 /cache > /dev/null 2>&1
mount /dev/block/mmcblk1p4 /data > /dev/null 2>&1
echo
echo "Show used and available space (in MB) on all mounted filesystems"
df -m
echo
echo "Unmount SD card ROM filesystems"
umount /system
umount /cache
umount /data
echo
echo "Remount emmc ROM /cache (CWM mounts this by default)"
mount /cache > /dev/null 2>&1
echo
echo "Done. Can now (if necessary) wipe /cache and /data for primary ROM and flash dual boot zip"
echo
And now ... here are unedited results of a successful batch run made on 11 Jun 2012 at 1630 PDST
Code:
~ # sh /tmp/part-sdc.sh
Android batch script to create ext partitions for SD card-based ROM
First unmount all filesystems of primary (emmc) ROM
Mount external (sdcard) and internal (emmc) memory
Create sdcard-backup directory on emmc with current date and time
Recommend delete any unnecessary backups of sdcard at this point
Backup directory: /emmc/sdcard-backup-11-Jun-2012-233034
Press ENTER to continue...
Backing up contents of sdcard FAT32 to emmc
Done...
drwxrwxrwx 16 root root 8192 Jun 11 23:36 /emmc/sdcard-backup-11-Jun-2012-233034
Unmount internal and external memory
Show existing partition map of SD card
Model: SD SU16G (sd/mmc)
Disk /dev/block/mmcblk1: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 10.7GB 10.7GB primary fat32 lba
2 10.7GB 11.1GB 395MB primary ext2
3 11.1GB 11.8GB 707MB primary ext2
4 11.8GB 13.9GB 2097MB primary ext2
Press ENTER to continue...
Delete any existing ext* partitions and show results
Model: SD SU16G (sd/mmc)
Disk /dev/block/mmcblk1: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 10.7GB 10.7GB primary fat32 lba
Press ENTER to continue...
Resize START/STOP values MUST be expressed in MB
Downsize FAT32 and generate new ext2 partitions
Resize START/STOP values MUST be expressed in MB!
This example shows TYPICAL repartitioning of 16GB card...
Information: You may need to update /etc/fstab.
Information: You may need to update /etc/fstab.
Information: You may need to update /etc/fstab.
Information: You may need to update /etc/fstab.
Upgrade from ext2 to ext3
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
Review changes
Model: SD SU16G (sd/mmc)
Disk /dev/block/mmcblk1: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 10.7GB 10.7GB primary fat32 lba
2 10.7GB 11.1GB 395MB primary ext3
3 11.1GB 11.8GB 707MB primary ext3
4 11.8GB 13.9GB 2097MB primary ext3
Press ENTER to continue...
Final review. Mount SD card ROM filesystems
Show used and available space (in MB) on all mounted filesystems
Filesystem 1M-blocks Used Available Use% Mounted on
tmpfs 408 0 408 0% /dev
/dev/block/mmcblk1p2 353 8 326 2% /system
/dev/block/mmcblk1p3 632 16 582 3% /cache
/dev/block/mmcblk1p4 1874 32 1742 2% /data
Unmount SD card ROM filesystems
Remount emmc ROM /cache (CWM mounts this by default)
Done. Can now (if necessary) wipe /cache and /data for primary ROM and flash dual boot zip
~ #
All you brave testers out there, please let me know if you see anything amiss. Thanks!
Disclaimer
Standard disclaimers apply. In short, I am not responsible for any harm you or your phone may incur by using any or all of this material.
Enjoy.
References
http://androidos.in/2009/11/manually-partition-sd-card-for-android/
http://www.gnu.org/software/parted/manual/html_chapter/parted_2.html
http://linux.die.net/man/8/tune2fs
Successfully Installed Dual Boot After Running Batch SD Card Partitioner
Shortly after running Android Batch SD Card Partitioner, I successfully flashed Dual Boot Zip v1.4: http://forum.xda-developers.com/showthread.php?t=1651356 featuing AOKP+Aroma_37a (emmc) and CM7 RC3 (sdcard)
don't know if that is the correct place
Hello,
Thanks for your patch, I am facing an issue with my Atrix (Orange UK), I have scrued up my internal storage, here I have posted once a Question but got no reply from nobody (POST).
Am I right to ask here, or is it wrong place too
Thanks and Thumbs up for the nice work
Ammar
Arwany said:
Hello,
Thanks for your patch, I am facing an issue with my Atrix (Orange UK), I have scrued up my internal storage, here I have posted once a Question but got no reply from nobody (POST).
Am I right to ask here, or is it wrong place too
Thanks and Thumbs up for the nice work
Ammar
Click to expand...
Click to collapse
Hello Ammar,
Please see my answer here: http://forum.xda-developers.com/showthread.php?p=27311205#post27311205
I hope this helps
sendust7
Hi,
I succesfullly rooted my Nook glowlight, but when I tried to go back to stock with my nook backup I found the backup was not ok (just 77MB) and now I have a bricked NSTG that won't get past the "Install Failed" screen.
I've tried almost every method I could find in the forums, but none worked for me.
Is there anything else beside n2T and Alpha-Format I could try to revive my device?
TIA
I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.
If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.
I'm sure somebody has other ways to get shell access.
Renate NST said:
I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.
If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.
I'm sure somebody has other ways to get shell access.
Click to expand...
Click to collapse
thanks for that I'll give it a try...
Sadly, I'm on a W7 box (not mine) and all I can see in the device manager is a nook with a yellow sign in it
ADB devices returns a blank list....
I tried updating the drivers for the nook: first uninstalled anything nooklike with usbdeview, and then pointed W7 to a folder where I had downloaded usbdrivers from this thread http://forum.xda-developers.com/showthread.php?t=1354487 but W7 keeps telling there are no drivers for nook in that folder.
If I boot without SD then the nook is recognized and USB drivers install fine. It's booting with CWM that the device is not recognized.
Stuck
There are drivers and drivers.
As a composite USB device the Nook uses both the stock Windows Mass Storage driver and the Google ADB driver.
See: http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
Renate NST said:
There are drivers and drivers.
As a composite USB device the Nook uses both the stock Windows Mass Storage driver and the Google ADB driver.
See: http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
Click to expand...
Click to collapse
It worked:
D:\nook_root\adbshell>adb devices
List of devices attached
11223344556677 recovery
D:\nook_root\adbshell>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
4 heads, 16 sectors/track, 59776 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ #
completely noob with the nook, can't seem to find /rom and Win32DiskImager does not find a device to read from to perform said backup
The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 0c 1 38 79,691,776 /boot
mmcblk0p2 vfat 0c 39 46 16,777,216 /rom
mmcblk0p3 ext2 83 47 141 199,229,440 /factory
mmcblk0p4 05 142 926 1,646,264,320
mmcblk0p5 ext2 83 142 285 301,989,888 /system
mmcblk0p6 vfat 0c 286 405 251,658,240 /media
mmcblk0p7 ext3 83 406 525 251,658,240 /cache
mmcblk0p8 ext3 83 526 926 840,957,952 /data
Unused 927 933 14,680,064
Renate NST said:
The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 0c 1 38 79,691,776 /boot
mmcblk0p2 vfat 0c 39 46 16,777,216 /rom
mmcblk0p3 ext2 83 47 141 199,229,440 /factory
mmcblk0p4 05 142 926 1,646,264,320
mmcblk0p5 ext2 83 142 285 301,989,888 /system
mmcblk0p6 vfat 0c 286 405 251,658,240 /media
mmcblk0p7 ext3 83 406 525 251,658,240 /cache
mmcblk0p8 ext3 83 526 926 840,957,952 /data
Unused 927 933 14,680,064
Click to expand...
Click to collapse
mmmm, a bit risky isn't it ?
I think I'll read the rest of the internets before proceeding I need to understand this.....
thanks again
srgarfi said:
mmmm, a bit risky isn't it ?
Click to expand...
Click to collapse
Well, you don't have anything at all in your partition table, not even the correct CHS.
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.
Renate NST said:
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.
Click to expand...
Click to collapse
Oh, ah, that changes everything! It's worth a try.
I need to find a dummy guide to perform this operations, any clues?
Edit: Found this, looks like a start http://forum.xda-developers.com/showthread.php?t=1279091
thanks again
booted in gparted live and took a peek at the Nook. This is what I found (sorry I don't know yet how to post images):
Device information
Model: B&N Ebook Disk
Size: 182 GiB
Path: /dev/sdb
Partition table: msdos
Heads: 255
Sectors/track: 63
Cylinders: 238
Total sectors: 3825664
Sector size: 512
Physical characteristics being so different I'm affraid trying to convert heads/cylinders from Renate's Touch to my Glo schema would be useless.
Could someone with a NSTG please share partition information?
Thank you all,
srgarfi said:
Physical characteristics being so different...
Click to expand...
Click to collapse
Well, they are not real physical differences.
You can juggle heads and sectors/track as long as the size of a cylinder stays the same.
It may be that the Glow has gone to a bigger cylinder, but it's suspicious that it's not a power of two.
Renate NST said:
You can juggle heads and sectors/track as long as the size of a cylinder stays the same.
Click to expand...
Click to collapse
Not good at math, I can't get an exact match
Here is a script that will partition your Nook internal SD card like the listing above.
You can either copy this to the SD card, chmod 777 it and run it
or just copy and paste it to the Windows command line window running ADB.
Then you can try some mounts and see what you've got.
(nookpart.sh is zipped.)
was about to try the script (thanks again!) but nook is stuck at "rooted forever" screen and nothing I do awakes it: power on, power on 30 sec, power on and n, plug it to pc, and every combination. Took off the sd and tried combinations again, nothing. I've searched a bit and all other cases resumed to reboot by pressing long power. Not this one....no hard reset available? Every piece of equipment must have a big red switch =)
Should I stop messing around and buy another one? (not in the states anymore, it will take like 40+ days to deliver here...)
EDIT: false alarm, battery was too low to power on. Where did the full charge go? I dunno....30 more minutes before I can try
Renate NST said:
Here is a script that will partition your Nook internal SD card like the listing above.
You can either copy this to the SD card, chmod 777 it and run it
or just copy and paste it to the Windows command line window running ADB.
Then you can try some mounts and see what you've got.
(nookpart.sh is zipped.)
Click to expand...
Click to collapse
Executed the script:
Code:
D:\nook_root\adbshell>adb shell sh /sdcard/nookpart.sh
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-934, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (39-934, default 39): Using default value
39
Last cylinder or +size or +sizeM or +sizeK (39-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (47-934, default 47): Using default value
47
Last cylinder or +size or +sizeM or +sizeK (47-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Selected partition 4
First cylinder (142-934, default 142): Using default value 142
Last cylinder or +size or +sizeM or +sizeK (142-934, default 934):
Command (m for help): First cylinder (142-926, default 142): First cylinder (142
-926, default 142): Using default value 142
Last cylinder or +size or +sizeM or +sizeK (142-926, default 926):
Command (m for help): First cylinder (286-926, default 286): First cylinder (286
-926, default 286): Using default value 286
Last cylinder or +size or +sizeM or +sizeK (286-926, default 926):
Command (m for help): First cylinder (406-926, default 406): First cylinder (406
-926, default 406): Using default value 406
Last cylinder or +size or +sizeM or +sizeK (406-926, default 926):
Command (m for help): First cylinder (526-926, default 526): First cylinder (526
-926, default 526): Using default value 526
Last cylinder or +size or +sizeM or +sizeK (526-926, default 926):
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 1 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 2 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 6 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8):
Command (m for help):
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
D:\nook_root\adbshell>
From CWM tried to mount /boot and failed. Took off the SD, booted nook (fingers crossed) and it displayed the "install failed" screen.
Nice try, thanks for the patience :good:
No, that's what I expected.
The partitioning worked fine
You had already bashed the boot partition.
Now try:
Code:
mkdir /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
ls -l /rom
Looks like there was already a /rom
Code:
D:\nook_root\adbshell>adb shell
~ # mkdir /rom
mkdir /rom
mkdir: can't create directory '/rom': File exists
~ # mount -t vfat /dev/block/mmcblk0p2 /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
mount: mounting /dev/block/mmcblk0p2 on /rom failed: Device or resource busy
~ # ls -l /rom
ls -l /rom
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #
Hmm, I thought of that at the last moment.
Code:
mkdir /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
ls -l /stuff
Renate NST said:
Hmm, I thought of that at the last moment.
Code:
mkdir /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
ls -l /stuff
Click to expand...
Click to collapse
yes, works, but I don't get it?
Code:
~ # mkdir /stuff
mkdir /stuff
~ # mount -t vfat /dev/block/mmcblk0p2 /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
~ # ls -l /stuff
ls -l /stuff
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #
in the meantime I booted noogie and did a backup of the semibricked nook just in case.... =)
Now I'll write CWM to the SD and boot again
That means that the partitioning is correct and that your /rom is intact.
Make a good backup of your personalized stuff:
Code:
adb pull /stuff
Now you have to fix up the boot partition.
I'd probably try to install the factory.zip
Code:
mkdir /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
ls -l /fact
Code:
adb pull /fact/factory.zip
adb pull /fact/rombackup.zip
Then copy factory.zip to the external SD card and do a CWR update with that.
>>> Please note that Vashiru reworked this guide for reliability and alternate values, so I recommend you check his various posts in this thread starting with this one. <<<
Click to expand...
Click to collapse
THE PROBLEM
As many of us have noticed, it is fairly easy to get an "Out of space" message when installing apps on our phones because, for some weird reason, Oppo decided that the storage part of the device should linger in the dark ages, when /userdata and /sdcard were separate partitions and you only had 2GB of data storage, even if your phone was a 32GB model.
Now, imagine that you are running KitKat and would like to try ART. This may be a bad idea as, if your data partition is more than 30% full, you will find that while converting your apps to this new format, Android will run out of space.
At OppoForums, a few bright people started looking into the issue and, of course, there is a way to improve the situation.
WARNING!
If you follow the steps below correctly, you should not run in any trouble. If you do not, however, you may end up spending much more time fixing your phone.
FIRST, THE THANKS SECTION
Anders tinkered with his device’s partition table until he got to where he had grown the /userdata partition to something useable. Yes, it’s some people’s definition of “play”
Jousa11 is the first person trying to put a guide together explaining the steps to reproduce Anders’ work. WARNING: I did no get to see said guide as Jousa quickly deleted it due to the risks involved. So, take that in account!
Rockman for providing the last resort rescue tools in case you brick your phone
Lucky for providing the WiFi fix
Please let me know if you are not on this list and I forgot to give you credit!
YOU WILL NEED
The hardware:
An Oppo Find5 phone(!)
A computer (Windows/Linux/Mac) with adb installed and working
A USB cable
On your computer:
adb
[Optional] fastboot
On your phone (SDCard):
parted + mke2fs + tune2fs
mmcblk0p21_persist_ext4.img
openrecovery-twrp-2.6.3.0-find5-TP-patch.img
[Optional] gdisk
You will use parted to work on your partition table; mke2fs and tune2fs to create ext4 filesystems on some of these partitions (parted does not know how to create ext4 partitions)
mmcblk0p21_persist_ext4.img is an image that you need to restore your /persist partition and avoid issues such as non-working WiFi.
openrecovery-twrp-2.6.3.0-find5-TP-patch.img is a patched recovery image. I know: you already have a recovery image if you are going through these steps. However, we are going to wipe it so you want to install this guy before rebooting. Note that if you forget, you can always flash it later using fastboot.
On your computer:
adb to access your phone recovery, push files to SDCard, reboot...
[Optional] fastboot. You will only need fastboot if you mess up your recovery partition.
WHAT IF SOMETHING GOES AWFULLY WRONG?
You may “brick” your phone. Apparently it’s near impossible to hard brick your Find5, though. See below.
First, Anders recommends making a backup of your partition table. I didn’t because I felt that if I messed something up, it would be a partitions’ content rather than the partition table but that’s not the wisest approach.
Furthermore, if you are really worried about what stilly error your fat fingers will cause (I know I should be!) you can also backup your partitions.
Backing up your partition table:
On your phone:
Code:
gdisk -b /sdcard/gpt.bin /dev/block/mmcblk0
Backing up a single partition:
On your phone:
Code:
dd if=/dev/block/mmcblk0p<partition id> of=/sdcard/backup-<partition id>.bin
On your computer:
Code:
adb pull /sdcard/gpt.bin
adb pull /sdcard/backup-<partition id>.bin
LAST RESORT
OK. So, you've bricked your phone. Now what?
First, you will need Windows. So if you're on a Mac or Linux and have no access to a Windows machine/VM, er..don't brick your phone.
- Download drivers and tools
- Download and follow the instructions
READY ? LET'S GET STARTED
>>>>>>>>>>>> First, Download The Files <<<<<<<<<<<<
Then...
On your computer:
UPDATE As dixxa pointed out, mke2fs and tune2fs may already be present on your device. It was not the case for me but you should check first; it seems like a good idea to use existing binaries.
Code:
adb reboot recovery
adb push parted /sbin
adb push mke2fs /sbin
adb push tune2fs /sbin
On your phone:
Code:
chmod 755 /sbin/parted /sbin/mke2fs /sbin/tune2fs
umount /cache
umount /sdcard
umount /emmc
umount /data
parted /dev/block/mmcblk0
You are now in the parted shell.
CAREFUL! Do not delete any partition below 20 or you will enter "Big Oops" territory. I recommend typing carefully and, yes, staying away from copy/paste operations that may swallow a character like, say, the '2' in '20'
Note that the size value I am using here is '4GB' for /userdata (rather than 2GB). I guess you could make /userdata bigger than 4GB, in which case you would have to recompute all the offsets in the commands below(!)
Code:
# rm sdcard
rm 29
# 28 thru 23 are reserved
rm 28
rm 27
rm 26
rm 25
# rm recovery
rm 24
# rm misc
rm 23
# rm cache
rm 22
# rm persist
rm 21
# rm data/emmc
rm 20
# now, re-create partitions but data is bigger
mkpart primary 1325 5421
name 20 userdata
mkpart primary 5421 5430
name 21 persist
mkpart primary 5430 5967
name 22 cache
mkpart primary 5967 5968
name 23 misc
mkpart primary 5968 5979
name 24 recovery
mkpart primary 5979 6012
name 25 reserve1
mkpart primary 6012 6019
name 26 reserve2
mkpart primary 6019 6028
name 27 reserve3
mkpart primary 6028 6062
name 28 reserve4
mkpart primary 6062MB 100%
name 29 sdcard
# exit parted shell
q
Let's create a file system on the partitions that require one. Note that I am formatting the SDCard using VFAT as, yes, EXT4 is a better FS, but it is also incompatible with Oppo's ROM and some apps may not require the proper permissions etc.
Code:
# Notes:
# -m 0: no reserved blocks
# -c 0: no max mount count
# -C -1: no mount count
# -i -1: max_int interval between checks
mke2fs -t ext4 -m 0 -L userdata /dev/block/mmcblk0p20
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p20
mke2fs -t ext4 -m 0 -L persist /dev/block/mmcblk0p21
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p21
mke2fs -t ext4 -m 0 -L cache /dev/block/mmcblk0p22
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p22
# Hey look it’s an ext4 SDCard!
mke2fs -t ext4 -m 0 -L sdcard /dev/block/mmcblk0p29
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p29
# Actually to avoid errors like unable to write to root of sdcard:
mkdosfs -n sdcard -F 32 /dev/block/mmcblk0p29
mount -t vfat /dev/block/mmcblk0p29 /sdcard
At this point, we have clobbered the /persist partition and this could cause issues as mentioned earlier. Let's restore it.
Code:
# Restore /persist partition
mount -t ext4 /dev/block/mmcblk0p29 /sdcard
# On computer
adb push mmcblk0p21_persist_ext4.img /sdcard/
# On phone
dd if=mmcblk0p21_persist_ext4.img of=/dev/block/mmcblk0p21
IMPORTANT! Flash your recovery partition now. If you wait until after rebooting, you will need to use fastboot instead.
Code:
# Recovery partition: on computer
adb push openrecovery-twrp-2.6.3.0-find5-TP-patch.img /sdcard/
# On phone
dd if=openrecovery-twrp-2.6.3.0-find5-TP-patch.img of=/dev/block/mmcblk0p24
Admire your work
Code:
parted /dev/block/mmcblk0 print
Reboot into your new recovery and install your favorite ROM
FAQ
Q: Is this dangerous?
A: Yes. Yes, it is.
Q: Any tip?
A: Yes. Follow these instructions carefully and if something wrong happens, unless you know what you are doing, leave your device alone and come here to ask for help.
Q: Can I hold you responsible for any damage to my phone/etc?
A: As usual, the answer is 'No'
Q: I found an error in your write-up!
A: Please let me know immediately.
-Chris.
You should probably use the latest TWRP 2.6.3.1 found here: http://techerrata.com/file/twrp2/find5/openrecovery-twrp-2.6.3.1-find5.img
Looks good to me. Just be very carefully doing this.
Sent from my Find 5 using xda app-developers app
gdisk -b /sdcard/gpt.bin /dev/block/mmcblk0
those commands need to be typed in recovery even that one ?
Yes although I imagine this particular command should also work when booting system.
Sent from my Find 5 using Tapatalk
This thread is fine the only problem here is with those 2 binaries: mke2fs and tune2fs
You don't need to push them or chmod them since they are already in the recovery
Except that that thread is perfect.
Since we're at toying with partition, can't we merge the partitions in some way ?
Just wondering is there any way to build a script to do this in an automated way thus avoiding user errors and typos?
There is a thread on the oppo forums
http://www.oppoforums.com/threads/guide-resizing-internal-storage-on-find-5-32gb.8361/
Hello everyone,
is the guide for the 32 or 16 gb model?
I have 16 gb Oppo find 5.
Thanks.
PS: what "on your phone" is supposed to mean"?
Click to expand...
Click to collapse
If you don't know what does that mean don't do it you'll screw your phone.
hi
Please would you make something like this for oppo find 7a x9006?
thanks
Anyone willing to recompute all the offsets dor just one 16gb partition?
Scribed henceforth from thy G pad.
Hi all, I am trying to do this mod and I am half way through it with a problem
I am stuck on the new file system, I cannot use mke2fs or tune2fs, i get
Code:
mke2fs: not found
like it doesn't even exist, but it does I can see it. I get the same error for tune2fs. but parted and gdisk work fine.
Yes I did push them and chmod 755 them.. and I have tried running it from the /sbin directory.
Help!
Hello!
I'm getting the same error over and over again creating /dev/block/mmcblk0p21 to /dev/block/mmcblk0p22:
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p21
"Bad magic number in super-block while trying to open /dev/block/mmcblk0p21"
"Couldn't find valid filesystem superblock"
So i can't create a file system on the created partitions. I have been looking everywhere for an answer. Somebody have an idea?
U should just wait. Andrew dodd found a way to make find7a have unified partition and he claims he can make it work on find5 as well. Let's give him a bit to figure it out tho.
Scribed henceforth from thy G pad.
Gdisk not working...
Ok guys sort of a noob here... Firstly, totally appreciate what you guys are doing here... I wants it bad, thass why i'm here.
So far... I have i have done...
"adb reboot recovery"
"adb push gdisk /sbin"
I figured that's how you are supposed to install it ... hope i'm not wrong, but i guess it pushed through fine
But after rebooting to system in TWRP , i opened terminal emulator and when i use the command
"gdisk -b /sdcard/gpt.bin /dev/block/mmcblk0"
I get ...
"/system/bin/sh: gdisk: not found"
now i'm too scared to proceed without backing up the partition tables... so please help...
edit - FYI , i'm running the last build of Asylum Carbon... should i just go back to latest oopo stable stock rom and then root my device again and then try all this again... would that help... ???
Directly from Andrew Dodds g+ " IT HAS BEGUN.
The first phase of Find 7a/7s LVM testing is here.* See linked post for details.* (Sorry to disappoint, but the first phase is "make sure we don't break existing configurations")
Once this phase is complete, the remaining list is:
Fix up the remaining TWRP issues (make RECOVERY_SDCARD_ON_DATA runtime instead of compile-time)
Make user-friendly conversion processes
Once things are solid on Find 7, I'll work on Find 5 and N1."
Stay thirsty my friends. Good things ahead
Sent from my A0001 using Tapatalk
Does this work for the 16gb model?
Can someone help please?
I'm trying to do this, but after enter in parted [parted /dev/block/mmcblk0] when i try to do "rm 29", i get "can't remove 29: no such file or directory
I'm doing the "on your phone" commands in TWRP command line., is that correct?
I'm running stable colorOS 1.0.9i
Finally I finish the process.
My notes:
Goal:
Keep my current system intact (stable colorOS 1.0.9i , because i have no patience to format, install a new ROM and reinstall/recofigure everything
So I backup everything on phone with TWRP and I push sdcard content (wich include the system backup i made) with ADB
1 - If I push mke2fs and tune2fs IT WILL NOT WORK. I flash the last find 5 recovery (openrecovery-twrp-2.8.1.0-find5.img) and I dont push or chmod anyting, parted, mke2fs, tune2fs are all already in the recover and that's the only way I could run mke2fs and tune2fs
edit: 1.5 - The phone commands had to be enter via ADB shell. In TWRP command line, after you enter in parted it will not accept commands.
2 - To "rm 29", i had to "umount /dev/block/mmcblk0", otherwise "rm 29" fail due to partition in use
3 - after this instruction:
mount -t vfat /dev/block/mmcblk0p29 /sdcard
(the last one on the 4 block of code)
We have this:
# Restore /persist partition
mount -t ext4 /dev/block/mmcblk0p29 /sdcard
This instruction was the only one that give me a error, so I move to the next ones.
The error was that the partition was busy, what makes senses because in the last instruction we mount the same partition on the same folder but with different file system!!??
So I move to the next instruction. I have no idea if it's a instructions mistake but it looks like, because it says "# Restore /persist partition" but the command has nothing to do with /persist
4 - FINISH
5 - Reboot in recovery. Push sdcard backup to /sdcard. restore system backup with TWRP restore
Voila, my phone exactly as before but with 3,76GB for APPS. Finally!!! The "running out of space" message on a flagship quad-core 2GB RAM phone!!!!!!?????? Was driving me CRAZYYYYY
Thanks Fickx for the up to date information, I just did my re-partition successfully, here's what I did:
- Use Rashr update the recovery to twrp-2.8.1.0
- reboot into recovery
- connect to PC (Make sure adb works, "adb devices")
- on PC:
> adb shell
> umount /cache
> umount /sdcard
> umount /emmc
> umount /data
> umount /dev/block/mmcblk0p29
> parted /dev/block/mmcblk0
> rm 29
>...
> rm 20
> mkpart primary 1325 5421
> name 20 userdata
> ...
> name 29 sdcard
> q
> mke2fs ...
> ...
> mount -t -vfat /dev/block/mmcblk0p29 /sdcard
Open another PC command terminal
> adb push mmcblk0p21_persist_ext4.img /sdcard/
> adb push openrecovery-twrp-2.8.1.0-find5.img /sdcard/
Back to original terminal in "adb shell".
> dd if=/sdcard/mmcblk0p21_persist_ext4.img of=/dev/block/mmcblk0p21
> dd if=/sdcard/openrecovery-twrp-2.8.1.0-find5.img of=/dev/block/mmcblk0p24
> exit
> adb reboot recovery
Flash the rom.