I need a video tutorial or a beter way of explaining how to get 2.1 on the raphael 800.
* Extract the latest Android filesystem to a ext2 partition on the internal Storage
*
Extract the latest kernel and modules to the root of the windows partition
*
Copy Haret.exe and a default.txt for your mobile to the windows partition (fat) and rename the text file to default.txt
*
Run haret.exe from WinMo, and you are on the way, to a better system!
I found this and downloaded the files to my computer but what next??? plz help
The method you seem to be describing is the ext2 method NOT the "typical" or normal method of using sqshfs...
I'm sure that's just mumbo jumbo, but what you need to do is this...
Download this package. That is the base package - you can just run with that if you wish. Make sure to copy the STARTUP.TXT for your device to whereever haret.exe is - either at the root of your SD or in /andboot folder on your SD card typically.
Now if you want to update your system, first download this - system.sqsh update. Extract & copy to where haret.exe is again. Overwrite the file currently in there.
Then you need to grab the newest zImage/modules, and rootFS. Note - you will need to rename the zImage file to just that - zImage. Also, the rootfs should be titled "rootfs.img" - nothing else.
Please do some reading next time as well. It seems you just went to the first thread you could find and got horridly lost. The ext2 method is more advanced, and IMHO the benefits on the RAPH are not that great. Vogue maybe, but that's a completely different device.
as mentioned in the main android for tp thread:
http://forum.ppcgeeks.com/showthread.php?t=104276
this is the thread for the raph800. alot of info, specifically for the raph800 (sprint touch pro).
hamagc said:
as mentioned in the main android for tp thread:
http://forum.ppcgeeks.com/showthread.php?t=104276
this is the thread for the raph800. alot of info, specifically for the raph800 (sprint touch pro).
Click to expand...
Click to collapse
And if you get packages from the first post in that thread, all you have to do is extract them to your SD. They're ready to go in every way for your RAPH800.
**Note - that ONLY applies to packages downloaded from the first post of that ppcgeeks thread...**
update your link
hey arrggggg.
the link for the z images was not working cuz u didnt update it
update your links on anapnea.com cuz they changed it.
glemsom.users.anapnea.net/android2/htc-msm-linux/ **do this**
glemsom.anapnea.net/android2/htc-msm-linux/ **instead of this**
its on the anapnea homepage
ty for the walkthrough though!
please help me. how can i install apps on my android?.. i tell you that i have android on my micro sdhc card and on the memory i have WM 6.5
cabasse_tronic said:
please help me. how can i install apps on my android?.. i tell you that i have android on my micro sdhc card and on the memory i have WM 6.5
Click to expand...
Click to collapse
That's a very odd question. you can install applications using the android market or if you have apk files download generic file browser and use it to install the apps.
apps that i heve on my memory card..
cabasse_tronic said:
apps that i heve on my memory card..
Click to expand...
Click to collapse
vapk files download a generic file browser and
use it to install the apps.
Oi file manager should do the trick.
Astro file manager does the job as well
And AstroZIP too...
But I've a question: is there a way to install an .apk file using just the terminal shell?
I.e.: if I've not Internet access and the build I use have not a burned in file manager...
I know, I can use an androidupdate.tar but suppose I've no way to build it up and have the .apk on the sdcard, from a previous download...
cabasse_tronic said:
please help me. how can i install apps on my android?.. i tell you that i have android on my micro sdhc card and on the memory i have WM 6.5
Click to expand...
Click to collapse
i believe you're using haret to run android from SD card, unpack androidinstall with 7zip, copy file browser app .apk into /system/app/ (etc. astro file browser), repack it and then install again with haret. now you can use file browser to install apps on SD.
or :
use terminal to copy file .apk into /data/app/ , reboot android
alternatively, taken from DirectMatrix post (not tested):
put .apk in your sd card root to easily find it then run command as below,
su
busybox install /sdcard/yourapp.apk /sd-ext/app
Oh... I suppose this is an answer to my curiosity too
Yes, I know... it'd be sufficient I googled for a while but, as I said, mine was a question arose at the time I was writing...
CU
---- EDIT ---- EDIT ---- EDIT ----
Ok, just tried...
New to this world and with just a little little little bit of knowledge about UNIX-Linux, maybe I did a mistake but:
copying the .apk in /data/app and resetting did the job instead using busybox didn't
As I can see having a look to busybox docs, the install command with no other parameters just copies the file so you can do the same with:
su
cp /sdcard/yourapp.apk /sd-ext/app
More... if I understood well, sd-ext is the application repository used if you enable apps2sd and if you have not (I don't, at present time, as I'm testing...) the method doesn't work...
Correct?
Apps2SD requires an ext3 partition on the SD card, and if you only have ext2 or fat32 it does not work.
how do I run this build off SD card??? I downloaded "androidinstall.tgz" from incubus's thread and I got the basefiles which includes haret and other necessary files. But when I run haret after couple of lines it says system.img not found.
I did put the androidinstall.tgz in the root of SD card!!! I have read the guide on how to boot using haret but new builds doesn't not have system.img files anymore. Can somebody please shed some light on this?
Sorry for the noob question!! I need to run it off SD coz I need to have WinMo as well.
The guide you read was out-of-date, the more recent system now requires that the androidinstall.tgz/tar goes in the andboot folder with all the haret files.
If you are running from SD your card root should have one folder, no files.
If you would like an alternative and more recent guide to using Android on Haret then may I suggest you have a look at the one in my Polymod thread, post #3 has a quick guide to running Haret installs, it's mostly geared to running Polymod, but should be useful for other Haret installs also
( Link in my sig ).
Is is possible to change the root folder of the sd card used by android? I don't like having it create so many files/folders in the root of my card...
HDR said:
Is is possible to change the root folder of the sd card used by android? I don't like having it create so many files/folders in the root of my card...
Click to expand...
Click to collapse
Of course, you can place Android where ever you wish... just adjust the rel_path statement on your startup.txt.
For example, my installs are in /sdcard/Androids/TP2Ref - from Android's perspective. So in my startup.txt, I have
Code:
relpath=Androids/TP2Ref
- Just make sure that goes in the cmdline section.
Pretty sure this is in the FAQ... Try searching before you post
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
HDR said:
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
Click to expand...
Click to collapse
Only way to do that is to modify the source. I could easily make the changes in init for you, but the next time rootfs is updated (which will probably be soon since stinebd has to prep it for GB), you will lose those settings.
I'm working on some NAND stuff at the moment, so if you feel adventurous, all you have to do is modify init in rootfs and "compile" it. I have a little guide on compiling stuff (see bottom of post #1 for rootfs): http://forum.ppcgeeks.com/tp2-andro...modules-tinboot-nand-boot-more-beginners.html
I'll have a look at that, thanks.
HDR said:
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
Click to expand...
Click to collapse
I can at least give you a easy solution for the FSCK files (no offense Nate ). Put this in the "CustomCommands" section of your froyo.user.conf:
Code:
rm -f /sdcard/*.rec
im totally agree; i dont see the point of having the possibility of choosing android to start in whatever location we want....if anyways android will keep creating files/folders in the root of our sd card.
if i recall correctly the very first releases didn't have this problem it would be great if u devs can change this behaviour by default
elamodelmerol said:
im totally agree; i dont see the point of having the possibility of choosing android to start in whatever location we want....if anyways android will keep creating files/folders in the root of our sd card.
if i recall correctly the very first releases didn't have this problem it would be great if u devs can change this behaviour for default
Click to expand...
Click to collapse
This is what Android needs by default, and where they would normally be created by the system. It's nice to stick as close to AOSP as we can, because then there's this small group of devs that work for this company 'Google' that then become our system image maintainers. Thanks.
So I am trying to port ICS to our kaisers, but the problem is I have very limited developer knowledge (actually none). As a result I am trying to port the HTC Wildfire's ics builds. But the only things I can do, is:
extract the system file out of the Wildfire build
delete a couple of files to get in down in size (the wildfire has more RAM than the Kaiser)
add the sysinit.rc file to the system file
recompress the system file to androidinstall.tar
And the furthest I have come with this method is seeing the boot logo flikkering while I still saw some of the white code on the screen.
The matter of the fact just is, I REALLY WANT TO LEARN HOW TO BUILD MY ANDRIOD BUILDS, but I don't have the knowledge or time to exactly learn the java code. So as a result I really just want to know what the keypoints are? CAn somebody please point me in the right direction?
** As an example: when you open the system file of an android build you get all kinds of folders, and from most of them I don't know what they mean, like from bin, etc, framework, lib, usr and xbin I haven't got the slightest clue of what they are there for.**
**Also I don't know what there should be changed in the build.prop and the sysinit.rc when you are trying to a build of another device on the kaiser. Are the build.prop and sysinit.rc dependent from the version of Android you are giong to run or are the dependant of the kind of device you're gonna run it or are they dependant of both??**
hom.hom said:
So I am trying to port ICS to our kaisers, but the problem is I have very limited developer knowledge (actually none). As a result I am trying to port the HTC Wildfire's ics builds. But the only things I can do, is:
extract the system file out of the Wildfire build
delete a couple of files to get in down in size (the wildfire has more RAM than the Kaiser)
add the sysinit.rc file to the system file
recompress the system file to androidinstall.tar
And the furthest I have come with this method is seeing the boot logo flikkering while I still saw some of the white code on the screen.
The matter of the fact just is, I REALLY WANT TO LEARN HOW TO BUILD MY ANDRIOD BUILDS, but I don't have the knowledge or time to exactly learn the java code. So as a result I really just want to know what the keypoints are? CAn somebody please point me in the right direction?
** As an example: when you open the system file of an android build you get all kinds of folders, and from most of them I don't know what they mean, like from bin, etc, framework, lib, usr and xbin I haven't got the slightest clue of what they are there for.**
**Also I don't know what there should be changed in the build.prop and the sysinit.rc when you are trying to a build of another device on the kaiser. Are the build.prop and sysinit.rc dependent from the version of Android you are giong to run or are the dependant of the kind of device you're gonna run it or are they dependant of both??**
Click to expand...
Click to collapse
ICS on Kaiser? Big mistake...
I know see that you have gotten it right about ics on the kaiser, but I still want to develop my own builds for the kaiser, gingerbread builds, then. So can anyone shed their light on helping me into the right direction of creating my own build from the source or porting a build from another (htc) phone??
if you want to port android start from this - take system from similar device (example click or wildfire) and follow directions from this thread http://forum.xda-developers.com/showthread.php?t=996431. Method from post #3 definitely works for Froyo and Gingerbread. If you find problem really helpful is using logcat and DDMS.
In my opinion porting AOSP ICS for Kaiser at the moment is a waste of time. Will be more problematic and you never will achieve a fast, fully operational system. BUT with Cyanogenmod9 situations can be change...
Almost there....
I have used the Official Cyanogenmod Stable release from the HTC Wildfire to port (as a test) and I have used Scoot CyanogenMod 7.1.0 RLS3 (Gingerbread 2.3.5) [07/08/11] to paste the files from into the CM for the buzz.
Michga said:
i have this one...
I'll look into the specs of wildwire and let you know if my steps would work. Just kinda busy this holiday season. But my steps were pretty simple. We have to know if this is an odex'd or deodexed version. If it is odexed version, it would be nice to deodex it first. I use Android kitchen from dsixda. The only part we need is the system folder. It has apps, etc, lib, bin and the rest...basically under the system we need to put Fresh Froyo (FF) files build.prop and sysinit.rc and move it to wildfire's system folder (these two files are required for booting)then under /system/etc you need to grab vold.conf(1) from (FF) and move it to wildfire's /system/etc. Ooops..I'll have to get back to you. Dinner time BTW, vold.conf is what loads SD card. I looked at the specs of wildfire and not sure if it works since it has a 7225 processor and 5 megapixel but it's worth a try. Then /system/etc, copy ppp and passwd from liquid's kernel and put it in that folder (like permissions)(2). Compare the folders with Fresh Froyo and if something is missing from Fresh Froyo to wildfire. Copy wifi folder (don't copy ppp folder, delete it if wildfire ROM has it). Now lets go to system/lib. Copy the following files from Fresh Froyo to wildfire libaudio.so, libaudiopolicy.so (audio drivers) libcamera.so libcamera_client.so libcameraservice.so (camera drivers) libgps.so (gps driver) libhtcgeneric-ril.so (phone driver) libicudata.so. Then copy egl folder to hw folder and bluez-plugin folder. Now go to system/modules and delete all files and get modules from l1q1d's latest kernel(3) and put it in the system/lib/modules folder. Then go to system folder and copy bin folder, media folder, xbin and usr folder to wilfire system. That's it. Save the system folder as androidinstall.tar and see how it goes. Goodluck.
Click to expand...
Click to collapse
So I have tried the method of post 3 of the link, but all I get is the kaiser to boot in Android, but it never stops booting, the infinite bootloop. I believe the cause for this bootloop to be the sheer size of the androidinstall.tar(as jholtom already explaines in his post in this thread). It at its least becomes 150 mb. I can't get it any smaller, because I need to add the xbin file of Scoot's Cyanogenmod 7.1 for Kaiser, which is 67 mb of size. While the official Cyanogen Wildfire rom also is about 67 mb of size.
Also some other problems
(1)vold.conf: I can only find vold.fstab does this matter?
(2)how do i extract passwd from liquid's kernel? And do I need to put this in the permissions folder?
(3)Instead of the latest files as posted by Michga, I have used the files from the update.zip provided by Scoot in his kernel with separate cache thread: http://forum.xda-developers.com/showthread.php?t=1152219
You need strip the system as much as possible. cut out the unnecessary applications that take space and are not required to work (example: radiofm, rom manager, thememanager), tts voices, rings even some libraries - try to compare catalogs from Scoot_CyanogenMod_7.1.0_RLS3 and wildfiresystem. Strip unnecesary files, copy all the missing files. If your androidinstall.tar reach size below 100mb should be ok with standard partitions. But you can always enlarge the partitions in atools.
What do you mean that xbin have 67mb? It have about 7mb
As you can see Michga wrote this for Froyo so some files will vary. (1) copy only volf.fstab (2) may be unneeded for scoot's kernel- i'm not copy this and system works (3) you can use files from scoot 7.1 RLS3 - these are the same modules as in the update.
Install the android sdk on computer, run DDMS and plug the Kaiser. You will then be able to see what at the time the phone is doing and what is causing the problem.
Sorry for my english
Well, also the strangest thing is that I redownloaded Scoot_CyanogenMod_7.1.0_RLS3 build from this thread, http://forum.xda-developers.com/showthread.php?t=948134, and extracted the file to my desktop and the file is 148 mb in size of which the xbin folder is 69.6 mb in size. How is that possible? I am using Windows 7 x64 and I am extracting the file with Winrar. And when I use 7-zip to get the system file back to androidinstall.tar, this file is also 148 mb, BUT THIS FILE I AM ABLE TO INSTALL....
I am using 7zip only (also Win 7 x64) and extracted RLS3 have 84.3MB. Strange...
hom.hom said:
Well, also the strangest thing is that I redownloaded Scoot_CyanogenMod_7.1.0_RLS3 build from this thread, http://forum.xda-developers.com/showthread.php?t=948134, and extracted the file to my desktop and the file is 148 mb in size of which the xbin folder is 69.6 mb in size. How is that possible? I am using Windows 7 x64 and I am extracting the file with Winrar. And when I use 7-zip to get the system file back to androidinstall.tar, this file is also 148 mb, BUT THIS FILE I AM ABLE TO INSTALL....
Click to expand...
Click to collapse
Impossible, you can't install 148 MB file because System partition on Kaiser is just 120 MB!
So my first problem with the immens build sizes have been solved by using 7zip for every step in my android adventure instead of Winrar.
But know the real problem the booting problem. I ran ddms and the conclusion I get is:
system_process Audiosystem AudioPolicyService not published, waiting....
....
....
HTC Acoustic can't open /dev/htc-acoustic -1
AudioHardware Could not set acoustic parameters to share memory -1
I already googled this problem and the solution is supposed to be to create an android dummy audio driver, but as I said already my knowledge is really limited. So i don't know how to create an android dummy audio driver.
**I also uploaded the warn screen of the ddms...**
did you copy libaudio.so, libaudiopolicy.so (and i'm not sure now - libaudioflinger.so?) from scoots build?
First of all, THANK YOU!!!!
**I just needed to copy all the libaudioxxxx.so files from Scoot's build to the Wildfire's build.**
I am able to boot Zerorom 1.0 from the HTC kaiser now. But there are still a couple of quirks in the build, like the missing statusbar, the not working wifi and the screen looks like it has the wrong panel type in this build. While with Scoot's build it's A-ok.
Do you have logs from ddms?
Maybe you cut too much. Of course you adjust build.prop to our phone. To resolve graphic problems make sure that you still have SystemUI.apk and replaced folders hw and egl from scoot's build. To wifi make sure that you replaced in etc: firmware and wifi folder. If this not help swap libhardware-legacy.so
These are the files of the ddms log and the files which I used to port the official Cyanogenmod release of the HTC Wildfire to the HTC Kaiser. The problems are a flikkering screen it goes on and off all the time, improper (or actually none proper) detection of touch and no wifi.
**I needed to separate the files I copied into two separate folder, system1 and system2, because otherwise I couldn't upload it to the site. I hope that this gives a proper insight in what I have exactly done. Before I copied this files, I deleted the original ones from the Wildfire's build.**
well... What am I to do with it? Download zerorom, merge with this and see what's wrong? I dont know what you do to get tar smaller and what contains folders from porting system. Im think that You better create a new thread called example Zerorom alpha port 0.1 and upload androidinstall.tar to mediafire or somewhere. Then I or someone else see or flash this to phone and tell you what is missing and why libskia.so and launcher still crashing
I've been watching the progress here and I have a few things to point out.
What if the panel size in the kernel is correct, but the screen is "over-drawn"? Maybe ICS doesn't have an option to draw to a screen with a 320x240 resolution? This would explain the status bar and launcher issues. Try rewriting the kernel with the highest resolution (480x328 I think?).
And about the WIFI issue, did you remember to copy the .ko file over to the new build and add the update?
I Know I'm pissing in the wind; I had less luck getting Honeycomb ported from the Wildfire to the Kaiser, so this is looking interesting. You could strip to the basics and just replace things one at a time like I did and see what happens.
PoXFreak, if I good understand this
hom.hom said:
I am able to boot Zerorom 1.0 from the HTC kaiser now. But there are still a couple of quirks
Click to expand...
Click to collapse
he wants to port zerorom from wildfire. And this is just 2.3.7(cyanogenmod) with few applications changed to only looks like ICS. So it shouldn't be these problems with porting gingerbread...
Same rules apply: If the original rom's apps require a resolution higher than what's provided, there could be overscan or "over-shoot" of the original screen into unseen parts of the screen.
As far as the WiFi issue, the wifi.ko file from Scoot's 2.3.5 CM "should" work, but I have not tested it myself.
I do have an unused Kaiser witha good screen and only 2 bad blocks if he wants help with it. I would need all the files he's working with in a tarball posted to mediafire or some other file hosting site.
Im not sure whats in the guide you are looking at and quite frankly I dont feel like looking, but a few of us many moons ago were working on Sense Roms. One trick we used was stripping the system folder of its apps and placing them in a new folder "app_s" in data then symlinking /data/app_s to system/app at boot time. This was one way of shrinking you system files. I also managed onced instead of using data/app_s I used sdcard/app_s however this slows things down a tad but it worked. We eventually gave up on sense roms cause the sense widgets would not work properly and the entire rom was extremely laggy. Good luck with ICS If you happen to get it running I will install it for ****s and giggles however I no longer use this phone, and havent for several years but I still have it and it still boots up
hom.hom:
What is the total size of this build?
Could you not move apps from /system/apps to /data/apps?
What about swapping libskia.so and install a different Launcher from another build?