Related
I was wondering if there is a way to start haret in android? the only version I can find is for WM, so maybe is there a type of emulation layer it could be loaded to? Even better if there was an android version we could use that to reboot an SD run android and also boot into different version without having to reboot the entire phone and load wm up again (and nand android could then "haret" a diff version through sd).
Not sure you actually understand what the difference between Haret and Nand is.
Haret is, ( and always has been), a WM program, in fact it would make no sense to have it running as an android program, what Haret does is allow a WM device to run a Linux OS, that is all it does.
I think what you want is a way to dual-boot, to run different builds, which is possible, using the installer menu to choose which one to run, as well as where it is installed.
How it works is this, install your main build to nand, sys on nand, data on nand.
Then install another build, sys on SD, data on SD.
Once installed you have 2 builds, one on SD, the other on nand, to switch, you must reboot, enter installer, change the target settings to SD or nand, and quit, it should now boot from the installed version you chose,
I think you may have to have 2 ext2 partitions on SD for this to work, not sure since I never tried it, but I do remember someone posting this idea on the forum some time ago.
basically I want to boot an sd build from within an sd build. This serves a few purposes, mainly no need to boot into a different os (wm in this case) just to boot a diff version, and to allow a type of reboot on an sd build. If this can be done in script that would work also but want an android app to kick the current build out of memory and load a new one in (or the same one reloaded) instead of it being wm based. This might be something we can do with the kernel to just dump the current gui and load the other gui onto it?
edit: BTW I am using a type of boot you are explaining but instead of installer in between I have wm with different "andboot" folders.
ghghgh14702 said:
basically I want to boot an sd build from within an sd build. This serves a few purposes, mainly no need to boot into a different os (wm in this case) just to boot a diff version, and to allow a type of reboot on an sd build. If this can be done in script that would work also but want an android app to kick the current build out of memory and load a new one in (or the same one reloaded) instead of it being wm based. This might be something we can do with the kernel to just dump the current gui and load the other gui onto it?
edit: BTW I am using a type of boot you are explaining but instead of installer in between I have wm with different "andboot" folders.
Click to expand...
Click to collapse
Interesting concept, and theoretically possible, since Android itself is a shell on the Linux core, it may be possible to do this, perhaps a remount of /system and /data, then a restart of the kernel, almost certainly requires some hardcore Linux knowledge, anyone up for this?
This posthttp://forum.xda-developers.com/showthread.php?t=594077 is for the dream.
We've been able to from internal or sdcard on vogue,kaiser, polaris for ages from boot.
The only other way is to use grub 'if possible'.
I think ghghgh14702 means that directly reboot Android. NOT shut down, then boot to wm, and then run haret.
In All the builds I've tried, the reboot menus all dont work. Most reboot meuns make the phone shut down.
I'm using a polaris, running Android in the sd card, and seems dont have a recovery mode.
I found sometimes Android stucks and reboots itself when I push the volume button to adjust the system volume. It is a DIRECTLY reboot, not reboots into wm.
So I think there is some way to reboot directly. Hope sb. can find it out.
Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.
Hi all,
is it poosible to get a2sd+ on stock htc sense froyo?. I`m desperately running out of space, but i want to retain the stock froyo because of app updates, those on customs had issue not been able to update for example map, yt, etc. I may be wrong. In that case is there a rom with stock sense and latest froyo update?
Any info about rooting the handset with latest froyo update (stock) would also be helpful.
Thanks.
Hi There
I found this link the other day about forcing apps to the SD card without rooting on Froyo
http://myhtcdesire.com/category/tipstweaks
I have tried it a few times but just can't get it to work for me, perhaps I am missing something
Hope thios helps
JaykaySLO said:
Hi all,
is it poosible to get a2sd+ on stock htc sense froyo?. I`m desperately running out of space, but i want to retain the stock froyo because of app updates, those on customs had issue not been able to update for example map, yt, etc. I may be wrong. In that case is there a rom with stock sense and latest froyo update?
Any info about rooting the handset with latest froyo update (stock) would also be helpful.
Thanks.
Click to expand...
Click to collapse
DISCLAIMER: be very, very careful especially if you don't have S-OFF yet and plan to use this method. Mind your exact Desire variant and read all the info on listed stuff before attempting
I use a rooted stock rom with Darktremors Apps2SD method. You just have to install the scripts and modify the init.rc script as described in this thread
You will need to prepare an update.zip with the boot.img or have S-OFF hboot (like AlphaRev) to flash the boot partition on which the init.rc script resides.
It might be also possible to use flash_image, but I'm not sure it will be possible without S-OFF.
I used AmonRA 1.7.0.1 Recovery R5 to repartition the SD, as it seemed to me that using Clockwork which was embedded in Unrevoked 3.21, caused my last USB brick.
This will enable you to move not only the apps but also the dalvik cache to the SD's ext partition. The data from /data/data still remains in the internal storage, but moving the apps and dalvik cache is a huge space saver.
IIRC moving some apps data from the /data/data (I think it was systems apps mostly but honestly I don't recall) to the ext partition may result in errors.
Right now the situation looks like this on my phone:
Code:
# df -h /data
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock5 147.6M 102.8M 44.9M 70% /data
# du -sh /system/sd/*
200.3M /system/sd/app
8.0M /system/sd/app-private
54.9M /system/sd/dalvik-cache
# ls -1 /system/sd/app /system/sd/app-private | wc -l
129
Additional bonus:
Because the ext partition is not being unmounted when connecting the phone as external storage to a computer, you don't end up with screwed up app links, and disappearing widgets when you do.
good luck
thanks for the info.
2 things: what is S-OFF and is there a windows based procedure as I dont have a *.nix system
JaykaySLO said:
thanks for the info.
2 things: what is S-OFF and is there a windows based procedure as I dont have a *.nix system
Click to expand...
Click to collapse
This particular *.nix system in my example is the Android OS as seen from the adb shell.
Please search the forum for what S-OFF is, there are tons of tutorials and howtos on this subject, it's basicly an unlocked variant of the HBOOT bootloader. The standard HBOOT won't allow you to flash partitions using fastboot mode like in earlier HTC models, Dream for example.
My advice is not to touch the HBOOT if you're not familiar with it as screwing something up when trying to change it is the quickest way to a bricked phone.
best of luck
"To begin, you'll need a Linux or a Mac system and basic knowledge on how to navigate through your Linux or Mac via a terminal program. The tools presented in this guide will only work with those systems."
As u said, its best I dont mess with hboot.
First things first - I think it should be possible to flash boot.img from an update.zip (just a regular update from the recovery mode). So no S-OFF modification needed this way.
Or just ask around the forum. It could be possible to flash the boot partition on the device using flash_image. Since my phone is already s-off I can't verify that.
JaykaySLO said:
"To begin, you'll need a Linux or a Mac system
and basic knowledge on how to navigate through your Linux or Mac via a terminal program. The tools presented in this guide will only work with those systems."
As u said, its best I dont mess with hboot.
Click to expand...
Click to collapse
Ah, that My bad, I thought you meant the code in my post.
Well you need a *.nix-ish environment for that particular solution, but that doesn't necessarily has to be an actual Linux / MacOS box.
There are a couple of ways to work around not having a Linux / MacOSX box:
First: If you have at least some knowledge of operating a unix shell, you can just download a live boot linux distro in the form of ISO image. Download and install VirtualBox, run the iso from there.
Second choice would be Cygwin, which is basically your *.nix environment for Windows.
Third is to install just a Windows perl interpreter needed for some of the scripts, and download a windows version of the mkbootimg binary, and just do the whole procedure manually. You pretty much just have to be able to run:
1. perl
2. cpio
3. mkbootimg
You can google all the needed exe's, and then you google "how to unpack boot.img" and take your pick - OR just take a peak inside the scripts from the semi-automatic solution (the thread you just quoted). The scripts are simplicity itself, pretty much don't differ much from a simple windows / dos batch file.
Fourth is to ask someone you trust to prepare the image for you
Either way, you have to modify the init.rc to be able to run the a2sd scipt on android boot.
OFC you can just start the process manually from a Terminal Emulator directly on the phone, and repeat it every time after you power on the phone, but that's hardly a comfortable way to go
Tell you what. If you feel really courageous I can fashion up a web form for you (and anyone else interested) which could allow you to submit a boot.img and have it modifed automatically, allow you to download a modified version. But: no warranties and also I might end up being an evil sneaky, sneaky bastard Your call
Thanks for the comprehensive info, but I`m not willing to experiment too much for the sake of not bricking the phone. I thought there might be a simpler solution....
+1 from me, getting headache from running out of space, I read online saying EXT3 was the method to go, but how to do it with rooted stock rom? (I head the only way to root Desire 2.2 is unrevoked) , please help
hongkongtom said:
+1 from me, getting headache from running out of space, I read online saying EXT3 was the method to go, but how to do it with rooted stock rom? (I head the only way to root Desire 2.2 is unrevoked) , please help
Click to expand...
Click to collapse
Like I wrote in the earlier posts. Partition with AmonRA recovery, install Darktremors APPS2SD, modify the init.rc script located on the boot partition, flash the modified boot - just browse the earlier posts. There are links to threads containing all the info you need.
I just got my new Desire a few days before. It works like a charm. The only 2 things I feel unsatisfied are: battery life and ROM capacity.
There is not much I can do on the battery side. I can put it aside and get used to that. But the ROM is really painful for me -- When I get the device, it had around 150MB free memory. But it is only 22MB left now!
I noticed that the Android 2.2 supported to install application on SD card. I used adb shell to setup the default installation to SD, and moved most of the programs to the SD card. However, it seems that internal memory was not free up as much as I was expected. Indeed, I did not have many software installed. And I am very suspicious if the cache of software (like mail, google maps, etc.) might always stay on internal memory.
I think one solution to solve the problem is to root my device and partition the SD card to increase the program storage. But I am worrying if it might bring security risk from malwares, or make the phone run slower and have bigger power consumption when use SD card more frequently.
Do you root your device for the app2sd? What's the pros and cons? I want to take your opinion before make the decision. Any suggestion will be very appreciated!
w162 said:
I just got my new Desire a few days before. It works like a charm. The only 2 things I feel unsatisfied are: battery life and ROM capacity.
There is not much I can do on the battery side. I can put it aside and get used to that. But the ROM is really painful for me -- When I get the device, it had around 150MB free memory. But it is only 22MB left now!
I noticed that the Android 2.2 supported to install application on SD card. I used adb shell to setup the default installation to SD, and moved most of the programs to the SD card. However, it seems that internal memory was not free up as much as I was expected. Indeed, I did not have many software installed. And I am very suspicious if the cache of software (like mail, google maps, etc.) might always stay on internal memory.
I think one solution to solve the problem is to root my device and partition the SD card to increase the program storage. But I am worrying if it might bring security risk from malwares, or make the phone run slower and have bigger power consumption when use SD card more frequently.
Do you root your device for the app2sd? What's the pros and cons? I want to take your opinion before make the decision. Any suggestion will be very appreciated!
Click to expand...
Click to collapse
Rooting , followed by alpha rev s-off n1 partitioning, is by far the best thing, so much fun.
I use defrost based on cyanogen mod, great support, and ota feature, with kernels galore, and the all important a2sd built in. As long as you have an ext partition on your sd card, all apps go straight into the ext partition with out you having to do anything.
Also remember is not jail breaking
Desire is the source of all suffering.
nitrox1 said:
Rooting , followed by alpha rev s-off n1 partitioning, is by far the best thing, so much fun.
Click to expand...
Click to collapse
What does alpha rev s-off allow you to do?
It basically provides full root access for your desire as opposed to soft root, where you could only r/w to the to the /system partition while in recovery mode.
What is S-OFF ? (Quotes from original AlphaRev website)
HTC implemented security on their new generation phones. This flag, called @secuflag, controls whether your phone has it's NAND or flash unlocked. Most noticibly S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, controls whether zip files being flashed recovery or fastboot, are signed by HTC The now notorious S-OFF (security off) disable this NAND security. Since we are unable to access the Radio itself (where secuflag is stored), we turn attention to HBOOT.
Sent from my HTC Desire using XDA App
MasDroid said:
It basically provides full root access for your desire as opposed to soft root, where you could only r/w to the to the /system partition while in recovery mode.
What is S-OFF ? (Quotes from original AlphaRev website)
HTC implemented security on their new generation phones. This flag, called @secuflag, controls whether your phone has it's NAND or flash unlocked. Most noticibly S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, controls whether zip files being flashed recovery or fastboot, are signed by HTC The now notorious S-OFF (security off) disable this NAND security. Since we are unable to access the Radio itself (where secuflag is stored), we turn attention to HBOOT.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
What does it allow you to do that you can't do without it?
stats101 said:
What does it allow you to do that you can't do without it?
Click to expand...
Click to collapse
It unlocks NAND so that you can write into /system partition. You can also flash radio, custom kernel, custom recovery, any unsigned ROM directly via fastboot without ClockWorks Rom Manager.
When you can write to /system, MetaMorph, AdFree and other apps that require access to this partition will just work. You don't need to reboot into recovery in order to delete/change/add files. Superuser will be able to update su binary automatically, Busybox Installer from Market will have no problems installing the most recent version directly into /system/bin or /system/xbin, etc.
While most users probably don't need it, it's very useful for developers. You can change system configs on the fly, add and load custom kernel modules without reboot and so on.
Basically, it will make your phone fully unlocked, just like the Nexus One developer phone.
nitrox1 said:
Desire is the source of all suffering.
Click to expand...
Click to collapse
Can't agree with that any more now
I TOOK IT HERE
Android ROM and rooting dictionary: all the terms explained
Android is a Linux-based operating system, and in Linux, there is something called root access. When you root your Android phone, you will get superuser access. It’s sort of like a special user account for system administration.
With root access, you have complete control over your phone’s operating system. It will let you install lots of great system apps, such as backup tools, that only are available to root users, and you’ll have the option to flash themes and custom Android ROMs. You can look at custom ROMs as different editions of the Android platform, and when you flash a new ROM, you install someone’s vision of Android.
For example, when I bought the HTC Desire in April 2010, I initially used the stock HTC firmware for a couple of months, which basically is HTC’s customized version of Android. Then I got bored with it, and I started using a ROM called MIUI by a group of Chinese developers. It added a lot of functionality and had a unique UI design. Then I got curious of HTC’s new device Desire HD, and I flashed a custom ROM that was based on the firmware of that phone. And when Android 2.3 Gingerbread arrived, I started using a virtually unmodified version of Android – Google’s vision of it.
In other words, when you have root access, you can use your phone as a hardware shell that you simply can put new versions of the Android operating system into. This post won’t discuss how to get root access, but it will try to explain all the funny words that you will encounter when reading about custom ROMs in forums such as xda-developers. There is an entire terminology surrounding Android ROMs and rooting, and these words sound like complete gibberish when you’re not used to them.
So I’ve tried to write a rooting dictionary that explains the most common superuser and Android ROM terms. I’m no expert, so please correct me in the comments if I’m wrong, and feel free to suggest additional words to include in this root access and ROM dictionary.
Android ROM and rooting dictionary
A2SD+
A2SD+ is an extension of Android 2.2 Froyo’s native support for installing apps on the SD card, but it virtually installs every app to the external storage. You can more or less expand your internal storage with the size of the partition you create on your memory card — because you need to partition your SD card to use A2SD+. It’s great if your Android phone has a limited amount of internal storage space. Most Android ROMs have built-in support for A2SD+.
AOSP
AOSP is short for Android Open Source Project, and when the term is used in ROM descriptions, it usually indicates that the ROM in question is based on the Android source code provided by Google itself, and not on some other ROM project or a company’s firmware.
Bootloader
The bootloader executes code before any operating system is launched. On Android devices, the bootloader is usually locked because manufacturers want you to use the version of Android they’ve provided. With a locked bootloader on Android phones, custom ROMs cannot be flashed.
BusyBox
BusyBox is an app on your phone that will give you access to additional Linux/Unix based commands. You may need BusyBox installed to perform some root level tasks, and some other apps that require root access may need BusyBox installed as well. BusyBox is self-dubbed “The Swiss Army Knife of Embedded Linux.”
ClockworkMod Recovery
I won’t get very technical here, because I can’t, but you can think of the Recovery Mode as Android’s equivalent of the BIOS on your computer. Not quite, since Hboot may be more similar to your PC’s BIOS, but you get the picture. It’s a boot menu that is shown without Android being loaded, and it gives you access to certain features such as doing complete backups of your phone (Nandroid backups) and installing custom ROMs. ClockworkMod is the most popular Recovery Mode, and it’s installed with the app ROM Manager.
CyanogenMod or CM
CyanogenMod, often abbreviated CM, is a custom version of vanilla (more or less unmodified) Android. It’s the most popular custom ROM for Android – a community effort, and many other ROMs are based on CyanogenMod. Among other things, it adds a bunch of extra customization features and options.
Dalvik & Dalvik cache
Dalvik is the cryptic name of the virtual machine (VM) in Android, and it’s the basis for running apps (with the .apk filename extension) on the platform. Before Android apps are launched, they’re converted into the compact Dalvik Executable (.dex) format, which is designed to be suitable for systems that are constrained in terms of memory and processor speed. Dalvik was originally written by Dan Bornstein, who named it after the fishing village of Dalvík in Eyjafjörður, Iceland, where some of his ancestors lived.
The Dalvik cache is a simply the cache used by Dalvik, and it’s the result of Dalvik doing optimizations of running apps. Some Android ROMs allow you to move the Dalvik cache to your SD card, in order to free up internal storage.
Data2SD / D2EXT / D2SD
If a ROM supports data2SD, D2EXT, or simply D2SD, it means that the /data folder on your Android phone’s internal storage can be moved to your memory card instead. That’s a good thing, because it will free up precious internal megabytes and leave more room for apps and games. Some say that having the data stored on your SD card is slightly slower, though.
D2ext is a short way of saying “data to the extended file system”. It requires that you have created a partition on your SD card.
Deodexed
The term “deodexed” has been mocking me ever since I rooted my first Android phone. What the frak does it mean, exactly? Well, it’s probably the hardest term to explain in this rooting dictionary, but I’ll do my best.
Apparently, when a ROM has been deodexed, it means that its apps have been prepared so they can be modified. Deodexed ROMs feature apps that have been repackaged in a certain way. Android applications, .APKs, contain .odex files that devs supposedly use to save space. These .odex files are extracted from the application packages and put in the /system/ folder on your phone, to speed up boot processes and to allow parts of applications to be preloaded.
However, this makes hacking and modifying those apps difficult because parts of the apps have been extracted to another location. Deodexing means that all pieces of an application package are put back together into one file, and it makes sure that a modified .APK won’t conflict with some separate odexed parts located somewhere else. Developers of custom ROMs choose to deodex their ROM packages, since it lets them modify various .APKs, and it also makes theming possible after the ROMs have been installed.
DSPManager
This is an equalizer app that Android devs like to include in their ROMs.
EXT2/3/4
This refers to ext2, ext3, and ext4 partitions on your SD card. They’re extended file systems for Linux that can be used by Android, usually in order to preserve internal storage space. Many custom Android ROMs require that you have an ext2, ext3 or ext4 partition on your memory card. Ext2 is the oldest type of extended file system, and ext4 is the newest. Some say that ext4 will put an unnecessary strain on your memory card, because it writes to it so much, and I think the ext3 file system currently is most common. To use one of these file systems, you need to create a special partition on your SD card with ROM Manager or GParted.
So what exactly is a partition? It’s a part of a hard disk, or a SD card in this case, that’s separated from the other parts. Think of partitioning as dividing your SD card into two sections that have different purposes.
Fastboot
Please correct me if I’m wrong, but fastboot is essentially a boot menu that you can do stuff from before Android is launched. On the HTC Desire, you can access it by turning off the device and simultaneously pressing the Power button and the Volume down button. From this menu, you can choose to boot into Recovery Mode, and more. I’ve also seen this technical (and likely more accurate) explanation: “Fastboot is a protocol used to directly update the flash file system in Android devices from a host over USB.”
Firmware
A phone’s firmware is basically its operating system. A “firmware update” means that the operating system, the software that controls the phone, is updated. “Stock firmware” means that the firmware is unmodified: it’s the version of the operating system the phone’s manufacturer delivers.
Flash and flashing
To flash a custom ROM, or a firmware, simply means that you install it. So, flashing is the process of installing a new version of the Android operating system, or just parts of it, like the radio. Flashing new ROMs is done via the Recovery Mode, usually with ClockworkMod Recovery.
HBoot
HBoot is loaded immediately when your phone is switched on, and it’s mainly responsible for checking and initializing the hardware and starting the phone’s software. It can also be used for flashing official software releases, as well as a few other things. HBoot can be compared to the BIOS on a computer.
IME
Input Method Editor (soft keyboard)
[Thanks to Hayden4018]
IMEI
International Mobile Equipment Identity. which you can get by by typing *#06# (works for Galaxy S)
[Thanks to turnado]
Kernel
The kernel is the central component of most operating systems: it’s a bridge between applications and the actual data processing done at the hardware level. The Linux kernel was initially created by legendary Finnish computer science student Linus Torvalds in 1991. Android kernels are often customized, optimized and modified for different purposes, such as over-clocking the processor or extending the battery life. Custom ROMs usually include a new kernel.
Linux
Linux refers to the family of Unix-like computer operating systems that use the Linux kernel. The name “Linux” comes from the Linux kernel, originally written in 1991 by Linus Torvalds. Android is a Linux-based mobile operating system.
MIUI ROM
MIUI is a heavily customized version of Android 2.2 from a team of Chinese developers, and it made a splash in the Android blogosphere back in September 2010. MIUI takes the best parts of Froyo, Samsung’s TouchWiz interface and iOS, and transforms the various elements into something quite unique that has managed to make many people excited. A lot of developers have released their own versions of MIUI, and the ROM is available for many different devices. Besides the official website (in Chinese), there’s a forum dedicated to MIUI at miui-dev.com.
NANDroid & NANDroid backups
NANDroid will let anyone with root access make a complete system backup. It lets you create a backup of every piece of information on your phone, and it can be restored later whenever you want. NANDroid backups are usually performed before flashing a new ROM, in case anything goes wrong, or if you want to return to your previous setup later. NANDroid backups are created from the Recovery Mode, often with ClockworkMod Recovery.
Odexed
See deodexed.
Radio
OK, so this is not the radio you’re listening to your favorite stations with. It’s the radio on your phone that handles communication, the radio that sends and receives voice and data. Flashing (installing) a new radio can improve your reception, and bring other benefits. A radio is flashed via Recovery Mode, just as a full Android ROM.
Radio interface layer (RIL)
Android provides a Radio Interface Layer (RIL) between Android’s telephony services and the radio hardware. Developers and enthusiasts enjoy messing around with every part of Android, and some of them modify the RIL, just like Android itself, the kernel and the radio, to make it better.
RC1, RC2 et cetera
When it comes to Android ROMs, RC means Release Candidate. It’s a candidate for the final release of a ROM, and they can be considered ROM betas.
Recovery Mode
As explained under ClockworkMod, the Recovery Mode is a menu that you can boot into that lets you perform complete backups of your phone (Nandroid backups), install custom ROMs and more. ClockworkMod is a very popular Recovery Mode, and you can get it via the app ROM Manager below.
ROM Manager
ROM Manager is an immensely popular app for root users, and it lets you flash ClockworkMod Recovery, install ROMs from your SD card, perform backups and even download new ROMs over-the-air.
Root
When someone mentions root, it usually just refers to having root access on an Android phone – also called being a root user, or a superuser. Root access is explained under superuser, and in the introduction to this dictionary.
S-OFF (security off)
On the HTC Desire and several other HTC Android phones, the company has implemented a form of “security.” It’s called @secuflag, and it controls whether your phone has its NAND or flash unlocked. S-ON (security on) will read-lock your /system and /recovery partitions, blocking you from performing certain root level actions directly from Android.
You can disable this security measure with S-OFF (security off), although you risk bricking your phone in the process (worst case scenario).
SetCPU
This is a popular application for overclocking or underclocking your phone’s processor, making it faster or slower. It may require a special kernel in order to work.
SuperUser
Android is a Linux-based operating system, and in Linux, there is something called root access. When you root your Android phone, you will get superuser access. The superuser, or root user, is sort of a special user account for system administration. SuperUser is also the name of an app, which lets you grant or deny superuser privileges to other apps.
Terminal and Terminal Emulator
Terminal Emulator, sometimes just referred to as Terminal, is an app that lets users access Android’s built-in Linux command line shell. The application emulates a Digital Equipment Corporation VT-100 terminal, and it’s mostly useful for programmers and for those with root access. For example, typing this in Terminal Emulator when a2sd is installed will move the Dalvik cache to the SD card:
su (gives the app SuperUser access)
a2sd cachesd (moves the Dalvik cache to the SD card)
Titanium Backup
Titanium Backup is the best backup tool for root users, since it allows you to backup all your applications as well as their data.
Zipaligned
Zipalign is a tool that optimizes the way an Android app (.APK) is packaged. It enables Android to interact with the application more efficiently, and in doing so, it has the potential to make the app and the entire Android system much faster. Zipaligned applications are launched more quickly, and they use less amounts of RAM. So, thumbs up for zipaligned Android ROMs.
WWE
WWE means “World Wide English”, and usually tells that an Android ROM is based on WWE, or World Wide English, firmware.
Thank you very much paul-ac. Very much appreciate your effort in creating this dictionary for helping newbies like me.
Wow, very nice writeup!
Sent from my GT-I9000 using XDA Premium App
thanks a lot it was very helpful
and for IME is it the same as (International Mobile Equipment Identity). which we can get by by typing *#06# on your standby screen.? or not
Nice one. thank you
turnado said:
thanks a lot it was very helpful
and for IME is it the same as (International Mobile Equipment Identity). which we can get by by typing *#06# on your standby screen.? or not
Click to expand...
Click to collapse
That's the IMEI, IME if I'm not mistakin' is Input Method Editor.
Very nice post, thank you. It would have been very useful when I buyed my first android phone.
really nice
Very cool, please keep this updated
Sent from my GT-I9000 using XDA Premium App
Nice copy-paste
galaxysdev said:
Nice copy-paste
Click to expand...
Click to collapse
Yes it is!
xxxxxxxxxx
I just like to ask what WIP means? ive seen it on other forums but i havent found any extraordinary about the rom or something
thanks in advance
fulii said:
I just like to ask what WIP means? ive seen it on other forums but i havent found any extraordinary about the rom or something
thanks in advance
Click to expand...
Click to collapse
work in progress
finally i know what deodexed means
please add modem. thx
BoKKeR said:
please add modem. thx
Click to expand...
Click to collapse
Radio=modem.
Sent from my GT-I9000 using xda premium
What is ETA mean?.
Sent from my GT-I9000 using Tapatalk
THX !