[Q] how to set up Android as a primary booting os - TouchPad Q&A, Help & Troubleshooting

So the question is:
how to set up Android as a primary booting os?
There is a solution, maybe somebody can share ?
Thanks!

Android is normally the OS that boots by default when you first install it, but if it is not on yours I guess you could try this method (in reverse, since it is a guide to boot webOS by default):
http://forum.xda-developers.com/showthread.php?t=1435318
Or if you have preware on webOS, install an app called CyBoot and its super easy to change.

ANtiHazarD said:
So the question is:
how to set up Android as a primary booting os?
There is a solution, maybe somebody can share ?
Thanks!
Click to expand...
Click to collapse
Do the following from terminal emulator app or adb:
su -
mount -o rw,remount /
mkdir /boot
mount /dev/block/mmcblk0p13 /boot
echo "Cyanogenmod" > /boot/moboot.default

install cyboot from webos and make android default. now, if android goes to a boot loop for some reason, u are stuck in android unless you know how to fix it. you'll have to weigh your options.

Related

[HOW-TO] Run Debian Armel on your N1

Hi all!
I want to share the way i have to run Debian on Nexus One
I'm editing my own install of deb-armel and ill upload to everyone but first i need to finish it
By now, we will use a qemu image ready and edit it to your needs
You'll need a SD parted with Amon_RA recovery, few files i'll upload later and some skills with Debian, of course hehe
Partition could be user-alike but i recommend:
Im using a microsdhc 8gb class-2 from my magic
- EXT3: 2gb (nice for install a lot of stuff)
- SWAP: 150MB
- The rest as fat32
You need also a rom with app2sd or mount ETX3 partition under /system/sd, im using Modaco's 1.3
First of all, im working on archlinux but this can be done on windows too using the qemu version for windows
Install qemu on your machine.
NOTE: Also you can start a new installation from 0 using images (iso) and info found on google
Now we will use the following QEMU images:
http://people.debian.org/~aurel32/qemu/armel/
We will download the followings Of course you can choose the small or normal version with X preinstalled (the X version preinstalled is not tested by me and i dont know if works)
debian_lenny_armel_small.qcow2 150M
initrd.img-2.6.26-1-versatile 2.1M
vmlinuz-2.6.26-1-versatile 1.2M
Put they in your home folder or where u want.
Now, lets run it.
Use the following command (run it from the folder you have the downloaded files) :
qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.26-1-versatile -initrd initrd.img-2.6.26-1-versatile -hda debian_lenny_armel_small.qcow2 -append "root=/dev/sda1"
Wait a moment... Debian-armel running under qemu
Here are the configuration by default:
- Keyboard: British English
- Language: English
- Mirror: ftp.uk.debian.org
- Hostname: debian-armel
- Root password: root
- User account: user
- User password: user
Edit the system to fit your needs, im not going to explain how to do this, im asumming you know how to. If u don't, use the debian reference guide:
http://www.debian.org/doc/manuals/debian-reference/
Of course, you'll need to edit basic things as locales, network, ssh preferences, etc...
Edit your system, update, configure packages, etc...
Once edited and configured, quit you virtual machine.
Now, we are going to convert the qemu image to a raw image, mount the fs and copy to your SD
Assuming you still in the same folder as the qcow2 image of debian (for windows, google a little, im sure there are something to do the same):
qemu-img convert -O raw debian_lenny_armel_small.qcow2 debian.raw
With this will obtain the qcow2 converted to a raw file (without touching the original qcow2 file)
Now mount it where u want or follow this steps:
sudo mkdir /media/debian
Before mount, lets see where start the partition on the raw file:
sfdisk -l -uS debian.raw
U will see a list of partions under the raw file, use the first, like this one:
debian.raw1 * 63 20225834 20225772 83 Linux
Now, we know the / starts at 63, mount this partition
sudo mount -o loop,offset=$((63*512)) debian.raw /media/debian
Ok, we have our partition mounted now, lets make a copy in our EXT3 partition on SD.
Use the USB Storage function from android, sd card reader... and mount the EXT3 partition
Once mounted, copy everything from /media/debian to /media/yourSDext3mounted
cd /media/debian
sudo cp -a * /media/yourSDext3mounted/
If everithing works as expected, umount the systems /media/debian/ and /media/yourSDext3mounted or use the Android notif to disconnect the USB storage function
Check if everything is now in the SD EXT3. Open a terminal and adb shell
adb shell
cd /system/sd
ls
U'll see the Debian / extructure and the app & app-private
Of course dont worry about this, u can still using apps2sd and debian at the same time
Now, it's time to boot debian
We need some modded files from the G1 version to boot it:
Download from Megaupload: http://www.megaupload.com/?d=Q67SNOBC
Download from MediaFire: http://www.mediafire.com/?mxgcyk3whdt
Also, files attached to post (rename the extension to tar.gz)
Put the files into your FAT32 SD partition, no in a folder just in "/"
Now, it's time to give it a try
U have two ways:
Open a terminal window in your PC
adb shell
cd /sdcard/
sh installer.sh
sh bootdeb
Or:
Open up a terminal in your N1, like Terminal Emulator on Market
cd /sdcard/
sh installer.sh
sh bootdeb
PROFIT!!!
Enjoy your debian-armel on your N1
For the next chapter, how to run X with VNC Viewer
Bye and thanks for reading!
Looks like Klingon to me.
I have Debian running too now
Nice! Cant wait to try it out!
nice, i've been looking for a n1 debian how-to
Installing debian is pretty much the same as running it on your g1. I had it working the day after I got mine using the g1 instructions.
So, what's the reason or running debian on your phone?
Jst wondering
u
The reason by now is just fun hehe
But, if we can run it natively via fastboot, would be awesome hehe
Sorry for the delay guys, ill do it now, the last night was too late for me 4am here hehe
EDIT: Just give some time more, i going to try it with the Cm 5.0 beta 1
jairuncaloth said:
Installing debian is pretty much the same as running it on your g1. I had it working the day after I got mine using the g1 instructions.
Click to expand...
Click to collapse
I couldnt get chmod or installer.sh from the g1 instructions to work. I tried it both with bacon and modaco 1.3. I skipped the jesusfreak part though so maybe thats why. Anyway seeing confirming instructions would be nice.
Because the g1 files need to be modded first
I have it running it under modaco 1.3 and now im going to try it with the new b1 from cyanogen
Guide ready
Enjoy it!
Hi,
i have one question about debian. Is the network traffic routed trough android, or does debian has direct access to the wlan adapter for monitor mode and aircrack ?
meld0
it's using the same ip and mac, so is shared for both
If there are the apropiate drivers maybe, don't really know
Calling Linux Experts!!! hehe
Is there any way to create a boot.img bootable via fastboot to run the ext3 partition of sdcard with debian?
Driskol said:
Calling Linux Experts!!! hehe
Is there any way to create a boot.img bootable via fastboot to run the ext3 partition of sdcard with debian?
Click to expand...
Click to collapse
sorry for being noob in this matter but, why do i need debian on my phone? what does it give me?
amir
The answer is a choice, Android or a Full Desktop OS with Firefox, Thunderbird, OpenOffice, etc...
When its booting I'm getting an error:
/system/bin/bootdeb: line 61: chroot: command not found
Doing "find / -name chroot" only returns binaries within the debian image.
Any ideas?
Driskol said:
The answer is a choice, Android or a Full Desktop OS with Firefox, Thunderbird, OpenOffice, etc...
Click to expand...
Click to collapse
How well does Firefox run?
Can anyone take some pics or video?
Any instructions for creating and mounting linux as an img file instead of using separate partitions?
tetlee said:
When its booting I'm getting an error:
/system/bin/bootdeb: line 61: chroot: command not found
Doing "find / -name chroot" only returns binaries within the debian image.
Any ideas?
Click to expand...
Click to collapse
Maybe your rom doesn't have Busybox
EDIT: Im going to make a img version tutorial
Of course, this version was without the highmem kernel, now with more ram, more flawlessly

Swap

Hi guys. can you please help me on swap. how can i enable it and disable it. and also set it to the amount that i want it. im still a bit new to this and i have also tried to look for a guide but cant find 1. thanks
Rawdi said:
Hi guys. can you please help me on swap. how can i enable it and disable it. and also set it to the amount that i want it. im still a bit new to this and i have also tried to look for a guide but cant find 1. thanks
Click to expand...
Click to collapse
If you are on Kings rom, it may be running already.
Type #free in terminal and see if it shows swap.
Rawdi said:
Hi guys. can you please help me on swap. how can i enable it and disable it. and also set it to the amount that i want it. im still a bit new to this and i have also tried to look for a guide but cant find 1. thanks
Click to expand...
Click to collapse
bbuchacher said:
In Terminal:
echo 30 > /proc/sys/vm/swappiness to change swappiness to 30 replace number with any number 1-100
cat /proc/sys/vm/swappinesss to see a current level
Click to expand...
Click to collapse
bbuchacher, just wrote it
thanks but the rom that im using is not using swap. how to i setup swap? can i push a user file?
Rawdi said:
thanks but the rom that im using is not using swap. how to i setup swap? can i push a user file?
Click to expand...
Click to collapse
It definitely depends on the rom. Some King roms he has a script you run. Other roms, all you do is go to Spare Parts and set what you want. It may be best to ask in the thread for that rom.
I remembered using this when I used CM:
http://forum.xda-developers.com/showthread.php?t=581328&highlight=swap
Enable swap
I used the method to enable swap in Linux on this and it worked fine on Cyanogen and Super-D.
I used Amon_RA Recovery 1.52 to partition my SDCARD and the new recovery lets you choose the size of your partitions.
so I created a 256MB Swap.
from a console/terminal do the following after creating your swap partition the size you want it:
1. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (makes system dir writable)
2. mkswap /dev/block/mmcblk0p3 (formats the swap partition on SD with swap format)
3. vi /system/etc/init.d/05userinit (make a new line at the bottom and add "swapon -a" with out the quotes this forced the swap to mount on boot if it is disabled in a kernel)
4. vi /system/etc/fstab (add a line that says "/dev/block/mmcblk0p3 swap swap" with out the quotes)
5. reboot
Hope you know how to use vi editor If not google it. "I" is insert mode and push track ball and hit 1 at the same time and that will esc you to command mode, in command mode do a :wq! and hit enter and that will save the file.
This works on all roms i have run into and no matter what others say it does help the performance.
I can make it easier (short of putting this in a script). Type each line in order and hit enter after each.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkswap /dev/block/mmcblk0p3
echo "swapon -a" >> /system/etc/init.d/05userinit
echo "/dev/block/mmcblk0p3 swap swap" >> /system/etc/fstab
reboot
TGA_Gunnman
The UNIX Dude

[Q] Help upgrading Market

I recently rooted my Nook color with Auto Nooter 2.12.25. It gave me the Google Market but it is the old one and it only displays 10 apps in portrait mode and some of the buttons have problems working. I read in a thread that the newer market fixes that and I downloaded an apk named com.android.vending02.apk but when I try to install it, the app manager doesn't have an install tab. I downloaded a 3rd party install manager and when I try to install it says that 'There is a problem parsing this package'.
I have read that people have installed the updated market but no one gives an explanation how. Does anyone know how do this? Thanks for your help.
Found solution
I found a solution.
Dont just post you found a solution, that helps no one. post what the solution was or atleast a link to the fix.
Good Call
I installed the APK at the top of this thread http://forum.xda-developers.com/showthread.php?t=872621 and then reset my NC and the new Market worked. Apparently, after reading through the thread, this method doesn't work for everyone. There are further instructions that may be of some use.
Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.
buffnutz1 said:
Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.
Click to expand...
Click to collapse
I had the same problem on my 1.1.0 NC rooted with Decad3nce's V1.1.0_r2 [01/29/2011] method (there's a huge long thread on that in the Development forum). I was dreading the possibility of having to wipe the machine and start over, but I just re-flashed the zip file, and everything's working fine again. Unfortunately, I'm still stuck with the old Market.
If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.
Thanks Woot! does this work on Froyo 0.6.7 too?
woot1524 said:
If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.
Click to expand...
Click to collapse
necroscopev said:
Thanks Woot! does this work on Froyo 0.6.7 too?
Click to expand...
Click to collapse
I can confim that it does, I used it my self to get the new market installed.
If you're booting off of an SD card and want to install the new market there. All you need to do is change one line.
FROM: mount -o remount,rw /dev/block/mmcblk0p5 /system (eMMC system partition)
TO: mount -o remount,rw /dev/block/mmcblk1p2 /system (SD-card system partition)

[Q] MCR fr17 Fear Kill Edition is based on ext3 or ext4

Hi All,
Sorry for such a noob question but the MCR fr17 Fear Kill edition runs on ext3 or ext4 ?
Also, is there a way to check if its ext3 or ext4? Many thanks in advanced.
You can check with by running mount from a terminal.
Being an MCR based ROM it should be EXT4 though.
T_T Pardon me for being ignorant but I'm very new to the terms used here.
Terminal <-- this meaning? I believe this is an external program run using the computer to SSH into the phone right? Or if I'm wrong, any guides for me to follow or can help to pinpoint to a link where I can learn all this?
Thanks in advanced.
Terminal = https://market.android.com/details?id=jackpal.androidterm
Install it, fire it up and at the prompt just type 'mount'
You'll be greeted with a couple of pages of gibberish, scroll to the top of it, and you'll see system & data mentioned:
Code:
/dev/block/mmcblk0p1 on[B] /system type ext3[/B] (ro,relatime,errors=continue,data=writeback)
/dev/block/mmcblk0p8 on [B]/data type ext3[/B] (rw,nosuid,nodev,noatime,errors=continue,data=writeback)
As you can see, my system is EXT3
Rusty! said:
Terminal = https://market.android.com/details?id=jackpal.androidterm
Install it, fire it up and at the prompt just type 'mount'
You'll be greeted with a couple of pages of gibberish, scroll to the top of it, and you'll see system & data mentioned:
Code:
/dev/block/mmcblk0p1 on[B] /system type ext3[/B] (ro,relatime,errors=continue,data=writeback)
/dev/block/mmcblk0p8 on [B]/data type ext3[/B] (rw,nosuid,nodev,noatime,errors=continue,data=writeback)
As you can see, my system is EXT3
Click to expand...
Click to collapse
Mine says ext4
Using fear 10
Sent from my LG-P990 using XDA App

[Q] XXLSA Android 4.1.2 and Low Battery: Stuck at Boot. Data Recovery?

Recently my phone had a low battery status. It booted up but apparently lost power somewhere when restoring the Apex Launcher screens.
Since then it just shows the Samsung logo and gets rather hot. I left it in this state for over an hour with no progress.
Boot and recovery mode work fine. Unfortunately adb is not in root by default, as such pulling is useless as nothing is mounted.
issuing
Code:
adb root
will result in:
Code:
adbd cannot run as root in production builds
I can issue for instance:
Code:
adb shell
su
e2fsck -pv /dev/block/mmcblk0p10
mount -t ext4 /dev/block/mmcblk0p10 /data
Unfortunately I cannot tar gzip and copy to the externalSD nor pull the data folder.
Starting dalvikvm fails:
Code:
127|[email protected]:/ # dalvikvm
dalvikvm
Dalvik VM init failed (check log file)
What options do I have to backup my data? Please provide me with concrete ideas and steps.
Many people are having similar problems, and I sincerely thank you if you can help me figure out a way to backup my data at this stage.
After reading the first two sentences and the title:
Buy a new battery.
Install something else, you are still on an early leak and not an official release.
I found a quick solution. All kudos and thanks go out to Philz as well as
TAHER128
Instructions and files are here:
http://www.youtube.com/watch?v=1TinSwsehZ8
After the new recovery mode and kernel is installed, reboot into recovery mode and go to the mount menu in order to select "mount USB storage". Backup everything to your PC.
From hereon out you are safe.
Install busybox if you want. Reflash a stock or custom rom if you want and/or dig your way through logs and fixes within a now powerful bash shell.
blairmiller said:
This problem is difficult to solve by your phone itself. Maybe you need to install some software to help you.
Click to expand...
Click to collapse
This thread is 2 months old
root
The reasons for getting a bootloop on your Android device might be anything. If you wish to know the reason why your Android phone is stuck on the bootloop, you need not type your problem on the Google search box. Just calm yourself for a while and think what you did just before. It could be anything! Here are some major reasons why your Android device is caught in a bootloop.

Categories

Resources