Related
Starting this thread here for running this Eclair-Hero build on our Kaisers. Many thanks to all devs below!!
jamezelle said:
King Klair Hero 0.6
First and Foremost this build was ported by Mssmison and the ril(radio interface layer), and audio libraries were written by Vilord!!! im pretty sure the gps library was written by Srwalter. vilord may have helped port it to eclair. (will get back to you on that). without DZO we would still be using windows mobile "" but were not ""
To Donate: to these fine gents visit http://sourceforge.net/apps/trac/androidhtc/wiki/WikiStart and scroll down to the donation links
B to the E to the T to the A
this is very beta, well almost alpha(first release for us vogue users so report any bugs that havent been mentioned in this post)
what works:
gps
calls
data
wifi
sync(dont sign in to google during htc wizard, wait till next boot!! you have been warned!!!)
market
gmail
what doesn't:
camera
bluetooth
gtalk
get more widgets
will add screenies later
ENJOY
Click to expand...
Click to collapse
UPDATE 17 Dec:
Download the new rootfs below for working WiFi! Thanks enatefox!
Download:
system.sqsh [ver 0.6.01]
Eclair-ready__rootfs.img (rename to rootfs.img, of course)
eclairhero.user.conf (goes on your SD card in /android/conf)
OR if you have a swap partition on your SD card: eclairhero-swap_partition.user.conf (goes on your SD card as /android/conf/eclairhero.user.conf)
And if you don't have them already:
zImage-15-12-09 (the latest kernel from 15 Dec)
startup.txt (My personal HaRET startup.txt)
rootfs changelog:
Copied /init.cfg/init.eclairhero.rc to /init.cfg/init.eclairhero.kaiser.rc
Copied /init.cfg/init.eclair.rc to /init.cfg/init.eclair.kaiser.rc
Altered init to check that media folder exists in /sdcard/android/media instead of /sdcard/media
Altered init to support eclair.user.conf and eclairhero.user.conf
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Go straight to version 0.6.01 as posted above, version 0.6 gives me weird SIM errors.
This build takes FOREVER (5-10min) to boot. It goes through and even attempts to make a number of thumbnails for your images during first boot. I suggest watching it over adb so you'll know when it's settled and ready for input.
The HTC widgets are not working with this build.
TaskKiller is an absolute must, like other Hero builds this one loves to keep apps open.
Hmm, this build has successfully rebooted itself twice, during heavy use. I wish I knew how that worked, so we could get it to reboot on command!
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Almost downloaded Hero, just got vanilla Eclair to boot the first time. I'll look into wifi. Maybe it's me but Eclair seems faster than Donut but I haven't messed with it much. That should make Hero much nicer.. will post back when I get further
rugalck said:
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Click to expand...
Click to collapse
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
@enatefox:
O
Hero is very buggy, has too many problems to run daily for now. Overall Eclair Mike the fastest yet though! And the fonts are much better for qvga. Text autocomplete has issues.
polyrhythmic said:
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
Click to expand...
Click to collapse
Nah, don't worry, it was something really really stupid.
In the same file you said, it was like "zImage 11-12-09" so now I saved it saying just "zImage". Now works fine.
Waiting for wifi updates, great work guys!
BTW, is there any way to take screenshots?
damn bootloop. I'll look at this tomorrow but that's a promise . I don't know where these wifi files came from. I dropped in the ones that I've used and we'll see. Right now I'm fixing telnet and some other issues to post back with but it will take a little bit of time. We're going to get this working for daily use.
Here's working wifi for Eclair:
http://www.mediafire.com/?ezyzekjozj3
EDIT, I didn't get Hero to boot for me (looping) but I forgot to update Eclair Hero's conf file to match conf.eclair.kaiser.rc.. can someone either do that and repost or wait for me to finish some perm issues with it and I will upload one for Hero. Sorry about that.
I have got to be doing something wrong. I am using all of the files from the 1st post and the rootfs.img from enatefox's last post and this sat for 30 minutes. I even copied the user file to the sd card, to the /sdcard/CONF folder and into the /sdcard/Android/CONF folder and still it sits. I'll get a post of the last few lines up later to see if I just need to wait more or not. I am also using an empy 2GB Fat32 SD Card with the 1.71 radio. All other builds work but this one???
Any ideas?
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
rugalck said:
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
Click to expand...
Click to collapse
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
polyrhythmic said:
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Click to expand...
Click to collapse
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
FYI, your 'conf' and 'android' folders should be named in lowercase, if they aren't already.
The only way we can tell what is wrong is to see whatever the console says before it freezes, or ADB logs if you can make it that far. Post whatever you've got.
j101399j said:
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
If it wasn't created then... you wouldn't need to delete it, do you?
ROM Size: That's because I use mixed files from the different Eclair thread's.
It's a "package" of what worked fine on my device.
Most of the files are from this thread, but the system.sqsh is from this one:
http://forum.xda-developers.com/showthread.php?t=600154
Mirror File: http://rapidshare.com/files/322793487/android.rar.html (up to 10 times, I don't have a premium account D: )
j101399j said:
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
rugalck said:
ROM Size: That's because I use mixed files from the different Eclair thread's.
http://forum.xda-developers.com/showthread.php?t=600154
Click to expand...
Click to collapse
thank you, will try
polyrhythmic said:
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
Click to expand...
Click to collapse
I competly forgot about needing all lowercase letters; as for the data.img file, that is what I though; Thank you
[EDIT]
That is so wierd; I had to place the system.img into the /sdcard/android folder and the use user file in these 3 places /sdcard /sdcard/android and /sdcard/android/conf
Now it works. Don't know what changed, but it works
j101399j said:
thank you, will try
Click to expand...
Click to collapse
http://rapidshare.com/files/322793487/android.rar.html
I can almost guarantee you that the .conf file in your SD root and the .conf file in /android/ are ignored, try deleting them and just leave the .conf in the /conf/ directory. And yes, everything including the system.img/system.sqsh should go in the /android/ folder now.
I bet you can boot this Hero build, but it has a lot of bugs, you'll probably be happier with plain Eclair that rugalck linked.
hey guys ill update when king drops 0.7
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
RDilus said:
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
Click to expand...
Click to collapse
If it's the first boot, make sure to have at least 300mb free in your SD card.
rugalck said:
If it's the first boot, make sure to have at least 300mb free in your SD card.
Click to expand...
Click to collapse
not to be rude but im not stupid -.-'
i have like 5GB free...
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.
THIS BUILD IS OUTDATED, CHECK:
http://forum.xda-developers.com/showthread.php?t=1177721
I'd like to "present" my recompilation of XDAndroid FRX06 to work with Neopeek's CWM 1.8
No credit for me, but for all XDAndroid devs and Neopeek &co for this.
It doesn't have any other modifications apart from making it available to install from CWM, so everything that applies to FRX06 is useful here. You're the one to decide if you prefer looped or partitioned installs.
Don't try this if you don't know what you're doing. It's only tested by me, so what I'm looking for are TESTERS. PLEASE READ EVERYTHING CAREFULLY BEFORE DOING ANYTHING.
Normally it would be easy to return to previous state by repartitioning/formatting SD, but who knows. I take no responsability for any damage to your device.
The instructions for installing CWM are in Neopeek's forum. Only points:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
2.- Startup.txt, ts-calibration, kernel and modules must be in the same dir as haret.exe, in this case inside "npkboot" dir.
3.-To move in the CWM menu with our Blackys:
Peteflyman said:
I just toggle between "Reboot system now", push "Vol Up" to get directly to "Power off", and then toggle "Vol Down" to get back to "Reboot system now". I just do that a couple of times then "Back menu button enabled" usually shows up. That's it. Hope it works for you guys as well!
Click to expand...
Click to collapse
After the "back menu button enabled" you can use power off button to confirm menu selection. Just select "install zip from sdcard", "choose zip from sdcard" and choose my zip (ofc, don't uncompress it).
4.- You don't need to install Gapps, they're included in the build.
5.- After installed, "reboot system now" and start haret again. Let it work for a while without touching anything until you see PIN or unlock screen to begin using Android.
6.- I'd recommend rebooting a second time before starting to configure everything...
It should work in any device where CWM and XDAndroid work, but the configurations I attach here are for TOUCH HD (Blackstone). If you want to try with other devices, be careful to use the appropiate config files (they shouldn't be difficult to find in your device's forum).
I'm using 1337 kernel & modules from Glemsom's autobuild and it works perfectly with my device, feel free to use the one that suits you better.
Download link:
http://www.megaupload.com/?d=SUBUG5I8
If you have any problem, I'll try to help, but for CWM problems please ask in their forum as you'll find better assistance.
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
if you want to install any other build,or reinstall frx06,go to recovery,choose mounts and storage,then format data,format cache,format system (don't format sdcard for obvious reasons) and then mount data,cache,system,go back and install zip from sd card,choose your zip.
also if you find a build without gapps,go to cyanogenmod.com and grab it there,you should pich gapps for cyanogenmod 6 because that's the froyo build....MDPI or HDPI doesn't matter in our case
many problems are result of gapps missing (some builds come without them,this one doesn't) such as call rejecting or showing black screen instead of lockscreen when you wake the device,so be sure to install them
arrrghhh said:
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
Click to expand...
Click to collapse
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Eodun said:
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Click to expand...
Click to collapse
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
farukb said:
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
Click to expand...
Click to collapse
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Eodun said:
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Click to expand...
Click to collapse
you can at least start with
/system
/app (add or remove apps)
/fonts (obvious)
/framework (the "look" of the build is defined here,so if you want your froyo to look like ginger,take some of the ginger files and swap with those in this one)
/media (it'll tell you what to do by itself)
other folders are build regarded and some playing and asking pros is advised here
any screenshots ?
Simon_WM said:
any screenshots ?
Click to expand...
Click to collapse
It's a vanilla Froyo, identical to FRX06, so I didn't think they were needed. Just look at any basic original Froyo install.
Eodun said:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
Click to expand...
Click to collapse
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
every card is "original" just the manufacturer is different....eg trandescent cards dont work,what's your card?
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Eodun said:
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Click to expand...
Click to collapse
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
arrrghhh said:
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
Click to expand...
Click to collapse
Well, I can't tell because I'm in android now and can't extract it XD Never had the curiosity to check.
Let me see... Yeah, it has a "2" inside sort of a "C", so it must be a C2 8Gb SanDisk MicroSDHC lol
Working on FRX07 update.zip to test if it works with CWM
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
ypsmav said:
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
Click to expand...
Click to collapse
helicopter88 is already working on that
ypsmav said:
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
Click to expand...
Click to collapse
I don't think so. But if you backup everything with titanium backup and then restore apps, appdata and system settings (only those that appear in green) you'll have everything as before.
Eodun said:
Working on FRX07 update.zip to test if it works with CWM
Click to expand...
Click to collapse
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
arrrghhh said:
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
Click to expand...
Click to collapse
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
ypsmav said:
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
Click to expand...
Click to collapse
@arrrghhh: Yeah, I know the update is available, but ypsmav noticed the problem: I need the new rootfs for CWM, and I'm not able to adapt it. As I said, work is being done for that.
Thanks for your replies
Ps It will be a big problem if latest kernel doesn't boot. I haven't been able to boot with it. Edit: But still have to check if it boots with a clean data.
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
chadouming said:
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I told it already, the "custom" folder is not filled. It will be kept empty. The user can put a file, which ofcourse is the file of the device he/she have or want to get repaired. All he has to do is copy and paste the file from the working zip( zip file of his currently installed rom, that encounter the problem) of his rom to the custom folder inside the rescue.zip.
And the things that are common will be scripts, but those too will contains device specific mound points, paths, etc. I think that will be common( ie, the working of script, once the mound is done). Am i right?
So all i have to figure out is mount points, paths etc.. i got a couple of them, about 15 or so. And pls help me to find the rest.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Mikevhl said:
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
Click to expand...
Click to collapse
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
wilwilwel said:
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Pls pm me the idea how to make the checking script. Or links that have info in this. Thank u in figuring out such a prob. I am unaware of that.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
showlyshah said:
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
Click to expand...
Click to collapse
I'll send this as a PM as well, but people might learn from this. I am not talking about any specific mount points for LG phones, I just pointed out that there are some roms which use sed to check the filename of its update.zip and do tasks according to that, you need to have one line in your updater script to run the script which detects what to do. That way a user of a Galaxy Nexus would rename it to update-maguro.zip and it would know to use mount points for the maguro, while if the exact same update.zip was to be named update-p990.zip, it would know to use the mount points for the LG optimus 2x. This way you could easily keep the zip up to date for any device, because they all use the same update.zip
About the recovery, you would need to build it for every phone once, but you could make one change to the recovery source and easily compile the recovery for all phones which are capable of running CWM. I believe this method to be more user friendly, as a recovery image has support for actually choosing what you want to do, instead of having to rename the file. A recovery image also has a better way of communicating with the user. Where a update.zip can only say "Hey, I had an error and I'm quitting now, I won't give you any details what the problem was because that's just how update.zips roll", a recovery image would be able to give more advanced outputs, like "An error occurred when trying to mount /data." And then give you the option to either try again, manually fix it by using a computer with adb, or quitting.
But that's just my personal opinion. The recovery would be way harder to make, but I was the original porter of CM6, CM7 and HTC Sense to the xperia mini pro and mini back in the days. I also made a custom recovery and roms for the HTC desire Z, maintain a CWM port for the HTC Chacha which I don't even own and have used the LG optimus 2x before. (currently a maguro owner) but I'm trying to say that I've been experimenting a lot with different phones and know what the possibilities of Android are. you could even make a live Android build, tailored for recovering your phone, which is ran by an update.zip! How cool is that? That would be VERY device specific though..
let me know what you think is the best way to do this. I was thinking of making a mobile time machine app for some time so it's good I saw this thread.