Related
i just installed jesus freak 1.5. i also purchased a 16gb micro sdhc card. I would like to know how to get apps to sd running correctly. I have followed another method and messed up the sd card. so i purchased a brand new one and before i even take it out of the package, i would like to talk to someone that has had sucesssful experience.
Thanx in Advance
A2SD in a Nutshell
the essence of apps2sd is:
1) creating a vfat/fat32 partition for storing user data
2) creating a second partition, ext2 to hold your apps and caches
3) creating directories within the ext2 partition on the SD to house your caches and apps
4) copying your apps and caches to the SD within the appropriate directories on the ext2 partition
5) rebooting within recovery console and deleting the original app and cache directories, AND
6) symbolically linking the ext2 apps/cache folders on the SD to the appropriate system partition folder names
7) rebooting to android and testing apps to determine which need to be reinstalled or reconfigured
your ext2 partition need not be very large relative to the volume of the SD; half a gig is normally adequate
pre-requisites:
you will need regular access to an OS that supports the ext2 filesystem, like linux. this is important because if your ext2 partition ever becomes damaged, the linux system has the tools to fix the ext2 filesystem errors.
you will need to know the commands for creating partitions on your SD
you should know how to use ADB to connect to your G1's shell, though this is optional
you need to know how to (re)boot to the recovery console and use its shell
you need to be familiar with the commands required to copy directories, create and delete directories, and create symbolic links
There are other Threads that have other programs and tutorials, but I used this one the other day on a JF 1.5 and it worked well.
http://forum.xda-developers.com/showthread.php?t=512743
Only issue I had was I had to move JF Updater back to Phone from SD , but that could have been a glitch when the phone checked for an update. The two apps used AppstoSD2 and a2sd pretty much do everything for you , very minimal command line required on your part.
Only thing to make it better would be an interface to either move the apps back to phone or integrate it so it would ask you when you install an app where to put it. But I am very happy with it. 16GB might be over kill , I have a 8 GB but they say not to go over 1.5 GB with the Ext2 partition, so while you will have 6.5 ( relative ) GB of space for Movies,Images, MP3's, Uninstalled apps, you are really limited to the 1.5GB for apps , well plus internal phone memory I guess. But for phone apps that's probably way more than enough.
question: how do you partition a 16gb sdcard? all the numbers and all that. ive done an 8 gb sd card and that was easy cause i was working with mb's. now with gb im lost. i got to parted and i typed up print and got 16.1gb if you could help me with the numbers for fat32,ext2/3,linux-swap. i would greatly appreciate it...
Personally, I would reccoment switching to a Cyanogen ROM. It's based off the same source as JF, but one of the features it has is automatic Apps2SD. This means you but have to push files here and there, whuch believe me can be a pain. It does still require an ext partition which you would have to format your self, but after that it will work without and modifications.
Do no more then 512 MB for your ext2(3,4) partition
Follow this guide for the card partitioning. Flash CM's rom and it will do apps2sd for you automatically.
Your other card is most likely not all lost and could be salvaged still, I would look into it if I was you, 16gb cards are not cheap.
And for the last time: it is Jeusus FREKE not Jesus Freak, Have some respect for the one who layed the foundation for us, at least enough to spell his name correctly.
AdrianK said:
Personally, I would reccoment switching to a Cyanogen ROM. It's based off the same source as JF, but one of the features it has is automatic Apps2SD. This means you but have to push files here and there, whuch believe me can be a pain. It does still require an ext partition which you would have to format your self, but after that it will work without and modifications.
Click to expand...
Click to collapse
I second that, and also jf won't be doing ROM any more :[
http://jf.andblogs.net/
As i see, more and more people are asking, how to install Android. And since previous tutorial is outdated, i will create new one.
So, first some theory. There are two types of releases: ones with ext2 partition and ones without. Second ones are much easier to install (just copy files to SD card), but ones with ext2 partition are faster and works overall better. All newer releases are with partitions.
So, how to install Android?
1. First we must prepare our SD Card. You will need 1GB+ Card. Some users are reporting that there are problems with several cards, so i suggest you stick to card you got with your X1 (it works 100%).
Now it's time to hook SD card to your computer. You can transfer files via X1, but I recommend getting a card reader, since file transfers will be more reliable then.
Before you begin, backup all your files on SD card. When partitioning, all data on your card will be deleted.
So, let's begin. Partitioning is fairly easy, but instead of writing this in text, i will show you video guide of creating partitions (thanks to user e334 for making this tutorial):
(Program in the video is Minitool Partiton Wizard. Grab home version from their page.)
2. After we properly make partition, it's time to download android build. Beware, that root of your SD card will be messy. There is a method to run it in folder (Andboot), but i didn't manage to make it right.
In the time of writing, (my opinion) best release is neopeek's SuperFroyo + v2c kernel. But releases are changing rapidly, since Android is still under development. I will try to update that page, but i suggest you always check the forums for some new releases.
As you can see, this release is in two parts (main release + kernel). But most of the time, there are releases with kernel included, so you don't have to download it separately. So anyway, download and extract main release, kernel and modules into root of the SD card (leave modules in .tar.gz file!).
After copying, use safely remove hardware before disconnecting SD card.
Now it's time for big final. Open file explorer on your X1, navigate to StorageCard\npkinstall folder and click install. If you have done everything right, your phone should go into "text mode" (black screen with bunch of text) and after about a minute, it should start displaying long list of files. That means it's installing android to EXT2 partition. When installation finishes, it will automatically reboot.
Your X1 Android is ready to use now. To launch android, open file explorer, navigate to \StorageCard and tap HARET. Again, it should start displaying text and after that logo should appear. When android appears to be loaded (start wizard pops up), leave it for another several minutes, so Android can initialize all background stuff it needs to.
Happy Androiding!
Frequently Asked Questions
How to return to Windows Mobile?
Simply restart your device. Android won't alter Windows Mobile or on board storage at all, so your windows mobile stays intact.
So, now my Windows mobile is running in background?
No. HARET will shut down Windows Mobile, so Android can have all the memory for himself.
Battery life is very short
Yes, android power management is not very good. But it's getting better, especially last days there were some major improvements in that area.
Camera/FM Radio/Something don't work
Android is still under development, so not all features are working yet.
I can't see my new EXT2 partition in windows
That's OK. Only linux sistems like Android and Ubuntu can see EXT2 partition. Although, you can install 3rd party software, that can add ext2 support to windows (google for "ext2 windows").
How big should i make ext2 partition?
EXT2 partition is system partition for Android. It needs to be big enough to fit all android system files in, but there is no point to make it too big, since data is stored to SD card anyway. Somewhere between 300 and 500MB should be fine. Make it 512 if you have space to spare or 300 if you are really low on SD card space.
I can't enter my SIM PIN!
PIN is currently not working in Android. Turn off PIN in Windows Mobile.
matejdro.. you are one of the best "teachers" thanks a lot.. very kind if you could update this threat everytime if something is new, because there are a lot of new kernels and things coming in.. i try to get in to this matter but at the moment all i understand is.. chinese mixed with japanese.. hehehe
Hey, please, can you add "how install dual boot" in this guide? I really need it, sorry my bad english
Sent from my FRG83 by Neopeek using XDA App
How big the ex2 partion must be? 300 ,500mb?
EDit: i have made the ext2 and the fat32 partition but i can only see the FAT32 in windows. Am I missing something?
viper. said:
How big the ex2 partion must be? 300 ,500mb?
EDit: i have made the ext2 and the fat32 partition but i can only see the FAT32 in windows. Am I missing something?
Click to expand...
Click to collapse
Nothing is wrong.
Actually, Windows can't read an ext2 partition, because it's a linux-based partition.
About the size.. i don't know, but i followed the tut' and put the same size. It works well.
Oggy972 said:
Nothing is wrong.
Actually, Windows can't read an ext2 partition, because it's a linux-based partition.
About the size.. i don't know, but i followed the tut' and put the same size. It works well.
Click to expand...
Click to collapse
Yep, i have realised that windows7 is unable to read that partition because i did install the android on it and everything went fine. My partition is 450mb large and its working normally. This is so much better then other xdandroid version beacuse with this build you can connect x1 and the pc via usb .
Added both questions to FAQ.
thank you so much for this!
can someone please give the proper instructions on how to use the andboot floder does the folder have to start with capital?
and the v3c kernel needs to be run using someother programs and methords which are there in that thread can you help me with them?
Is it necessary to leave some unallocated space on SD card as shown on video ? And what size of swap partition should be ?
I'm not sure why he left unallocated space, but it's not necessary.
For swap partition, I'm not even sure if android uses it. You can live without it.
hello
I need help
If i start the exe it boot.
But when it is finished it restarts and then there is windows .
Whats wrong ?
Have you done everything correctly? Delete everything and try again.
Also, what is your battery level?
I have successfully install Android with ext2 partition on my X1. But, when I boot to Android, it always hang.
Sometime it hang at the first boot (when Android ask me to configure Google account to sync), sometime it hang when I try to change Android setting, sometime it hang when I play music, but often it hang when I put Android on standby (I press the power button).
I use 4GB SD card and partitioned it into two partition, FAT32 2,5GB and ext2 450MB.
I have try two Android build : CyanogenMod 6.1 and X1-frg83-06112010. Both have the same problem. I also try replace the kernel (zImage) with sp3dev, but the problem still there.
The other thing I try was extract androidinstall.tar.gz directly to my ext2 partition, but Android still hang.
Do you ever encounter this problem? How to fix this?
Hello
Now i have android all is ok and does go.
But one problem if i press the ok and the other buttons does go.
But a little time later no buton does go anymore.
Whats the problem ?
Signing in...
Hi,
All went well.
Now 1st boot it tries to get to me google.
Nothing happens.
It tells me 5 minutes, but that was 10 minutes ago
I am on 3G
Any help?
Edit: (Will boot again, and let you know if it works.)
Edit: Rebooted, and skipped the google account login. Will try with WiFi on loging into google again.
?
Sorry, i don't understand you. What is bugging you?
hi there i am a complete newby to this and wanted to install the new cm7 mod on my xperia x1i.
my questions - am i right in assuming that you dont actually install it and that it is run from the memory card, if i am right ? do i just need to delete it to get back to winmo 6.1 and then reboot ?, could you also recommend a good or the best winmo 6.5 for me ?
thankyou for any help you can give me.
You are correct - it doesn't actually install Android to your phone, persay. The INSTALL.exe file merely extracts the initial android software packages to the EXT2 partition you created on your SD card. It doesn't install as a program.
To "uninstall" it, it is as simple and rebooting in Android - unless you configured your phone to automatically boot into Android when it boots WinMo (I'm sure you didn't), it will boot into WinMo, not Android. To remove Android completely, simply reformat your SD card, making sure to backup files you need, and to remove the EXT2 and Linux Swap partitions you created.
As for good WinMo builds, I was a user of Christian's build's for a while (christian-web.nl/sections.php?section=Xperia_rom). They were very stable for me, had a lot of great programs preloaded. I realized how great it is to have a ROM that already has all the programs I need installed; it saves a lot of time.
If you plan on trying to use exclusively Android, you might as well use any pure/light build - something that boots fast, seeing as you have to boot two OSes to get to Android.
Hi there,
So my N1 is rooted and has SuperOSR rom installed. The native app2sd that comes with the rom failed to work, so I disabled it and went back to the method I was using on CM7, Link2sd. I need a method to move apps/cache/lib files to sd-ext, as the tiny internal storage on the N1 is insufficient to hold even a 10th of the apps (and their data) that I have installed. And Link2sd has, at least in the past, been the perfect option to do so.
At first, all seemed well after installing and setting up Link2sd. Mount scripts were created with no problems, apps/cache/lib files all moved over to sd-ext without a hitch. Everything was going really well. Until I rebooted. Then, all hell broke loose.
The problem is this - for some reason, the second partition (sd-ext) is not being mounted during boot time. I'm not sure why, as this is exactly what the Link2sd mount scripts are supposed to accomplish. A Link2sd "mount warning" notice confirmed this problem, saying that "since 2nd partition was not mounted during boot time, linked apps will be invisible to the system until quick reboot". Indeed, every app that I had linked was not visible to the system, and most widgets on my homescreen showed only the message "problem displaying widget".
Luckily, a way to temporarily fix this is by simply quick-rebooting the rom. This will get the linked apps to show up again. But the problem is, widgets are still dead, input method gets reset (goes back from Swiftkey to native Android keyboard), and SMS gets reset back to the standard android SMS app. Of course, all of this can be changed back, but it takes time and effort to load each individual widget and restore each individual input/sms setting. It's really not practical every time you have to reboot your phone that you have to:
1. Quick-reboot the rom
2. Change input method back to Swiftkey
3. Manually restore every widget on your home screens
4. Change sms app back to Go sms.
So, my question is, how do I avoid having to do all this? I've already tried the "re-create mount scripts" option on Link2sd, but it doesn't matter. Still have the same errors upon rebooting phone every time. I'm pretty sure this means that the Link2sd mount scripts are either not being created correctly, or are being deleted every time the phone reboots. How do I fix this? Trying to get in contact with the developer of the app (bakpinar) has proven unsuccessful.
Does anyone know of any other scripts that I can flash/install that will successfully and consistently mount the 2nd partition (sd-ext) during boot time? I'm fairly certain that this is all I need, as everything else with Link2sd has been working correctly. Thanks in advance for any advice!
Ok, so since I haven't gotten any responses on this, I'm going to attempt two methods that i THINK might remedy this issue. The first one is this:
Method 1:
1. Full wipe and reinstall of SuperOSR rom
2. Format sd-ext to ext3 filesystem (found out that rom's native app2sd program wouldn't work due to my sd-ext partition being FAT32)
3. Enable rom's native apps2sd option upon booting.
4. Reboot
5. Install Link2sd from market, enable dex/lib file linking ONLY (native apps2sd program only moves app files, not dex or lib). Going to be interesting to see what link2sd says about the mounting scripts...
6. Reboot, collect results.
The 2nd method I'm going to try is this.
1. Full wipe and reinstall of SuperOSR rom.
2. Flash DTAPPS
3. Boot into ROM
4. Download and install test applications
5. Collect results
I'm not sure if either of these methods will work, however I know the 2nd method worked for CM. I will update a bit later as to which method (if any) fixed the issue. Sorry for the double post.
I commented to the ROM cook nelo360 a while back that there are some strange sd-ext mounting issues. If you look at the dmesg as it boots, it does post some strange error messages. Essentially, ext3 mounts as ext2, and ext4 mounts as ext3. Despite it not mounting as the proper format type, it still works.
Since the ROM is pulled off of AOSP, as CM is too, sort of, much of the same apps2sd apps probably work decently well.
Definitely need an ext3 or ext4 partition. As I'm understanding your post, that did not happen initially, and is crucial to many apps2ext to work, including the built-in one.
Really? Ext4 as 3 and ext3 as 2? Well that would explain why Link2sd was having issues. Hmm.
What I ended up doing was fully wiping the phone, flashing the rom, and then immediately afterwards flashing DTAPPS. Using the GUI interface found on the market, I moved apps to sd-ext and cache to sd-ext as well. The result has been mixed. While there was noticeably more space initially to install apps (something like 190mb internal), that space has declined at almost as fast a rate as when I had no apps2ext of any sort installed at all. This makes me think that while DTAPPS successfully moved some of the initially installed apps over to the sd-ext, it hasn't been moving any new ones i've installed or their cache files. I tried re-moving apps/cache with the gui interface and by using the old-fashioned terminal emulator method, but had no success. Still looking at about 100mb free space on internal. Considering that I only have about 1/4 of the apps installed that I usually have installed on my phone at any given time (I use A LOT of apps), it's become apparent that soon I am going to run out of space again.
As I can't find any method to fix this, I'm afraid I'm going to have to call it quits with this ROM and try something else. Which is a real shame, because stability-wise this ROM beats Cyanogenmod and other ROMS I've tried hands down, while not sacrificing many features. I guess for a user who doesn't use a lot of apps or need a lot of space for them, this ROM would be ideal. Unfortunately, I'm not that type of user.
One problem I've found is that with any automatic apps2sd/ext system is the control of what is actually on the SD vs. internal memory is hard to work out.
With the built in apps2sd, which you seem to have trouble with, not every app was transferred to ext. I found that with the built in system, my internal memory kept dropping until it hit 25 mb or so. However, it never really dropped below that. Everything I kept installing probably went to the ext partition. I installed a lot of apps, and it wasn't an issue. (But you're right, it may not be as many as you want).
I didn't have a great way to check this though. Root explorer showed both the data/apps/ folder and the sdcard/ext folder linked together, so it just listed everything together. I'd have loved a way to actually manually transfer whatever apps were on internal memory to ext, but never found an easy way to do so, or even to confirm what was in which directory.
So even though it looks like the internal memory is steadily and quickly dropping, if you continue to install, and have the two directories appropriately linked (sorry, I don't know what the difference between all the different kinds of scripting apps2sd are), I don't think you'll run out of space as quickly as you think you will.
What are the diference between super froyo and cyanogen and the rest of the android? I'm a noob and would like to install one of this to my kaiser.
Thanks
The "builds" you're asking about are just different versions of the same build.
The 29-8-11 build is version 2.2.2 Froyo, Super Froyo (IIRC) is build 2.2.1, and Cyanogenmods are just that, "mods" to an originally stock build, wether it be Froyo, Gingerbread, Eclair, etc.
I honestly can't say I hate or dislike any build or modded version, as they all have their benefits. The one great thing about Android is the ability to "make it your own" through customization, where-as iOS (iPhone) pretty much locks you into a certain form and functionality, which the benefit is stability.
My suggestion... grab the 29-8-11 build on sourceforge and build a kernel with 3-4mb above the total install size of 87mb, give yourself a 15-20mb cache file and install it. Customization comes with time, trial and error, and some effort, but you will be happy with the results.
PoXFreak said:
The "builds" you're asking about are just different versions of the same build.
The 29-8-11 build is version 2.2.2 Froyo, Super Froyo (IIRC) is build 2.2.1, and Cyanogenmods are just that, "mods" to an originally stock build, wether it be Froyo, Gingerbread, Eclair, etc.
I honestly can't say I hate or dislike any build or modded version, as they all have their benefits. The one great thing about Android is the ability to "make it your own" through customization, where-as iOS (iPhone) pretty much locks you into a certain form and functionality, which the benefit is stability.
My suggestion... grab the 29-8-11 build on sourceforge and build a kernel with 3-4mb above the total install size of 87mb, give yourself a 15-20mb cache file and install it. Customization comes with time, trial and error, and some effort, but you will be happy with the results.
Click to expand...
Click to collapse
Can you give me the sourceforge link.
I follow this :http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret
I partition using the atools but nothing happen.Receive an error message someting like ext2 ext3 and something missing.Get an error using the above.Maybe it's my bad.
This is the latest error
did you keep the D-Pad pressed ?
That is nothing to do with the D-pad, that is a fault of not installing the system to NAND, something I'm unfamiliar with as I never used or even liked HaReT.
It appears as if you're installing to SD, but the card is not formatted correctly with the 3 (maybe 4 now) partitions needed, one for system, another for data, and the rest for your use.
It should be easy peasy to install to NAND as ATools is really optimized for NAND installations now.
Now I made ext 2 & 3 to my sd card. 1st attempt took 6hrs and still installing files and now trying 2nd attempt.
I use atools and choose haret.once Linux running I choose ext 2 . I follow everything but android doesn't seems to run. Now under file folder there's only ext2 appear ext3 is missing . Have been trying to install few times but nothing happens. My card is 16gb class4.
Can I have the link for the latest froyo dated. 29.8.11.
First off, forget about keeping Windows Mobile and go straight to Android. I never liked running from a SD card.
Here's the link..
http://sourceforge.net/projects/androidhtc/files/2011-08-29-froyo/
Select the correct build for your Country (eu, us or all), preferrably an "odexed" version, download it and copy it to your FAT32 formatted SD card in a folder labled "andboot" without the quotes.
If you check around, I have a post or 2 with the "KAISIMG.NBH" file attached. I always build a new kernel for any new installs as I like to make modifications depending on build size. The one I posted is for this build with a meager 500MHz overclock, 15mb for cache and around 92mb for data with an EXT4 FS.
If you use the 29-8 build, there is no need to update anything as the update modules are included.
How many partition do i need and how many mb do i need on each partition.I'm using 16 gb.
update: I make 1 fat32 and 3 ext2 with 200mb each using gparted.
where does the downloaded or installed apps goes to.Is it on the fat32 or the ext. what's the difference ext2, ext3,ext4.Can I reformat the sd card once my device is androided to add more mb to the ext. If my ext. not enough to install apps (if the apps need to be install to ext. not fat32)sorry for so many question.
Do I need 'bse'( *img -> Virtual disk on sdcard (you need to create it, you can create it with bse) to create virtual disk.?
First off, you're speaking in HaReT terms, a completely different language for me.
I only know how to install /system and /data to NAND, NOT an SD card. No 3 separate partitions on my SD, only 1 formatted to FAT32.
Again, you're running Android "through" Windows by clicking an .exe file in file explorer, not the way I'm running it, which just involves pressing the power button, so you are, in fact, speaking a different language.
Build a kernel with ATools for NAND, not HaReT, and leave everything alone when presented with where to install. /system goes on NAND, /data goes on NAND.
That is my recommendation because I'm all about speed, and a class 6 SD couldn't provide that. Think of NAND as class 10...
I follow this for Nand : http://sourceforge.net/apps/trac/an... pls guide me on how to install through Nand.
Make sure you are using a FAT32 formatted SD card when attempting a kernel update. If you are sure it is formatted correctly, try another. I have 5 SD cards here, 2 of which won't work for kernel update, regardless of format.
If all else fails, look around for the RUU installer for the Kaiser.
Am i getting this right? i'm installing it to my device from yesterday night.
Edit:How long does it going to take 1 day? 1 week? now the number is [43617.514121]android_usb gadget:full speed config #1:android
I connected it on my pc and change to power supply.Is this normal?
Very simply, keep your phone away from any computers!
The only problem I see is the USB is connecting and disconnecting.
DO NOT keep the phone connected to the computer.
If you have followed all the instructions for a NAND install, this conversation would not take place... its THAT simple.
Reformat your SD card, out the KAISIMG.NBH directly on the SD, not inside any folders. Once thats done, make a new folder on the SD called "andboot" and place the androidinstall.tar file inside the new folder. If you're using a rom other than Scoot's or the SourceForge, you'll need an update for the cache.
Install takes less than 2 minutes with even the slowest SD card and first boot usually runs 3-5 minutes. ALL up and running, ready to use in less than 10 minutes.
@PoxFreak, at last i manage to install Android to my Kaiser HaRET way.I think i know what's the problem.I think it's due to my radio. I was using 1.71 and 1.70 it doesn't work. So i install shipped rom to my kaiser and install android .
@Poxfreak,
I manage to install CyanogenMod 6.1.2 Release 6 by using NAND.It took me .... like you say about 5 mins+.I was wondering I have 2 Kingston 4gb microsd card both can be use to install HaRET but only one of them can install NAND.So now I would like to use back my 16gb sd card as an external to install apps.Will I be able to do that instead of using the 4gb? Can I partition it?
Thanks