Related
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!
where can i download haret?
where can find a android version running with haret?
wich requirement?
Thanks in adance
Hate to point out the obvious but the second post at the top answers all your questions.
mbelgrano said:
where can i download haret?
where can find a android version running with haret?
wich requirement?
Thanks in adance
Click to expand...
Click to collapse
use my andboot folder here http://forum.xda-developers.com/showpost.php?p=8019588&postcount=144
and the androidinstall here (says download rls 15) http://forum.xda-developers.com/showpost.php?p=7757239&postcount=1
put that file in andboot folder also, put in root of sd card and run haret (press center dpad once asked and hit install system), follow the rest of my instructions in the andboot attachment post.
Thanks
I not able "download rs15" because mediafire seem not aivable at link
http://www.mediafire.com/?qsfmx07quc9f294
ghghgh14702 said:
use my andboot folder here http://forum.xda-developers.com/showpost.php?p=8019588&postcount=144
and the androidinstall here (says download rls 15) http://forum.xda-developers.com/showpost.php?p=7757239&postcount=1
put that file in andboot folder also, put in root of sd card and run haret (press center dpad once asked and hit install system), follow the rest of my instructions in the andboot attachment post.
Click to expand...
Click to collapse
I am also unable to download file from RLS15 link =(
Can you guys help me a little bit since i'm newbie with this.. i've never flashed a rom (still with 6.0), however my phone isn't locked to any phone company..
1. to instal from sd card do i need a new radio and new ROM >6.1? or only a new radio is necessary? or my ROM and Radio of origin works good? i bought my kaiser more than two years ago...
2. to install instead WM (think you call nand or something ;P) the same questions.
Thanks for all help in advance.
Unfortunately mediafire.com seems to be down for some time now. Does someone has a copy of RLS15 to share via torrent/http. I can offer webspace too in case to help with this situation.
tekknokrat said:
Unfortunately mediafire.com seems to be down for some time now. Does someone has a copy of RLS15 to share via torrent/http. I can offer webspace too in case to help with this situation.
Click to expand...
Click to collapse
Thanks Now i can donload
but the procedure indicated in andbod is installation that remove data from my phone?
I think that haret allow try a version
Is it possible to odex files that you downloaded from the market? If so can someone post a quick tutorial? Few questions for the tutorial:
Will the odex apps still be able to be uninstalled?
Will the apps run faster like the system odex files?
Can this be done visually (gui program to auto convert), or does this need to be done via terminal?
Can this be done on the phone and with a pc running linux? If so can you list both?
Look for a script /system/bin/odex.sh. If you don't find one, try putting this there, but I believe kallt_kaffe has a newer and better version than this.
Frankly, I don't odex anything anymore.
Hi!
I've made a StarGate Bootanimation for Galaxy S II. (for Android 2.3.5)
Thanks to crispixfr for the original version (for SGS1).
Actually i resized his version, replaced its sound (the original was too dull), and updated the script for SGS2 Android 2.3.5.
Install:
First of all you have to unrar the two parts. -i had to split the .ZIP with rar because xda forum allows only 8MB attachments.
After that:
a) Install With ClockWorkMod
OR:
b) Install with root explorer (extract the .zip and paste the bootanimation.zip in system/media and PowerOn.wav in system/etc)
I recommend to increase the system volume to maximum for real experience.
(Settings>Sound settings>Volume>System volume)
Previews:
great animation. Have it also in my SGS1. The problem wich i have, is that the sound of locking symbols is to fast.... But maybe our gs2 is to damn fast.
best regards
PS. also i have a power on and off from Transformes wich i love have them on every phone that i own (glad to share with you guys)
hhhans1 said:
great animation. Have it also in my SGS1. The problem wich i have, is that the sound of locking symbols is to fast.... But maybe our gs2 is to damn fast.
Click to expand...
Click to collapse
You mean that the sound doesn't match the picture?
Maybe your phone plays the video slower than mine.
no no..you got me wrong...IT MATCH..but it plays fast then i used to sgs1. in sgs1 is more like in the movie (but i think is about that in sgs1 it take longer to boot).
it's like 1.2.3.4.5.6.7 done but no issues about sync video/audio
Looks good will give this a go i was getting a bit bored of the Galaxy Nexus boot animation anyway
Thanks you for to have updating my boot animation !!! Crispix is the best !!! And you too now lol
Just one thing before i flash which part do i flash via CWM or is it both do i flash one and then after it reboots flash the other one or how does it work?
cheers
i have the same question as Jonny68 appreciate answers when possible thank you again
EDIT: Jonny alpha build 6 is out by the way mate
jonny68 said:
Just one thing before i flash which part do i flash via CWM or is it both do i flash one and then after it reboots flash the other one or how does it work?
Click to expand...
Click to collapse
As i have said in the first post: First of all you have to unrar the two parts.
So there is only ONE ZIP file, which you'll have after extracting the RAR files.
After that, you only have to flash the extracted ZIP file!
@OP: why two files?
TecQuality said:
@OP: why two files?
Click to expand...
Click to collapse
As i have said in the first post: -i had to split the .ZIP with rar because xda forum allows only 8MB attachments.
Just flashed this via CWM, rebooted and there it makes a noise as it boots but my existing boot animation is still there, tried rebooting again and same thing
jonny68 said:
Just flashed this via CWM, rebooted and there it makes a noise as it boots but my existing boot animation is still there, tried rebooting again and same thing
Click to expand...
Click to collapse
R U sure your kernel is version 2.3.5?
BTW, try the second install method!
Hey thanks a lot for this great boot animation Fenyo1, loving it!
Fenyo1 said:
R U sure your kernel is version 2.3.5?
BTW, try the second install method!
Click to expand...
Click to collapse
Siyah 2.1.1 so yeah definitely.
I'll try again and report back later.
Fenyo1 said:
As i have said in the first post: -i had to split the .ZIP with rar because xda forum allows only 8MB attachments.
Click to expand...
Click to collapse
Put ur file onto multiupload ;-)
Directly from my SGS II using xda premium
Sometimes is not working the regular method (trough CWM). You need to push the files manually.
Choose a file explorer wich can gain read writte rights on system folder (personaly i use root explorer).
Step 1. Unzip the zip file wich doesn't work trough CWM flash, and you will obtain several folders (system/media wich contain bootanimation.zip) and etc/ wich contain PowerOn.wav. Copy this files in a folder inside your internal sdcard or external sdcard. Mainly you are interested on bootanimation.zip and PowerOn.wav
Step2. With file explorer mount with R/W the system folder and copy the bootanimation.zip from your folder to your /system/media folder. If you allready have a bootanimation.zip there, it will be overwritted.
Step 3. With file explorer mount R/W the etc folder, and copy from your folder PowerOn.wav to your etc folder.
Step 4. Reboot. Enjoy.
I think the same steps are also for the other kernels wich use the sanim.zip.
I don't remember in what folder is stored, but it will be like, rename the extracted bootanimation.zip to sanim.zip, and copy the new file to the respective folder. The poweron.wav is going to the etc folder.
If you have a copy error please check if you have read/writte rights on that folder. For default you have Read Only rights.
Hope that helps, and all credits go to the OP for this great animation.
best regards
This is a great animation.
Running on Checkrom Rev 3.1.1 with Green Monkey theme.
Thanks for the effort.
well done
Already answered
thanx man , it's realy good
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?